A framing example, not a case study and not a measured outcome: "You spent €100k on Meta and Google. Here's what actually produced the €300k that hit your bank account." Say that it is an example. Then use their month.
The client conversation this report has to win
Spent X. Bank shows Y. This view explains Y. Platform ROAS can live in the appendix. Two ROAS numbers and no payment line still confuse the client.
They open Ads Manager or the processor between meetings. A monthly PDF is often stale that afternoon. A live share link lets both sides open one report before the QBR.
What a client reporting tool is being asked to show
Dashboards, portals, templates, live links. For this retainer: Meta spend from Meta, Google spend from Google, one processor total, openable on a Tuesday. A PPC template locks columns and the change note. If it adds the two revenue claims, a cleaner PDF still invents money.
Ours is the PPC report template, with platform claims and payments in separate columns.
Payment revenue next to the Meta export and the Google export
Processor first. Platform claims beside what cleared. Then the live link. Refresh each client workspace, mark where a claim sits above the payout, send the link before the meeting, defend payment revenue in the room.
Product list, not a demand claim: Stripe, Lemon Squeezy, Polar, Dodo, Yolfi. An entirely Shopify-native DTC book may fit a checkout-specific stack better. Plans: Thexly for agencies and pricing.
One sale claimed twice: what the report should not add
Click Meta, later Google, one purchase. Both claim it. The processor records one charge. Do not add the revenue columns. Each claim beside its own spend. Payment revenue once. A chart that adds them has the PDF's problem. Longer read: one sale, two claims. Blended talk: blended ROAS and MER versus platform ROAS.
Client reporting software and PPC report templates: live link versus PDF
Software, in this search, means both sides see the same numbers between meetings. Live helps when the platforms move after you send. Live is not the same as payment-verified. A live board of platform totals still double-counts.
Keep Looker, or another portal, for SEO, email, and social. Weighing a specific tool? See AgencyAnalytics alternative. A monthly template can hold a tiny book. It fails when Tuesday's Ads Manager disagrees with Friday's file. Stack page: Sheets, Looker, and AgencyAnalytics. SEO reporting: SEO agency reporting software.
For a Google-only client, start with our Google Ads report template for clients.
Ours is the client reporting template, with platform claims and payments in separate columns.
What a client reporting portal means here
A shared place for the same live report, instead of a monthly export. A "demo" on this page is that link: refresh the workspace, claims next to what cleared, send it. Not a separate demo product. One workspace and one share per client. Book-level packaging: one Agency view across clients.
What this page does not try to be
Not a pixel suite. Not CAPI, Conversion API, or passback. Not spend sync or ROAS sync. Thexly does not pull ad spend. Not a first-touch, last-touch, or multi-touch method, and it does not set platform windows. Not a white-label domain. The live page describes a shared link, not your brand on their URL.
Choosing a tool? Our agency guide to marketing attribution software sets out the four kinds.
Where the rest of the reporting guides fit
FAQ
What should a client reporting tool show besides platform ROAS?
Each platform's spend, the dates, and payment revenue. Not the sum of the two revenue claims.
How do I talk about €100k of spend and €300k in the bank without calling it a case study?
Call the line a framing example. "You spent €100k on Meta and Google. Here's what actually produced the €300k that hit your bank account." Then use the client's own payout.
Why is the sum of Meta and Google revenue a bad client total?
Both can claim one sale. The processor shows one charge. "What we made" is payment revenue.
Does Thexly pull ads spend into the report?
No. No spend sync and no platform ROAS sync.
Is a shared live link the same as a white-label portal?
No. The live FAQ means both sides open one report per client, instead of a PDF. It does not describe a white-label domain or a separate login product. Live also does not, by itself, mean payment-verified.
Which guide do I send a client who wants the Google or Facebook export explained?
Google Ads reporting, or Facebook / Meta to match their label.
What did you wish they could open, the last time a PDF met their bank app?
Internal links
- Thexly for agencies
- Pricing
- Google Ads reporting
- Facebook Ads reporting
- Meta Ads reporting
- Why Meta and Google both claim the same sale
- Blended ROAS and MER vs platform ROAS
- One Agency view across clients
- Sheets, Looker, AgencyAnalytics vs a payment read
- SEO agency reporting software
- PPC reporting for agencies: spend to revenue