> Quick answer: The Conversions API connects your server directly to Meta's ad systems. Three setup paths exist: Gateway (code-free), partner integrations (Shopify, WooCommerce), and direct API code. Each needs a Pixel ID, Business Manager access, and an access token from Events Manager.
Browser tracking alone misses conversions. Ad blockers, iOS privacy changes, and cookie restrictions all create gaps. The Conversions API fills those gaps with server-side data that lands directly in Meta's systems.
---
What Is Conversions API and Why Set It Up?
The Conversions API sends conversion events from your server to Meta instead of relying on a user's browser.
How Conversions API differs from Meta Pixel
Meta Pixel runs in the browser. It captures events when a user loads a page. Ad blockers, browser restrictions, and network issues can block it. The Conversions API runs server-side. Nothing blocks it. Per Meta's developer documentation, server events are processed identically to browser-based Pixel events for measurement, reporting, and optimization.
Why server-side tracking improves campaign performance
More complete event data means better optimization signals. Meta's ad systems use conversion data to find the right audiences and bid more efficiently. Gaps in your tracking create gaps in that signal.
When to use Conversions API vs. Meta Pixel vs. both
Use both. Meta recommends running the Conversions API alongside your Meta Pixel, not instead of it. Browser events capture fast, real-time signals. Server events fill the gaps. Together, they give Meta the most complete picture.
---
Prerequisites. What You Need Before Starting
You need three things before touching any setup steps.
Business Manager account and permissions
You need a Meta Business Manager account with admin access to the ad account or dataset you plan to use. Without those permissions, you cannot generate tokens or configure Events Manager.
Meta Pixel ID
Your Pixel ID is your dataset ID. It ties server events to the right ad account. Find it in Events Manager under your connected data sources.
Cloud environment (for Gateway) or developer resources (for direct)
The Gateway method needs a cloud account on AWS or GCP. The direct API method needs a developer who can write and deploy server-side code.
Network and firewall considerations
Per Meta's policy documentation, firewall-restricted businesses must allowlist Meta's IP addresses for outbound requests. That IP list changes frequently. Check it periodically and update your allowlist.
---
Three Ways to Set Up Conversions API
Pick the method that matches your team and tech stack.
Option 1. Conversions API Gateway (code-free, self-serve)
No coding required. You deploy a pre-built Gateway to your cloud environment. AWS EKS, AWS App Runner, and GCP GKE are all supported. Per Meta's documentation, setup time drops from weeks to hours. The Gateway auto-updates when Meta ships new features.
Option 2. Partner integrations (Shopify, WooCommerce, Google Tag Manager)
If you run on a supported e-commerce or CMS platform, a partner integration handles the heavy lifting. You authenticate, grant permissions, and map your Pixel. No server configuration needed.
Option 3. Direct API integration (custom code)
Full control. Your dev team sends HTTP requests directly to the Conversions API endpoint. Best for businesses with complex data requirements or custom tech stacks.
---
How to Set Up Conversions API Gateway (Step-by-Step)
The Gateway is the fastest path for most businesses without dedicated engineering resources.
Generate an access token in Events Manager
Go to Events Manager. Select your Pixel. Click Settings. Under the Conversions API section, generate an access token. Per Meta's developer documentation, tokens generated here work with all Graph API versions from v12.0 onward. No App Review or special permissions required.
Select your cloud provider (AWS or GCP)
Choose AWS EKS, AWS App Runner, or GCP GKE. Have your cloud credentials ready. The Gateway wizard walks you through provisioning from inside Events Manager.
Deploy the Gateway to your cloud environment
Follow the on-screen deployment steps in Events Manager. The wizard provisions the infrastructure in your cloud account. You own the environment. Meta does not store your data.
Configure your Meta Pixel to send events to the Gateway
After deployment, Events Manager gives you a Gateway endpoint. Point your Pixel to that endpoint. The Gateway forwards events to Meta and handles deduplication automatically.
Test event flow and verify setup
Use the Test Events tool in Events Manager. Send a test conversion. Confirm it appears in the dashboard. Check that the event carries the correct parameters before going live.
---
How to Set Up Conversions API Through a Partner
Partner integrations are ideal if you run Shopify, WooCommerce, or another supported platform.
Find your platform in the partner gallery
Open Events Manager. Select your dataset. Click "Add Events" and choose "From a Partner." Browse the gallery to find your platform.
Authenticate and grant permissions
Log in to your platform account when prompted. Grant the integration the permissions it needs to read order and customer data.
Map your Meta Pixel to the partner integration
Select the Pixel ID you want to associate with the integration. Confirm the mapping. The integration starts sending server events immediately.
Verify events are flowing
Check Events Manager within 24 hours. You should see server events alongside your browser Pixel events. Match quality scores appear once enough events are processed.
---
Getting Started with Direct API Integration
This path is for developers who need full control over event data and payloads.
Prerequisites for developers
You need server-side code, a valid access token, and your dataset ID. Your server must make outbound HTTPS POST requests to Meta's Graph API.
Generating an access token for direct use
Generate the token in Events Manager, same as the Gateway method. Or create one through a custom app in Meta's developer console. Events Manager tokens are simpler and require no App Review.
Making your first API request
Send a POST request to the Conversions API /events endpoint, passing your dataset ID, access token, and event payload. Include customer information fields. email, phone, and IP address. More match fields improve event quality scores.
Testing and debugging
Use the `test_event_code` parameter to send test events without affecting live reporting. View results in the Test Events tab inside Events Manager. Confirm all required parameters are present before deploying to production.
---
Verify Your Setup and Monitor Events
A live setup is not a verified setup. Confirm everything is working correctly.
Use Events Manager to confirm events are received
Open Events Manager and check your dataset's activity feed. Events should appear within minutes of being sent. Look for both browser and server event types in the same view.
Check deduplication between Pixel and Conversions API
If you run both browser Pixel and server Conversions API, Meta deduplicates automatically when you use the same Pixel ID. The Gateway handles this out of the box. For direct integrations, pass a consistent `event_id` across both browser and server events.
Monitor event match quality
Events Manager shows a match quality score for each event type. Higher scores mean better audience matching and optimization. Add more customer information fields to improve your scores over time.
Troubleshoot dropped or mismatched events
Low match quality usually means missing or incorrectly hashed customer data. Dropped events often trace to network issues or misconfigured endpoints. Check the Diagnostics tab in Events Manager for specific error codes and recommended fixes.
---
Best Practices for Conversions API Setup
Follow these principles to get the most out of your integration.
Use the same Pixel ID for browser and server events
Per Meta's best practice guidance, one Pixel ID for both sources keeps your dataset clean and simplifies reporting.
Implement deduplication to avoid double-counting
Pass a consistent `event_id` from both your browser Pixel and your server. Meta uses it to remove duplicate events before they reach your reporting.
Send customer information for better event matching
Email, phone number, first name, last name, and IP address all improve match quality. Hash all PII before sending. Meta accepts SHA-256 hashed values.
Test in a staging environment before production
Fire test events using your staging environment before going live. Confirm all event types and parameters are correct. Only then push to production.
---
Or let Coinis do it.
From a product URL to a live Meta campaign. AI-generated creatives. On-brand copy. Direct publish to Facebook and Instagram. Real performance reporting. All in one platform.
Start free. Upgrade when you're ready.
15 AI tokens a month. No credit card.
Frequently Asked Questions
What is the difference between Meta Pixel and the Conversions API?
Meta Pixel runs in the user's browser and can be blocked by ad blockers, iOS restrictions, or network issues. The Conversions API sends events from your server directly to Meta, so nothing in the browser can block it. Per Meta's developer documentation, both types of events are processed identically for reporting and optimization. Running them together gives Meta the most complete tracking signal.
Do I need coding skills to set up the Conversions API?
Not necessarily. The Conversions API Gateway is a code-free, self-serve option available directly in Events Manager. You provision it to your own cloud environment (AWS or GCP) without writing any code. Partner integrations for platforms like Shopify or WooCommerce also require no coding. Only the direct API integration method requires developer resources.
Does the Conversions API replace the Meta Pixel?
No. Meta recommends running both together, not replacing one with the other. Browser events from Meta Pixel capture fast, real-time signals. Server events from the Conversions API fill the gaps created by ad blockers and privacy restrictions. Using the same Pixel ID for both lets Meta deduplicate events automatically.
What is event deduplication and why does it matter?
Deduplication removes duplicate conversion events when both your browser Pixel and your Conversions API fire for the same user action. Without it, one purchase could be counted twice, inflating your reported conversions and distorting optimization. The Conversions API Gateway handles deduplication automatically. For direct integrations, pass a consistent event_id in both your browser and server events so Meta can match and remove duplicates.