Vercel

What you need

You need permission to deploy the Vercel project, access to its backend and Tyton’s private server SDK, and an approved conversion plan.

Configure and deploy

1. In the project’s environment settings, add the Tyton server key as TYTON_SECRET_KEY for the intended environment. Keep preview and production credentials deliberate. Vercel environment changes apply to new deployments; see Vercel’s environment guide.
2. Add the approved Tyton call where your backend confirms success. Wait for conversion() before the function ends, or use a durable job you have deliberately set up. Starting a call and letting the function end may lose it.
3. Deploy with verification mode first. On the deployed site, test one action that succeeds and one that fails. Check Tyton’s recorded test before starting tracking and switching to live settings.

Success check

Check that the deployed function has the right key, your app recorded the business outcome, and Tyton returned a safe status. A passing local test does not check the deployed settings. Never log credentials or customer identity.

The SDK has bounded retries and no persistent queue on your server. Vercel functions have execution limits; review the runtime documentation for your deployment. Tyton’s durable queue starts only after gateway acceptance.

If you get stuck

Check the function’s environment, deployment version, and request duration. A protected preview may block a provider webhook; use an intentionally authorized test endpoint without weakening production access controls. A preview hostname must also match the reviewed browser target and allowed site configuration.

Check which repositories contain your marketing site and payment backend. Follow split-site setup when they differ.