These buttons fire the e-commerce events Relay forwards to your server-side destinations
(GA4, Meta CAPI, generic HTTP, …) and that the diagnostics trace + verdict show end to end:
add_to_cart and purchase with value/currency.
Add it to the cart, then complete the purchase, and watch the purchase event
travel browser → ingest → store → destination in Relay's trace.
A higher-value conversion so the value/ROAS tracking has some variety.
/api/event carrying value +
currency props — the canonical payload your destinations receive. Add a GA4 or
Meta CAPI destination in Relay and these become server-side conversions; if one rejects an
event, the Overview verdict says exactly which and why.
email + phone (fake, consented test data) so
you can watch user-data hashing end-to-end: add a vendor preset (TikTok / Snapchat
/ Pinterest) with hashFields = email,phone, and the destination receives a SHA-256 of
the phone — never the raw value. The email demonstrates Relay's privacy floor: it's scrubbed to
[email] at ingest before anything is stored, so it can't be hashed at forward time
(true email matching needs hash-at-ingest — on the roadmap).
One-click repurchase that fires a purchase with the same
order_id (NW-1002) as the Team-plan purchase above. Complete that
purchase first, then click this — Relay's duplicate-conversion detection
flags the repeat order_id in the trace so the same sale isn't double-counted at
your destinations.