Do you need server-side tracking and the Conversions API?

What is server-side tracking?

Normally a purchase is recorded by a tag running in the customer’s browser, such as the Meta Pixel or the Google tag. Server-side tracking sends the same purchase information from your store’s server, or from a server you control, directly to the ad platform. Because it doesn’t rely only on the customer’s browser, fewer purchases go missing.

What is the Meta Conversions API?

The Conversions API is Meta’s way of receiving events from a server instead of a browser. It is designed to run alongside the Meta Pixel, not replace it. The pixel and the server both send the purchase, and Meta keeps one.

On Shopify, the Facebook & Instagram app sets this up for you. Its “Enhanced” and “Maximum” data-sharing levels use the Conversions API as well as the pixel; “Standard” uses the pixel only.

How do you avoid counting each order twice?

This is where most set-ups go wrong. Meta only treats a browser event and a server event as the same purchase when:

• the event name matches (for example, both are “Purchase”), and
• the event ID matches, usually the order ID or a shared ID created at checkout.

Meta deduplicates matching events received within 48 hours of each other. If the IDs don’t match, or one side sends no ID, both events count and your reported sales jump. A sudden rise in Meta purchases after switching on server-side tracking, with no rise in store orders, is the classic sign.

What about Google?

Google offers two main ways to recover lost signals:

• Enhanced conversions send hashed customer details, such as email address, with each purchase so Google can match more orders to ad clicks.
• Google tag gateway serves Google’s tags from your own domain instead of Google’s, so fewer are blocked. If your site already runs through Cloudflare, it can be switched on there at no extra cost.

Full server-side tagging through a Google Tag Manager server container is also an option for larger stores, but it adds hosting and maintenance. For many stores, the platform apps plus enhanced conversions cover most of the gain.

Is it worth it for a small store?

If you’re on Shopify and already using the official Meta and Google apps, switching on the built-in options is low effort and usually worth doing. A custom server-side set-up is worth it when ad spend is meaningful, purchase volumes are steady, and you can see a real gap between platform conversions and store orders.

Whatever you choose, consent still applies: if your site asks visitors for cookie consent, server-side tracking should respect their choice.

How do you know it’s working?

1. Compare platform purchases with store orders for the same period, before and after the change.
2. In Meta Events Manager, check that browser and server purchase events show as deduplicated, and that event match quality is reasonable.
3. Check a handful of individual orders appear once, with the right value.

Platform settings and defaults change often. This guide reflects Google Ads, Meta and Shopify as at 14 November 2026. For the short version, see the related FAQ answer.