To set up Meta’s Conversion API (CAPI) on a Webflow site, you’ll need to integrate both client-side (Pixel) and server-side (CAPI) tracking to maximize data capture for your client’s ad campaign.
section.
Since Webflow is not a server-based CMS, you need an external tool (e.g., Zapier, Make [Integromat], or a custom backend) to send server-side events.
Option: Zapier + Webflow + Webhooks
https://graph.facebook.com/v12.0/<pixel-id>/events
.Required parameters in the payload:
event_name
: e.g., Purchase, Leadevent_time
: UNIX timestampuser_data
: Hashed email, IP address, etc.custom_data
: Optional values like purchase amountaccess_token
: Your API tokenFor form data, use Webflow Forms to send to Zapier via Form Submission Trigger.
Meta CAPI requires hashed user data to match identities:
Zapier may automatically hash recognized fields (like emails) if you use Meta’s built-in integrations.
Alternatively, link the client-side Pixel and send custom events to a backend via GTM + Google Cloud Functions or similar.
This is more complex but gives precise control over data passed to Meta.
To integrate Meta’s Conversion API with Webflow:
This setup will help improve tracking accuracy and ad performance through stronger signal quality.