demo · v134

Mixed-mode: partial trigger_context_id adoption

Real campaigns migrate gradually. A /checkout page updated to include trigger_context_id coexists with older /cart pages that haven't been touched. Triggers with a context ID are unlimited; triggers without one still hit the per-source cap. Move the sliders to see the partial uplift as adoption grows.

Total conversions to simulate 30 conversions

Per-source cap (source registration field) cap = 20

% of triggers with trigger_context_id 50% carry ctx_id

Conversions fired

—

Reports sent

—

Dropped (capped)

—

Breakdown

// Trigger without ctx_id → counts against per-source cap:
// { "event_trigger_data": [{ "trigger_data": "1" }] }
//
// Trigger with ctx_id → cap is NOT enforced (Chrome 134):
// { "event_trigger_data": [{ "trigger_data": "1" }],
//   "trigger_context_id": "order-789" }
//
// Mixed campaign: old flows (no ctx_id) are capped; new flows are not.
// The uplift scales linearly with the fraction of triggers carrying ctx_id.
// A campaign at 50% adoption gets ~50% of the way to the unlimited ceiling.

see also