Question from Reddit:
New to Webflow and trying to install the Facebook pixel code to track events from ads. It looks like I can do this manually and by partner integration on the Facebook pixel setup. Has anyone tried doing this before and which is the best method?
Also, I would like to know what is the best setup Pixel by itself or Pixel with Conversion API? All help appreciated.
Answer from Nabil:
The short answer is:
The best method for installing the Facebook Pixel on Webflow is manually using Google Tag Manager (GTM) for precise control over event firing.
While the partner integration is simpler, it often limits your ability to set up custom events or control the pixel precisely.
The best setup today is absolutely the Facebook Pixel combined with the Conversions API (CAPI).
This dual tracking setup is essential because the browser-based Pixel is increasingly blocked by ad blockers and privacy changes, leading to lost conversion data.
The CAPI sends the same event data directly from your server (or a server-side tagging solution like Stape or Google Cloud Platform) to Facebook, ensuring you capture nearly all conversions, which improves ad performance and optimization.
The long answer is:
Since you’re new to Webflow, the initial choice between manual and partner integration is important.
Although Facebook’s partner integration seems easier, it often limits where and how you can fire your PageView and other standard events like ViewContent or AddToCart.
It typically just drops the base code onto every page.
The manual installation via Google Tag Manager is the superior method because it gives you granular control.
You place the GTM container snippet in Webflow’s custom code sections, and then manage all your Facebook Pixel tags and triggers inside GTM.
This is the industry-standard best practice.
Regarding your second question, the best setup is a hybrid approach using both the Facebook Pixel (client-side) and the Conversions API (CAPI) (server-side).
The standard Pixel alone is no longer sufficient due to changes like Apple’s Intelligent Tracking Prevention (ITP) and general ad blocker usage, which cause data loss.
The Conversions API solves this by sending the exact same event data directly from your server to Facebook, creating a reliable, high-quality stream of data.
An excellent, future-proof solution is to use the Facebook Conversions API combined with Webflow’s APIs and a server-side tagging environment hosted on Stape or Google Cloud Platform.
This works by having your website’s client-side GTM capture the necessary user data, like the Facebook Click ID (fbclid).
When a conversion event occurs, like a form submission or a purchase, your GTM sends this data not directly to Facebook, but to your server-side container on Stape or GCP.
This server-side environment then uses the Webflow’s APIs to look up or validate transaction details, and subsequently sends the event server-to-server to Facebook via the CAPI.
Simultaneously, you keep the standard client-side Pixel running as a backup and a way to quickly implement features like Dynamic Product Ads.
This dual setup maximizes data accuracy, minimizing the number of conversions that Facebook misses, which directly leads to better ad optimization and more accurate ad spend attribution.
This is a robust setup that circumvents browser and privacy limitations while providing a higher match quality for Facebook.
About The Author
