Question 1

What does a post-cookie attribution stack actually look like in 2026?

Accepted Answer

A blend, not a single tool. Layer 1: server-side conversion APIs (Meta CAPI, TikTok Events API, Google Enhanced Conversions through server-side GTM) to recover the deterministic signal iOS ATT and ITP killed in the browser. Layer 2: a Bayesian MMM (Meta Robyn or Google Meridian) for top-down channel allocation, refit weekly. Layer 3: GeoLift-style geo-incrementality tests to calibrate the MMM priors and isolate true lift from correlation. Layer 4: clean-room joins (AWS Clean Rooms, Snowflake Data Clean Room, Habu, or Google PAIR) for advertiser-publisher matching without sharing PII. Privacy Sandbox APIs (Attribution Reporting, Protected Audience) slot in for in-browser noisy attribution as Chrome rolls them out. MTA stays as a directional supporting signal where consent allows — never the primary truth.

Question 2

Meta Robyn vs Google Meridian for Bayesian MMM — which do you pick and why?

Accepted Answer

Robyn is faster to stand up, uses Nevergrad multi-objective optimisation, and has stronger out-of-the-box adstock and saturation transforms (Hill, Weibull). Meridian, released as Google open source, is Bayesian-native, models geo hierarchies cleanly, and incorporates reach-and-frequency curves natively which matters for video and CTV. Selection criteria we use: data granularity (geo or national), channels in play (Meridian is better for YouTube / video heavy mixes, Robyn for retail-media-heavy DTC), team R vs Python skills, and whether you need to enforce informative priors from past GeoLift experiments. We have shipped both. For most DTC and B2C ecom clients with national daily data and 8-15 channels, Robyn ships faster. For brand mixes with geo data and heavy video, Meridian wins.

Question 3

How does server-side CAPI actually recover iOS ATT signal loss?

Accepted Answer

Browser-side pixels lose roughly 60-80% of iOS conversion signal because of ATT opt-out and Safari ITP. Server-side CAPI sends events directly from your servers to Meta / TikTok / Google with hashed first-party identifiers (email, phone, click ID — fbclid, ttclid, gclid). The platform deduplicates against any pixel events that did fire. Done well, match rates land at 70-85% on Meta CAPI vs 25-40% pixel-only. Implementation involves event schema design, an Event Match Quality (EMQ) audit for Meta (we target 8/10+), consent-mode gating for EEA traffic under TCF v2.2, and a server-side GTM container as the orchestration layer. Typical timeline: 3-5 weeks end-to-end including QA against the Meta Test Events tool.

Question 4

How do you run GeoLift-style incrementality experiments, and why bother if you already have an MMM?

Accepted Answer

GeoLift uses synthetic control: you turn a channel off in matched test geos and the algorithm builds a counterfactual from donor geos. Output is a clean iCAC and incremental ROAS by channel. We use it to calibrate MMM priors — the MMM gives you allocations every week, but it is correlational; incrementality is causal. Typical cadence: 4-6 GeoLift experiments per year on your top spending channels (Meta, Google, TikTok, CTV, paid podcast). Each runs 4-8 weeks. We then use the lift estimates as informative Bayesian priors in the next Robyn or Meridian refit. This is how you stop overspending on channels that look great in last-click but are 30% incremental.

Question 5

Can you do consent-aware identity stitching that actually respects TCF v2.2 and GPC?

Accepted Answer

Yes — this is the load-bearing piece most teams get wrong. Architecture: a consent-management platform (OneTrust, Didomi, Sourcepoint) emits a TC string per pageview; an event router (server-side GTM or a custom edge worker on Cloudflare / Fastly) reads the TC string plus the GPC header and gates which downstream destinations fire. Identity graph joins happen in your warehouse (Snowflake / BigQuery / Databricks), keyed on a consented identifier (hashed email, LiveRamp RampID, UID2 token). For users who refused consent, you keep aggregate counts only — no row-level joins. Output is a graph where 100% of edges are auditable back to a TCF purpose and a GPC signal. We document this for the DPO.

Question 6

LiveRamp ATS vs UID2 — which identity layer should we adopt?

Accepted Answer

Different problems. LiveRamp Authenticated Traffic Solution (ATS) is publisher-side authenticated identity — it lets publishers send a RampID into the bid stream for logged-in users, and is the broadest of any non-Google authenticated solution. The Trade Desk Unified ID 2.0 (UID2) is an open-source deterministic ID derived from hashed email, designed for the open programmatic ecosystem outside Google. If you are an advertiser running heavily through The Trade Desk and the open exchange, UID2 has better reach there. If you need broad publisher footprint including premium publishers using LiveRamp, ATS wins. In practice we implement both — they coexist, the cost is implementing two encryption flows, and the lift from running them in parallel is 10-20% extra addressable reach versus either alone.

Question 7

How do you model LTV by cohort × channel for B2B SaaS?

Accepted Answer

Two-stage Bayesian survival model. Stage 1: a Weibull or Cox proportional-hazards churn model gives you per-account survival probability over months 1 to 36, conditioned on plan tier, seat count at signup, ICP fit score, and onboarding-event covariates (time-to-first-value, integration-connected). Stage 2: an expansion-revenue model (zero-inflated negative binomial works well) layers in upsell and seat-expansion. Multiply through and you get expected LTV per account. Then bucket by acquisition channel — paid search brand, paid search non-brand, paid social, content/SEO, outbound SDR, partner — and you get LTV per channel cohort. The gap is usually 2-4x between best and worst channels, and almost never matches first-touch attribution. This is what drives reallocation away from channels that look efficient on CAC but deliver low-LTV cohorts.

Question 8

How do you detect creative fatigue and rotate ads before performance collapses?

Accepted Answer

Time-series anomaly detection per creative-ad-set pair, watching CTR, post-click CVR, and frequency. Three signals: (1) a Bayesian change-point detector on CTR (PyMC or Ruptures) catches structural breaks at 5-7 days of impression exposure; (2) frequency cap — when average frequency per unique reach exceeds 3-4 for response campaigns, fatigue is imminent; (3) a saturation curve fit per creative — once daily impressions exceed the inflection point, marginal CPA explodes. Output is an automated rotation queue that swaps the bottom-decile creatives, with refresh suggestions piped from a generative-creative pipeline (Midjourney / Runway for variants, LLM for copy variants), and bid adjustments pushed back into Meta and Google APIs. For high-spend accounts we have seen 15-25% CPA improvement from disciplined rotation alone.

Post-cookie measurement: Bayesian MMM, server-side CAPI, clean-room identity

Tools and standards in production

Marketing AI Systems

Bayesian MMM

Server-side CAPI

GeoLift Incrementality

LTV Cohort × Channel

Creative Fatigue Detection

Consent-aware Identity Stitching

Marketing Data Engineering

Event-stream pipelines

Server-side GTM + edge

CDP integration & activation

Clean-room first-party joins

Frequently Asked Questions