Guide
Set up your Meta Pixel
Your Pixel sends website activity to Meta. Its Pixel ID tells Tyton where that activity belongs. Start by finding your website’s dataset in Meta, then save its ID in Tyton so your agent can help you install and test the tracking.
Already have a website dataset? Go straight to step 3 and copy its ID.
Keep the Tyton setup checklist open to save your progress.
Open your business in Meta
Sign in to Meta Business Suite and choose your business portfolio from the business selector. This is where Meta keeps your business assets and the people who can manage them.
Starting fresh? Choose Create a business portfolio, enter your business details and follow the confirmation prompts. If a teammate already manages the portfolio, ask them to give you access to it and your website’s dataset.
Find your website’s dataset
Open Events Manager in the same business and look under Datasets or Data sources. If your website already has a dataset, open it. Reusing it keeps your existing tracking together.
For a new website 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. Meta calls this source a dataset; its website tracking uses a Pixel.
Copy the ID into Tyton
Open your website dataset’s Settings and copy the numeric Dataset ID, also called the Pixel ID for this web source. 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. Your browser Pixel and Conversions API should use the same website dataset.
The Pixel ID is public and appears in website code. Keep your Conversions API token private.
Install tracking on your website
Ask your connected agent to check for existing tracking and set up Tyton with the ID you saved. On a web builder such as Framer, paste the snippet your agent provides and publish the site. Tell your agent if your marketing website and app live on separate domains.
Review which actions will count as conversions, approve the plan and ask your agent to start it when you’re ready. Follow the Conversions API guide to add server tracking to the same dataset.
Check your first PageView
In your dataset’s Test Events tab, enter the published website URL and choose Test events or Open website. Keep that tab open. Visit a page, make the appropriate consent choice, then return to Meta and look for a fresh PageView with Browser as its source.
If nothing appears, check browser blockers and the installation. In Brave, temporarily turn Shields off for your test website only, reload and try again. Restore your protections afterward.
Want to check the Pixel on the page?
In Chrome, use Meta Ads Data Advisor (formerly Meta Pixel Helper). Visit your published site and open the extension to inspect the detected Pixel ID and browser events. Use its diagnostics with your existing installation; review any proposed setup changes with your agent to avoid duplicate tracking. Confirm receipt in Meta Test Events, then follow the checklist’s separate server test for Conversions API.
If Meta blocks a step
Check the selected business and your dataset access with its administrator. If Meta specifically asks for business verification, complete the checks shown in your account and resume here once access is available. Menu labels can vary between accounts.