# Set up Tyton

Connect your website and agent, then review and test what you want to track.



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

Have your website URL, permission to edit and publish it, and an agent you can connect to Tyton. To send events to Meta, you also need access to your Meta business and its Pixel ID. You can start reviewing your site before you have those credentials.

To check and set up your Meta Pixel and Conversions API step by step inside Meta Events Manager, try the free [Tyton Chrome extension](/chrome-extension), which asks for your approval before anything changes.

## Connect your site [#connect-your-site]

1. Create your Tyton account, confirm your email, and pick the Free plan or a paid one. In the dashboard, add your website. Use the site you intend to track, not its hosting provider’s homepage.
2. Follow your [agent connection guide](/docs/connect/codex). Sign in to Tyton when your agent asks and pick that site. Check the **Integrations** page in Tyton: the app shows **Connected** only after it has used its access.
3. Add your [Pixel ID](/docs/meta/pixel-dataset). Add the recommended [CAPI token](/docs/meta/conversions-api-token), or choose **Skip for now** when offered after the other setup steps. You can add it later.

Dashboard wording may differ during rollout. If you skip the token, Tyton is not connected to Meta’s server-side Conversions API (CAPI).

## Work on the right website [#work-on-the-right-website]

Use **Website** at the top right of your dashboard to switch sites. Your choice opens immediately—there is no extra View button. Overview, Events, Get started, and Meta setup keep that same website as you move between them. Opening a link for a specific website switches to the website in that link.

For the Meta-side steps, open [the setup checklist](/dashboard/meta-setup). It takes you from creating your business and dataset to publishing the Pixel and checking fresh browser and server events. Checking a task off records your progress; it does not turn on tracking or prove that Meta received an event.

Your agent has its own connection to one website. Changing the dashboard selector doesn't switch that connection. To ask your agent to work on another website, connect it again from **Connect an AI app** on the **Integrations** page and pick that website. Sites & Pixels shows all your websites; your subscription and account settings apply to the account.

## Remove a website [#remove-a-website]

1. Open **Sites & Pixels** and find the website you want to remove.
2. Open **Manage connections → Delete website and data**. Read what will be removed.
3. Type the website's domain, then choose **Permanently delete**. Choose **Cancel** to leave it as it is.

This permanently removes that website's Tyton keys, setup and stored event history. It **does not cancel your subscription**, change your hosted website, or delete your Meta dataset or data already sent to Meta. Remove the Tyton snippet or SDK from your website separately. A browser Pixel already loaded on a page or a Meta request already in progress cannot be recalled.

You can also ask your connected agent to delete its website. It must check the exact website and ask for your explicit confirmation first. If a billing change is in progress, finish that before deleting. If the result is unclear, refresh Sites & Pixels before trying again.

## Choose and test conversions [#choose-and-test-conversions]

Give your agent this request:

> Inspect this site and its backend. Show me each real outcome you recommend tracking, where it happens, and what proves success. Keep sales enquiries and newsletter subscriptions separate. Ask about missing details before proposing changes.

1. Review the [conversion proposal](/docs/tracking/conversion-approval): what counts, what does not, and how success will be confirmed. You can approve the plan alone, or approve starting tracking after the checks pass.
2. Ask your agent to add tracking where each approved action actually succeeds. In verification mode, test every planned browser and server action, including failures. Verification mode records the test in Tyton without sending it to Meta.
3. Check that tracking has been activated before switching to live settings. Refresh the page, then agree to a [Meta test](/docs/meta/test-events) using a real, controlled action.

## Success check [#success-check]

Your agent can show which site was connected, which outcomes you approved, which browser or server actions passed testing, and what Tyton recorded. To confirm Meta received an event, check Meta separately.

## If you get stuck [#if-you-get-stuck]

If your agent cannot access the backend, the required private SDK, or a widget’s reliable success signal, ask it to show what is missing. You can finish the parts it can verify, but the affected conversion still needs that missing piece before it can be called working.
