"Server-side tracking" and "Conversions API" get used interchangeably, as if they were the same thing. They aren't. One is infrastructure, the other a specific platform's interface. Once you get the difference, the whole topic suddenly makes sense.
Server-side tracking = infrastructure
Server-side tracking is how you measure: data from the site goes to your server-side GTM container on your domain, which then forwards it onward. It's a general approach, not one platform's tool. Underneath it, measurement runs for GA4, Meta, Google Ads and others at once.
Conversions API = a platform interface
A Conversions API (CAPI) is one platform's specific server-to-server interface for sending it conversions. Meta has the Conversions API, TikTok has the Events API, Pinterest has the Conversions API. It's the "door" a conversion enters that platform through. See the overview in the docs: what a Conversions API is.
How they relate
The relationship is simple: server-side tracking is the overarching infrastructure, and a Conversions API is one of the destinations you send data to from it. The server-side GTM container takes an event from the site and sends it to Meta via its Conversions API, to GA4 via the Measurement Protocol, to Google Ads via their interface — all from one place.
- You can run a Conversions API without full server-side GTM (direct calls), but you lose central control and reliability.
- Server-side GTM with no API connections would have nowhere to send — the APIs are its outputs.
- In practice they go hand in hand: server-side tracking as infrastructure, Conversions APIs (and similar interfaces) as destination gateways.
And the pixel?
The pixel is client-side (it runs in the browser). The Conversions API is its server-to-server counterpart. The recommended practice is to run the pixel and the Conversions API together with deduplication — details in the Meta Conversions API guide.
Summary
Server-side tracking is "how you measure" (infrastructure); a Conversions API is "where you send it" for a specific platform (an interface). They aren't rivals or synonyms — server-side tracking typically uses a Conversions API as one of its outputs. The full picture is in the complete guide to server-side tracking.