Matched audiences on LinkedIn, Meta and Reddit, upload files for Google, TikTok, X and Pinterest, suppression that holds out customers, and lead forms synced to the CRM. The same governed list behind the campaign and the sequence.
LinkedIn, Meta and Reddit receive matched audiences through connected ad accounts on managed credentials.
Google, TikTok, X and Pinterest receive customer-list files in the exact layout each upload dialog expects.
Customers, open deals and competitors held out of prospecting audiences on the cadence you set.
Every audience push parks with its name, source list and row count; attaching it to a campaign stays with your buyer.
The audience in the ad account was a CSV someone pulled in March. Sales has moved on to new accounts; the campaign is still spending on the old ones.
Suppression lists are rebuilt when someone remembers. Between rebuilds, budget reaches accounts that already pay you and deals already in flight.
Hashed emails here, company names there, a template with twelve columns somewhere else. Shaping the same list five ways is a day nobody budgets for.
Lists, CRM segments and signal cohorts shaped to each platform’s matching keys and pushed to LinkedIn, Meta and Reddit, with match rates read back.
Customer-match and list-audience files for Google, TikTok, X and Pinterest in the exact layout each upload dialog expects, delivered to Drive.
Customers, open deals and competitors held out; engaged and in-market accounts kept in; both rebuilt weekly from the CRM so targeting tracks the pipeline.
LinkedIn lead-gen submissions enriched, scored and synced to the CRM within minutes, and closed pipeline pushed back as conversions so the platform optimizes toward revenue.
A list, a CRM segment or a signal cohort in plain language: tier-one ABM accounts, everyone researching your category, all customers for suppression.
Accounts and contacts resolved from the source list, enriched where matching keys are missing, deduplicated against the CRM.
Customers, open opportunities, competitors and do-not-contact records removed before the audience exists, and checked again before any push.
Company names and domains for LinkedIn, hashed emails for Meta and Reddit, the customer-list template for Google, TikTok, X and Pinterest.
Pushed where a connection exists and staged for approval; exported to Drive as an upload-ready file where it does not.
Match rates read back and recorded on the source list, and the whole build rerun on the cadence you set.
The tiered target list pushed as a matched company audience to LinkedIn and a contact audience to Meta, rebuilt every Monday from the CRM with suppression applied and match rates posted.
Every customer, open opportunity and competitor held out of prospecting campaigns on Meta and LinkedIn, refreshed weekly so the exclusion never depends on someone remembering.
Companies researching your category this month, their decision makers verified, shaped as a Google customer-match upload file and delivered to Drive for the campaign built for them.
LinkedIn lead-gen submissions enriched, scored and synced to the CRM within minutes, with the source campaign on the record and qualified events pushed back as conversions.
| By hand | With AstroFabric | |
|---|---|---|
| Source of truth | A CSV exported at campaign launch | The governed list sales works, refreshed weekly |
| Suppression | Rebuilt when someone remembers | Rebuilt on cadence from the CRM, applied before any push |
| Platform formats | Five templates shaped by hand | Shaped per platform from one list |
| Match rate | Read in the ad account, recorded nowhere | Read back and stored on the source list |
| Lead forms | Downloaded weekly, uploaded later | Enriched and in the CRM within minutes |
| Governance | Whoever had the login | Every push approved, logged and attributable |
The 400-account ABM list pushed as a matched company audience, the match rate reported, refreshed every Monday.
Every customer and open opportunity as a suppression audience on Meta, rebuilt weekly so prospecting spend reaches new accounts.
Companies researching your category this month, their decision makers verified, as an upload file in Drive for the campaign built for them.
Three of a hundred. The full playbook library ships in every workspace, and anything you can describe becomes a mission.
Audience pushes park in the approval queue with the audience name, the source list and the row count. Attaching it to a campaign stays with your media buyer.
Platforms receive hashed matching fields in the format their upload expects. Scores, evidence and notes stay on the source list in your workspace.
The platform builds and refreshes audiences. Campaign structure, bids and budgets remain in Ads Manager with the people who own them.
LinkedIn, Meta and Reddit through connected ad accounts on managed credentials, with no developer tokens or app reviews of your own. Google, TikTok, X and Pinterest receive platform-ready upload files instead: the agent produces the exact customer-list format and you upload it under Audiences.
A standing mission rebuilds customer, open-deal and competitor audiences from the CRM on the cadence you set and pushes the refresh for approval. The same suppression applies before any list becomes a prospecting audience, so the exclusion is enforced at the source rather than remembered.
Yes. LinkedIn lead-gen form responses sync into the CRM enriched and scored, and qualified or closed-won events push back to LinkedIn as offline conversions, so the platform learns from pipeline instead of clicks. Every sync and push is logged and approval-gated.
No. The platform builds, refreshes and pushes audiences; campaign structure, creative, bids and budgets stay in the ad account with the people who own them. A media buyer attaches the approved audience to a campaign the way they do today, with the source list and refresh date visible.
Only the matching keys each platform needs: company names and domains for company audiences, hashed emails for contact audiences, in the format the upload expects. Scores, signals, evidence and notes stay on the source list in your workspace, and every push is logged with its row count.
Yes. A cohort can be defined by intent on your topics, hiring in a function, a recent funding round or a technology change, crossed with your ICP and suppression lists. The cohort becomes a persistent list, so the audience refreshes as the signal set changes.
The agents estimate the likely match before pushing so you know whether a list will clear a platform minimum, and can enrich missing keys or expand the list with lookalikes of your best customers before the push. The recorded match rate on each refresh shows what worked.
The first matched audience this afternoon; suppression refreshed every week after.