Should you sum Meta + Google revenue?
No. Do not add Meta reported revenue to Google reported revenue and call it client revenue. Use payment revenue when you need a number a client can open in their own dashboard and recognize.
Platform dashboards are built to credit their own contribution. They are not sitting in a shared room agreeing on one sale. Two confident reports can still point to one bank deposit.
Why the sum invents money
Someone clicks Meta, later searches Google, clicks again, and buys. Meta credits a sale. Google credits a sale. Stripe records one charge. Two claims, one payment.
That does not make Ads Manager useless. Each platform is answering a different question: did we play a role? The client is asking how much money hit the account.
A sample account, not an industry average
On Thexly's sample account, Meta claims $12,400 and Google claims $9,800, for $22,200 combined. Stripe shows $14,600. The $7,600 gap is an illustration from the sample account, not a benchmark for every client.
The shape is what matters: combined claims can sit above payment revenue when journeys overlap.
What to show the client instead
Start from payment revenue. Platform ROAS still helps you optimize inside each channel, but it is a weaker source of truth for the retainer conversation.
When you need a client-facing revenue story, count each paid conversion against payment truth once. Give the client a live view instead of a PDF that is stale the afternoon you send it.
- Connect the processor the client actually settles in.
- Place platform claims beside payment revenue.
- Use platform ROAS for in-channel optimization, not a summed revenue line.
Where Thexly fits
Thexly Agency is for Stripe-class SaaS, AI, fintech, and similar checkouts where Meta and Google claims need to be reconciled to payment revenue. Agency is $79/mo for up to 10 clients, with live share links.
If your book is almost entirely Shopify-native DTC, tools built for that operating system are usually a closer fit.