Why Most Digital Marketers Can't Defend Their Numbers

Analytics · Marketing Accountability

Why Most Digital Marketers Can't Defend Their Numbers

SECTION 01Reporting vs defending

Reporting a number is easy: open a dashboard, copy the metric, paste it into a deck. Defending a number is hard: explain why it changed, prove you caused it, and connect it to the business. Most marketers stop at reporting.

Report Only:
"ROAS is 3.2 this quarter."

What the room hears:
"Here is a number."

When asked "Why did it drop from 3.8?":
"Um... the market changed, I think."

The number collapses under the first
follow-up question. Trust drops.

Defend:
"ROAS dropped from 3.8 to 3.2 this quarter.
The main driver was a 22% rise in CPC on
brand terms — competitors entered the auction.
I tested a bid cap and a new landing page;
the bid cap recovered 0.3 ROAS in two weeks.
If we hold the cap, we expect 3.5 by next
quarter — still below 3.8, but stable."

What the room hears:
"They know why it changed, what they did,
and what happens next."

The number holds. Trust grows.

SECTION 02The three gaps behind every undefendable number

When a marketer can't defend a number, it is almost always one of three gaps — attribution, causality, or business context. Close them, and the number becomes defensible.

Attribution Gap Example:
"Meta drove 40% of conversions."

When asked:
"How do you know it wasn't organic or brand
search?"

You can't answer — because you only looked at
last-click attribution, and last-click gives
all the credit to the final touch.

The number is real. The defence is not.

Causality Gap Example:
"Conversions rose 30% after the campaign
launch."

When asked:
"How much of that was the campaign, and how
much was the seasonal spike?"

You can't answer — because you didn't run a
control group or a holdout.

The number is real. The defence is not.

Causality needs evidence, not correlation.

SECTION 03Real examples — numbers that fall apart

The same dashboard number can be a strong defence or a weak one. The difference is the thinking behind it.

SECTION 04How to build a defence

You do not need a new dashboard to defend a number. You need to change how you work — and how you talk about your work.

• Know the attribution model — and its limits.
• Run holdouts or control groups — where you can.
• Write down the decision — what you changed and why.
• Tie every metric to a business outcome — revenue, pipeline, margin.
• Have a "what I would do next" line — defence is forward-looking.

SECTION 05How to talk about it in the room

A defensible number is only half the job. The other half is talking about it so the room trusts it. Here is the structure that works.

Weak Answer:
"ROAS is 3.2 this quarter."

Manager: "Why did it drop from 3.8?"
You: "The market changed, I think."

Manager: "What did you do about it?"
You: "Not much yet."

The conversation ends. Trust drops.

Strong Answer:
"ROAS dropped from 3.8 to 3.2 this quarter.
The main driver was a 22% rise in CPC on
brand terms — two competitors entered the
auction.

I tested a bid cap and a new landing page.
The bid cap recovered 0.3 ROAS in two weeks;
the landing page was flat.

If we hold the cap, we expect 3.5 by next
quarter — still below 3.8, but stable."

Manager: "Good. What do you need from me?"
The conversation continues. Trust grows.

SECTION 06Interview Q&A — marketing analytics

SECTION 07Test yourself — number defence quiz

SECTION 08Frequently asked questions

SECTION 09Related reads