Conversion tracking ad algorithms can use: Meta Conversions API and Google enhanced conversions

Ad platforms now decide who sees your ads and how much to bid, using the conversions you report. If a share of your sales or leads never reaches them, because of blocked cookies, browser restrictions or a tag that didn’t fire, they optimise on a partial picture. Meta’s Conversions API and Google’s enhanced conversions are the two standard ways to close that gap.

What each one does

Google’s documentation describes enhanced conversions as using SHA-256 hashing on customer data before it’s sent. Since April 2026, enhanced conversions for web and for leads are a single on/off setting in Google Ads, accepting data from website tags, Data Manager and API connections.

Before you start: get the basics right

Server-side tracking makes good tracking better. It doesn’t fix bad tracking. First confirm:

1. The right events exist: purchase (with value and currency) for stores; a lead or form submission for service businesses.
2. Each event fires once, on the thank-you or confirmation step, not on button clicks.
3. The conversion you optimise for is the one that matters. See ads get clicks but no sales.

Setting up Meta’s Conversions API

Option 1: your platform’s integration (recommended)

Shopify, WooCommerce and many other platforms have Meta integrations that send server events for you. Check the integration’s settings for “Conversions API” or “maximum data sharing”. This is the route for most small businesses.

Option 2: one-click setup in Events Manager

If you have a Meta Pixel, Meta lets you set up the Conversions API for website events from Events Manager with no code or setup fees.

Option 3: a custom or partner integration

For custom sites or CRM events, you send events to Meta’s API yourself or through a partner tool (an automation platform or Meta’s Conversions API Gateway). Use this when you need events the platform integrations don’t cover. For CRM stages such as “qualified” or “won”, see offline conversions explained.

Deduplication: the step people miss

If the Pixel and the Conversions API both send the same purchase, Meta must know it’s one purchase. Meta’s documented method:

• Send the same event_id from the browser Pixel (as eventID) and the server event.
• Use the same event name on both (for example Purchase).
• Meta deduplicates matching events received within 48 hours.

Platform integrations normally handle this. If you’ve built anything custom, check Events Manager’s deduplication diagnostics.

Send good customer information

The more matching information you send with server events (hashed email and phone, external ID, the fbp browser ID), the more events Meta can match to people. Events Manager shows an event match quality score for each event.

Setting up Google enhanced conversions

1. In Google Ads, go to your conversion settings and turn on enhanced conversions.
2. Choose how data is provided: your Google tag, Google Tag Manager, or a platform integration. Many store platforms and tag templates can capture the email from the order confirmation.
3. Make sure the customer data is available on the conversion page (the thank-you page usually has the order email).
4. If you hash data yourself, follow Google’s normalisation rules: trim spaces, lowercase, phone numbers in E.164 format (+9715…), then SHA-256.
5. Check the enhanced conversions diagnostics in Google Ads after a few days.

For leads that become sales offline, enhanced conversions for leads lets you upload the outcome later and match it to the original lead. See offline conversions explained.

Consent and privacy

Both features share customer data with Meta or Google, even if hashed. Before switching them on:

• Update your privacy notice to say you share data with advertising platforms for measurement.
• Respect your consent banner choices, where you use one.
• Send only what’s needed.
• In the UAE, check your obligations under the Personal Data Protection Law with your adviser. See UAE PDPL and marketing consent.

How to check it’s working

• Meta Events Manager: events from “Browser” and “Server”, deduplication status, event match quality.
• Google Ads: conversion action status, enhanced conversions diagnostics.
• Your own numbers: compare a week of platform-reported purchases with your store orders. They’ll never match exactly (see why Meta, Google and GA4 never agree), but big gaps point to tracking problems.

Frequently asked questions

Do we still need the Meta Pixel?

Yes. Meta recommends running the Pixel and the Conversions API together, deduplicated.

Will this increase our reported conversions?

Often, because events that were lost get recorded. Treat any jump as a correction to your data, and re-check your cost-per-result targets afterwards.

Is server-side tagging (a tagging server) required?

No. Platform integrations cover most small businesses. A dedicated tagging server can help with complex sites, but adds hosting and maintenance.

If you’d like your tracking audited and set up properly, that’s part of our tech stack service, working with our traffic sources service on the campaigns themselves.