v134 · privacy sandbox / ads

Trigger Context ID Builder

Build an Attribution Reporting trigger registration JSON and see exactly how setting trigger_context_id lifts the 20-report-per-source cap. Configure conversions, switch the context ID on and off, and watch the drop counter change in real time.

Attribution Reporting trigger header endpoint ready
Before Chrome 134: every source could generate at most 20 aggregatable reports regardless of trigger volume. If you sent 50 conversions for the same source, 30 were silently dropped. Chrome 134 lifts that cap when trigger_context_id is a non-empty string on the trigger registration, enabling unlimited aggregatable reports per source for high-volume flows.

Trigger registration

Source settings

Trigger settings

checking 0 / 64 code points
checking spec format: 0x + ASCII hex digits

Conversion impact comparison

Generated trigger registration JSON

Attribution-Reporting-Register-Trigger header

see also