It’s no secret that tracking your Meta Ads results has become more challenging over the years. Privacy regulations, browser restrictions, ad blockers and changes such as Apple’s App Tracking Transparency have all made it harder to get a complete picture from browser-side tracking alone.
Whilst this may seem discouraging, there's something you can do to improve the quality and reliability of the data you send to Meta.
That’s where Meta Conversions API (CAPI) comes into play.
What is Meta Conversions API?
Conversions API is designed to create a more direct connection between your marketing data and Meta.
Simply put, it allows you to send marketing and conversion data directly to Meta from your server, website platform, app or CRM, rather than relying only on what can be tracked through someone's browser.
This can help improve measurement, attribution and the signals Meta uses to optimise your campaigns.
What’s the difference between Conversion API and Meta Pixel?
Meta Pixel is a browser-side tracking tool that helps you track actions people take on your website, such as viewing a page, submitting a form or making a purchase.
The problem? Browser-side tracking has limitations. Think privacy settings, cookie restrictions, ad blockers and changes introduced by Apple and other platforms.
Conversions API works differently. Instead of relying only on someone's browser, data can be sent to Meta directly from your server or another data source.
That makes it less affected by browser-side issues such as ad blockers and cookie restrictions. But—and this is important—CAPI is not a way to bypass privacy rules or user consent. You still need to make sure the data you collect and send complies with applicable privacy laws and Meta's requirements.
The way to look at it is that Conversions API complements the Meta Pixel. For website campaigns, Meta generally recommends using the two together rather than choosing one or the other.
How can Meta Conversions API and Meta Pixel work together?
Let's say someone clicks on your Meta ad and submits a form on your website.
The same conversion may be sent to Meta from the browser through the Pixel and from your server through Conversions API.
You may wonder: won't Meta count that conversion twice?
Nope.
When the browser and server events are set up correctly with matching event information, Meta can recognise that they represent the same action and deduplicate them.
If the browser-side event doesn't make it through, the server-side event may still provide Meta with information about the conversion.
That doesn't mean CAPI magically captures every conversion that would otherwise be lost. But combining browser and server-side data can give Meta more reliable signals than relying on the Pixel alone.
And better data isn't useful only for reporting. These signals also help Meta understand which people are taking valuable actions and optimise your campaigns accordingly.
What does Facebook Conversion API track?
Conversions API can send many of the same events you already use with the Meta Pixel.
These can include actions such as:
- Page views
- Leads
- Registrations
- Purchases
- Add to cart
- Checkout
- Subscriptions
- Search
You can also send custom events relevant to your business.
And CAPI isn't limited to what happens on your website. Depending on your setup, data can also come from sources such as your CRM, app, physical store or other offline activity.
This is one of the reasons CAPI can give you a better understanding of what happens after someone becomes a lead.
Let's say your Meta ad generates 20 leads but only three eventually become paying customers. If your CRM and Conversions API setup sends that information back to Meta, you can give Meta a much more valuable signal than simply telling it that someone filled out a form.
How to set up Meta Conversions API for your WordPress site?
Good news: you don't necessarily need to build a server-side integration from scratch.
Meta supports different ways of setting up Conversions API, including partner integrations, Conversions API Gateway and direct integrations. Which option makes sense depends on your website platform and setup.
For a WordPress website, a partner integration or compatible plugin is usually the easiest place to start.
#1 Check your current Meta Pixel setup
Before adding CAPI, check that your Meta Pixel and the events you actually want to measure are set up correctly.
Head to Meta Events Manager, select your data source and check which events Meta is currently receiving.
While having a Pixel isn't technically required to use Conversions API, for most website advertising setups you'll want Pixel + CAPI working together.
#2 Choose how you want to connect Conversions API
In Events Manager, Meta provides different setup options depending on your website and data source.
For WordPress, look for an available partner integration or use a WordPress plugin that supports Meta Pixel and Conversions API.
If your setup is more complex, you can also use Conversions API Gateway or build a direct integration.
#3 Connect your website and Meta account
Follow the instructions for the integration you've chosen. You'll typically need to connect the relevant Meta Business account, dataset/Pixel and website.
The exact steps will vary depending on your WordPress setup and the integration you're using.
#4 Test your events
Don't stop at “connected successfully”.
Head back to Events Manager and check that your events are actually being received correctly.
Pay attention to whether browser and server events are being deduplicated, whether the right events are firing and whether Meta is receiving enough information to match those events accurately.
Meta also provides an Event Match Quality indicator, which can help you identify whether there are opportunities to improve the customer information sent with your events.
And that’s it! Your Conversions API setup is up and running.
Conclusion
Conversions API has gone from being something advertisers started talking about after iOS 14 to becoming an important part of a more reliable Meta Ads tracking setup.
It won't solve every tracking problem, and it doesn't replace the Meta Pixel or your privacy obligations. What it can do is give Meta better-quality data for measurement, attribution and campaign optimisation when used alongside your existing browser-side tracking.
If you're spending money on Meta Ads and conversions on your website actually matter to your business, it's worth making sure your tracking setup is sending Meta the best data it reasonably can.
Need help with the setup or your Meta advertising? Get in touch with us.
