A complete sample chapter — a representative example at the same depth as the other 15. Get the complete map →

I — Data, Measurement & Analytics

TL;DR

• What it is: the measurement ruler the rest of the map spends against — how a brand knows what worked, decides what's true, and decides where to spend next under accelerating signal loss. I owns measurement methodology; every other domain owns the thing it measures and consumes I's ruler.
• The organizer: not the funnel and not a tidy decision tree, but basis-of-truth × signal-integrity — a causal-certainty ladder (last-click → MTA/DDA → MMM → incrementality) run against a signal-loss gradient. The practitioner's real agony: do I trust the dashboard, the model, or the holdout?
• The 2026 shift: the identity layer keeps eroding (Privacy Sandbox fully retired Oct 2025, ATT, consent attrition), so the field has pivoted off touchpoint tracking and back onto modeled and experimental methods — MMM is in a genuine renaissance and incrementality is the apex arbiter.
• The non-negotiable: incrementality is the arbiter. No platform-reported ROAS, no server-side-recovered conversion, and no platform-modeled conversion enters as fact. This rule rests on the peer-reviewed economics literature (Lewis-Rao, Gordon et al., Ghost Ads), NOT vendor decks.
• Don't: trust a platform grading its own homework, confuse recovered signal with incremental signal, read GA4's "AI Assistant" number as your AI share (it undercounts by an order of magnitude), or quote a vendor lift band as a point estimate.

