Meta Conversions API: keep ad tracking accurate

Key takeaways

The Meta Conversions API sends events such as purchases and leads from your website's server to Meta, alongside or instead of the browser pixel. It recovers some events that browsers and ad blockers lose, which helps Meta optimise adverts towards real customers. It does not remove the need for consent and a lawful basis under UK law.

• Server events survive ad blockers and browser limits better.
• Run it with the pixel and deduplicate with an event ID.
• Shopify, WooCommerce and others offer built-in set-up.
• Consent and a lawful basis are still required in the UK.

What is the Meta Conversions API?

The Meta Conversions API (CAPI) is a Meta tool that lets a business send website and offline events, such as leads and purchases, directly from its server or platform to Meta, rather than only from the visitor's browser through the Meta pixel. Meta uses these events to measure and optimise adverts.

• How UK businesses can turn social media followers into customers
• The Meta pixel and UK GDPR: consent before you track

Why do small businesses use it?

Small businesses use it because browser-based tracking misses events when ad blockers, browser privacy features or short cookie lifetimes interfere. Missing events mean Meta optimises towards the wrong people and reports fewer results than happened. Server events fill some of the gap, which matters most when ad spend is optimised for purchases or leads.

• Facebook lead ads for small businesses: set-up and pitfalls

How do you set it up?

Most small businesses set it up through their platform's built-in Meta integration, such as Shopify or WooCommerce, or through Meta's partner integrations, which take minutes. Custom websites can use a server-side tag manager or a developer. Send the same event from the pixel and the server with a matching event ID so Meta counts it once.

Does the Conversions API avoid cookie consent?

No. The Conversions API changes where the event is sent from, not whether you may send it. Sending personal data such as hashed emails or browsing events to Meta for advertising needs a lawful basis under UK GDPR, and the pixel or cookies that identify a visitor still need consent under PECR. Respect the visitor's cookie choice in both.

• Cookie banners and UK law
• GDPR and social media marketing in the UK

How do you know it is working?

Check Meta Events Manager. It shows events received from the browser and the server, whether they are deduplicated, and an event match quality score. Compare purchases reported by Meta with your shop's actual orders over a month: the gap should narrow but never disappear.

When is it not worth the effort?

It is not worth much effort if you spend little on Meta adverts, if most sales happen by phone or message, or if you are not optimising adverts for website events. A service business taking enquiries by WhatsApp gains more from replying faster than from server tracking.

• Click-to-WhatsApp ads: start sales chats from an advert

What does this look like in practice?

A pattern we see in e-commerce: Meta reports far fewer purchases than the shop records, so campaigns are cut. Turning on the platform's Conversions API integration with deduplication usually narrows the gap and gives Meta better signals to work with.

• See client work
• Social Media Marketing for UK businesses
• The follower conversion scorecard: find where buyers drop out

Conversions API checklist

• Decide whether your ad spend justifies it.
• Use your platform's integration if available.
• Send matching event IDs from pixel and server.
• Respect cookie consent choices.
• Update your privacy notice.
• Compare Meta's figures with real orders monthly.

Next step

Compare last month's purchases or leads in Meta Ads Manager with your own records. A big gap is the case for the Conversions API.