@sellable/install 0.1.166 → 0.1.168
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -218,6 +218,24 @@ reconstruct raw account rows or domains manually. Account rows are not people
|
|
|
218
218
|
leads yet. The confirmation creates the `domainFilterId` that constrains the
|
|
219
219
|
follow-on `search_prospeo` people search.
|
|
220
220
|
|
|
221
|
+
Prospeo company/account search is useful when the source plan depends on
|
|
222
|
+
website traffic (`company_website_traffic`), confirmed AI Attributes including
|
|
223
|
+
`pricing`, `uses_ai`, `has_api`, `has_chrome_extension`, `has_sso`,
|
|
224
|
+
`has_open_source`, `has_marketplace`, `has_blog`, `has_knowledge_base`,
|
|
225
|
+
`has_soc2`, `data_residency: "EU"`, news, awards, website pages, products,
|
|
226
|
+
integrations, key customers, Google discovery, location headcount, or
|
|
227
|
+
structured ICP. When using `company_icp.company_sizes` for micro/SMB/midmarket
|
|
228
|
+
or enterprise sizing, pair it with `company_headcount_range` or rely on the MCP
|
|
229
|
+
normalization that derives the range; inspect the sample for size drift. For
|
|
230
|
+
lookalike seeds passed as `seedCompanies` or `seedDomains`, omit `company_oids`;
|
|
231
|
+
the MCP backend resolves real Prospeo company IDs. Do not invent company_oids.
|
|
232
|
+
For company ICP geography, `geographic_scope` only accepts `single_country` or
|
|
233
|
+
`multi_country`; put North America style regions in `geographic_markets` as
|
|
234
|
+
specific markets such as United States and Canada. Product is not a
|
|
235
|
+
company_icp.departments value; use `titles_include` for product roles. Do not
|
|
236
|
+
use `company_intent`, and do not invent unsupported support-channel filters or
|
|
237
|
+
AI Attribute guesses like phone/email/chat/ticket/social.
|
|
238
|
+
|
|
221
239
|
After scouting, ask for a second approval on Start Import. For
|
|
222
240
|
LinkedIn engagement (`signal-discovery` internally), name how many
|
|
223
241
|
recommended posts will be scraped and the target engager/source-candidate
|