Connect Meta Ads to Claude and ChatGPT
Ads Manager can tell your AI what you spent and what it attributed. It cannot tell you what you kept. MerchantFlow joins Meta spend to your orders, costs and fees so the answer accounts for the whole picture.
What you can ask once it is connected
“How did Meta perform against Google last week?”
Meta: A$1,240 spend, 2.8x ROAS on A$3,470 attributed revenue. Google Ads: A$890 spend, 4.1x ROAS on A$3,650. Google returned about 46% more per dollar. Blended MER across both was 3.3x. Note that this is spend and attributed revenue - profit is reported blended, not split per campaign.
Example answer, shown to illustrate the shape and level of detail. Your figures come from your own connected account.
What Meta Ads alone cannot tell you
Connecting an AI directly to Meta Ads is genuinely useful, and for some questions it is all you need. It stops being enough the moment the question involves money you spent somewhere else.
- What each order actually cost you to buy and to ship
- Revenue Meta did not attribute to itself, and revenue it attributed twice
- Spend from your other platforms, which shapes blended performance
- Refunds, which land after the attribution window has closed
What MerchantFlow adds
- Multiple ad accounts supported properly: campaign ids are namespaced per account, so two accounts running a campaign with the same id are never collapsed into one
- Spend deduplicated before totalling, including when country-level rows supersede a campaign-level row for the same day
- Exclude specific Meta campaigns from profit - brand or always-on spend can be parked so your P&L reflects the campaigns you actually judge on return. This is available for Meta only
- Per-country spend taken from Meta's own country breakdown where it reports one, rather than allocated
- Every day re-anchored to your store's timezone, because Meta reports in the ad account's
- Paused and archived campaigns still counted in history, so last quarter does not shrink when you tidy up
MerchantFlow reports spend, attributed revenue and ROAS at campaign level. Profit is blended across the business rather than attributed per campaign, and the AI is told this directly so it says so instead of estimating. Meta issues a long-lived token rather than a refreshing one, so a Meta connection needs reauthorising periodically - MerchantFlow tells you when. History is limited to 37 months by Meta's own reporting API.
How to connect it
- 01
Connect Meta Ads to MerchantFlow
Authorise Meta Ads from your MerchantFlow integrations page. We start pulling and normalising the data straight away.
- 02
Add MerchantFlow as a connector in Claude or ChatGPT
Approve read-only access from your AI client's connector settings. Nothing to install on your machine. Your dashboard shows the current steps for whichever client you use, because the clients move their menus often.
- 03
Ask in plain English
Your AI now reads the same figures as your dashboard, joined across every source you have connected.
Included on every paid plan, trials included. Starter reads 90 days of history, Pro reads 12 months, and Plus and Agency read your full history.
The tools your AI calls
These are the actual tools MerchantFlow exposes for Meta Ads questions. Every claim on this page maps to one of them.
get_ad_performanceget_channel_roasget_pnl_summaryCommon questions
Can it change anything in Meta Ads?
No. The connection is read-only and no write access exists to grant. Your AI can read figures and reason about them; it cannot create, edit, pause or delete anything.
Will the numbers match my dashboard?
Yes. Your AI calls the same calculations the MerchantFlow dashboard uses, so the same question over the same period returns the same figure in both places.
