Framer

What you need

You need access to Framer’s custom code and publishing settings, plus an approved Tyton tracking plan. For server tracking, you also need a backend you control. Tyton is not a built-in Framer form destination.

Install and connect

1. Add the v2 verification snippet through Framer’s site custom-code settings. Keep one installation and connect the consent manager. Follow Framer’s custom-code guide and check the published site.
2. If the form sends to your backend, select it, find Send To, and add an HTTPS webhook. A webhook is Framer’s request to your backend when a form is submitted. Verify its signature using Framer’s instructions.
3. Only after your backend validates and accepts the submission should it call the approved server conversion. Use verification mode first. Test a failed submission and a repeated webhook before starting tracking.

Use the submission identity

Framer documents Framer-Signature and Framer-Webhook-Submission-Id. Verify the signature with the original request body and submission ID, following the official example. Use that stable submission identity for event retries. Keep the webhook secret on your backend.

The server SDK remains private and needs an authorized artifact. For paired browser/server Leads, use a supported way to give the browser the same confirmed submission ID. If that does not exist, do not invent matching IDs or claim browser pairing.

Success check

Check that your backend saved one successful submission, failed forms produced no conversion, and repeat requests kept the same submission ID. After activating tracking, check the fresh event in Meta.

If you get stuck

Send the conversion after a confirmed successful submission. If an embedded widget gives you no reliable success signal or webhook, leave that conversion untracked for now. A Framer page also does not give your agent access to a separate checkout or backend. See split-site setup.