What Is CAPI Tracking? A Complete Guide for Marketers

If your Meta or TikTok reporting suddenly looks worse than your actual sales, the problem probably isn’t your ads, it’s your tracking. This is exactly the gap that CAPI tracking closes. Conversions API (CAPI) tracking sends conversion data straight from your server to an ad platform, instead of relying on a browser pixel that iOS updates, ad blockers, and cookie restrictions increasingly interfere with.

Without it, you’re stuck guessing how many sales your pixel actually missed. In this guide, we’ll break down what CAPI tracking is, how it works, which platforms support it, and how to set it up so your ad platforms finally see the full picture.

What Is CAPI Tracking?

CAPI tracking (short for Conversions API tracking) is a server-to-server method of sending conversion data, like purchases, leads, or sign-ups, directly from your business’s server to an ad platform such as Meta, Google, or TikTok. Instead of depending on a cookie or a script running in someone’s browser, your server reports the event straight to the platform’s API endpoint.

The term “CAPI” originally comes from Meta’s Conversions API, released in 2020, but it’s now used loosely to describe any server-side conversion API, including the versions offered by Google, TikTok, Snapchat, Reddit, Pinterest, LinkedIn, and Microsoft Advertising. In practice, CAPI tracking is rarely used on its own. Most advertisers run it alongside their existing browser pixel, then deduplicate the two data sources so every conversion is counted once, not twice.

How Does CAPI Tracking Work?

At a basic level, CAPI tracking follows the same pattern regardless of which ad platform you’re sending data to:

• A conversion happens. Someone completes a purchase, submits a form, or signs up on your website or app.
• Your server captures the event. Details like the event name, timestamp, order value, and any available identifiers (email, phone number, click ID) are collected on your backend, not the user’s browser.
• Identifiers get hashed. Personal data like emails and phone numbers is converted into SHA-256 hashes before it ever leaves your server, so the platform never receives raw personal information.
• The event is sent via API. Your server sends a POST request containing the hashed data directly to the ad platform’s Conversions API endpoint.
• The platform matches the event. Using the identifiers you sent, the platform connects the server-side conversion back to the original ad click or impression, then feeds that data into its optimization algorithm.

Because none of this depends on a script loading in the browser, CAPI tracking keeps working even when a user has an ad blocker installed, rejects cookies, or browses in a privacy-restricted mode like Safari’s Intelligent Tracking Prevention.

The strength of that match depends heavily on how many identifiers you’re able to send. Most platforms accept a combination of hashed emails, hashed phone numbers, external IDs, IP addresses, user agents, and click IDs, such as Meta’s fbc and fbp parameters.

Sending several of these together, rather than relying on just one, is what actually moves match rates in practice. For the full, current list of accepted parameters and event types, Meta’s own Conversions API documentation is worth bookmarking, since platforms tend to update these requirements over time.

Why CAPI Tracking Matters for Advertisers

Browser-based tracking has been losing accuracy for years, and CAPI tracking exists specifically to close that gap. A few concrete reasons it matters:

• Recovers missed conversions. Pixels alone miss conversions from ad blockers, disabled JavaScript, and browsers with strict privacy settings. CAPI tracking captures those events from the server side instead.
• Improves algorithm optimization. Ad platforms optimize delivery based on the conversion data they receive. If that data is incomplete, the algorithm learns from a biased sample and can undervalue campaigns that are actually performing well.
• Extends attribution windows. Cookie-based attribution typically breaks down after a matter of days. Server-side data isn’t tied to cookie lifespan, so it holds up better across longer sales cycles.
• Supports offline and CRM events. CAPI tracking isn’t limited to on-site actions. It can also report offline conversions, like a sale closed over the phone, back to the ad platform.
• Keeps data flowing as privacy rules tighten. Since personal identifiers are hashed and consent still applies, CAPI tracking gives advertisers a compliant way to keep measuring performance as cookies and device IDs become less available.

This is also a big part of why your ad platform’s dashboard rarely matches your tracker’s numbers exactly. Different attribution windows, counting methods, and tracking sources will always create some gap between what each system reports.

Picture a Safari user who blocks third-party cookies by default. They click your Meta ad, land on your site, and complete a $150 purchase ten minutes later. With pixel-only tracking, there’s a real chance that conversion never makes it back to Meta at all, since Safari’s tracking prevention limits how long tracking data survives in the browser. With CAPI tracking running alongside the pixel, your server captures that same purchase and reports it directly to Meta’s API, regardless of what happened in the browser.

