Conversion API
Server-side conversion tracking
How it works
A pixel reports conversions from the visitor's browser. Ad blockers, browser tracking protection and missing consent stop part of those reports. A Conversion API sends events from server to server instead: your website, your CRM or a tracking tool sends the event to the platform together with identifiers such as a hashed email address or a click ID. The platform then matches it to the right user and ad click.
Almost every major ad platform has one, each under its own name: Meta (Conversions API), Google Ads (conversion import, for example through the Data Manager API), TikTok (Events API), LinkedIn (Conversions API), Microsoft Ads (UET Conversions API) and Snapchat (Conversions API).
Why it matters
Bidding algorithms only learn from the conversions that reach them. If some are missing because the browser blocked them, the campaign gets fewer signals and optimizes less precisely. On top of that comes everything a pixel can never see: a deal won in the CRM two weeks later, or a payment by invoice. Through the Conversion API the platform learns about those too, and can look for people who become customers rather than people who fill in forms.
TSO sends conversions to the APIs of Meta, Google Ads, TikTok, LinkedIn, Microsoft Ads, Snapchat and ChatGPT Ads, and to Meta also the CRM stages used for lead optimization.
Example
A contractor gets 100 inquiries a month through the website form. The Meta pixel reports only 78 of them; the rest are lost to ad blockers and browser restrictions. With the Conversion API, all 100 leads reach Meta. How many of them Meta can match to a user depends on the data sent along.
The contractor also reports the 12 jobs that come out of those inquiries in the CRM. Now Meta sees not only which ads bring inquiries but which ones bring paying jobs, and can optimize for exactly those people.
Common mistakes
- Counting twice: if pixel and server send the same event without a shared event ID, the platform counts it twice and the campaign looks better than it is.
- Sending too few identifiers: an event without email, phone, click ID or browser cookie can't be matched to anyone. In Meta, event match quality shows how well matching works.
- Only sending the lead: the biggest gain is in the later stages. If you only send the form submission, you're using the API as a slightly sturdier pixel.
- Ignoring consent: server-side doesn't mean consent-free. Which data you may send without consent is a question for your data protection counsel.
How TSO handles it
Frequently asked questions
Do I still need the pixel if I use a Conversion API?
In most cases, yes. The pixel provides signals that only exist in the browser, such as cookies and click IDs. The platforms recommend running both side by side and deduplicating them with a shared event ID.