Open Event Delivery for the app in the Developer Portal. The available events, payload fields, consent purposes, and envelope fields come from the current platform registry.
Configure the declaration#
Enable Browser pixel, Signed server delivery, or both.
Select the canonical events the integration consumes.
Remove payload fields the integration does not need.
Choose one consent purpose for every selected event in the browser. For server delivery, choose a purpose for each event your backend needs and leave the others unsent; at least one event is required.
For server delivery, enter the public HTTPS endpoint and select only the context and envelope fields the integration requires.
Review the browser and server payload previews, save the draft, and submit the complete app release for review.
Customer matching#
customer_match is available only to an app with the customer_matching capability and read_customers permission. When an eligible customer is known, the server event may include a Tringify-generated external reference and normalized SHA-256 email or phone matches. email_sha256 and phone_sha256 follow the common ad-platform form (lower-case email, phone as international digits); google_email_sha256 and google_phone_sha256 follow Google's Data Manager rules (dots removed before the @ in Gmail addresses, phone in E.164 with its +), so send those to Google. Internal customer IDs and raw contact values are not delivered.
Session identity#
Select session_id only when the destination must associate browser and server events from the same consented storefront visit. The value is a pseudonymous Tringify session reference, not a storefront cookie or customer identifier. A reviewed browser declaration and its signed server declaration receive the same value for the same canonical event. Map it to the destination's documented session or client identity; do not expose it to page scripts, URLs, logs, or unrelated providers.