Meta's Offline Conversions API Is Gone: What to Use Now
Meta discontinued the Offline Conversions API in May 2025. Offline and CRM events now go through the Conversions API. What changed, which action_source to use, and how to migrate without losing data.
Written by Qualimize Team
Founder, Qualimize
- Published
- Last updated
- Reading time
- 9 min read
Table of contents
- 01 The short answer
- 02 What the Offline Conversions API was
- 03 What changed, and when
- 04 What to use now: the Conversions API
- 05 How to migrate, step by step
- 06 Timing rules that catch migrations out
- 07 What this means for lead businesses in India
- 08 Checklist: is anything still on the old API?
Full article
The short answer
Meta's Offline Conversions API is no longer available. Meta's Graph API v20.0 changelog said it would be discontinued in May 2025, when Graph API v16.0 expired, and Meta's documentation now calls it the legacy API for offline events. Use the Conversions API instead: it accepts offline, store and CRM events, sent to a dataset with the right action_source.
If you were still uploading offline sales through the old API or an old connector, those uploads are not reaching Meta. The fix is to move to the Conversions API, which most CRMs and connectors already support.
What the Offline Conversions API was
For years, Meta had a separate API for events that did not happen online: in-store sales, phone orders and deals closed by a sales team. Businesses uploaded these to offline event sets, and Meta matched them to people who had seen or clicked an ad.
Website and app events went through the Pixel and later the Conversions API. Offline events went through this second, older pipe, with its own setup and its own quirks. Meta's documentation still mentions the upload_tag parameter as supported for advertisers using the legacy API.
Running two pipes for the same advertiser was the problem Meta set out to remove.
Two separate pipes meant two sets of credentials, two places to check for errors and two ways of describing the same customer. A store that ran both web and offline tracking often had a website purchase in one system and the same customer's in-store purchase in another, with nothing tying them together in Events Manager. Moving everything to one API, with a field that says where each conversion happened, is the simpler model Meta settled on.
What changed, and when
Meta first extended the Conversions API to accept offline events and began recommending it for new offline integrations. Deprecation of the Offline Conversions API was first expected in Q3 2024, then moved, according to Meta's own changelog.
Meta's Graph API v20.0 changelog, released in May 2024, set the final timeline: the remaining Offline Conversions API endpoints were deprecated on Marketing API v20.0, and the API would be discontinued when v16.0 expired in May 2025. It advised advertisers with existing integrations to move to the Conversions API before then.
As of November 2026, Meta's offline conversions documentation describes the Conversions API as its recommended integration method for sending offline and physical store events.
What to use now: the Conversions API
The Conversions API is the single server-side route for web, app, offline and CRM events. Each event names where the conversion happened through action_source, and Meta's server event documentation lists the options, including website, app, phone_call, chat, email, physical_store, system_generated and business_messaging.
For in-store sales, Meta's offline conversions page says to send events to a dataset with action_source set to physical_store. For lead stage updates from a CRM, Meta's Conversion Leads specification uses system_generated, and that is what most CRMs send for stage changes.
The rest of the event looks like any other Conversions API event: an event name such as Purchase, an event_time, hashed customer information, value and currency for purchases, and an event_id.
One practical benefit is that offline and online events now sit together. A dataset can hold website Lead events from the Pixel and Conversions API alongside CRM stage events and store purchases, so Events Manager shows one view of the customer journey rather than two disconnected ones.
The customer information rules are the same for every event. Meta's customer information parameters page asks for email trimmed and lowercased, phone numbers with symbols and leading zeros removed and the country code included, and names lowercased without punctuation, all hashed with SHA-256. Offline data is often messier than web data, so this normalisation step matters even more.
How to migrate, step by step
Start by finding what still points at the old API. That includes scripts written by a past developer, Zapier or other connector steps labelled offline conversions, and any monthly CSV upload habit.
Then move each flow to the Conversions API. Pick the dataset you will send to, generate a Conversions API access token in Events Manager, map each offline event to a standard event and the right action_source, and send a few test events with a test event code before switching on.
- List every script, connector and manual upload that used offline event sets
- Choose the dataset (Pixel) to send offline and CRM events to
- Generate a Conversions API access token in Events Manager
- Map each event: store sale to Purchase with physical_store, CRM stage to the right event with system_generated
- Hash email and phone after normalising, with the 91 country code on Indian numbers
- Test with a test event code, then remove it and go live
Timing rules that catch migrations out
The Conversions API has a strict time limit. Meta's server event documentation says event_time can be up to 7 days before you send the event, and if any event in a request is older, the whole request is rejected. Meta's offline conversions page repeats that limit, and separately says physical store transactions should be uploaded within 62 days of the conversion; the 7-day event_time rule is the one that gets requests rejected, so plan around it. Teams used to uploading a month of sales at once need to switch to daily or real-time sending.
Meta's CRM implementation guide adds two batch rules: each batch can include up to 1,000 events, and if there is an error in the batch, the whole batch is discarded. It also warns against back-dating event_time to squeeze in older data, which may cause backfilled data to be discarded.
In practice this means a monthly upload habit has to become a daily or real-time process. That is a change in how the sales team records outcomes, not only a technical switch.
Build for failure too. If a connector goes down over a long weekend, the events it missed may be close to the 7-day limit by the time it recovers. Send the backlog promptly, in small batches, and drop any event that has passed the limit rather than letting it take a whole batch down with it.
What this means for lead businesses in India
Most Indian lead businesses never used offline event sets; they managed leads in spreadsheets or a CRM and sent nothing back to Meta. For them, the retirement changes nothing directly, but it clarifies the path: lead stage feedback goes through the Conversions API, the same way as every other server event.
The useful question is not whether you were on the old API, but whether your CRM sends outcomes to Meta at all. If it does, check it uses the Conversions API. If it does not, the steps above are the same steps you would follow for a first-time setup. Qualimize, for example, sends Contact, Lead, SubmitApplication and Purchase through the Conversions API when a rep changes a status.
Example: a Bengaluru furniture showroom runs Meta ads to drive store visits and records sales in its billing software. Under the old setup, an agency uploaded a monthly sales file to an offline event set. Under the Conversions API, the same sales need to go out within 7 days, each as a Purchase with physical_store, the bill amount, INR and the customer's hashed phone. The data is the same; the rhythm is daily instead of monthly.
Checklist: is anything still on the old API?
Old integrations rarely announce that they have stopped working. A script keeps running, a connector shows green, and nothing reaches Meta. Run through this list once, especially if an agency or a former developer set up your tracking.
If any item points at offline event sets or an offline conversions step, treat it as broken until it has been moved to the Conversions API and you have seen test events arrive in Events Manager.
- Scripts or cron jobs that call offline event set endpoints
- Zapier, Make or other connector steps labelled offline conversions
- Agency processes built around monthly offline uploads
- Monthly sales CSVs that someone still prepares for upload
- Campaign reports that once showed offline purchases and now show none
- CRM or POS plugins not updated since before May 2025
Comparison tables
Offline Conversions API vs Conversions API
| Offline Conversions API (legacy) | Conversions API | |
|---|---|---|
| Status | Discontinued in May 2025 | Meta's recommended route for offline events |
| Where events go | Offline event sets | A dataset |
| Event types | Offline only | Web, app, offline, CRM, messaging |
| How offline is marked | By using the offline API | action_source, e.g. physical_store or system_generated |
| Graph API support | Offline events last supported in v16.0 | Supported in current API versions |
| Back-dating limit | Not relevant: API retired | event_time up to 7 days before sending |
Which action_source to use for offline and CRM events
| Where the conversion happened | action_source | Meta's description (paraphrased) |
|---|---|---|
| In a store or office, in person | physical_store | Conversion made in person at your physical store |
| Over the phone | phone_call | Conversion made over the phone |
| On a messaging app, SMS or chat | chat | Conversion made via a messaging app, SMS or online messaging |
| CRM stage update | system_generated | Conversion happened automatically; required for Conversion Leads CRM events |
| Somewhere else | other | Conversion happened in a way not listed |
FAQ
Is the Meta Offline Conversions API deprecated?
Yes. Meta's Graph API v20.0 changelog said the Offline Conversions API would be discontinued when Graph API v16.0 expired in May 2025. Meta's documentation now calls it the legacy API and recommends the Conversions API for offline and physical store events.
What replaced the Offline Conversions API?
The Conversions API. It accepts offline events alongside web and app events. You send them to a dataset and set action_source to describe where the conversion happened, such as physical_store for in-store sales or system_generated for CRM stage updates.
How do I upload offline sales to Meta in 2026?
Send each sale as a Purchase event through the Conversions API with value, currency, hashed email and phone, and the right action_source. Send within 7 days of the sale, ideally the same day, because Meta rejects requests containing older events.
Can I still upload a CSV of offline conversions to Meta?
Meta's current documentation centres on sending offline events through the Conversions API. If you rely on file uploads, check Events Manager for the options available on your account, and remember the 7-day event_time limit applies to Conversions API events.
Do I need to migrate if my CRM sends lead stages to Meta?
Only if it uses the old Offline Conversions API. Ask your CRM provider or check its documentation. A CRM that sends stage events through the Conversions API needs no change.
Where does Qualimize fit?
Qualimize sends CRM stage events through the Conversions API, not the retired Offline Conversions API, with action_source system_generated, the Meta lead ID, hashed contact details and a stable event ID. There is nothing to migrate. It does not upload in-store sales from a POS system.
Key takeaways
- Meta discontinued the Offline Conversions API in May 2025, with the expiry of Graph API v16.0.
- Offline, store and CRM events now go through the Conversions API, to a dataset.
- Use action_source to mark where the conversion happened: physical_store, phone_call, chat or system_generated.
- Events older than 7 days get the whole request rejected, so monthly uploads must become daily or real-time.
- Check old scripts and connectors; anything still pointed at offline event sets is no longer reaching Meta.