CAPI Tracking vs. Pixel Tracking: What’s the Difference?

Most advertisers don’t have to choose one over the other, but it helps to understand how the two methods actually differ:

Aspect	Pixel Tracking	CAPI Tracking
Data source	User’s browser	Your server
Affected by ad blockers?	Yes	No
Affected by cookie restrictions?	Yes	No
Setup complexity	Low (one script tag)	Higher (server-side integration)
Can track offline events?	No	Yes
Recommended use	Run alongside CAPI	Run alongside pixel, with deduplication

Meta, and most other platforms, actively recommend running the pixel and CAPI tracking together rather than picking one. When both are set up with proper event deduplication, you get the best of both: the pixel’s speed and simplicity, plus the reliability of server-side data. Our guide on what a postback URL is covers the older server-to-server method that CAPI tracking has largely replaced for platforms that support it.

Which Platforms Support CAPI Tracking?

Nearly every major ad platform has released its own version of a Conversions API over the past few years. Here are the ones you’ll encounter most often:

Platform	API Name
Meta (Facebook & Instagram)	Meta Conversions API
Google	Enhanced Conversions / Offline Conversion Import
TikTok	TikTok Events API
Snapchat	Snapchat Conversions API
Reddit	Reddit Conversions API
Pinterest	Pinterest Conversions API
LinkedIn	LinkedIn Conversions API
Microsoft Advertising (Bing)	Conversions API for UET

Each platform has its own documentation, required parameters, and event-matching logic, so an integration built for Meta won’t automatically work for TikTok or Snapchat. If you’re focused on Meta specifically, our full guide to the Facebook Conversion API walks through the setup in detail, and our TikTok Events API guide does the same for TikTok.

How to Set Up CAPI Tracking

There are generally three ways to implement CAPI tracking, depending on your technical resources:

• Custom server-side development. Your developers build a direct integration with each platform’s API. This gives you full control but takes the most time and budget to build and maintain, especially if you’re running ads on more than one network.
• Server-side tag management. Tools like server-side Google Tag Manager let you route events through your own server container before forwarding them to ad platforms, without writing a full custom integration.
• A tracking platform with built-in CAPI support. Tools like ClickFlare handle the server-side connection for you. You connect your pixel and access token for each platform, map which events to send, and the tracker takes care of formatting and delivering the data through the correct API.

Whichever route you take, the core setup steps look similar:

1. Generate a pixel ID and access token from the ad platform’s events manager.
2. Define which events you want to send (purchase, lead, sign-up, and so on).
3. Map the data fields you want to include with each event, such as order value, currency, or hashed email.
4. Set up event deduplication if you’re also running the platform’s pixel, usually with a shared event ID.
5. Test the integration using the platform’s test events tool before sending live data.

If you’d rather not build and maintain a custom integration for every platform you advertise on, a tracking platform with built-in CAPI support can handle most of this for you. Here’s what that actually looks like in practice.

ClickFlare’s CAPI Tracking Features

If you’re evaluating tools to handle CAPI tracking without building a custom integration, here’s what ClickFlare’s Conversion API Integrations include:

• Native integrations for 9 platforms. Connect Meta, Google Ads, TikTok, Microsoft Advertising (Bing), Snapchat, Reddit, Pinterest, LinkedIn and SmartNews from the same Integrations tab, without touching a server or writing code.
• Event Type Mapping. Map any ClickFlare-tracked event, standard or custom, to each platform’s own event names, so a “Sale” in ClickFlare can be sent as “Purchase” on Meta and under a different event name on another platform.
• Event filters. Control exactly which conversions get sent back, for example only sending events above a certain payout, from a specific country, or on a specific device, so low-quality conversions never reach your ad account.
• Built-in deduplication support. ClickFlare lets you map a shared event identifier (its click and transaction ID token) so platforms like Meta can match pixel and CAPI events to the same conversion instead of counting it twice.
• Workspace-level access control. CAPI integrations can be scoped to specific workspaces, so only the right team members or clients see and use a given integration.
• Included on every plan. Unlike trackers that gate Conversion API access behind their most expensive tier, ClickFlare includes it starting on its entry-level plan.

In practice, this means setting up CAPI tracking for a new platform is a matter of pasting in a pixel ID and access token, mapping your events, and saving, rather than writing and maintaining server-side code for every ad network you run.

ClickFlare’s CAPI Tracking Guide

Setting up CAPI tracking in ClickFlare is very simple.

You need to go to Integrations, select Conversion API, and choose the platform you wish to send data to from the list.

