Set up Meta, step by step

Keep Tyton’s Meta setup checklist open beside Meta. Choose your website at the top right. You can save your Pixel ID and token there, check off each task and see new activity while you test.

Your route through setup

1. Choose your business. Open Business Suite, select the existing business portfolio or create one, and confirm your access.
2. Find your website dataset. In Events Manager, reuse your existing website dataset. For a new setup, choose Connect data → Web → Next, then follow the dataset creation prompts. Open its Settings, copy the numeric Dataset ID / Pixel ID into Tyton and choose Save Pixel ID. Check the label beside the number: a Page ID, business ID or ad account ID belongs to a different asset.
3. Connect the website. Ask your agent to check the published site and prepare the installation with that Pixel ID. If marketing and signup are on separate domains, tell your agent about both. On a web builder, you’ll paste the snippet it supplies and publish.
4. Add Conversions API. Open that dataset’s Settings → Conversions API, find Set up manually / direct integration → Generate access token, and paste it into Tyton’s secure field.
5. Publish the integration. Review the conversion plan with your agent, then approve it and request the start when you’re ready. Your agent checks successful and failed actions, confirms activation and switches the integration out of Tyton verification mode. Publish the changes on every relevant site.
6. Check the browser. Open Meta Test Events and the published website. Make the appropriate consent choice. Look for a fresh PageView · Browser in Meta and a fresh browser receipt in Tyton.
7. Check the server. Save the Meta test code before a controlled, authorized successful action. Compare the Tyton event with Server in Meta Test Events.
8. Check double-counting. For a paired conversion, compare the browser/server event names and Event IDs, then inspect Meta’s deduplication result. Server-only conversions can be marked as such.
9. Finish the test. Clear the server test code when ready, then check the next legitimate conversion. A test dataset needs a reviewed move to the production destination and a fresh check there.

Know what each check means

• Checked by you: you recorded completing a task or seeing an event in Meta.
• Browser / Server → Tyton: Tyton has a fresh observation from that source.
• Tyton → Meta API: a project event has an accepted CAPI response. Confirm the dataset and event in Meta too.

Start watching shows new activity arriving in Tyton. Activation happens in the installation step. Tyton’s verification mode keeps setup checks inside Tyton; a Meta test code labels server requests that are sent to Meta. Use an authorised test flow for payments, since a test code leaves your checkout’s payment behaviour unchanged.

If your screen looks different

Meta uses different labels across accounts. First check that you’ve selected your business and the right dataset. If an option is missing, ask the business administrator to check your access. Complete business verification if Meta specifically requests it, then pick up where you left off.

Meta says “No websites found”

Keep the existing dataset and look at its event rows. A received PageView · Meta pixel shows browser activity; a received Purchase · Conversions API shows server activity. Check each event’s time and details to see whether it belongs to your test.

If events are listed but Websites is empty, ask your agent to inspect the page URL attached to the browser event and the server event’s event_source_url. The empty label alone gives too little information to diagnose the cause. Meta’s Overview says events may take up to 30 minutes to appear, so use Test Events for your controlled check.

Connect your website to this dataset

Brand Safety → Domains records domain ownership. To receive website activity, your dataset also needs a working Pixel installation on the published site.

1. Choose the destination. In Events Manager, select your existing website dataset. For a new setup, use Connect data → Web. Open its website / Meta Pixel setup if offered and enter your website URL when prompted.
2. Match the ID. Copy this website dataset’s numeric ID from Settings into Tyton. Ask your agent to use that same ID for the website installation.
3. Install and publish. Have your agent check the live website first, then install the agreed Tyton integration if it is missing. On a web builder, paste and publish the snippet your agent provides. Include separate marketing and app domains in the setup. Don’t add another Pixel script over an existing installation.
4. Connect the server side. Save the CAPI token for this same dataset in Tyton’s secure field. Have your agent confirm that website conversions include the page URL where the action happened. Never paste the token into your website code.
5. Confirm the browser side. Open this dataset’s Test Events, enter the published website URL and click 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.
6. Confirm the server side separately. Follow the server test step above with a saved test code and an agreed successful action. Check that the matching event arrives in this same dataset with Server as its source.

Removed the Pixel code from your website? Reuse the existing dataset and ask your agent to restore the agreed installation.

After the browser PageView arrives, continue with the server test to check Conversions API.

Inspect the Pixel in Chrome

Open the official Meta Ads Data Advisor extension (formerly Meta Pixel Helper). Visit your published site, make the appropriate consent choice and open the extension to inspect its Pixel ID and browser events.

Use its diagnostic view with the existing Tyton installation. Review proposed setup changes with your agent before approving them, so you keep one agreed tracking setup. Confirm receipt in Test Events afterward; the server check remains a separate step.

The website opens, but Test Events stays empty

Using Brave? Check Shields first. On your website tab, click the lion icon beside the address bar and temporarily turn Shields off for this site. Reload the website, make the appropriate consent choice, and return to Meta Test Events. Shields can block the browser Pixel, leaving Test Events empty or causing the Event Setup Tool to say it cannot detect a Pixel.

Using another browser? Check ad-blocking extensions or built-in tracking protection. Temporarily pause the blocker for your test website only, then reload and try again. Private windows can also block tracking.

Restore your protections after testing. Don’t turn them off globally, bypass the website’s consent choices, or ask your visitors to disable their protections. Browser testing and server-side CAPI testing are separate checks.

The results appear back in Meta’s Test Events tab. Your website can look exactly the same while sending an event. If the Meta tab stays empty:

1. Keep it open in the same browser while you visit the published site. Make the appropriate consent choice.
2. Ask your agent to check whether the expected Pixel actually loads and sends a fresh PageView. Compare its ID with the dataset selected in Meta.
3. If it does not fire, check the published installation, consent, browser blockers and tracking activation. Review any dataset traffic allowlist too.
4. If the correct Pixel fires but the test remains empty, have your agent inspect the browser request, test session and Meta diagnostics. Do not mark the test complete from an older event in Overview.

Keep this step unchecked until you see the fresh event in Meta. Have your agent trace the existing test before repeating a signup or payment.