Why Ad Teams Disagree on Metrics (Instead of Acting on Them)

The meeting was supposed to be about the campaign. Twenty minutes in, nobody has talked about the campaign. To understand why ad teams disagree on metrics, watch this room: the media buyer is reading spend off Ads Manager, the account manager is quoting the tracker, and the spreadsheet open on the shared screen says something different again. The client deck — sent yesterday — already disagrees with all three. This is the daily tax of having no single source of truth for ad data: the team argues about which number is right instead of acting on any of them.

Why ad teams disagree on metrics: four numbers, none agreeing

There is rarely one number in an ad operation. There are at least four, and they live in four systems that were never designed to reconcile with each other. It is a near-universal problem: most organizations still name data silos and inconsistent data as a top barrier to confident decision-making (Forrester, 2024).

Ads Manager reports platform-attributed conversions inside its own attribution window — a 7-day click, 1-day view model that credits the platform generously for anything it touched. The tracker counts clicks, postbacks and server events on its own clock, often deduplicating differently. The spreadsheet is a human snapshot: someone pulled figures at 9am Tuesday, rounded, and pasted them into a tab that has not been touched since. The client deck freezes a fifth moment in time, formatted for narrative rather than precision.

Once you see this, the argument changes character. It is not a hunt for the liar. It is four valid measurements colliding, and the team treating the collision as a mystery to solve every single meeting.

It helps to walk through a concrete case. A DTC brand runs Meta and Google. On Monday, Ads Manager reports €18,400 in attributed revenue for the week. The tracker, deduplicating against actual orders, reports €14,900. The Monday spreadsheet — pulled Friday afternoon before the weekend's sales landed — shows €13,200. The client deck, built Sunday night, quotes €16,000 because the analyst averaged two of the three and rounded. Four numbers, a €5,200 spread, and not one of them produced by an error. Meta over-credits view-through conversions; the tracker is stricter; the spreadsheet is stale by two days; the deck is a compromise nobody can reconstruct. The team spends the first half of the call deciding which of these to believe, and by the time they agree, the call is nearly over.

What is striking about this case is how ordinary it is. There is no broken pixel, no misconfigured UTM, no fraud. Everything is working as designed — and the numbers still do not agree, because they were never built to. That is the part teams keep missing. They treat the spread as a bug to be fixed, when it is a structural feature of running four independent measurement systems and expecting them to converge.

Why the argument is so expensive

The obvious cost is time — the twenty minutes at the top of every meeting spent reconciling instead of deciding. The deeper cost is what does not happen while that reconciliation runs.

A losing campaign keeps spending during the debate, because nobody cuts a campaign while its performance number is still contested. A winner does not get scaled, because the team cannot agree it is actually winning. Budget reallocation stalls. The decisions that move money wait for an agreement that, structurally, can never arrive — because the underlying systems will keep disagreeing tomorrow exactly as they did today.

Then there is the trust cost, which is the quietest and the most damaging. The client can see their own Ads Manager. When your deck shows a different ROAS than their dashboard, you do not look precise — you look like you are either confused or massaging the figure. A 2024 analysis from the data-integration vendor Funnel found that marketers routinely manage data across dozens of sources without a reconciliation layer, which is the structural reason these mismatches are the norm rather than the exception. Every mismatch the client notices spends a little of the trust you will need when you ask them to approve a budget increase.

What a real source of truth is — and isn't

The instinct is to chase a perfect number: the one true ROAS, the figure that is correct for every purpose. That number does not exist, and chasing it is how teams burn months building reconciliation spreadsheets that break the moment a platform changes its attribution model.

A source of truth is not one perfect number. It is one agreed number per question, read by everyone from the same place, refreshed on the same cadence.

That agreement has two parts. First, a convention: which figure governs which decision, decided in advance so it is not negotiated live. Second, a shared surface where everyone reads that figure the same way — not four exports reconciled by hand, but one cross-channel view pulled the same way for everyone.

This is the structural problem behind multi-account reporting chaos: the more accounts and channels you add, the more independent measurement systems you are silently asking to agree, and they never will on their own. And it sits right next to the ROAS-trust problem — but it is a different problem. The ROAS question is "is this number accurate?" This question is "why do we have four of them, and which one do we act on?"

Writing the convention down

The convention is the cheap half, and almost nobody does it. It is a single page that maps decisions to numbers: pacing uses the platform billing figure; profit uses the tracker reconciled to the order system; the client deck reports the platform figure with a footnote naming the window. Each line removes one future argument.

The discipline is not in writing the page — it is in refusing to renegotiate it mid-meeting. When someone says "but Ads Manager shows more," the answer is no longer a twenty-minute reconciliation; it is "yes, and for this decision we agreed to use the tracker figure — here it is." The convention is only worth anything if the team treats it as settled. The moment one number gets relitigated, all of them are back in play, and the meeting reverts to arithmetic.

Building the shared surface

The second half is harder because it cannot be solved with a document. Four people reading four exports will reconcile by hand no matter how good the convention is, because they are each looking at a different snapshot pulled at a different moment. The only way to remove the manual reconciliation is to remove the four exports — to give everyone one surface that pulls the same figure the same way on the same cadence.

Where the shared view fits

A tool does not end the argument by being right. It ends it by giving everyone the same starting figure so the conversation can move past it.

Wevion connects Meta, Google, TikTok, Taboola and more through their official APIs and presents one cross-channel view, synced about every 15 minutes. The media buyer, the account manager and — through a shared report — the client are all reading the same spend, the same cost-per-result, pulled the same way. There is still judgment to apply: the platform number still over-credits, the human still decides which figure governs which call. What disappears is the reconciliation ritual at the top of the meeting, because there are no longer four spreadsheets to reconcile — there is one view, and a conversation about what to do with it.

It does not act on its own and it is not instant — the sync runs roughly every quarter-hour, not live. What it changes is who is reading what. When the agency, the buyer and the client share one cross-channel reporting view, the argument about which number is right stops being a daily event, and the team gets its meetings back.

The shift that actually matters

The win here is not technical. It is behavioural. A team with no agreed number defaults to debate, because debate feels like diligence — surely we should figure out which figure is correct before we act? But the figures will not converge, so the diligence never ends, and the spend keeps flowing while it doesn't.

A team with one agreed number, read from one shared surface, defaults to action. The number is not perfect; everyone knows that, and they have decided which figure governs which decision anyway. So the meeting skips the reconciliation and goes straight to the only question that moves money: given what we are all looking at, what do we do now?

The scale of the underlying problem is not small. Salesforce's 2024 State of Marketing report found that marketers draw on an average of roughly fifteen data sources to do their jobs, a figure projected to keep rising — which means the four-numbers problem in our example is a conservative version of what most teams actually face. The more sources you add without a shared surface and an agreed convention, the more reconciliation arguments you manufacture, and the fewer decisions you make per meeting. The trend is the wrong direction unless something collapses those sources into one view.

That is the whole game. Stop trying to make four systems agree. Pick one number per decision, read it from one place, and spend your meetings on the campaign instead of on the arithmetic. If you want to see what one shared cross-channel view looks like in practice — across every channel, synced about every 15 minutes, with the human still making every call — start a 14-day Wevion trial alongside the permanent free plan and watch the top-of-meeting argument disappear.

This guide is part of our agency tools hub — explore the full cluster for related playbooks.