CRM CAPI: Connect Any CRM to the Meta Conversions API, Google Ads, TikTok, LinkedIn and GA4
The Meta Conversions API was built for website events.Your most valuable events happen in the CRM: a rep marks a lead as qualified, books a meeting, closes a deal. adsfox CRM CAPI turns those CRM stage changes into server-side conversions and sends them to Meta, Google Ads, TikTok, LinkedIn and Google Analytics 4 at the same time, with the click IDs and contact data the platforms need to match them.Campaigns stop optimizing for form fills and start optimizing for qualified leads and revenue.One CRM connection, one event mapping, no changes to how your sales team works.
Join 350+
happy clients.
What CRM CAPI means in practice
Your CRM sends conversion events straight to the ad platforms as server events.
Instead of relying on the pixel alone, adsfox listens to your CRM and sends New Lead, Qualified Lead, Non-Qualified Lead, Sale and Lost, each with an optional value.
Meta, Google, TikTok and LinkedIn receive the same events in their own Conversions API format, so a lead your team qualified on Tuesday becomes a training signal for every campaign by Tuesday afternoon.
Stronger matching than a typical CAPI setup
Most CRM to Meta integrations send only an email and a phone number, often as a manual offline upload.
adsfox captures more on the first visit: FBCLID and the _fbp cookie for Meta, GCLID for Google Ads, TTCLID for TikTok, LI_FAT_ID for LinkedIn, the GA4 client ID, IP address, user agent and landing page URL.
Every event carries an event ID for deduplication.
More signals means the platforms recognize more of your customers and learn faster which leads turn into sales.
Multi-platform by default, one mapping
You do not build a separate integration per platform.
Map your CRM statuses once (for example Proposal Sent to Qualified Lead, Closed Won to Sale with the deal value) and adsfox translates the mapping into the Meta Conversions API, the Google Ads offline conversions API, the TikTok Events API, the LinkedIn Conversions API and the GA4 Measurement Protocol.
Consistent event names and values everywhere, so reports and optimization goals agree with each other.
The full lead journey in GA4
adsfox keeps every event tied to the same person through shared identifiers, including the GA4 client ID captured on the first visit.
GA4 does not split the journey into separate users, so you can see which channels, pages and campaigns produce qualified leads and real revenue, build funnels from lead to sale, and compare sources by value instead of by form count.
CRM CAPI, but not only for a CRM
Any system that can send a webhook can feed the Conversions API through adsfox: newsletter software, cold outreach tools, webinar platforms, call tracking, your own backend.
Booking and form tools such as Calendly and Typeform have ready-made integrations.
If your qualification happens in a spreadsheet or an automation platform, that works too.
Measurably more qualified leads
Our clients get 17.6 to 40.4 percent more sales-qualified leads when they tag leads within 3 days, optimize campaigns for qualified leads and exclude non-qualified leads from targeting.
Meta reports a 19 percent lower cost per high-quality lead for advertisers who connect their CRM and switch the campaign objective from lead volume to conversion leads.
A lightweight setup takes minutes; stable optimization on the new signals usually takes about a month.
What is CRM CAPI (Conversions API for CRM)?
CRM CAPI is a Conversions API integration that sends events from your CRM, rather than from your website, to advertising platforms as server events. The Conversions API was designed as a server-to-server alternative to the pixel: it does not depend on the browser, cookies or ad blockers, and it can carry data the browser never sees. A CRM CAPI setup uses that channel to report what happened after the form: the lead was qualified, the meeting took place, the contract was signed, the deal was lost. Those outcomes are what you actually want more of, and they are what the platforms cannot see on their own.
adsfox is a Conversions API for CRM layer for all major platforms. It connects to your CRM through a native integration or a webhook, standardizes stage changes into a fixed set of events (new lead, qualified lead, non-qualified lead, sale, lost) with values, and sends them to Meta, Google Ads, TikTok, LinkedIn and GA4 within minutes of the change.
Meta Conversions API for CRM: conversion leads, Instant Forms and the 90-day rule
The Meta Conversions API (still searched as the Facebook Conversions API) accepts CRM events tagged as CRM or offline events. adsfox sends each stage change with hashed email and phone, the FBCLID, the _fbp cookie, IP address, user agent and, for leads from Instant Forms, the Facebook lead ID. That combination is what Meta uses to match a CRM record to the person who clicked the ad.
Once qualified lead and sale events arrive in Events Manager, you can switch lead campaigns to the conversion leads optimization goal, build lookalike audiences from qualified leads and buyers, and exclude non-qualified leads from targeting. Two things to plan for: Meta stops using updates to leads older than 90 days for optimization, so stage updates need to be timely, and the integration that pulls leads from Meta into your CRM has to exist first, because CRM CAPI closes the loop by sending the outcome back. Step by step: how to integrate adsfox with Meta Ads, how to configure the pixel for CRM events and new CRM data and events in Meta campaigns.
Pixel tracking vs. the Conversions API
The pixel runs in the browser and depends on cookies, scripts and the user's consent settings. The Conversions API runs server to server and can send events from web servers or from a CRM. Keep the pixel for page views and remarketing; let the Conversions API carry the lead outcomes. adsfox deduplicates the two with event IDs, so nothing is counted twice.
Google Ads Conversions API: offline conversions and enhanced conversions for leads
For Google Ads the equivalent of CRM CAPI is the offline conversions API. adsfox stores the GCLID from the ad click with the lead and uploads qualified lead and sale conversions with the conversion action, timestamp and value, so Smart Bidding can optimize for conversion value instead of raw leads. When the GCLID is missing, adsfox also sends hashed email or phone through enhanced conversions for leads, which keeps match rates high in privacy-first browsers. Guides: how to connect adsfox with Google Ads and how to create a Google Ads campaign optimized for qualified leads.
TikTok Conversions API and LinkedIn Conversions API
The same CRM events go to the TikTok Events API (with TTCLID and hashed contact data) and to the LinkedIn Conversions API (with LI_FAT_ID and hashed email). Both platforms allow lead campaigns to optimize for downstream events and to exclude audiences built from non-qualified leads. For B2B this is often the biggest win: LinkedIn leads are expensive, and sending Sales Qualified Lead events back is the only way to make the platform find more of them. Guides: TikTok Ads and LinkedIn Ads.
GA4 Measurement Protocol: the CRM as a data source for analytics
GA4 has no native Conversions API, but the Measurement Protocol does the same job. adsfox sends every stage change to GA4 with the original client ID and the lead value as the event value, so a sale closed six weeks after the click is attached to the session and source that produced it. Mark qualified lead and sale as key events, and GA4 reports lead generation the way it reports e-commerce: revenue by channel, campaign and landing page. Guide: how to integrate adsfox with Google Analytics 4.
Which CRM systems work with Conversions API through adsfox?
Almost any. Ready-made integrations cover HubSpot, Salesforce, Pipedrive, Zoho CRM, Bitrix24, Microsoft Dynamics 365, Close, Freshsales, Zendesk Sell, monday.com CRM, Keap, Insightly, SugarCRM, Nutshell, Livespace and more. Any other system that supports webhooks or an API, including custom CRMs and tools connected through Zapier or Make, can send lead stages the same way. You keep your CRM, your pipeline and your sales process; adsfox only listens to status and value changes. Teams without a CRM can use the built-in adsfox CRM, which is included in every plan.
- General procedure for connecting CRMs to adsfox
- Pipedrive integration (webhook)
- Zoho CRM integration (webhook)
- CRM integration via Make
- Webhooks in adsfox CRM
How to set up CRM CAPI with adsfox
- Connect your CRM (native integration or webhook) and add one adsfox snippet to your website so click identifiers are captured with every lead (website integration).
- Map your statuses to the standard events: new, qualified, non-qualified, sale, lost. Add values where they exist (deal value for sales, expected value for qualified leads, zero for non-qualified).
- Connect the ad platforms. For Meta you need admin access to the Business Portfolio to connect the data source and generate the Conversions API access token; Google Ads, TikTok and LinkedIn are connected with an account login.
- Verify delivery. In Meta Events Manager check the data source, match quality and deduplication; in Google Ads check the conversion actions; in GA4 check the events in real time.
- Switch optimization goals to qualified lead or sale once the events flow steadily, and exclude non-qualified leads from targeting.
Plans start at $239 per month billed annually (see pricing), setup is guided at no extra cost, and agencies manage all clients from one account (adsfox for agencies).
CRM CAPI as part of lead generation optimization
CRM CAPI is the delivery mechanism. It works best together with lead generation tracking (source, campaign and identifiers stored with every lead), a clear lead qualification process in sales, and offline conversion tracking for phone sales and in-person deals. The whole system is described on the lead generation optimization page. If you already run server-side tracking with adsfox, CRM CAPI uses the same first-party data layer. Want us to run the campaigns on top of the data? Our Facebook Ads agency and Google Ads agency teams do that every day. Book a demo or see pricing.
What our clients say
What I value most about working with you is having a dedicated specialist. The person matters, what they can do and how they communicate, and that is what I appreciate at adsfox. With other agencies and freelancers I could never get satisfying results. Now, after two years of working with you, it simply works.
Piotr
Owner, outdoor LED lighting manufacturer (luminous paving stones)
Given my own marketing background, I would definitely recommend working with adsfox. Highly recommended. These guys know what they are doing. I think adsfox is a great partner to work with.
Przemysław
Marketing director, event services company (crew and technical staffing)
What I value most about adsfox is that it is not a "pay and wait" arrangement. At any moment I can see where the money goes and what return it brings, and I have direct contact with specialists who advise me not only on ads but also on my offer and strategy. I delegate the complicated stuff and still keep full control over the outcome.
Dawid
Owner, e-commerce store (personalized wooden gifts)
Our revenue grew significantly and we won a lot of new clients, which is not easy in our business. That month was a record in terms of revenue, and a lot of women decided to book our services. Our schedule was packed, so we actually had to pause the ads for a while.
Justyna
Owner, women's body shaping and fitness studio
I am very happy with the cooperation. Many more customers started calling. We also see much higher traffic in our stats, both from Facebook and from Google, and it turns into phone calls and new bookings. I am very pleased with working with you.
Marcin
Owner, paintball park and outdoor events venue
With you I now pay almost 10 times less per conversion and get 200 new subscriptions a month, so for me this is a game changer.
Łukasz
Marketing manager, online courses and consulting (personal development)
CRM CAPI FAQ
Both report outcomes that happen outside the website. Offline conversion uploads are often manual, delayed and limited to an email or a click ID. CRM CAPI sends CRM events as server events in near real time through the Conversions API, with richer matching data (click IDs, browser cookie, IP address, user agent, event ID for deduplication) and with lead values, so the platforms can use them for optimization, not only for reporting.
The Meta Conversions API (Facebook and Instagram), the Google Ads offline conversions API with enhanced conversions for leads, the TikTok Events API, the LinkedIn Conversions API and the Google Analytics 4 Measurement Protocol. One set of CRM events is mapped to the right format for each platform.
Yes. adsfox connects to HubSpot, Salesforce, Pipedrive, Zoho, Bitrix24, Microsoft Dynamics 365, Close and dozens of other systems, and to any CRM that can send a webhook. Your pipeline, fields and sales process stay as they are. See the general procedure for connecting CRMs.
A small, consistent set works best: New Lead, Qualified Lead, Non-Qualified Lead, Sale and Lost, plus a value where relevant. Meta recommends passing lead stages as a variable from your database rather than hardcoding them, so that every progression through the funnel becomes an event. adsfox handles the mapping and the formatting per platform.
No. You can connect the CRM first and start sending events to Events Manager. When you launch or relaunch campaigns, the algorithm already has a history of qualified leads and sales to learn from instead of form fills only.
Usually not. Keep your existing pixel ID and any Conversions API connection you already have for web events; adsfox adds the CRM layer for lead stages and values on top of it. Create a new pixel only if your Business Portfolio structure requires it.
Admin access to the Meta Business Portfolio (Business Manager). You need it to connect the data source, set permissions and generate the access token for the Conversions API connection. Delivery, match quality and deduplication are then checked in Meta Events Manager.
For Meta: hashed email and phone for matching, the Facebook lead ID for leads from Lead Ads, an event name, an event time (up to 7 days before sending) and an event ID for deduplication. adsfox also sends the FBCLID, _fbp cookie, IP address and user agent when available. Google Ads needs the GCLID or hashed contact data, the conversion action, time and value.
A lightweight setup takes minutes when CRM access and ad account access are ready: connect the CRM, add the snippet, map statuses, connect the platforms. Stable optimization on the new signals usually takes about a month, because the platforms need a steady stream of qualified lead and sale events before you switch campaign goals.
Yes. When the platforms receive qualified lead and sale events instead of form fills, they optimize toward people who look like your buyers and away from low-intent submissions. Our clients see 17.6 to 40.4 percent more sales-qualified leads, and Meta reports a 19 percent lower cost per high-quality lead for advertisers using conversion leads optimization with a CRM integration.