From a pile of models to a system
Nine sessions gave you nine ways to answer "what worked?" - and they disagree, on purpose. The mistake is to pick a winner. The 2026 answer is to orchestrate them: each method is good at a different question and a different cadence, and you wire them into a loop where the causal method calibrates the correlational one and the fast method steers the day-to-day. No single tool is the truth. The system is.
The calibrated loop: MMM + incrementality + DDA 6 min live
Three methods, three roles, wired in a cycle. MMM sets the strategic budget. Incrementality experiments give MMM its causal calibration. Data-driven attribution steers the daily tactical moves inside that budget. Each feeds the next - and the feedback arrows are the whole point.
LiveEach method's job, cadence, and question3 min▶
| Method | Answers | Cadence |
|---|---|---|
| MMM (strategic) | How should we split the whole budget across channels? | Quarterly / annual |
| Incrementality (causal) | Does this channel actually cause sales, and by how much? | A few big tests a year |
| DDA / MTA (tactical) | Which campaigns and creatives to shift this week? | Daily / weekly |
The failure mode is using one for another's job - a daily MTA number to set the annual budget, or a slow MMM to pause a campaign today. Match the method to the decision's stakes and speed.
The 2026 stack, wired on Lumen 6 min live
The loop becomes a pipeline: raw events land in the warehouse, three method families read from the same governed tables, and their outputs converge on one set of decisions. And it all sits inside the 2026 privacy reality - which is exactly why MMM and lift resurged.
LiveThe 2026 privacy reality this sits inside3 min▶
Why this shape and not a single MTA dashboard? Because of what broke:
- Cookies partly survived Chrome's long deprecation saga - but MTA broke anyway. Safari and Firefox block third-party cookies, Apple's ATT gutted mobile signal, and SKAN / AAK aggregation strips user-level detail. MTA now misses an estimated 30 to 60% of touches.
- MMM and lift resurged precisely because they run on aggregate and experimental data - which no browser update or OS privacy change can revoke. Privacy-proof by construction.
- So MTA is demoted, not deleted: it is a tactical signal on the consented slice you can still see, kept honest by MMM and lift. That is the whole reason the stack is a loop and not a single tool.
The lazy 2026 take is "cookies came back, so MTA is fine again." It is wrong: cookies were never the only thing that broke MTA. Safari, Firefox and ATT never used third-party cookies to begin with, and their walls are still up. Any stack betting on MTA alone is measuring a shrinking, biased half of reality.
The eleven-pitfall checklist + ethics 6 min live
Every pitfall below has sunk a real attribution program. Read them as a pre-flight checklist - if your stack does any of these, fix it before you trust a number.
| Pitfall | The fix |
|---|---|
| 1 · Calling heuristics "data-driven" | Heuristics are fixed rules. Reserve "data-driven" for Markov / Shapley / DDA that learn credit from the data. |
| 2 · Last-touch as default truth | It is a tactical read that over-credits demand-capture. Never set a budget on it alone. |
| 3 · Treating correlation as causation | Only experiments are causal. Label MTA / Markov / Shapley / MMM as correlational everywhere they are reported. |
| 4 · Not normalizing Markov removal effects | Removal effects do not sum to 1 - always normalize before you split revenue, or credit leaks. |
| 5 · Exact Shapley at O(2^n) cost | For many channels use Monte-Carlo Shapley; exact coalitions explode past ~15 channels. |
| 6 · Attribution windows silently changing results | Fix and document the lookback window. A 7-day vs 30-day window can flip which channel "wins". |
| 7 · Missing-touchpoint bias (2026) | MTA misses 30-60% of touches. Do not report it as complete - triangulate with MMM and lift. |
| 8 · Double-counting across tools | GA4, the ad platforms and MMM all claim the same conversion. Reconcile to one governed number. |
| 9 · Ignoring view-through vs click-through | An impression is not a click. Keep them separate or you inflate awareness channels. |
| 10 · MMM without incrementality calibration | An uncalibrated MMM is a confident correlation. Anchor it with lift-test priors (Session 9). |
| 11 · Overfitting deep models on sparse data | LSTM / attention MTA needs volume. On thin data a simpler model generalizes better - do not chase the fancy one. |
LiveThe ethics layer you own as the builder3 min▶
Three responsibilities that are not optional in 2026:
- Privacy and consent. Model on data you have the right to use. Aggregate and experimental methods (MMM, lift) are not just privacy-resilient - they are the privacy-respectful default.
- Honesty about incomplete data. When MTA sees half the touches, reporting its number with false confidence is a form of lying. Carry the uncertainty forward - intervals, not just points.
- Transparency to stakeholders. Tell the CMO which model produced a number, what it over-credits, and how sure you are. The builder who names the model's limits earns more trust than the one who hides them.
Assemble Lumen's measurement plan ★ 7 min · map it
Turn the loop into an actual plan: for each business question Lumen's CMO asks, which method answers it, and on what cadence? Encode it so it is a living config, not a slide.
Question first, tool second. The plan is organized by the CMO's questions, not by your models. That is what makes it a plan and not a tech inventory.
Cadence is a first-class field. Daily tactics and quarterly strategy run on different clocks. Writing the cadence down stops anyone using a weekly number for an annual decision.
Every row carries its caveat. The caveat column is the honesty layer - it travels with the number so no one forgets what the method cannot say.
The best measurement teams pin a version of this table to the wall. When a stakeholder asks "what's our ROAS?" the answer is "which decision are you making?" - and the table routes them to the right method. That reframe alone prevents most attribution arguments.
The reconciliation dashboard ★ 8 min · run it
Put the three methods side by side for each channel. Where they agree, you have confidence. Where they diverge, you have your next investigation - or your next lift test.
Three columns, one channel per row. The dashboard's job is not to average the methods - it is to surface the disagreement, which is where the learning is.
Where they agree, ship it. When MMM and lift both land near 0.30 for paid social, that is a calibrated, near-causal number - act on it with confidence.
Where they diverge, route it. Paid search high on MTA but low on MMM and lift is the classic last-click bias - the disagreement itself is the finding, and it tells you what to test next.
The pitfalls audit on your own stack ★ 7 min · run it
Turn the eleven pitfalls into a runnable checklist. Score your own stack, and let the failures become your roadmap.
Be honest in the booleans. The audit only works if you mark the pitfalls you are actually committing. Optimistic scoring defeats the purpose.
The open risks are your backlog. Each True is a concrete engineering or process fix - documenting a window, adding a lift test, reconciling double-counts.
Re-run it quarterly. Stack health is not a one-time score. As you close risks and add methods, the audit tracks whether your system is getting more defensible or just more complex.
Most real 2026 stacks score somewhere around 50-60% on first audit - and the two risks that hurt most are almost always "MMM not lift-calibrated" and "correlation reported as causal." Fix those two and you have leapfrogged the majority of marketing measurement programs.
Ship it ◐ 60 min total
- Write your own measurement plan. Take Build-along 1 and replace Lumen's questions with your organization's real ones. One page, question-first, cadence and caveat on every row.
- Build a real reconciliation view. Even with two methods (say GA4 DDA + a simple MMM), stand up the agreement dashboard from Build-along 2 for your top five channels.
- Run the audit for real. Score your actual stack against the eleven pitfalls. Turn the open risks into a prioritized backlog - fix "not lift-calibrated" and "reported as causal" first.
- Optional capstone: assemble everything from B1-B10 into a single notebook - SQL journeys → heuristics → Markov/Shapley → MMM → geo-lift → reconciliation - as your portfolio proof you can build the whole loop.
Three questions before you go 🎯 ◐ 90 seconds
1 · The unified 2026 stack is best described as...
No single tool is the truth. MMM sets the budget, lift tests calibrate it causally, and modeled attribution steers tactics - each feeding the next in a loop. The disagreement between them is a feature, not a bug.
2 · In this whole stack, which methods are causal?
MTA, Markov, Shapley and MMM all describe correlation. Only incrementality experiments withhold a channel and measure the delta, which is why lift is the causal anchor the rest of the stack gets calibrated against.
3 · Name a top pitfall that breaks real attribution stacks.
Markov removal effects do not sum to 1 - skip the normalization and credit leaks. And GA4, the ad platforms and MMM will each claim the same sale unless you reconcile to one governed number. Both are on the eleven-pitfall checklist.
What this session covers
This capstone synthesizes the entire builder track - every method from B1 to B9 - into one orchestrated, auditable stack. It is the integration layer no single course teaches, drawn from the whole source universe of this program.