demo · v134 · privacy-sandbox
Trigger Volume Probe
Probe a heavy conversion flow (a big shopping cart, a long form, a multi-step checkout). Compare pre-v134 (20-per-source cap silently drops events) to v134+ (trigger_context_id set → no cap, every conversion lands). Live histogram and dropped-event counter.
waiting for backend trigger route…what changed in v134
Pre-v134, the Attribution Reporting API capped aggregatable reports at 20 per source. Heavy carts that triggered, say, 35 conversion events on a single source silently dropped the last 15 — measurement was incomplete and the caller had no visibility.
v134 lifts that cap when the trigger registration sets a non-empty trigger_context_id. The advertiser is opting in to per-conversion granularity; in exchange the platform stops trimming. Privacy is preserved by separately enforcing source-level noise budgets — see the linked spec.