Framer
Check your Framer site's Meta tracking
Paste your Framer URL to see what tracking ships in the initial HTML. Framer sites navigate like single-page apps, so a Pixel pasted into Site Settings fires once on load — route changes, form submits, and purchases need explicit events, and anything server-side needs a sender outside Framer.
Real browser. Pro and Team from a workspace. Static scan stays free, no login.
SPA navigation eats PageViews
Framer swaps pages client-side. Without extra wiring, the Pixel reports one PageView per session no matter how many pages a visitor sees — which also starves retargeting audiences.
Custom code is head/body only
Framer's custom code slots take your snippet site-wide. There are no server hooks: a form submission exists only in the browser unless something sends it out.
Caply covers the SPA and the server
The snippet tracks in the browser, and Lead/Purchase are sent from Caply's servers with hashed contact data — so a blocked browser doesn't erase the conversion.
Framer tracking questions
- Why does my Framer site show almost no PageViews in Meta?
- Framer is a single-page app — the Pixel's automatic PageView fires once on the first load. Subsequent route changes need a manual fbq('track', 'PageView') or a snippet that watches navigation.
- Can Framer send Conversions API events?
- Not by itself. Framer has no server-side tracking. You need an external service to receive the event and forward it to Meta — that is the job Caply does.
- Where do I add tracking code in Framer?
- Site Settings → General → Custom Code. Use the 'End of <head>' slot for the Pixel and Caply snippet.
After the scan
Send Framer 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 · Webflow · Next.js · Full scanner