Conversion API
CAPI
In short
A Conversion API (CAPI) is an interface that sends conversions directly from server to server to ad platforms like Meta or Google, without the browser.
Also known as: Conversions API, Meta Conversions API
A Conversion API (CAPI for short) is an ad platform interface that lets you send conversions directly from your server to the platform – without going through the user's browser. The best known is the Meta Conversions API; Google Ads, TikTok and LinkedIn offer comparable interfaces. How they differ in match keys, lead events and time limits is covered in our article conversion APIs compared.
How the Conversion API works
Instead of a tracking pixel firing in the browser, your server (or a tool) sends an API request to the platform. It contains:
- Event: e.g. lead, purchase or closed deal
- Timestamp and optionally value and currency
- Matching data: click IDs like fbclid (or the
fbcvalue derived from it) or gclid, plus email address, phone number and name pseudonymized with hashing (SHA-256) - Event ID: for event deduplication with the pixel
The more matching data you send, the better the platform can match the event to a user and thus to an ad click. Meta rates this with its Event Match Quality score.
Example
An insurance broker generates 300 leads a month from Meta, 24 of which become customers. The pixel only reports the leads it sees in the browser. Through the Conversion API, the 24 closed deals are also sent – with the commission as value, weeks after the click. Meta learns which audiences actually bring in customers instead of just optimizing for cheap leads.
Conversion API for lead generation
The biggest lever is offline conversions: deals closed in the CRM and payments never happen in the browser and can only be reported through a Conversion API. Value-based bidding needs exactly these values.
With the LeadMetrics Conversion API you send leads, purchases, trials, subscription events, won or lost deals and custom metrics to Meta, Google Ads, TikTok and LinkedIn. Per project you decide which LeadMetrics event maps to which platform event, and whether only attributed data or (for Meta and TikTok) all data is sent. Data comes from sources like HubSpot or Stripe, and every lead has a log of the events sent.
Common mistakes
- No event ID: Pixel and CAPI send the same event and the platform counts it twice.
- Unhashed data: Contact data must be normalized and hashed before sending.
- Only sending leads: If you don't report the closed deal, you're giving away your most valuable signal.
Ready for better tracking?
Frequently asked questions
Guides on this topic
AI Marketing Team for Lead Generation: What Agents Can Take Over - and What Data They Need
What an AI marketing team of agents for research, ads, inbox and analysis can do, where humans need to stay in the loop and why, in lead generation, it optimizes for the wrong leads without CRM data.
Read guideHow to Improve Meta Event Match Quality: What Data to Send
How to improve Event Match Quality in Meta: which customer data counts, how to normalize and hash it, and how fbc, fbp and event_id help your score.
Read guideMeasure Real ROAS in Lead Generation: From Click to Closed Deal
How to measure real ROAS in lead generation: attribute CRM revenue to campaigns, read CPL, CPA and ROAS correctly and send deal values back to Meta and others.
Read guideArticles on this topic
- Fake Leads from Google and Meta Ads: Where They Come From and What HelpsBots, made-up numbers, accidental taps: why Google's and Meta's filters don't stop fake leads, which form safeguards work and how to optimize for real leads instead.
- Performance Max for Lead Generation: How to Rein In Display Leads with Channel PrioritizationSince October 2026, Performance Max lets you set the Display Network and Search partners to low priority and cap their budget. How channel prioritization works and how to use it for better leads.
- AI Agents in DMs: How to Keep Leads from Chats MeasurableTikTok is testing an AI agent that qualifies leads in direct messages, and Meta offers Business Agent for WhatsApp, Messenger and Instagram. What the agents do, why chat leads often go missing in reporting and how to attribute them all the way to the deal.
- Measuring Incrementality: Do Your Ads Really Bring Additional Leads?Google has opened Conversion Lift studies for Search and Performance Max without a Google rep. What incrementality means, why attribution doesn't show it and how to check it in lead generation, even with low volume.
Related terms
All termsServer-Side Tracking
Server-side tracking sends tracking data to ad and analytics platforms from a server instead of the browser – more robust and under your control.
Tracking Pixel
A tracking pixel is a snippet of code from an ad platform that captures page views and conversions in the browser and reports them to Meta, Google and others.
Event Deduplication
Event deduplication makes sure a conversion sent through both the pixel and the Conversion API is only counted once by the ad platform.
Event Match Quality
Event Match Quality (EMQ) is a Meta score from 0 to 10 that rates how well your server events can be matched to a Meta account using customer data.
Offline Conversions · Reporting deals that happen off your website back to ad platforms
Offline conversions are conversions that don’t happen on your website – like a closed deal in your CRM – and are sent back to ad platforms like Meta.
Client-Side Tracking
Client-side tracking captures user actions with JavaScript directly in the browser and sends them from there to analytics and ad platforms.