Webflow

What you need

You need access to Webflow’s custom code and publishing settings, plus an approved Tyton plan. To track confirmed success from a server, you also need an editable backend and Tyton’s private server SDK.

Install and connect

1. Inventory existing Pixel, GTM, and form integrations. In Webflow’s site settings, use the custom-code area for the reviewed v2 verification snippet. Publish to the intended test domain. See Webflow custom-code guidance.
2. Check where each form sends its data. Connect the approved tracking call only after your backend confirms it accepted a submission. Webflow can send form webhooks to your backend; verify those requests and keep a stable submission ID. Follow Webflow’s form settings.
3. Submit one valid form and one invalid form. Check the saved submission and Tyton’s recorded test before starting tracking.

Success check

Check that an accepted sales enquiry has its own conversion, an invalid form has none, and repeated webhook requests reuse the submission ID. Keep newsletter and sales forms separate, even if both use Meta’s Lead event.

If you get stuck

Connect form tracking to a confirmed successful submission. For an embedded widget, use its documented success callback or a webhook your backend can verify. If neither exists, leave that conversion untracked until you have a reliable success signal.

Webflow custom code is browser code. Do not put the Tyton server key or Meta token there, and do not point a raw Webflow webhook directly at Tyton’s event gateway. Use your own verified backend handler. See split sites.