Webflow and Framer conversion tracking for paid ads
Track ad conversions on Webflow and Framer: install tracking in the site-wide head, fire leads only on successful submits, and send them to ad platforms.
By DATALYR · · 4 min read
Contents
What conversion tracking needs on a site builder
Conversion tracking on Webflow or Framer needs two things: a tracking script in the site-wide head, so every landing visit keeps its campaign and ad click ID, and a conversion event that fires only when a form or booking actually succeeds. Then the conversion has to reach the ad platform.
Both builders let you add code to every page. The common mistakes are installing a pixel on the thank-you page only, which loses the landing visit, and counting button clicks as leads.
This guide covers where the code goes in each builder, how to fire the conversion, what to do with embedded forms and schedulers, and how to check the result.
Where the code goes
In Webflow, site-wide code goes in Site settings, on the Custom code tab, in the Head code section. In Framer, open Site Settings and use the Custom Code section; Framer's own Meta Pixel article says to paste tracking code at the start of the head tag. Both apply to the published site, so test on the live URL, not the editor or a preview.
That is also how the Meta Pixel, the Google tag and the LinkedIn Insight Tag are installed on these sites. A pixel in the head records page views on every page, which is what ad platforms need for retargeting and for tying a later conversion to the landing visit.
DATALYR's script installs the same way: one snippet in the global head custom code of Webflow or Framer. Use the exact workspace ID DATALYR shows, and load either the snippet or the npm package, never both.
Fire the lead on success, not on click
Fire the conversion when the form platform confirms the submission, not when the button is clicked. A click fires on validation errors, double clicks and abandoned forms, and the ad platform then optimizes toward people who fail your form.
On a site builder the simplest reliable trigger is a success page: redirect to a thank-you page after a successful submission and fire the event there. If the form shows an inline success message instead, fire the event from the form's success callback.
DATALYR's script records page views and campaign context automatically. Conversions are explicit: call track for the lead and identify with the email, so later stages from your CRM or billing match the same visitor.
Example: clicks versus submissions
This is a hypothetical week on a Webflow landing page. The page gets 1,000 visits, the form's button is clicked 140 times, and the form platform confirms 100 successful submissions.
A pixel event attached to the button reports 140 leads. That is 140 ÷ 100 = 1.4 times the real number, and 40 of the reported leads are people who hit an error, double-clicked or gave up.
With $2,800 of spend that week, the button event shows $2,800 ÷ 140 = $20 per lead, while the real cost is $2,800 ÷ 100 = $28. The platform also learns from 40 events that never became leads. Firing on success fixes both.
What the button saw versus what happened
Button-click event
140 leads reported
Includes errors, double clicks and abandoned forms.
Success event
100 leads reported
Matches the form platform's confirmed submissions.
Embedded forms and schedulers
Third-party forms and schedulers embedded in a page run in their own frame, so your page often cannot see their submit. Typeform, for example, offers its own Google Tag Manager integration, which its help center lists for Business plans. A redirect to a thank-you page on your own site after submission works with most tools.
Schedulers are better tracked from their own side. DATALYR's Calendly and iClosed sources record each booking from the scheduler's webhook and match it to the visit, so a blocked script or closed tab does not lose the conversion.
For CRMs and other tools without a DATALYR source, Zapier can send the stage.
Send it to ad platforms and verify
A conversion rule sends each lead to Meta, Google Ads, TikTok, LinkedIn and other connected platforms from DATALYR's server. If a pixel in the browser already sends the same lead, decide which one owns that conversion so the platform does not count it twice; for LinkedIn, remove your own lintrk conversion calls for that event.
To verify, open the published page in a private window with ?utm_source=doctest, submit the form with a test email, and confirm in DATALYR's Events that one lead arrived with the doctest source. Then check the platform's own diagnostics for the delivered conversion.
Related articles.
Tracking ·
UTM parameters: build a campaign taxonomy you can trust
Create consistent campaign tags, test the complete redirect path, and verify that source information survives the journey to a business outcome.
Tracking ·
First-party data: build an inspectable marketing measurement record
Inventory the data your business collects directly, separate measurement from advertising sharing, and verify each field’s purpose and destination.
Conversion tracking ·
Meta Conversions API: setup, deduplication, and verification
Map a real conversion to the correct Meta destination, choose one delivery owner, and verify receipt separately from matching and attribution.
