Find or create your Pixel
Find the right Meta Pixel and save its number in Tyton.
What you need
Have your published website URL ready and open the Meta business portfolio your team uses. Your Pixel ID is the number Tyton needs to send activity to the right website dataset.
Choose the data source
- Open Meta Events Manager in the same business. Under Datasets or Data sources, look for your existing website dataset and reuse it.
- For a new setup, choose Connect data → Web → Next. Choose Create new dataset if offered, give it a name you’ll recognise and follow the prompts. Enter your website URL when asked.
- Open the website dataset’s Settings and copy its numeric Dataset ID / Pixel ID. In Tyton’s Meta setup, select your website, paste it into Dataset / Pixel ID and choose Save Pixel ID.
Check the label beside the number before copying. A Page ID, business ID or ad account ID belongs to a different asset. Use the same website dataset for your browser Pixel and Conversions API.
Success check
Check that Tyton shows the number you copied. Your agent can now use it to prepare the installation. On a web builder, paste and publish the snippet your agent supplies. Continue with the setup checklist to add Conversions API and check that events arrive.
The Pixel ID is public and may appear in browser code. The CAPI token is secret.
If you get stuck
If the dataset is missing, check the selected business and ask its administrator for access. If Tyton already has a different Pixel ID, ask your agent to review the destination change before replacing it.
Meta’s menu labels vary across accounts. Meta’s Pixel setup help is available while signed in. If Meta asks for business verification, complete the account checks it shows before continuing.
Check the Pixel on your website
In Chrome, Meta Ads Data Advisor (formerly Meta Pixel Helper) lets you inspect browser tracking. Visit the published website, make the appropriate consent choice and open the extension. Compare its detected Pixel ID with the one saved in Tyton and look for a PageView.
Use the extension’s diagnostics with your existing installation. Review any proposed setup changes with your agent to avoid adding duplicate tracking. Then confirm a fresh browser event in Meta Test Events; Conversions API has a separate server check.