Facebook offline conversions tell Meta which ad leads became customers: the booked call, the show-up, the deal your team won. DataCops sends them from HighLevel, HubSpot or any CRM to Meta through the Conversions API, within Meta's 7-day window, matched to the ad click.
Trusted by agencies and brands running paid media
Facebook offline conversions, now Meta offline conversions, are sales or steps toward a sale that happen away from your website and are sent back to Meta: a booked appointment, a phone sale, a deal won in your CRM, a paid invoice. Meta matches each one to the person who clicked or saw your ad, counts it as a result of that ad and learns to find more people like the ones who bought.
DataCops keeps the ad click on your own domain when the visitor lands. When the lead books, shows up, qualifies or buys in HighLevel, HubSpot or any CRM, DataCops finds that click again and sends the stage to Meta through the Conversions API, the same day. No weekly CSV, no code.
DataCops sends Facebook offline conversions from HighLevel, HubSpot or any CRM to Meta through the Conversions API, matched to the ad click that started each sale.
What Meta learns from
Meta learns from what it is told. For most lead businesses that is the form, and nothing after it.
The pixel sees the form fill and the thank-you page. The booked call, the show-up and the won deal happen where it cannot follow.
Opportunity in your CRMDeals close in HighLevel, HubSpot or Salesforce, on the phone or in person. Nothing tells Meta that the lead became a customer.
Safari clears cookies set by a browser script after 7 days. A deal that closes three weeks later has no fbclid left to match.
Bot form fills count as leads too. Every one tells Meta to find more people like it.
Meta shut down its separate Offline Conversions API and offline event sets in May 2025. Offline and CRM sales now go through the same Conversions API as website events, into a dataset.
Meta turns away events sent more than 7 days after they happened. A monthly or weekly CSV of won deals loses its oldest rows, so each stage should go out on the day it happens.
Meta matches an offline sale to a person by hashed email and phone, and by the click ID when there is one. The more of these you send, the more sales Meta can credit to an ad.
Four steps from the ad click to the won deal, with nothing to wire in HighLevel or HubSpot.
Stages your CRM reports
Meta Sent once 
Google Ads Sent once 
TikTok Sent once 
LinkedIn Sent once Each stage goes out as your CRM reports it, well inside Meta's 7-day limit.
Traffic Visibility
First-Party Script
Blockers and ITP cut your sessions
“15 minutes to get server-side tracking live. After 3 days failing with another app and a DIY server-side Google Tag Manager, that alone sold me. Then support jumped on a Google Meet with me on a Sunday afternoon to finish the job. Nothing else comes close.”
The six places people ask about most. Each card shows what actually reaches Meta.
Pick the lifecycle stage that means a lead is qualified. DataCops holds each lead from your site, checks HubSpot every 5 minutes and sends the conversion to Meta when the lead reaches that stage. Leads that never qualify expire after 14 days. Deal stages are not read.
Install once for your agency and pick the sub-accounts to connect. The form or survey lead, the booking, the show-up, the won deal with its value and the paid invoice each reach Meta as HighLevel reports them. Cancellations, no-shows and lost deals are never sent.
There is no native Salesforce connector. When an opportunity closes, a Salesforce flow, Zapier, Make or n8n posts it to your private DataCops webhook with the customer's email or phone, the value and the order ID. DataCops finds the ad click and sends it to Meta.
The DataCops Shopify app sends each paid order to Meta as a server-side purchase with its value, so orders the browser pixel missed, blocked or lost still count against the ad that brought the buyer.
On a paid plan, Ads Warmup takes a CSV of up to 20,000 past customers or sales and sends them to Meta and the other platforms you pick. Rows are dated when you send them, so use it to warm up an ad account, not to rewrite past reports. For a sheet you add sales to every day, send each new row to your webhook through Zapier or Make.
Any tool that can post a webhook can send offline sales. Add one webhook step to your Zap with the email or phone and the value. DataCops matches the ad click and sends the sale to Meta, Google Ads, TikTok and LinkedIn, so you need no separate Zap per platform and no click ID in your CRM.
A bot that fills in your form becomes a lead your ads try to find more of. DataCops checks every visit for bots and datacenter traffic, and for VPNs and proxies if you choose. Switch on Real people only for a platform and flagged visits never reach it.
Sales that come from your CRM are sent as your CRM reports them, with no bot check, so qualify them there before you send.
How DataCops spots bots Meta, delivery A CSV upload can report success and still match nothing. DataCops logs every send to Meta with its status and the reason.
Ways to get offline sales into Meta. Checked September 2026 against each tool's own help pages.
So nothing surprises you later.
Post each sale to your DataCops webhook, directly or through Zapier, Make or n8n.
The lifecycle stage you choose as qualified goes to Meta.
Paid invoices from HighLevel, Shopify orders and webhook sales are sent today.
Meta offers no way to take back a sale once sent. Google Ads refunds are corrected.
About 5 minutes per site. Agencies: about 15 minutes per client.
Add the DataCops script
One script and one DNS record, so every Facebook ad click is kept on your own domain.
Connect Meta
One-click sign-in to your Meta ad account and dataset. Add Google Ads, TikTok and LinkedIn if you use them.
Connect where your sales happen
HighLevel, HubSpot, your webhook or a CSV. Pick the stages to send.
DataCops is a tool that sends Facebook offline conversions from HighLevel, HubSpot or any CRM to Meta through the Conversions API, matched to the ad click that started each sale, with a bot verdict on every visit and a log of every send.
Meta shut down the separate Offline Conversions API and offline event sets in May 2025. Offline and CRM events now go through the regular Conversions API into your dataset, and Meta rejects a request if any event in it is more than 7 days old. DataCops sends each stage when it happens, so it lands inside that window.
One script and one DNS record collect on your own domain. With your DNS on Cloudflare, the free Worker reads the click ID at the edge before the page loads. The click is kept on the server for up to 90 days, and a sale is matched by click ID or hashed email and phone. A signed server-set cookie on your domain lasts up to 400 days where enabled.
HighLevel natively: form or survey lead, booked, showed, won with value, paid (delivered to Meta as Schedule, Showed and Purchase). Cancelled, no-show and lost send nothing. HubSpot sends one lifecycle stage. Any CRM, Salesforce and Pipedrive included, posts to a private webhook.
Every visit gets a bot verdict against 360+ billion IPs and 350+ monitoring points. Real people only is a per-platform switch, off by default. CRM, webhook and CSV events carry no bot flags, so the check applies to the site visit. Every form email is checked for disposable providers, domains with no mail server and an email risk score, and LeadCops can hold a lead until your CRM confirms it.
Upload a CSV of up to 20,000 past customers, see a 0 to 10 match score for each, and send them to Meta as server-side events, dated when you send. Sending needs a paid plan.
A purchase with an order ID reaches Meta once, and a HighLevel won deal and its invoice count as one sale. A delivery log row for every conversion shows sent, held, skipped or failed with the reason. Shopify orders come through the DataCops Shopify app.
Best for: lead gen, clinics, home services, B2B and agencies advertising on Meta whose sales close in a CRM or on a call.
Free to start. See pricing.
HighLevel's own Meta action sends pipeline events for contacts who came from a Facebook lead form. If that is nearly all your leads, it may be enough.
Meta Events Manager still has a manual Upload events option for a CSV, by hand, per file. For a single import, that can be enough.
Refunds and cancellations do not reach Meta. See what happens to a refunded sale.
Health mode keeps page links to the domain and event names neutral. Read Meta health restrictions first.
Platform rules checked October 2026. Rules change; check Meta's own page before you build.
Facebook offline conversions, now called Meta offline conversions, are sales or steps toward a sale that happen away from your website and are sent back to Meta: a booked call, a show-up, a deal won in your CRM, a paid invoice. Meta matches each one to the person who saw or clicked your ad, so your campaigns learn from buyers and not only from form fills.
Server-side conversions to Meta, Google Ads and TikTok, no code.
See Conversion APIFeed your customer list to the ad platforms before you spend.
See Ads WarmupVerified leads, and conversions only once a lead qualifies.
See LeadCopsCRM, store and CSV sales matched back to the ad click.
See Offline ConversionsSend HighLevel, HubSpot and CRM sales to Meta the day they happen, logged per send.
Setup in 5 minutes. No credit card.
Live traffic quality
Visits · last 24h
Without filtering, 26.5% of your reported traffic is bot noise inflating dashboards and draining ad spend.
Make confident, data-driven decisions with
actionable ad spend insights.
© 2026 DataCops. All rights reserved.
