How to Activate Intent Data in Ads: LinkedIn, Meta, Google and Native Integrations

The short version

Activating intent data in ads means converting a list of accounts that are researching your category into an audience an ad platform can serve to. There are four routes: upload a list manually to each channel, use the intent vendor's native connector (Bombora, G2, ZoomInfo and 6sense all ship LinkedIn integrations), run ads through an ABM platform's own display network (6sense, Demandbase, RollWorks), or push the audience through a paid-media activation platform that syncs to multiple channels at once (Metadata.io, our disclosed sponsor, is one option; Influ2 and RollWorks are others).

The channel constraints matter more than the vendor choice. LinkedIn is the only major platform that accepts a company list natively, which is why it is the default home for account-level intent. Meta and Google only accept contact identifiers (hashed emails, phones), so account-level intent has to be enriched to people first. Programmatic DSPs accept account segments via IP or cookie mapping, with the widest reach and the loosest accuracy. Every channel has a minimum matched-audience size, and intent decays within weeks, so refresh cadence is the variable most teams get wrong.

Activation routes at a glance

Before the per-channel steps, here is how the four routes compare on effort, refresh, and what you actually get. "Native connector" means the intent vendor pushes audiences directly; "activation platform" means a third party sits between your intent source and the ad channels.

For which intent sources feed these routes best, see our in-market buyer provider comparison and the first-party versus third-party explainer.

LinkedIn Matched Audiences

LinkedIn is the easiest channel for account-level intent because Campaign Manager accepts a list of companies directly and matches it against LinkedIn's own company pages. Per LinkedIn's Matched Audiences documentation, a Company List can contain up to 300,000 companies, a Contact List up to 300,000 contacts, and an audience must reach at least 300 matched members before campaigns can serve to it. LinkedIn also recommends the list have at least 1,000 companies for consistent delivery; matching typically completes in 24 to 48 hours.

The important nuance is that a company list targets everyone on LinkedIn who works at those companies. On its own that is far too broad. The standard pattern is to intersect the uploaded list with job function, seniority and title filters so that a surging 5,000-person enterprise resolves to the 40 people who plausibly sit on the buying committee. LinkedIn's Audience Expansion should be turned off for intent campaigns; it dilutes the list you paid for.

Native routes into LinkedIn are the most mature of any channel. Bombora's LinkedIn integration sends Company Surge audiences into Campaign Manager; G2's LinkedIn Matched Audiences integration pushes accounts showing buyer intent on G2 into LinkedIn; ZoomInfo's LinkedIn integration syncs contact and company lists; 6sense's LinkedIn Ads integration syncs dynamic segments that update as accounts move stage. Demandbase offers the same via its Audience sync. If you only ever automate one channel, automate this one.

Meta Custom Audiences (Facebook and Instagram)

Meta has no company-list upload, so account-level intent has to be turned into people before it can be used. Meta's Customer List Custom Audiences accept hashed emails, phone numbers, first and last name, city, state, zip, country, date of birth, gender, and Meta's own identifiers; the more identifiers per row, the higher the match rate. Meta's Business Help Center states a Custom Audience must include at least 100 people from a single country for ads to serve. Files can be uploaded as CSV or TXT and Meta hashes the data locally in the browser before upload.

The practical problem is match rate. Most Meta profiles are registered to personal email addresses, so a list of work emails from ZoomInfo or a CRM export matches poorly. Reported B2B match rates on Meta vary widely and Meta itself does not publish a benchmark; the usable rule is that you will need a list several times larger than your target audience to clear the 100-person floor with confidence. Activation platforms address this by enriching each account to multiple contacts and appending phone numbers where available. Influ2 is built specifically around person-level ad targeting across LinkedIn and Meta; Metadata.io (sponsor) syncs enriched contact audiences to Meta as one of its channels.

Google Customer Match

Google Customer Match works like Meta's customer list: you upload hashed emails, phone numbers, or name plus address, and Google matches against signed-in users across Search, Shopping, Gmail, YouTube and Display. Google's Customer Match policy requires the advertiser to have collected the data first-party and to meet account eligibility requirements (good policy compliance history, at least 90 days of history, and more than USD 50,000 lifetime spend for some features; check the current policy page as thresholds change). Google's Help Center states a list should have at least 1,000 matched members to be eligible for targeting in most campaign types.

The first-party requirement is the one that trips up intent activation. Google's policy says uploaded data must be collected directly by the advertiser from customers who have consented; purchased lists from a data vendor are explicitly outside policy. In practice, that means the compliant use of Customer Match with intent data is to upload contacts already in your CRM who happen to sit at surging accounts, not to upload a third-party contact export. Several activation platforms handle this by using their own first-party relationships or by restricting Google to retargeting site visitors from surging accounts. Read the policy before you build the workflow.

Programmatic DSPs and ABM display networks

Programmatic display is where account-level intent data originated, and it remains the widest-reach channel for it. Two mechanisms are in use. IP-to-account mapping matches a company's office IP ranges to ad requests, which worked well when people sat in offices and works less well now that many do not. Cookie and mobile-ID based B2B audience segments, sold through data marketplaces on The Trade Desk, StackAdapt, Google Display & Video 360 and others, use identity graphs to associate individuals with employers. Both are probabilistic; expect meaningful spillover to non-target impressions.

Bombora sells Company Surge audiences as third-party segments through most major DSPs, including The Trade Desk, DV360, Amazon DSP and StackAdapt, priced as a CPM data fee layered on media cost. 6sense and Demandbase each operate their own DSP (Demandbase acquired its display technology, 6sense built on a partnership then its own stack) and both use account identification tied to their intent models, so the audience updates as accounts move between buying stages. RollWorks, built on the AdRoll bid stack, offers the same pattern for smaller lists. StackAdapt is the most common independent DSP for B2B teams that want to buy Bombora, G2 or ZoomInfo segments without an ABM platform contract.

For deeper coverage of B2B display execution, the sister site abmadvertisingplatform.com covers ABM display, retargeting and DSP reviews in detail.

Native integrations: Bombora, G2, ZoomInfo, 6sense and Demandbase

Every major intent vendor now ships connectors that skip the CSV step for at least one ad channel. The table below is what each vendor documents publicly; verify current availability on the linked integration pages because vendors add and drop connectors frequently.

Where activation goes wrong

Stale lists

Bombora describes a typical surge window as a few weeks; G2 reports that buyers on its site are often weeks from a decision. A list uploaded once a month is targeting accounts whose research phase may be over. If you cannot automate refresh, run shorter flights and rebuild the audience at the start of each one.

Targeting the whole company

A surging account with 20,000 employees is not 20,000 buyers. Without job function and seniority layers on LinkedIn, or contact selection by title before a Meta or Google upload, most impressions land on people who will never see a purchase order. Define the buying committee for your category first; our buyer's guide covers how.

Ignoring minimum audience sizes

LinkedIn's 300-member floor, Meta's 100-person floor and Google's roughly 1,000-user threshold are hard constraints. Teams with a tight ICP routinely fall below them. Solutions: widen the intent threshold, pool several weeks of surging accounts, or add more contacts per account before upload.

Policy violations on Google

Uploading a purchased contact list to Customer Match breaches Google's policy and can suspend the account. Keep Google activation to first-party contacts and site retargeting.

Measuring clicks instead of accounts

Intent-driven ads are judged on whether target accounts engaged and progressed, not on CTR. LinkedIn's company engagement report, ABM platform account dashboards, and CRM opportunity source reports are the right instruments. For channel benchmarks, abmbenchmarks.com collects public reports, including Metadata's 2026 benchmark report (disclosed sponsor).

Frequently asked questions