Independent paid media review for finance decisions
CFO Paid Media Review: What to Verify Before Approving, Renewing, or Questioning Ad Spend
Platform dashboards report platform activity. Agency reports summarize agency-measured performance. Before finance approves more spend, renews an agency, questions a budget, or prepares for a board discussion, the reported performance should be compared against downstream business records.
- Read-only review available
- No campaign edit rights required for the diagnostic review
- No account takeover
- No agency replacement pitch
- No budget recommendation made for the operator
- Written findings support the decision, but do not make it
- Implementation remains separate
- Operator keeps the management decision
What a CFO paid media review is
A CFO paid media review is an independent finance review. It puts platform-reported performance, agency-reported performance, and downstream business records side by side, then checks whether the reported numbers reconcile with the records the business uses to make decisions.
The review does not run campaigns. It does not manage budgets. It looks at whether reported conversions, ROAS, revenue, CRM outcomes, Shopify orders, and imported conversions are supported by finance records, CRM records, and order records.
Most finance teams see two things before a spend decision. One is a platform dashboard. The other is an agency report. Both describe activity, and neither is the same as verified revenue. This is the core of an independent paid media audit: separate the diagnosis from the people who run the campaigns, and write down what the records confirm.
The output is written. The decision stays with the operator.
What it is not
A CFO paid media review is not a campaign management pitch. It is not a plan to reduce spend, and it is not a plan to increase it. It does not tell you to keep your agency, and it does not tell you to drop it.
It is not an agency attack, and it is not a platform attack. Reported performance is not assumed to be wrong. The point is narrower than that. Check the reported numbers against downstream business records, and document where they line up and where they do not.
It is not attribution software. It is not a dashboard subscription. It is not a no-cost account scan used to sell you something larger. It is a written review with a fixed scope, delivered read-only, with implementation kept separate.
Why platform-reported performance is not the same as verified revenue
Platform-reported performance and verified revenue measure different things by design. A platform counts conversions and revenue using its own attribution rules, its own windows, and its own tags. Finance records document revenue in the systems the business runs on.
Those two counts can diverge for reasons that have nothing to do with anyone acting in bad faith. An attribution window credits a conversion to an ad the customer saw days earlier. A view-through setting credits an impression with no click. A tag fires on a page load instead of a completed action. None of that requires deception. It is how the systems are built.
That is why platform-reported ROAS vs. verified revenue is worth checking before a spend decision. A dashboard is a report. A finance record is a record of what happened. When the two disagree, the review documents the size and the source of the gap rather than assuming either side is simply right.
Why agency-reported performance needs independent review
An agency report is prepared by the party whose work is being evaluated. That is not an accusation. The point is independence. Someone outside the reporting chain checks the numbers against business records.
An independent review checks the data behind the agency report against the records the business keeps itself. It does not assume the agency is wrong. It asks a plain question. Do the reported outcomes match the CRM records, the order records, and the finance records? Where they match, that is worth knowing. Where they do not, that is worth knowing too.
This matters most around a renewal. Before you extend a contract, an independent review before agency renewal gives you a documented basis for the discussion instead of a report that has not been checked against business records.
What finance should verify before approving more spend
Before approving more spend, finance should verify that the current spend is supported by records, not just by the dashboard. The question is not whether the campaigns are busy. It is whether the reported results show up where the money is counted.
A review looks at:
- Whether reported conversions match CRM records or order records
- Whether platform-reported ROAS reconciles with verified revenue
- Whether the same conversion is being counted more than once
- Whether conversions fire on completed actions or on page loads
- Whether imported offline conversions match the source records they came from
More spend on top of unverified tracking can extend the same uncertainty. Verify the basis first. Then an increase, if you make one, rests on records instead of a report.
What finance should verify before an agency renewal discussion
Before a renewal discussion, finance should verify that the agency-reported performance matches the records the business keeps. A renewal is a commitment. It should rest on outcomes you can confirm, not only on a report from the agency you are renewing.
The review documents whether the reported conversions, revenue, and ROAS reconcile with CRM records, Shopify order records, and finance records across the contract period. It does not tell you to renew, and it does not tell you not to. It gives you a documented spend basis, so the renewal discussion is grounded in what the records support.
This is a diagnostic, not a replacement pitch. This review does not become a campaign management pitch.
What finance should verify before increasing or reducing spend
Whether you are looking at an increase or a reduction, the same records apply. A spend change is only as sound as the numbers behind it. If the tracking is unresolved, both directions are being considered from an unverified basis.
Before a change in either direction, verify:
- That reported performance reconciles with downstream business records
- That conversions are not duplicated across tags or platforms
- That the revenue in the dashboard is revenue the finance records confirm
The review does not recommend a direction. Increase, hold, or reduce, that decision stays with the operator. What the review adds is a documented basis, so the decision rests on verified revenue rather than platform-reported activity alone.
The conversion tracking questions finance should ask
Many gaps between reported performance and verified revenue trace back to how conversions are tracked. These are questions finance can ask without touching a single campaign setting. Much of this comes down to bad conversion tracking, which does not always show up in the dashboard, because the dashboard reports whatever the tags tell it.
Duplicate conversion counting
Ask whether a single conversion can be counted more than once. It happens when two tags fire for the same action, or when a platform and an analytics tool both claim the same event. This is duplicate conversion counting, and it raises the reported number without a separate confirmed outcome. The review checks whether the count in the dashboard matches the count in the records.
Page-load conversions
Ask what actually triggers a conversion. If a tag fires when a thank-you page loads, a reload or a direct visit can register as a conversion that does not match a completed action. These are page-load conversions, and they can count the page instead of the outcome. The review checks whether conversions represent completed actions or pages that simply loaded.
Offline conversion imports
Ask whether imported conversions match their source. When offline conversions are uploaded from a CRM or a call system, the import can double-count, mismap, or bring in records that do not reconcile with the source. An offline conversion import audit checks the uploaded conversions against the records they claim to represent.
Downstream records: CRM, Shopify, orders, and finance records
A dashboard reports what the platform measured. Downstream business records show what the business received. A review reconciles the two, because the records are what finance already uses to close the books.
Google Ads vs. CRM
For lead generation, the test is whether Google Ads conversions match CRM records. A form fill is not a qualified lead, and a qualified lead is not a closed deal. Google Ads vs. CRM reconciliation checks whether the conversions the platform reports line up with the pipeline the business recorded.
Meta Ads vs. Shopify
For ecommerce, the test is whether Meta-attributed revenue matches Shopify order records. Meta counts conversions through the pixel and the Conversions API on its own attribution rules. Meta Ads vs. Shopify reconciliation checks that reported revenue against the orders Shopify recorded. For Meta, the review uses an analyst, view-only role, so nothing in the account changes.
Potentially recoverable waste in a finance review
A finance review may surface potentially recoverable waste, which is spend the records suggest may not be doing what the dashboard implies. It is a documented finding, not a promise. The review flags it. The operator decides what, if anything, to do about it.
The word potentially is doing real work. A finding that a conversion is counted twice, or that a tag fires on a page load, points to spend that may be recoverable once the underlying issue is addressed. That is a possibility the records support, not a certainty. Corrected tracking changes what you can see. It does not, on its own, change what a campaign returns.
So the review documents potentially recoverable waste as a category, with the records behind it, and leaves the size and the response to the operator.
Why read-only review matters
A review does not need to touch your campaigns to check your numbers. For this diagnostic review, read-only access can be enough to inspect tags, attribution settings, conversion actions, and reported results. Nothing is edited. Nothing is paused. The account runs exactly as it did before.
This matters for two reasons. The first is control. A read-only paid media review means no campaign edit rights and no account takeover, so the operator keeps running the account throughout. The second is cleanliness. A read-only posture captures the account as it actually is, without the review changing the thing it is measuring.
In Google Ads, this maps to the platform's Read-only permission tier. In Meta, the review uses an analyst, view-only role. Either way, diagnosis stays separate from implementation, and implementation remains separate from the review.
What a Paid Media Verdict gives finance
The output of the review is a Paid Media Verdict. It is a written document, not a dashboard and not a call. It is built to be read by finance and used in a board discussion.
Written findings
The verdict documents what the records support, what stays unresolved, and what may qualify as potentially recoverable waste. Each finding points back to the records behind it, so the review can be checked rather than taken on trust.
Documented spend basis
The verdict gives finance a documented spend basis. That is a plain account of whether the reported performance reconciles with downstream business records. It is what a spend approval, a renewal discussion, or a board discussion can rest on.
Operator decision retained
The verdict does not make the call. It does not tell you to approve, renew, increase, or reduce. Findings support the decision, but they do not make it. The management decision stays with the operator.
What happens after the review
After the review, you have a written record and a decision to make. What you do with it is yours.
Some operators use the verdict to approve spend on a clearer basis. Some carry it into a renewal discussion. Some take the findings to whoever manages the account and fix what the review surfaced. The review does not push a direction, and it does not sell the next step. Implementation remains separate by design.
If you want to see the shape of the output first, see a sample verdict. If you want the detail of how the review runs, here is how the review works.