B2B Buyer Intent Enrichment

Add current person-level or account-level buying topics to records you already have. The Actor accepts up to 10,000 people or companies per run and returns one joinable dataset row per input.

Which Actor should I use?

We publish four Actors. Start at the top.

1. Company Intent Signals — first look, one domain, $0.05. https://apify.com/cag_ai-actors/company-intent-signals
2. B2B Account Intent Finder — new companies on your topics. Preview up to 25 companies, then $0.15 per matched account. https://apify.com/cag_ai-actors/b2b-account-intent-finder
3. B2B Buyer Intent Enrichment — you already have a list. $0.15 per match. https://apify.com/cag_ai-actors/b2b-buyer-intent-enrichment
4. Topic-Based Lead Prospecting — Later. For new companies from a theme, use Account Intent Finder. For a first look at one company, use Company Intent Signals. https://apify.com/cag_ai-actors/topic-based-lead-prospecting

What it does

• People: send an email or LinkedIn /in/ URL and receive current intent topics, strength, and percentile.
• Companies: send a domain or LinkedIn /company/ URL and receive account-level topics plus people counts.
• Cost preview: use costPreviewOnly to get the exact number of billable Delivr matches before requesting data.
• Demo: use demoMode for clearly labeled sample output with no credentials and no paid result events.

Unmatched inputs are normal. They can remain in the dataset for easy joins, but they are not charged as matched Actor result events.

Input

{
  "entityType": "person",
  "items": [
    { "id": "lead-1", "email": "jane@acme.com" },
    { "id": "lead-2", "linkedin_url": "https://www.linkedin.com/in/example" }
  ],
  "minScore": "high",
  "topicIds": [],
  "costPreviewOnly": false,
  "includeUnmatched": true
}

For companies, set entityType to company and use domain or linkedin_company_url.

Output

Each row includes the input id as inputId, whether it matched, the top topic, all returned topics, the data date, and a dataSource marker (delivr or demo). The Actor does not echo API credentials and does not log input identifiers.

Authentication

The production Actor can use a Delivr provider key stored as DELIVR_API_KEY and DELIVR_API_SECRET. Private deployments can also accept bring-your-own credentials through encrypted Actor input fields. Bring-your-own-key rows do not trigger the matched-result event because the user already pays Delivr directly. Do not put credentials in plain text in saved tasks or source control.

Pricing configuration

Recommended Apify model: pay per event with one custom event named matched-intent-record. Charge only matched, non-demo, non-preview rows. Keep platform usage included for predictable pricing.

Suggested launch price: $0.15 per matched record, with Bronze/Silver/Gold discounts after unit economics are confirmed. The upstream Delivr rate is usage based, so pricing must be reviewed whenever its rate card changes.

Privacy and responsible use

Use the Actor only for lawful business purposes and records you are allowed to process. Inputs and results may contain personal data. Choose an appropriate Apify storage-retention policy, restrict access, honor suppression and deletion requests, and do not use output for eligibility, employment, housing, credit, insurance, or similarly sensitive decisions.

Local development

npm install
npm test
npm run check
npm start

Local runs use Apify storage. Set DELIVR_API_KEY and DELIVR_API_SECRET for a live test, or set demoMode: true in storage/key_value_stores/default/INPUT.json.

Sources

• Delivr intent enrichment quickstart
• Delivr rate limits and metering
• Apify pay-per-event guidance