Install a development release on a store controlled by the app organization and test the complete path before submitting for review.
Essential scenarios#
Confirm no browser or server event leaves Tringify before the selected consent purpose is granted.
Confirm each selected event contains only its declared payload, context, and envelope fields.
Reject an invalid signature, altered body, and stale timestamp before processing the batch.
Return a non-2xx response once and confirm the repeated event is handled idempotently by
event_id.Exercise browser-only, server-only, and dual-transport configurations used by the app.
For dual delivery, confirm the external provider receives the same deduplication identity from both transports.
Disable the merchant pixel and confirm browser delivery stops without disabling an independently configured server transport.
Change a test endpoint through a new release and confirm existing installations continue using their current configuration until updated.