What it means for your advertising
A tracking pixel runs in the visitor's browser, where ad blockers, browser privacy settings and lost connections can stop it. A Conversions API sends the same event from your side, so fewer are lost. Meta and LinkedIn each have one; Google does the same job with enhanced conversions and conversion imports.
Most setups run both, and the platform matches the two reports of each event so it's counted once. A server connection can also send results that happen later, away from your website, such as an enquiry that became a signed contract, which tells the platform which leads were worth having.
Moving tracking to a server doesn't take it outside privacy law. It usually still relies on identifiers set in the visitor's browser, so treat it like your pixel when you ask for consent (PECR).
An example
A visitor accepts cookies and sends Java Roasters an office coffee enquiry, but their browser's tracking protection stops the Meta pixel. Java Roasters' website also sends each enquiry to Meta's Conversions API from its server, so this one is still counted, and only once.
Java Roasters is a fictional business, and its figures are illustrative.
How we handle it
Our standard setup tracks conversions in the browser through Google Tag Manager, which suits most campaigns. If your website or customer system already sends conversions through an API, tell us when we plan, so each enquiry is counted once. Our guide to tracking your ad enquiries covers the setup.