Send Server-Side Conversions to the Meta Ads API (CAPI)
VerifiedSends server-side conversion events to Meta CAPI with hashed user data.
What this workflow does
This automation accepts conversion events, sanitizes and hashes user identifiers via the Crypto node, formats click IDs and event details, and transmits the payload server-to-server using the HTTP Request node.
It is intended for performance marketers, lead-generation teams, and e-commerce operations that need reliable Meta ad attribution beyond browser-based tracking.
Who is this for?
Performance marketers, lead generation teams, e-commerce stores, and developers who need reliable Meta ad attribution.
What problem it solves
Browser-based Meta Pixel tracking is often blocked or inaccurate due to iOS 14+ privacy changes and ad blockers, leading to poor ROAS and attribution.
Live workflow preview
Interactive canvas of every node and connection — scroll and click to explore. Powered by n8n's preview.
Open the template on n8n to import and run it. View source template →
What it automates
Form submissions as conversions
Send lead form data from a CRM or website backend to Meta CAPI so every qualified lead is recorded server-side.
E-commerce purchase events
Forward completed orders from your backend system to ensure purchase conversions are tracked even when browser pixels fail.
Multi-touch campaign optimization
Log click IDs (fbc/fbp) and user data directly to Meta so ad platforms receive complete event data for better bidding.
How the workflow works
The 3 nodes in this automation, in order.
- 1HTTP RequesthttpRequest
- 2Cryptocrypto
- 3Codecode
Apps & integrations used
How to set up Send Server-Side Conversions to the Meta Ads API (CAPI)
- 1Import the workflow into your n8n instance.
- 2Obtain your Meta Pixel ID and CAPI Access Token from Events Manager.
- 3Copy the webhook URL from the Webhook trigger node.
- 4Configure your form, CRM, or backend to POST the required payload to the webhook URL.
- 5Paste your Pixel ID and Access Token into the final HTTP Request node credentials.
- 6Activate the workflow and test with a sample event.
How to customize this workflow
- →Change the event_name in the payload to track different actions such as AddToCart or ViewContent.
- →Add extra user data fields before the hashing step if your source provides more PII.
- →Insert a filter node after the webhook to process only events from specific sources.
- →Route successful responses to a logging or notification node for monitoring.
Send Server-Side Conversions to the Meta Ads API (CAPI): pros & cons
Pros
- +Handles SHA-256 hashing and data normalization automatically
- +Bypasses browser restrictions for more reliable delivery
- +Ready-made payload formatting that matches Meta CAPI requirements
- +Uses only standard n8n nodes (HTTP Request + Crypto)
Cons
- –Requires a valid Meta CAPI Access Token and Pixel ID
- –You must still send accurate user and event data from your source
- –No built-in deduplication with browser pixel events
Frequently asked questions
It receives conversion data via webhook, hashes PII, formats it, and sends it server-to-server to the Meta Conversions API.
User reviews
Verified reviews from the community shape this listing's rating.
Loading reviews…
Similar workflows
Other sales & crm automations worth a look.