Event names and deduplication
Use the same event name and ID when browser and server report one action.
Match the event and ID
When the browser and server both report one customer action, give both copies the same official Meta event name and event ID, and send them to the intended Pixel or dataset. That is how Meta can recognize a match. See Meta’s matching rules.
For example, if a payment ID is payment_42, use that same orderId in both places. Tyton turns it into order_payment_42. You may instead supply the same explicit eventId; that takes priority. Do not add order_ twice.
Preserve identity
- Take the ID from the confirmed payment or accepted submission.
- Reuse it and the original event time on retries, refreshes, and webhook redelivery.
- Give a new payment or submission a new ID. Each renewal needs its own payment ID; the subscription ID alone is insufficient.
Never put an email address in an event ID. A checkout handoff UUID helps link the browser to checkout; it is not the payment or conversion ID.
Use supported names
Tyton accepts PageView, ViewContent, Search, AddToCart, AddToWishlist, InitiateCheckout, AddPaymentInfo, Purchase, Lead, CompleteRegistration, Contact, Schedule, StartTrial, Subscribe, SubmitApplication, CustomizeProduct, FindLocation, and Donate.
Approved conversion() calls use the plan’s mapping. Low-level event names are case-normalized, but signup is too vague to use on its own. First agree on what happened: an account registration, a newsletter signup, an application or a subscription. Then choose the event that fits. Trigger the event when the app confirms the action succeeded. See Meta’s event reference.
Check the result
Tyton groups matching browser and server observations under one event. For a Purchase, the server sends the Conversions API event and the browser supplies its matching observation. Check the delivery status, then open Meta Test Events to check that Meta received and matched both copies. Keep the same event ID on retries so Meta can recognize duplicates.