# Verify events in Meta

Check what Tyton tested, what Meta received, and what Meta counted.



## What you need [#what-you-need]

Choose a Meta data source you are allowed to test, and have its token and Events Manager access ready. First finish [Tyton’s tracking tests](/docs/tracking/conversion-approval) and agree which actions may send events to Meta.

Tyton’s verification mode checks that your tracking call runs, without sending the event to Meta. Meta’s `test_event_code` is different: it marks an event that really is sent to Meta as a test.

## Check events in Meta [#check-events-in-meta]

1. Select your data source in [Events Manager](https://business.facebook.com/events_manager2/) and open **Test Events**. Obtain the server test code shown there. Follow [Meta’s testing instructions](https://developers.facebook.com/docs/marketing-api/conversions-api/using-the-api/); screens can vary.
2. In [Tyton’s Meta setup](/dashboard/meta-setup), select your website and save the code in **Meta test event code → Save test code**. Confirm the matching CAPI token is saved. Have your agent check activation and switch the published integration out of Tyton verification mode, then refresh before the agreed test.
3. For the browser check, enter your published website URL in Meta’s website test section and choose **Test events / Open website**. Make the appropriate consent choice and visit a page. Return to the Meta tab and look for a fresh **PageView · Browser**.
4. For the server check, complete one agreed successful action, such as an accepted signup. Use an authorised payment test flow for Purchase. Compare the business record with the Tyton event and the **Server** event in Meta. For paired conversions, compare the event name and Event ID, then check Meta’s deduplication result. See [the deduplication guide](/docs/tracking/deduplication).

## Success check [#success-check]

Look for your fresh event in Meta Test Events and check its name, time and source. For browser/server pairs, check that Meta matched the two copies. Tyton’s `queued` status means delivery is waiting; `sent` means Meta accepted the server event. For sales credited to an ad, check Ads Manager separately.

## Finish or troubleshoot [#finish-or-troubleshoot]

You can also manage the code in [Sites & Pixels](/dashboard/sites) under **Manage connections → Test event code**. Use **Save test code** to turn testing on or **Clear test code** to turn it off. These controls are separate from your Pixel ID and saved Conversions API token, so you don’t need to paste the token again.

In Tyton’s Meta setup, empty the **Meta test event code** field and choose **Clear test code**. Check that it shows **No test code saved** before checking normal activity. Keep the saved token in place.

If the browser test is empty, check [Brave Shields and other per-site blockers](/docs/meta/setup-checklist#the-website-opens-but-test-events-stays-empty). In Chrome, you can also use [Meta Ads Data Advisor (formerly Meta Pixel Helper)](https://chromewebstore.google.com/detail/meta-ads-data-advisor/fdgfkebogiimcoedlicjlajpkdmockpc) to inspect the installed Pixel ID and browser events. Restore protections after testing and keep the site’s consent choices in place.

If nothing arrives, check the selected dataset, consent, active installation, verification mode, test code, and [delivery status](/docs/tracking/event-delivery), in that order. Do not generate new purchase IDs simply to retry an uncertain delivery.