Open Tyton
Tracking

Choose and approve conversions

Choose what counts, test it, and decide when tracking may start.

Video walkthrough coming soonFollow the steps below for now.

What you need

Connect the paid site you intend to track. For each outcome, decide what a real success looks like in your app or business records.

Review the proposal

  1. Ask your agent to show each proposed conversion, the pages or forms it covers, the Meta event it would use, and how it knows the action succeeded. Review what it will leave out too.
  2. Correct unclear choices. “Sales enquiry accepted” and “Newsletter subscription saved” can both map to Lead, but need distinct conversion IDs. A checkout that starts can map to InitiateCheckout; it is not a Purchase.
  3. Approve the exact choices in your signed-in Tyton review, or through your connected agent where available. Say whether you want to approve the plan only or also start tracking once its checks pass.

Test before starting

Your agent adds the tracking calls where each approved action is confirmed successful. Browser verification mode and server verify: true let Tyton record that those calls ran without sending events to Meta. Test browser and server paths, including failures that must produce no conversion.

If you explicitly chose approve-and-start, Tyton can activate the matching setup after your connected agent has just tested it with its current key. Otherwise, the signed-in owner starts tracking after testing. Check Tyton’s actual status before removing verification mode, then refresh the browser.

Success check

Before live tracking, check the approved choices, recent Tyton test results, and active status. Also check the payment or submission in your own system. Match each test event to a confirmed payment or accepted submission.

Changes and troubleshooting

If you change what counts, review and approve the new version. Preparing a new installation pauses the old one and resets its test results. If your conversation with the agent simply restarted, ask it to resume the same installation instead of creating another.

Pausing stops new planned authorizations. Events already queued may finish; low-level calls and other trackers are separate. Never bypass approval with track() to make a test pass.