Webflow
Check your Webflow site's Meta tracking
Paste your Webflow URL to see exactly what ships in your HTML. Webflow gives you full custom-code access on paid site plans, so the browser Pixel is rarely the problem — the missing piece is a server-side sender for the events iOS and ad blockers never let the Pixel report.
Real browser. Pro and Team from a workspace. Static scan stays free, no login.
Full head access, no server
Webflow lets you paste any code site-wide or per page, but it hosts no backend you control. Form submits and Ecommerce orders have no native path to Meta's Conversions API.
Webflow Ecommerce fires browser-only events
The built-in Facebook Pixel integration covers standard events in the browser. There is no event_id deduplication story and no retry when the request is blocked.
Leads deserve server-side too
Most Webflow sites optimize for Lead, not Purchase. Caply sends Lead server-side with a hashed email from the form, which is what raises Event Match Quality on lead campaigns.
Webflow tracking questions
- Where do I put the Meta Pixel in Webflow?
- Site Settings → Custom Code → Head. Per-page code goes in each page's settings. Both require a paid site plan.
- Does Webflow support the Conversions API natively?
- No. Webflow fires browser events only. Server-side requires an external service — Caply's snippet plus our servers, or a tagging server you host and maintain.
- Will the scanner see events on my SPA-like interactions?
- The static scan reads initial HTML. Interactions that fire tags after JavaScript need the deep scan (Pro), which renders the page in a real browser.
After the scan
Send Webflow sales from the server. Count each one once.
Caply sends Purchase and Lead from managed servers with hashed customer data, deduplicated against your Pixel by event_id. Pro $29 or Team $99, 14-day trial (card required).
Other platforms: Shopify · WooCommerce · Wix · Squarespace · Framer · Next.js · Full scanner