What connecting unlocks
Ad platforms report what happened inside the ad platform. Your first-party analytics and Stripe know what happened afterwards. Connecting the two lets you judge spend on revenue you can verify, and hand the platforms better signal in return.
One connection per platform unlocks three things:
- Reporting on the Paid Ads page — spend, clicks, conversions and cost per conversion, with return on ad spend computed against first-party revenue.
- Audiences — segments of your own visitors, contacts and companies, synced to the platform as customer-list audiences.
- Server-side conversions — your verified conversions forwarded to the platform from our servers, so its bidding learns from purchases and leads that really happened.
The same data is available to the Assistant through get_ads_stats, and to any agent on your MCP endpoint.
Connect Meta Ads
1. Open Connections, expand the Meta Ads card under Recommended integrations and click Connect account. 2. Sign in with your own Meta account and approve. 3. Your ad account is detected automatically — an active account is preferred — and so is the account’s first pixel, which server-side conversions need.
If the wrong ad account or pixel was picked, correct the Ad account ID or Pixel ID field on the card.
Connect Google Ads
1. Open Connections, expand the Google Ads card under Recommended integrations and click Connect account. 2. Sign in with the Google account that manages your ads. The customer ID is detected; if the login manages several accounts, pick one. A manager (MCC) account is detected in most cases too. 3. Once connected, optionally fill in your conversion action IDs on the card — purchase, lead and sign-up — from Google Ads → Goals → Conversions. Server-verified conversions upload to the matching action. A lead falls back to the purchase action if you set only one, but a purchase never falls back to a lead action.
Google Ads calls run under our platform’s Google Ads developer token. If the card’s Test reports that token as pending approval, your connection is saved and nothing has to be redone — reporting, Customer Match and conversion upload start once the token is approved.
Reporting: spend against real revenue
The Performance tab shows spend and results per platform and per campaign. The difference from the platforms’ own dashboards is the revenue side: attributed revenue and blended ROAS come from your first-party data and Stripe, not from the pixel, so a platform claiming a sale it did not drive does not inflate the number. The Attribution tab shows which channels and campaigns the revenue actually came through.
For that to work, your conversions need to be counted correctly — see Conversion goals — and revenue needs to be connected — see Connect Stripe.
Audiences from your visitor graph
The Audiences tab turns the people you already know into ad audiences. An audience is one of four kinds:
- Target — for example engaged visitors who have not converted, or everyone who visited
/pricing. - Suppress — usually your customers, so you stop paying to reach people who already bought.
- Lookalike — seeded from your converters.
- Account — built from identified companies, filtered by industry.
Pick the platforms to sync to — Meta and Google Customer Match — and the audience is sent as a hashed customer list. Each platform has a minimum audience size before it will serve; the card reports the match size so you know where you stand. Auto-retargeting keeps an engaged-visitors audience and a sales-outreach audience synced daily and suppresses customers, if you switch it on.
Server-side conversions
Switch on Server-side conversions (CAPI) in the Audiences tab and your verified conversions are forwarded from our servers to the connected platforms. By default revenue and every goal with the Conversion role forward automatically; opt individual goals out, or turn auto-forward off and pick the goals yourself.
Because the event comes from the server rather than a browser pixel, it survives ad blockers and it carries the purchase or lead your records actually hold. For Meta it needs the pixel id on the card; for Google, the conversion action ids above.
What the AI can do with campaigns
The AI business analyst reads ad performance freely. For Google Ads it can also pause or resume a campaign, change a daily budget, and create a Search campaign — each only when you ask, each as an approval card you accept before anything changes, and a created campaign always starts paused. It does not run campaigns on Meta, and it never spends on its own.
Frequently asked questions
Will the AI change my campaigns on its own?
No. Reading performance needs no approval, but pausing or resuming a Google Ads campaign, changing a budget or creating a campaign each posts an approval card, and nothing changes until you approve it. A campaign the AI creates is created paused, so launching it is a second decision.
Do audiences and server-side conversions need a paid plan?
Yes. Reporting works on every plan once an ad account is connected; building and syncing audiences and forwarding server-side conversions are part of the paid plans.
Are privacy opt-outs respected?
Yes. Sharing with ad platforms is where Global Privacy Control applies, so a US visitor who sent a GPC signal is excluded from audience syncs and conversion forwarding, as are unsubscribed contacts.
Keep going
Turn your company into one AI-ready data platform on a single hosted MCP endpoint.