demo · v134
Per-conversion stream vs. capped batch
The motivating case API callers brought to the working group: high-volume conversion flows (e.g. a checkout cart with N line items) where every line was a separate measurable conversion. Pre-Chrome 134 the per-source aggregatable report cap (20 reports per source) silently dropped events at the tail. With trigger_context_id set, that cap goes away. Drive both pipelines below at different traffic volumes and watch the drops.
probing Attribution Reporting…
The Attribution Reporting API is registered via response headers and not exposed as a callable JS surface. This page calls the local trigger-registration endpoint and renders the accepted/drop counts it returns. The relevant headers are shown beneath each column.
Header-backed stream
35
checking
0 / 64 code points
without trigger_context_id
waiting for backend…with trigger_context_id
waiting for backend…see also
- Feature index
- Baseline concept — sibling concept
- Spec — trigger_context_id
- ChromeStatus entry