Event delivery gives an installed app a consent-gated projection of Tringify's canonical customer-event stream. The app declares one event set in the Developer Portal, selects the fields it needs, and chooses browser delivery, signed server delivery, or both.
Choose a transport#
Transport |
Use it when |
Boundary |
|---|---|---|
Browser pixel |
A provider SDK needs browser execution or browser identifiers. |
Runs in an app-hosted cross-origin sandbox unless the release uses a separately reviewed first-party adapter. Both receive only selected events and fields after consent. |
Signed server delivery |
Your backend forwards events to another service or performs durable processing. |
Receives signed HTTPS batches from committed platform events. |
Release and installation behavior#
Saving changes updates the next app draft. Submit a new release when changing transports, endpoints, events, payload fields, consent purposes, context, or envelope fields. Installed stores continue using their current configuration until an approved update is applied.
Consent is enforced before delivery#
Each event has one consent purpose per transport it uses. Server delivery can carry fewer events than the browser pixel, for example only purchases. Tringify evaluates the visitor's consent before materializing a server delivery or forwarding a browser event. An endpoint response, pixel script, or provider configuration cannot widen the reviewed purpose.