The ground shifted under your dashboards
Last session you learned that multi-touch attribution is the only one of the three measurement systems with low privacy resilience - it needs to follow individual people across touches. This session is the story of what happened when the industry took that ability away. Between Apple's tracking prompts, the postback systems that replaced device IDs, and browsers blocking third-party cookies, the user-level data MTA depends on has been gutted. The uncomfortable part: many teams still trust their MTA numbers, and still repeat a headline that makes them feel safe. A leader in 2026 needs to know exactly what broke, so you can stop over-trusting a report built on data that is no longer there. Six sessions, one real brand, zero code.
Three forces converging on a cracking funnel 6 min live
MTA did not break for one reason. Three separate forces - each large on its own - all landed on the same dependency: the ability to follow one person's touches from ad to purchase. Together they knock 30 to 60% of the touchpoints out of your user-level reporting.
LiveForce 1 - Apple's App Tracking Transparency (ATT)2 min▶
Since ATT, iOS apps must show a prompt asking permission to track the user across other companies' apps and sites. Globally, opt-in rates have run as low as around 14%. For the ~86% who decline, the IDFA - the device advertising identifier that let you stitch a person's app touches together - is effectively gone. The practical result: advertisers lose an estimated 40 to 60% of iOS conversion visibility. For a DTC skincare brand like Lumen, whose buyers skew mobile and iPhone-heavy, that is not an edge case - that is the majority of the audience going dark to user-level tracking.
A mobile-first brand watched its "attributed" iOS conversions fall off a cliff the quarter ATT enforcement tightened - not because sales dropped, but because the ability to see which ad touched those buyers vanished. The revenue was real; the attribution was blind. Teams that did not understand ATT panicked and cut the channels that had simply gone invisible.
LiveForce 2 - SKAdNetwork became AdAttributionKit (AAK)2 min▶
Apple's answer to "how do you measure ads without tracking people" was SKAdNetwork, and in iOS 18.4 it replaced that with AdAttributionKit (AAK). The important thing for a leader is not the acronym - it is the shape of what these systems return. Instead of a clean, immediate, user-level record of "this person saw this ad and bought", AAK sends back postbacks that are delayed by hours or days, coarse-grained (bucketed, not exact), and deliberately noised for privacy. That design is fundamentally incompatible with the user-level dashboards MTA was built on. You cannot rebuild an individual journey from data that is intentionally aggregated, late, and fuzzy.
So even the "privacy-preserving measurement" Apple offers as a replacement does not restore MTA. It gives you enough to optimize campaigns in aggregate, not to trace one customer's path - which is exactly what multi-touch attribution requires.
LiveForce 3 - third-party cookies were already gutted2 min▶
Long before any of this, Safari and Firefox began blocking third-party cookies by default around 2020. Between them, plus widespread ad-blockers, a large share of web traffic was already invisible to cross-site tracking years ago. Third-party cookies are the web equivalent of the IDFA - the thing that let you follow a person from an ad on one site to a purchase on yours. On the two browsers that block them by default, that link was already broken well before 2026. This matters enormously for the myth we are about to bust, because it means the fate of cookies in Chrome specifically was never the whole story.
The myth: "cookies survived, so we're fine" 5 min live
Here is the headline that is quietly giving teams false confidence in 2026, and why it is wrong. Google did not follow through on fully removing third-party cookies from Chrome - but that reprieve did not save multi-touch attribution.
LiveWhy the reprieve does not rescue MTA3 min▶
Follow the logic slowly, because this is the exact reasoning that lets you correct a confident colleague without a slide deck:
- Chrome cookies surviving fixes one surface. It restores cross-site tracking on Chrome web traffic - and nothing else.
- The other surfaces were already dark. Safari and Firefox block cookies by default; iOS non-consenters have no IDFA; in-app measurement runs on delayed, coarse postbacks. None of those depend on Chrome's decision.
- Add it up and coverage is still broken. Across a real audience, a third to two-thirds of touches are missing from user-level view. A dashboard that only cleanly sees Chrome-web users is not measuring your business - it is measuring a shrinking, non-random slice of it.
A marketing team celebrated the Chrome news and renewed their user-level attribution vendor for another year, convinced the crisis had passed. Their reporting still silently excluded the majority of their iOS and Safari buyers - so it kept over-crediting the channels those users happened to be trackable through, and the budget kept drifting toward a distorted picture. The reprieve did not save them; it just delayed the reckoning.
Why MMM and incrementality came back 5 min live
When user-level tracking broke, the industry did not invent something new - it dusted off the two methods that never needed to track individuals in the first place. MMM uses aggregate data, so it is largely immune to all of this, and incrementality measures aggregate geo outcomes, so it is immune too. The past decade leaned MTA-heavy; the future leans MMM-plus-lift.
LiveWhat to demand from your measurement team3 min▶
You do not need to build any of this. You need to steer it. Three demands a leader should make in 2026:
- Stop treating MTA as ground truth. Keep it for tactical, within-channel steering, but demote it from "the number we set budgets on". Its coverage is structurally broken and will not recover.
- Stand up MMM as the strategic anchor. Because it uses aggregate data, it survives everything that broke MTA - and four credible open-source toolkits (Google Meridian, Meta Robyn, PyMC-Marketing, and one more) are now free, so cost is no longer the excuse it once was.
- Fund incrementality tests to keep it honest. The only causal check you have. Budget for a few geo-lift experiments a year to calibrate the MMM.
Self-studyIdentity resolution - the patch layer, honestly2 min read▶
Your team will propose patches, and some are worth doing - just know what they are and are not. First-party data (your own logged-in customer relationships) restores signal for people who identify themselves to you. Data clean rooms let you match aggregated audiences with a platform without either side exposing raw user data. Server-side tracking moves collection to your own servers to survive some browser blocking. Consent-mode modeling statistically fills gaps for users who declined tracking. Each recovers a little coverage. None of them rebuilds the full cross-site, cross-app journey MTA assumed - that world is gone. Treat identity resolution as a way to sharpen your first-party view, not as a rescue for multi-touch attribution.
Audit your own exposure ★ 10 min · everyone
Before you can fix a measurement problem you have to size it. Estimate how much of your reporting depends on the user-level tracking that broke - using Lumen as the worked example, then your own brand.
Estimate your iOS + Safari share. For a DTC skincare brand like Lumen, mobile-heavy and iPhone-skewing, this is likely the majority of buyers - and much of it is dark to user-level tracking thanks to ATT and Safari's default blocking.
Ask which reports feed on user-level data. Any dashboard that shows individual conversion paths, retargeting attribution, or "assisted conversions" is drinking from the broken well. Flag each one.
Put a number on it. If roughly 30 to 60% of touches are missing, then a report claiming precise per-channel credit is, at best, describing a non-random minority of your customers. Say that number out loud - it reframes every meeting.
Write the exposure sentence: "Roughly half our audience is invisible to the user-level tracking our main attribution report depends on, so I will not set the annual budget on that report alone."
Write the three vendor questions ★ 10 min · pen and paper
Every measurement vendor in 2026 will tell you they have "solved" the privacy break. Your job is to test that claim in three questions. Draft them now - you will use them at your next renewal.
Question one - the coverage question. "What percentage of our conversions can you actually observe at the user level, and how do you handle the rest - modeled, estimated, or simply dropped?" A vendor who claims near-total coverage in 2026 is either misleading you or heavily modeling.
Question two - the aggregate question. "Do you offer aggregate, privacy-durable measurement - MMM and incrementality - or only user-level attribution?" If they only sell MTA, they are selling you the method that broke.
Question three - the causal question. "How do you validate your attribution against a causal experiment - can you calibrate to a geo-lift test?" A vendor whose numbers have never been checked against a holdout is selling correlation with confidence.
Write all three on one card. Bring it to the next vendor call. Watch how fast the conversation gets honest.
The vendors who thrive in 2026 answer these three questions cleanly - they tell you their real observable coverage, they offer aggregate methods, and they calibrate to experiments. The ones who dodge, deflect, or bury you in jargon about "advanced identity graphs" are usually patching MTA and hoping you do not ask. The three questions are a lie detector.
This week ◐ 25 min total
- Size your blind spot. Estimate the share of your customers on iOS and Safari, and confirm with your team roughly how much of your main attribution report is measured versus modeled.
- Correct the myth once. The next time someone says "Google kept cookies, so we're fine", walk them through why the other surfaces were already dark. Teaching it is how you own it.
- Ask about MMM readiness. Find out whether your team has ever built or bought an MMM, and whether they know the free toolkits (Meridian, Robyn, PyMC-Marketing) exist. Cost is no longer the blocker.
- Optional: skim Meta Blueprint's free measurement path or one 2026 industry write-up on the cookieless shift - just enough to hear the same three forces described in the vendors' own words.
Three questions before you go 🎯 ◐ 90 seconds
1 · What did Apple's ATT and the SKAdNetwork-to-AdAttributionKit shift do to iOS measurement?
With opt-in near 14%, the IDFA is gone for most users, and AAK deliberately returns aggregated, delayed, privacy-noised data - none of which supports the user-level journeys MTA needs.
2 · A colleague says "Google cancelled cookie deprecation, so our MTA is fine." The correct response is...
Chrome's reprieve restores only Chrome-web tracking. The other surfaces were dark before 2026, so MTA coverage is still structurally broken regardless of what Chrome does.
3 · Why did MMM resurge as the privacy-durable anchor?
MMM models channels in aggregate, so it is largely immune to ATT, SKAN/AAK, and cookie loss. Free toolkits (Meridian, Robyn, PyMC-Marketing, and one more) removed the old cost barrier.
What this session covers
This session distills the 2026 privacy-and-measurement reality - the part no pre-2024 course teaches well - into a leader-first framing. Certificates and full video courses stay with their official sources.