On-site conversions
On-site conversions track actions that happen on your Webflow site. Use them to measure third-party form submissions, dynamic interactions, or any custom user action that other goal types don’t capture.
How on-site conversions work
Trigger a conversion with custom code
On-site conversions use the wf.sendEvent() API to trigger a conversion. When a visitor performs the action you’re tracking, the goal is recorded and attributed to your optimization.
Your development team will need to add the necessary logic to trigger the conversion when the action occurs.
Add the custom code to your site
When the conversion occurs on a specific page, add the code snippet to the custom code section of your page settings before the </body> tag.
For more information, see Custom code in Page settings.
If the conversion can occur on any page across your site, add the code snippet to the footer code in the site settings. For more information, see Footer code in Site settings.
Using Google Tag Manager (GTM)
If you use Google Tag Manager and already have a trigger for this action, create a custom HTML tag that calls wf.sendEvent() and attach it to the existing trigger.
Prerequisites
Before tracking on-site conversions, you need to create a custom goal in Webflow.
Example: HubSpot form submissions
In this example, a visitor fills out a form on your site to request a demo. Assumes you’ve created a custom goal in Webflow with the event name form_submitted.
Example: Calendly meeting bookings
In this example, a visitor books a meeting through an embedded Calendly widget. Assumes you’ve created a custom goal in Webflow with the event name meeting_booked.