Meta offline conversions: moving to the Conversions API
Meta retired the Offline Conversions API in 2025. Send CRM, call and in-store conversions through the Conversions API, matched and on time.
By DATALYR · · 4 min read
Contents
What happened to Meta offline conversions
Meta discontinued its Offline Conversions API in May 2025 and directed advertisers to the Conversions API, which now handles offline events. Offline conversions still exist: a sale closed over the phone, in a store or in your CRM can still be sent to Meta. They simply travel through the same Conversions API as website events.
Meta's Graph API changelog for version 20.0 says the Offline Conversions API would be discontinued when version 16.0 expired in May 2025, and asked advertisers to move their integrations to the Conversions API before then. Meta's offline conversions page now calls the old API Meta's legacy API for offline events.
If an older tool or Zap still posts to an offline event set, check that it actually delivers. Segment, for example, says its Facebook Offline Conversions destination no longer accepts data because Meta discontinued the API.
Tell Meta where it happened
Every Conversions API event carries an action_source that says where the conversion happened. The values include website, app, email, phone_call, chat, physical_store, system_generated, business_messaging and other. A sale closed on a sales call is a phone_call; a renewal that bills automatically is system_generated.
The value is a description, not a trick for better matching. Choose the one that describes the real event so Meta's reporting and your own audit trail agree.
Leads from Meta Lead Ads (Instant Forms) have their own route. Meta's Conversions API for CRM sends lead stages with the Meta lead ID, action_source set to system_generated, and custom_data fields event_source set to crm and lead_event_source naming your CRM. That route powers the Conversion Leads performance goal, which Meta says works only with Lead Ads.
Two routes for offline outcomes
Website or booking leads
Conversions API event
Matched with hashed email, phone, fbc and fbp from the visit.
Instant Form leads
Conversions API for CRM
Matched with Meta's lead ID; feeds the Conversion Leads goal.
Send within Meta's time limit
Meta accepts an event_time up to 7 days before you send the event. If any event in a request is older than that, Meta returns an error for the whole request and processes none of its events.
The limit applies to the gap between the conversion and the upload, not between the click and the conversion. A deal that closes 40 days after the lead is fine if you send it the day it closes. A deal that closed last week and waits for a monthly batch is not.
For the Conversion Leads goal, Meta also asks for uploads at least once a day and for the optimized stage to happen within 28 days of the lead.
Example: a weekly batch that fails
This is a hypothetical example. A sales team exports closed deals every Monday and uploads them in one request. On Monday, November 16, the batch includes a deal closed on Saturday, November 7.
November 16 minus November 7 is 9 days, which is past Meta's 7-day limit. Because one event is too old, Meta rejects the entire request, including deals that closed on November 13, 14 and 15 and would have been accepted on their own.
Sending each stage when the CRM record changes avoids the problem. So does a daily batch, as long as nothing waits more than a few days.
Give Meta something to match
An offline conversion helps only if Meta can match it to a person who saw or clicked an ad. Meta matches on hashed customer information such as email and phone, and on browser identifiers such as the fbc click cookie and fbp browser cookie when the event can carry them.
A CRM record usually has the email but not the browser identifiers. Carrying the visit forward fixes that: when the lead's email is tied to the visit that came from a Meta ad, the later conversion can include the click and browser context from that visit.
DATALYR's Meta delivery hashes email, phone, names and location before sending, and builds fbc from the original fbclid with the time it first arrived.
Send CRM stages without an export
DATALYR receives sales stages from HubSpot, Calendly, iClosed and, through Zapier, from any CRM or booking tool. Each stage joins the earlier visit by email, and a conversion rule sends it to Meta: a booked call as Schedule, a qualified lead as Lead, a won deal as Purchase with the deal amount as its value and the deal ID as the order ID.
The won deal's amount is a contract value. DATALYR sends it to Meta as a conversion value but never counts it as revenue; cash comes from Stripe or another payment source.
Because deals often close after Meta's attribution window, DATALYR's setup suggests optimizing Meta on the booked-call or qualified stage and using won deals for reporting.
Related articles.
Tracking ·
Server-side tracking: architecture, responsibilities and limits
Understand what moves to the server, what still depends on browser identity, and how to verify one conversion without creating duplicate events.
Conversion delivery ·
Offline conversion tracking: connect a lead to the sale that follows
Define the lead-to-sale record, preserve eligible matching data, and verify imported outcomes without confusing acceptance with advertising credit.
Conversion tracking ·
Meta Conversions API: setup, deduplication, and verification
Map a real conversion to the correct Meta destination, choose one delivery owner, and verify receipt separately from matching and attribution.