First, you need to set up the basic settings of the integration, such as giving it a name, assigning it to a workspace, and determining the action source (for example, Website).

Next, you need to connect the actual ad network pixel. This part may vary slightly from platform to platform, but for most ad networks you need to input the pixel name (as it is shown on your account), the pixel ID (a string of numbers), and the access token (which you need to generate from your ad account).

You have the option to enable test mode. You can enable this option if you want to test the integration, using the test code under your pixel.

Under Event Type Mapping, you need to decide which ClickFlare events you will be posting to your ad network, and which event you will be matching them to. In the below example, we are sending ClickFlare Leads as “Lead” in Facebook, and Sale as “Purchase”.

Under Event Data Configuration, you can configure which parameter you’re going to post. ClickFlare automatically includes required parameters in the CAPI payload, such as click ID, country, IP address, and external ID. These are required by the ad network, so you cannot remove or edit them.

You can send additional events, such as email addresses and phone numbers. ClickFlare already includes a deduplication parameter to prevent your conversions from being sent twice.

With ClickFlare’s CAPI tracking, you can also apply an event filter. In order to control your event quality in your pixel, you can apply specific filters. For example, you can select to only send events coming from the United States, or only events with a payout greater than 20. You can choose from a number of filters, and you can apply multiple filters simultaneously.

Common CAPI Tracking Challenges to Watch For

• Duplicate conversions. Running CAPI tracking alongside a pixel without proper deduplication will inflate your reported conversions. Always pass a matching event ID from both sources. With ClickFlare, this is already built-in.
• Poor event match quality. The more identifiers you send (hashed email, phone number, click ID), the higher your match rate. Sending only one identifier often leads to weaker attribution. ClickFlare allows you to send multiple identifiers.
• Missing consent handling. CAPI tracking still involves personal data, so it still requires a valid legal basis and proper consent management, the same as any other tracking method. Under regulations like the GDPR, that generally means explicit consent before you collect and transmit the data at all. You can find the full breakdown of what’s required on GDPR.eu’s guide to cookies.
• Sending bad data. Without validation, failed payments, test orders, or internal team conversions can end up in your reported data, skewing optimization. Filtering events before they’re sent solves this.
• Treating it as set-and-forget. Match rates and event delivery should be monitored on an ongoing basis, not just checked once at launch.

How to Choose the Right CAPI Tracking Tool

If you’d rather not build a custom integration from scratch, here’s what to look for in a tracking platform:

• Which platforms does it support? Make sure it covers every ad network you actually run traffic on, not just Meta and Google.
• Can you control which data gets sent? Look for event mapping and filters, so you can exclude low-quality conversions before they reach your ad platform.
• Does it handle deduplication? This should be built in, not something you have to engineer yourself.
• Is it included in your plan, or gated behind an add-on? Some trackers lock CAPI tracking behind their highest, most expensive tiers.

If you’re comparing options more broadly, our breakdown of the best ad tracking software in 2026 covers pricing, integrations, and which tool fits which type of advertiser.

Final Thoughts on CAPI Tracking

So, what is CAPI tracking, in short? It’s the server-to-server method that lets you send conversion data directly to Meta, Google, TikTok, and other ad platforms, without depending on a browser cookie that might get blocked. As privacy restrictions keep tightening, CAPI tracking has moved from “nice to have” to a near-requirement for anyone running paid traffic seriously. The advertisers seeing the most consistent performance today are the ones combining pixel tracking with CAPI tracking, and monitoring both closely.

Frequently Asked Questions

What is CAPI tracking used for?

CAPI tracking is used to send conversion events, like purchases, leads, or sign-ups, directly from your server to an ad platform, so campaigns can be measured and optimized even when browser-based tracking is blocked or restricted.

Is CAPI tracking the same as pixel tracking?

No. Pixel tracking sends data from the user’s browser, while CAPI tracking sends data from your server. Ad platforms recommend running both together, with deduplication, for the most complete data.

Do I need a developer to set up CAPI tracking?

Not necessarily. Building a custom integration requires development work, but tools with built-in CAPI support, like ClickFlare, let you connect your pixel and access token without writing any code.

Is CAPI tracking GDPR compliant?

CAPI tracking can be GDPR compliant, but it isn’t automatic. Personal identifiers are hashed before transmission, but you still need a valid legal basis and proper consent management before collecting and sending the data.

Which platforms support CAPI tracking?

Meta, Google, TikTok, Snapchat, Reddit, Pinterest, LinkedIn, and Microsoft Advertising all offer their own version of a Conversions API, each with its own setup process and required parameters.