The organizer — basis-of-truth × signal-integrity (the module's spine)

Organize the work by how confident you can be that X caused Y, given how much identity-level signal survived. That is a graded property, not a clean either/or decision — and it is worth saying plainly that I is the map's leading honest exception to the "every domain has one sharp decision axis" rule. The locked map records this: I (with K) is evidence the decision-axis rule bends for methodology/infrastructure domains, which organize by a graded property rather than a single agonized choice. The only true market-action decision ("given measured incrementality, where do I spend?") lives downstream in F. I owns the ruler, not the spending move.

The ladder, ordered by strength-of-causal-claim: - Correlational — last-click → rules-based MTA → data-driven attribution (DDA). Cheap, high coverage, weak causal claim; over-credits digital. - Modeled — marketing-mix modeling (MMM). Privacy-durable, regression-based, needs experiment calibration to be valid. - Experimental — incrementality / geo-lift / RCT. Strongest causal claim, expensive, often statistically underpowered at realistic budgets.

Run against the signal-loss gradient: identity-resolved at one pole (deterministic logins, hashed PII, first-party data), modeled/aggregate at the other (where the touchpoint data has simply disappeared). Every 2026 development — server-side recovery, the MMM revival, dark agent traffic, the Privacy Sandbox's death — is a response to signal loss, which is why this is the spine.

The funnel does not organize I — and this is the strongest anti-funnel evidence in the whole map. I measures funnels (acquisition → activation → retention → revenue; CAC/LTV are lifecycle-shaped), so the funnel is an object I reports on, never how I is built. More pointedly: MMM and incrementality deliberately abandon the touchpoint-sequence view because, under signal loss, the data to populate a funnel disappeared. I is where you watch the funnel die for a concrete, grounded reason.

Decision logic (ADVISE) — what's the ruler, and how much should I trust it?

• Match the method to the decision (the triangulated stack — the 2026 consensus). No single method is trusted alone:
• Daily in-channel optimization on a validated channel → MTA/DDA. Cheap, high coverage, weak causal claim. Use it to steer, not to adjudicate.
• Quarterly/annual cross-channel + offline allocation → MMM. Privacy-durable and modeled — but a badly-specified MMM is confidently wrong (multicollinearity, identifiability). Calibration-with-experiments is what makes it trustworthy, and it's the expensive part the "MMM-on-a-laptop" story papers over.
• "Should I scale spend on this channel?" → incrementality / geo-lift. Strongest causal claim — but frequently statistically unmeasurable at realistic budgets (Lewis-Rao: median 95% CI on ad ROI exceeds 100 percentage points; an informative experiment can need >10M person-weeks). Incrementality breaks ties.
• Treat recovery ≠ lift. Server-side/CAPI recovers signal completeness (~15-40%, match rate ~85-90%), not incremental performance. A recovered or modeled conversion is a measured conversion, never an incremental one. Wall it off from F's spend decision — the arbiter rule extends to recovered AND modeled numbers.
• Build vs buy vs model the measurement stack (the one genuine decision axis here). DIY GA4 → managed BI → warehouse-native + an analytics-engineering team → causal/MMM. The decision is gated by warehouse maturity, data-quality discipline, and whether you can run and calibrate experiments (the expensive part). This axis predicts cost, headcount, latency, and trust — and it coexists with the causal-certainty gradient rather than replacing it.
• Audience deltas drive the ruler: B2B → dark-funnel + self-reported; DTC → MER/blended + post-purchase survey; B2C/brand → MMM + brand-lift; retail-media → IAB commerce-media incrementality standards; any offline spend → matched-market / MMM.
• Agent pole — instrument it, but temper the flip. Use the 3-number disclosure + server-side + verified-agent signature; but recognize the denominator is currently unknowable (~70% of AI traffic arrives referrerless). The leading re-test trigger cannot yet fire cleanly — itself a finding. Don't flip to agent-primary on a number you can't actually measure.

Operating capability (RUN)

The instrument (I-A) — the execution substrate. The real layer isn't GA4, it's the data pipeline: ELT (extract → load to a warehouse: BigQuery/Snowflake/Databricks/Redshift) → transform with dbt + identity resolution + data-quality tests → reverse-ETL activation (push audiences back to CRM/ad platforms). Define each metric once in a semantic layer (dbt Semantic Layer) so "CAC" and "qualified lead" don't silently disagree tool-to-tool. The analytics engineer owns this seam — not the marketer. Stack (categories): web/product analytics, warehouses, ELT + reverse-ETL, semantic layer, data observability. Named current tools → ledger. Mostly automated pipeline + human governance; AI earns its keep first as anomaly detection ("is the tracking even working").

The ruler (I-B) — MMM + experiments. MMM now runs on a laptop (Bayesian MCMC in minutes on a cloud GPU), but the load-bearing work is calibration with geo-experiments and guarding against identifiability/multicollinearity. Largely human-statistician + automated re-runs.

Recovery / identity (I-C) — the signal-recovery layer. Server-side GTM + CAPI/Enhanced Conversions (now ~one-click) → CMP + Consent-Mode-v2 wiring → CDP (build/buy/composable per warehouse maturity) → identity resolution (deterministic vs probabilistic; match rate as the operating KPI) → clean-room queries. Increasingly automated setup, human governance. This is also where zero-party/first-party data becomes "data quality = AI output quality," not just privacy compliance.

Unit economics (I-D) — the shared output language. CAC, LTV, LTV:CAC, payback, MER, blended ROAS, contribution margin — used as audience-divergent bands, not points.

The agent pole (I-AT1). Server logs + GA4 Measurement Protocol + Web-Bot-Auth signature capture + the 3-number disclosure (below). A data/log-engineering workflow, not a content one.

The agent angle (human↔agent)

The human side of I is a mature ruler. The agent pole is the frontier where the ruler breaks — and that breakage is the honest headline, not a footnote.

• The referrerless problem. As of Jun 2026 (ledger), ~70.6% of AI traffic arrives referrerless (446k-visit dataset) and lands misclassified as "Direct" — LLM interfaces strip referrer headers. Conductor (Nov 2025): 89% of brands cannot properly attribute AI referral traffic. The structural finding: there is no clean denominator for AI-referred share with current instrumentation.
• GA4's AI Assistant channel is a floor, not truth. GA4 launched a native "AI Assistant" channel ~2026-05-13 (broad ~Jun 2026; medium=ai-assistant; ledger). But Perplexity routes to Referral, AI Overviews/AI Mode route to Organic, the ~70% referrerless still routes to Direct, and history isn't reclassified. Anyone reading GA4's AI number as "our AI share" under-reads by an order of magnitude.
• The 3-number disclosure is a genuine cross-practitioner norm: (1) referrer-attributed AI + (2) estimated-Direct-that-is-actually-AI + (3) AI-Overview/AI-Mode exposure that never appears in any referrer. Report all three; don't pretend one number serves.
• Agent conversion is visible only at the cart (server-side/webhook, first signal at checkout). The unit of measurement shifts from "did a human convert" to "did an agent select/transact."

Boundary: L single-homes the agent-identity primitive (Web Bot Auth / KYA, L4) and owns agent transaction measurement (L8). I owns pre-transaction agent-traffic/conversion measurement methodology (I-AT1) and builds the general ruler. Verification of an agent's identity rides on L4's signature; I takes a pointer. E owns AI-visibility/citation/share-of-model measurement (E2); E2/E3 take a pointer into I-AT1 for the referrerless plumbing.

The agent-transaction-share re-test metric is jointly owned: I instruments and defines it, L and the focus-frame consume it.

Audience deltas

• B2B: the dark funnel + self-reported attribution is the dominant reality — 70-80% of the B2B journey is in untrackable dark-social, and the "how did you hear about us?" free-text field surfaces 30-50% of pipeline that digital attribution misses. Account-level (not user-level) measurement; MQL→SQL→pipeline; multi-buyer-committee; long-cycle/lagged-conversion modeling.
• B2C / brand: MMM + brand-lift / brand-equity measurement (survey brand tracking, attention metrics) as the dominant ruler — the B-thread's measurement application (B owns brand strategy; I owns brand-lift measurement).
• DTC / ecommerce: short-cycle, same-session, platform-ROAS-skeptic pole (MER, blended ROAS, server-side, payback by vertical); the post-purchase survey ("how did you hear" at checkout) is the DTC analog of B2B self-reported attribution.
• Retail-media / commerce-media (RMN): new-to-brand, in-store attribution, RMN clean rooms. F owns RMN spend; I owns RMN measurement methodology — anchored by the IAB / IAB Europe Commerce Media Measurement Standards V2 + Incremental Measurement Guidelines, the cleanest independent standards-body codification of "incrementality is the arbiter."
• B2A / A2A (agent): the I-AT1 frontier — referrerless, spoofable UAs, dark AI-Mode exposure, conversion-visible-only-at-cart. I owns the measurement methodology; L single-homes the identity primitive.

Edges & hand-offs

• I ↔ F (paid): I builds the ruler (attribution models, MMM, incrementality methodology, identity, clean rooms); F decides spend against it. Platform ROAS lives in F as a claim; I owns the holdout that adjudicates it. Server-side/CAPI implementation is shared — I owns whether the recovered signal is trusted (the incrementality gate); F owns pixel-vs-CAPI as campaign ops. Watch that "EMQ optimization" doesn't migrate into F as a performance lever divorced from the trust question.
• I ↔ H (lifecycle/CRM): the CDP is the canonical shared object — identity resolution + data governance + measurement-input methodology = I; segmentation strategy + lifecycle activation/journeys = H. Same split for predictive analytics (model-validation methodology = I; churn/propensity/NBA application = H) and unit economics (CAC/LTV measurement methodology = I; the programs those metrics evaluate = H).
• I ↔ E (search/discovery): I owns general attribution infra + the referrerless/UA mechanics of agent-traffic measurement (I-AT1); E owns AI-visibility/citation/share-of-model measurement (E2) as its domain KPI.
• I ↔ G (earned/PR): G's EMV ban routes here — I provides the metric of record (incrementality/MMM/self-reported attribution) that replaces EMV; G owns the earned-media practice and AMEC framing.
• I ↔ L (agent commerce): L single-homes the agent-identity primitive (Web Bot Auth/KYA, L4) and owns agent transaction measurement (L8); I owns pre-transaction agent-traffic measurement methodology (I-AT1) + the general ruler. The agent-transaction-share re-test metric is jointly owned.
• I ↔ K (privacy/compliance): K owns the legal rule (GDPR/ePrivacy/CPRA, ATT-as-policy + the German antitrust case, AI-Act data governance); I owns the measurement consequence (consent rates, Consent-Mode wiring, modeled conversions, signal loss). Cross-link, not single-home.
• I ↔ D (owned/web/CRO): D owns on-site CRO test execution; I owns experimentation methodology (power/stats, geo-incrementality). Same tool on the seam: methodology→I, execution→D.
• I ↔ J (martech/ops): the martech stack is J's; the measurement data pipeline (ELT → warehouse → dbt → reverse-ETL) + the semantic layer + the data-quality discipline are I's (I-DE). AgentOps→J; agent-traffic measurement methodology→I.
• I ↔ A (strategy/budget): A owns budget strategy and the KPI/north-star choice; I owns the measurement of unit economics. A SETS, I MEASURES.
• I ↔ B (brand): B owns brand strategy; I owns brand-equity / brand-lift measurement.
• I ↔ N (VETO): I owns the incrementality ruler and vetoes the two most double-count-prone numbers in the map — affiliate "influenced sales" and B2B "partner-influenced revenue."
• I ↔ M / I ↔ O: M7 enablement measurement and O8 event ROI (pipeline-influenced vs sourced) consume I's ruler; the enablement/event capture metrics stay home in M/O.

Measurement

This is the measurement domain, so the discipline is the deliverable: - Incrementality is the arbiter — and its evidence base is academic, not vendor. The mechanism rests on the peer-reviewed economics literature: Lewis & Rao (QJE 2015) — 25 large field experiments showing ad-ROI confidence intervals routinely exceed 100pp; Gordon, Zettelmeyer et al. (Marketing Science 2019) — observational/attribution methods systematically diverge from RCT ground truth, usually overstating; Ghost Ads (Johnson, Lewis & Nubbemeyer, JMR 2017) — platform/observational effects are overstated, with branded search + retargeting worst (they harvest in-market demand). Pair any metric with a business outcome. - Three things not to trust as fact: 1. Platform-reported ROAS/CPA — the platform grading its own homework. Vendor over-attribution bands (platforms over-credit ~20-60%; branded search/retargeting 5-10× inflated) hold as direction, never as a point estimate — they're book-of-business artifacts. 2. Server-side-recovered conversions — measures signal completeness, not lift. 3. Platform-modeled conversions — structurally unavailable to exactly the low-consent/small accounts that need them most (Consent-Mode-v2 thresholds), and the platform marking its own homework. - Geo-test design norms (heuristics, not law): 4-8 weeks minimum; ≥5-8 markets per arm (2-market tests are underpowered); ≥~200 conversions in control; the real cost is the opportunity cost of withholding spend in control markets. Carry the Lewis-Rao warning: most "significant" tests are over-powered survivors or under-powered noise. - Agent pole: the 3-number disclosure + server-side conversion capture + verified-agent signatures — but report the unknowable denominator honestly.

Compliance & risk gate

• K owns the rule; I owns the measurement consequence. The legal objects (GDPR/ePrivacy, US state patchwork, ATT-as-policy, AI-Act data-governance, DPAs, data residency) live in K. I owns what they do to the ruler: consent rates, Consent-Mode wiring, modeled-conversion gaps, signal loss.
• Consent is now a hard performance dependency. As of Jun 2026 (ledger): Google Consent Mode v2 is a hard requirement for GA4→Google-Ads conversion data in EEA/UK; no consent → no remarketing-list population + conversion-modeling disabled; modeling needs ≥700 ad clicks/7d/country and degrades below ~20% consent. In one documented Consent-Mode-v2 misconfiguration, only ~40% of lost conversions were recovered by modeling — the rest permanently lost.
• The data-governance-for-AI risk. Feeding marketing data into RAG/vector pipelines creates DLP blindness on embeddings — a real, under-grounded risk (mostly vendor/dev-blog sourcing today; flagged as an open item).
• Substantiation: an incrementality "win" surfaced as a public lift claim is an FTC substantiation object — keep it defensible.

Pitfalls & vendor-hype to avoid

The defining weakness of this domain is near-universal measurement-vendor self-interest — incrementality vendors sell skepticism-of-platforms, CMP vendors sell consent anxiety, server-side vendors sell recovery percentages, agent-traffic vendors sell dashboards. Discount all of them. - The arbiter rule was itself nearly captured. Across the seed and four sub-passes, "incrementality is the arbiter" was sourced almost entirely from incrementality vendors — the exact self-interest failure this project exists to prevent. It is now re-anchored to Lewis-Rao / Gordon et al. / Ghost Ads. Lean on the academic lit and the IAB standards, not vendor case studies. - "95-99% CAPI success" is a conflation. That's an event-transmission metric, not a match rate; credible e-commerce match rates are ~85-90%. And a matched conversion is a measured one, not an incremental one. - Vendor iROAS/lift magnitudes are book-of-business artifacts (e.g. "median iROAS 2.31×, n=225"). The direction triangulates with the academic anchor; the magnitudes are not load-bearing as point estimates. - MMM tools carry their maker's bias. Meridian flatters Google channels; Robyn flatters Meta. Trust the method/tooling facts; distrust in-tool channel ROI. (Note: Meta has discontinued active Robyn development — it is now legacy/maintenance-mode; the durable open-source pair is Meridian + PyMC-Marketing — verify vs the repo before fully load-bearing, ledger open item.) - Don't read GA4's AI number as your AI share — it's a floor that undercounts by an order of magnitude. - Keep the Salesforce "AI influenced ~20% of orders" number firewalled from any agent-completed metric. It says influenced, not agent-completed — a re-test trigger built on it would fire spuriously. - AI-in-measurement efficacy stats are single-lineage vendor. Anomaly detection ships and is real (highest-adoption entry point); the ">60% of enterprises" adoption and ROI numbers are directional only. Watch the "insight→action gap" — AI generates more insight than orgs operationalize; it needs a human/statistical validation gate.

Current-as-of & re-ground triggers

• Privacy Sandbox fully retired (event 2025-10-17, VP Anthony Chavez): Topics, Protected Audience, Attribution Reporting API, IP Protection and more all retired; only CHIPS, FedCM, Private State Tokens kept; UK CMA released Google from its commitments. Killing Google's own Attribution Reporting API reinforces the shift to MMM + incrementality + server-side. (re-ground 90d.) Flips when: the W3C interoperable browser-attribution replacement matures.
• 3p cookies remain default-on in Chrome — no removal timeline, no user-choice prompt (the Apr-2025 decision holds). Reliability still erodes via Safari/Firefox/Brave default-blocking + ad-blockers + consent rejection. (re-ground 90d.)
• ATT: opt-in ≈ 25% of all users / ≈ 35-46% of prompted users; ≈75% not trackable at IDFA level; SKAdNetwork (SKAN 4) is the aggregate replacement. [Watch — re-opened] German Bundeskartellamt preliminarily found ATT self-preferencing (preliminary assessment 2025-02-13); the proceeding has since escalated — an abuse finding + Apple agreed to revise the prompts (under regulator evaluation since Dec 2025), case ongoing. A €150M figure in circulation likely conflates the separate French Autorité ATT fine (Mar 2025) — unconfirmed for Germany, do not load-bear (ledger 2026-06-22). This is the one thing that makes a "settled" ATT constraint move again. (re-ground 90d.)
• MMM renaissance is real and open-source-driven: Google Meridian (released 2025-01-29) + PyMC-Marketing are the durable pair; Robyn is legacy/maintenance-mode. Meridian GeoX (open-source geo-incrementality feeding MMM as Bayesian priors) announced 2026-05-05, "begins testing later in 2026" — announced/early, not GA. (re-ground 90d.)
• GA4 April-2026 attribution restructure: first-click and remaining rules-based models removed → DDA is now effectively the model; DDA force-reset on some properties (needs 400+ conversions); begin_checkout demoted; generate_lead now requires value+currency. The facts hold (trade-press corroborated); the agency "it broke everything" severity framing is self-interested. (re-ground 90d.)
• ~70.6% of AI traffic is referrerless → misclassified "Direct"; 89% of brands can't attribute AI referrals (Conductor, Nov 2025). There is no clean denominator for AI-referred share with current instrumentation. (re-ground quarterly.)
• The agent-transaction-share re-test metric (I's owed deliverable): autonomous-agent-completed share of US online retail orders — explicitly excluding AI-influenced framing. Public watch number: Adobe Digital Insights quarterly AI Traffic Report (methodology-disclosed, >1T US-retail visits; Q1-2026: AI-sourced US-retail traffic +393% YoY; AI traffic converted +42% vs human in Mar-2026). Authoritative confirming leg: first-party verified-agent-completed share (Web Bot Auth Signature-Agent at checkout — clean but operator-only). Two-gate threshold: Watch line = 5% sustained 2 quarters; Trigger line = 10% sustained, OR +2 sequential quarters of >50% QoQ growth off a ≥2% base → re-open the spine-vs-audience structure decision. Caveat: the metric's definition (completed vs assisted) is load-bearing and contested — re-confirm each quarter that the cited number still means completed-by-agent. (re-ground quarterly; the fastest-decaying lens in the domain — see Domain L.)