Your Conversions API access token

Open Events Manager, select your business and choose the website dataset whose Pixel ID you saved in Tyton. If it’s missing, ask your business administrator to check your dataset access.

Open the dataset’s Settings and scroll to Conversions API. Look for Set up direct integration or Set up manually, then choose Generate access token. Follow the token-generation prompts for your dataset if Meta offers Dataset Quality API choices.

Keep the token out of chat, screenshots and website code. Your agent can guide you through the screen while you save the token yourself.

Open Tyton’s Meta setup checklist and select your website. In Connect Conversions API, paste the token into the password field and choose Save token. Tyton stores it encrypted. Saving prepares the connection; the test below checks delivery.

Open the same dataset’s Test Events tab and copy the server test code into Tyton’s Meta test event code field. With your agent, finish the approved installation and activation, then switch the published integration out of Tyton verification mode. Complete one agreed successful test action and look for it with Server as its source in Meta Test Events.

Use an authorised payment test flow if you’re checking Purchase. A Meta test code labels server events; it doesn’t change what your checkout charges. Follow the event testing guide to check browser and server delivery separately, then clear the saved test code when you finish.

Check the event’s delivery status in Tyton first. If Meta reports an invalid or expired token, generate a replacement for the same dataset and save it in Tyton. For permission errors, ask the business administrator to check the token’s access to that dataset.

If a token leaked, revoke its access in Meta as well as replacing it. Generating another token alone is not proof that the old one stopped working. Keep credentials configured while troubleshooting: waiting events may retry when access is restored.