How to answer the objection you cannot answer: Sometimes the sceptic is right and your data cannot settle the question. Three responses that keep your credibility, and the one that ends it.
Read the full article below for detailed insights and actionable strategies.
Customer journey
The customer journey last-click attribution misses
One conversion. Five touchpoints. Last-click credits the final touch with 100%.
Last-click attribution
Every other channel gets zero credit, even though they created the demand.
Causal inference
Occasionally a sceptic raises something your data genuinely cannot settle, and how you respond in that moment decides whether anything you said before is believed. Three responses work. One does not.
The three that work
| Response | When to use it |
|---|---|
| "That is outside what this design can resolve" | The objection is about a mechanism the method cannot see |
| "Here is the test that would settle it" | The objection is empirical and testable |
| "You may be right, and here is what I would expect if you were" | The objection is plausible and you disagree |
The third is the strongest and the least used. Stating what you would expect to observe if the sceptic were correct turns a disagreement into a shared prediction, and shared predictions get checked.
The one that does not work
Answering a question you were not asked. Responding to "how do we know this is not just seasonality" with an explanation of the modelling approach reads as evasion, whether or not it is meant that way. If you do not have the answer, say the words.
The three objections that are usually correct
Seasonality, when the window spans a period with a known pattern and you have not adjusted for it. Say so and re-run on a comparable period.
A structural change the model cannot see: a competitor exiting, a pricing change, a supply problem. An aggregate method has no visibility of any of these, and the person raising it usually has direct knowledge. Concede it and note it as a limitation on that channel.
Creative and auction dynamics. A causal read on channel-level data cannot distinguish a channel that stopped working from creative that stopped working. That is a real boundary and it is worth stating before it is raised.
What to do with a testable objection
Convert it. "We can settle that by holding this channel dark in half our regions for four weeks" is a much better meeting outcome than winning the argument. The design is in the geo testing guide and the sizing questions in how to measure incremental lift.
Agreeing the test in the room also fixes the threshold in advance, which is what stops the result being relitigated later.
Why conceding does not weaken you
Because the alternative is defending a claim past what the evidence supports, and everyone in the room can see when that is happening. A report that names its own limits and then survives the parts it did claim is more persuasive at the end of the meeting than one that claimed everything and was chipped at throughout.
Our own output carries that shape deliberately: an estimate, its confidence interval, the coverage share, and an explicit observational design label, from a Google Analytics export at €99 for a first read, refundable if it does not move a budget decision. Channels it cannot measure are named rather than scored.
The interactive demo shows the same fields on a sample store with no signup, which is a low-stakes way to let a sceptic examine the format first.
The phrase worth having ready
"This design cannot resolve that. Here is what would." It is short, it is honest, and it ends the exchange in a better place than any defence.
Related answers
Get attribution insights in your inbox
One email per week. No spam. Unsubscribe anytime.
Key Terms in This Article
Analytics
Analytics is the systematic computational analysis of data. It reveals customer behavior and measures campaign performance.
Attribution
Attribution identifies user actions that contribute to a desired outcome and assigns value to each. It reveals which marketing touchpoints drive conversions.
Attribution Debt
Attribution debt is the gap between what your ad platforms claim drove revenue and what actually caused it, carried quarter after quarter into the budget. It is how marketing debt accrues: allocate on claimed conversions long enough and the plan itself becomes the liability.
Causality
Causality is the relationship where one event directly causes another, essential for identifying specific actions that drive desired outcomes in marketing.
Confidence Interval
Confidence Interval is a statistical range of values that likely contains the true value of a metric. In marketing analytics, it quantifies uncertainty around estimates, indicating the precision of an outcome or causal effect.
Google Analytics
Google Analytics is a web analytics service that tracks and reports website traffic.
Holdout Test
A holdout test is an experiment where a portion of the audience does not see a campaign. This measures the campaign's true incremental impact.
Related Articles
Sixty-second versions of these ideas: Causality Engine on YouTube Shorts.
Ready to see your real numbers?
Own the budget? Upload your GA4 export and see which channels drive incremental sales, with confidence intervals, in minutes. Have to defend it? Start with the live demo and take the read to your CFO.
Full refund if you don't see value.
Stay ahead of the attribution curve
Weekly insights on marketing attribution, incrementality testing, and data-driven growth. Written for the person who owns the budget and the person who has to defend it.
No spam. Unsubscribe anytime. We respect your data.