# Troubleshooting

Find where tracking stopped before changing keys or event IDs.



## Agent cannot connect [#agent-cannot-connect]

1. Check that your agent uses Tyton’s URL ending in `/mcp` and supports remote HTTP connections.
2. Sign in to Tyton when your app asks, pick the website and allow access. If the sign-in page says the request has ended, start again from your app.
3. If your app can’t sign in, connect with a server key instead. If the pairing code expired or was already used, get a new one on the **Integrations** page. Follow your [client guide](/docs/connect/codex) for the exact settings.

## Setup is complete but there are no events [#setup-is-complete-but-there-are-no-events]

Open your tracking plan and check that you approved it, tested the actions, and started tracking. Once tracking is active, remove verification settings, reload your site, and complete a fresh action with any required consent. Look for that action in **Events**. Earlier verification tests stay in the test results.

## Lead appears after a failed form [#lead-appears-after-a-failed-form]

Ask your agent to send the event after your app or backend accepts the lead. Use the form’s confirmed success response or a verified webhook as the trigger. Then test a failed submission and check that it leaves your conversion count unchanged.

## Payment succeeded but tracking failed [#payment-succeeded-but-tracking-failed]

Do not change the successful payment in your app. Check Tyton’s SDK result and [delivery status](/docs/tracking/event-delivery). If a retry is approved, keep the original payment ID and time. Do not charge the customer again or create a second conversion ID.

## Browser works but server Purchase is missing [#browser-works-but-server-purchase-is-missing]

Check the payment handler that confirms success, its private key, whether it waits for Tyton’s SDK result, and the CAPI token. A browser Purchase can show what the browser observed, but it cannot replace the server Purchase sent through CAPI.

## Counts look duplicated [#counts-look-duplicated]

Compare the event names and IDs from browser and server, then look for another tool sending the same event. Browser and server copies should share one event ID. Before removing a tracker, confirm which integration is responsible for each event.

## What to include in a support request [#what-to-include-in-a-support-request]

Open [Support](/dashboard/support) in your dashboard and send us a message. Your selected website is filled in, and we’ll reply to your account email.

Share the site, approximate time, event name, whether it came from browser or server, the displayed status or error code, and what you expected. Include what you already checked. Leave out tokens, keys, cookies, customer details, and raw network data.

For crawler traffic, open **Sites & Pixels → Bot protection → Edit** to review the activity and choose a mode. See [bot protection](/docs/tracking/bot-protection) for what each mode covers. You can manage tracking-alert emails in your account’s notification settings.
