Facebook offline conversions let you tell Meta which ad clicks ended in a real-world result: a phone booking, an estimate, a signed contract or a paid invoice. Today you do it through a Dataset in Events Manager, fed by the Conversions API (CAPI) or a manual file upload. The old standalone Offline Conversions API is gone. If a guide still tells you to create an "offline event set" and call that endpoint, it is out of date.
This guide is written for home service owners and marketing managers: HVAC, plumbing, roofing, electrical, landscaping, turf and restoration. Your sales close on the phone or at the kitchen table, not in a checkout cart, so the Meta Pixel never sees the part that pays you.
TL;DR
- Offline conversions send job outcomes (booked, estimated, sold, paid) from your CRM back to Meta, so ad reporting and optimization follow real revenue instead of form fills.
- Meta discontinued the standalone Offline Conversions API in May 2025. The current route is a Dataset plus the Conversions API, or a CSV upload for low volume.
- Every event needs a timestamp, a value, a unique order ID and at least one customer identifier. Upload within 62 days of the conversion.
- Check results in Ads Manager under Columns, and check raw events in the Dataset's Event Activity view.
- The tool matters less than the discipline: someone has to mark jobs as booked and sold in the CRM every day.
Table of Contents
- What Facebook offline conversions are, and why home services need them
- What changed: the Offline Conversions API is retired
- Which offline events to send for a home service business
- What data each event must include
- Step-by-step: set up offline events in Meta
- Timing rules that quietly break reporting
- See the results in Ads Manager
- Troubleshooting: why offline conversions go missing
- Our perspective
- Where Leapify Media fits
- FAQ
- Sources
What Facebook offline conversions are, and why home services need them
An offline conversion is any valuable action that happens outside your website or app, and that you report back to Meta after the fact. Meta's own documentation frames it as a way to measure how ads lead to real-world outcomes such as store purchases or phone orders. For a retailer that means a register sale. For you it means something else.
Think about the path of a typical $9,000 roof replacement lead:
- A homeowner sees your ad on Facebook or Instagram and fills in a lead form.
- Your office calls, books an inspection and runs the estimate.
- Three weeks later the customer signs.
- The job is invoiced and paid a month after that.
Meta sees step 1 only. Without more data, its system treats a tire-kicker who never picks up the phone exactly like a homeowner who signs a five-figure contract. It will happily find you more of the first kind, because they are cheap and plentiful.
Sending steps 2, 3 and 4 back changes two things:
- Reporting. You see cost per booked job and return on ad spend by campaign, ad set and ad, not just cost per lead.
- Optimization. Meta can learn which lead profiles turn into revenue and shift delivery toward them.
If you already run the same loop in Google Ads, the logic will be familiar. We covered it in offline conversion tracking in Google Ads for home services. Meta's version needs the same CRM discipline with a different delivery mechanism.
What changed: the Offline Conversions API is retired
Many top-ranking pages still describe the old workflow. Here is the short history, so you can spot outdated advice.
- Meta built the Offline Conversions API in 2016 for brick-and-mortar retailers.
- Integration tools froze their old connectors, and the standalone endpoint was discontinued on May 14, 2025, with Graph API v16.0 as the last supported version.
- Meta now directs advertisers to the Conversions API and Datasets for web, app and offline events together.
The practical consequences for you:
- Offline events live in a Dataset in Meta Events Manager, not in a separate offline event set.
- API events carry an
action_sourcefield. For events from a physical location or a phone or in-person sale, the value commonly used is "physical_store". - Any CRM plug-in, Zap or script built on the old endpoint needs to be rebuilt or replaced. If your agency or CRM vendor set something up before 2025, ask what it now sends and where.
Because Meta's tools change often, treat Meta's developer documentation and Events Manager as the final word on field names and limits.
Which offline events to send for a home service business
More events is not better. Send the milestones that separate real buyers from curiosity, and keep the list short enough that your team can keep it accurate.
| Event | When to send it | Why it helps |
|---|---|---|
| Booked appointment | Office confirms a date for the visit | Fast signal, arrives within days |
| Estimate delivered | Tech or sales rep presents a price | Filters out no-shows and bad fits |
| Job sold | Customer signs or approves | Strongest signal for most trades |
| Job paid | Invoice settled | Real revenue for return on ad spend |
A few practical rules:
- Pick one primary event. For short-cycle work such as plumbing repair or HVAC service calls, "booked" or "completed" is usually enough. For roofing, turf installs and large remodels, "sold" is the more useful anchor because the sales cycle is long.
- Attach a value. Send the sold amount or invoice total in US dollars. Without value, you cannot calculate return on ad spend.
- Do not send everything twice. If a conversion already happens on your website and is tracked by the Pixel or CAPI, keep the offline event for the later stage. Meta deduplicates offline events using order ID and event details, not against Pixel or website events, so a double-send can inflate your numbers.
If phone calls are your main conversion, your offline pipeline starts at the call log. Our HVAC call tracking setup walks through getting that first layer of data in place.
What data each event must include
Meta can only credit an ad if it can match the event to a person who saw or clicked it. That requires identifiers, and the more you send, the better the match.
A useful reference is the file specification for offline conversion programs. LiveRamp's documentation for the Meta integration lists a transaction category, a UTC timestamp, the amount in USD, an order ID, data-processing options and a supported identifier. Translate that to your CRM like this:
- Event name or category: Lead, Schedule, Purchase or a custom name you define.
- Event time: the moment the action happened, in a consistent time zone. Sloppy timestamps are a leading reason events fail to attribute.
- Value and currency: the job amount in USD.
- Order ID: a unique ID per job or invoice. Reusing one ID for several events can collapse them.
- Customer identifiers: email and phone number at a minimum, plus name, city, state and ZIP when you have them. Meta expects identifiers to be normalized and hashed before they are sent, which CAPI-ready integrations and Meta's upload tool handle.
- Click identifiers: if your lead form or landing page captured the Facebook click ID (fbclid, stored as fbc) or browser ID (fbp), send them. They improve matching beyond email and phone.
Handle customer data carefully
You are moving personal information from your CRM to a third party. Use only data customers gave you in the course of doing business, make sure your privacy policy says you share data with advertising platforms, and respect opt-outs. Some states require specific disclosures and opt-out mechanisms for sharing personal data for advertising. Ask your attorney which apply to your service area. Where an integration offers data-processing options, set them deliberately rather than leaving the defaults.
Step-by-step: set up offline events in Meta
1. Create or choose a Dataset
In Meta Events Manager, open Data sources and either create a new Dataset or reuse the one tied to your Pixel. Many advertisers keep web and offline events in the same Dataset so that Meta sees the whole customer journey. A separate offline Dataset is fine if you want cleaner reporting. Make sure the right people hold admin access, because only admins of the business or the dataset can upload data, according to Meta's permissions guidance.
2. Decide how data will flow
You have three realistic options, and they differ mainly in how much manual work your team absorbs.
| Method | Best for | Effort | Weak point |
|---|---|---|---|
| CRM or POS integration with CAPI | Any business with a CRM that tracks job stages | Setup once, then automatic | Breaks silently if a field mapping changes |
| Server-to-server CAPI from a data warehouse | Larger operations with a developer or data team | Highest setup cost | Needs engineering upkeep |
| Manual CSV upload in Events Manager | Low volume or a pilot | Weekly manual work | Slow, easy to forget, easy to misformat |
The Conversions API gives a server-to-server connection from your CRM or data warehouse to the Dataset. Some enterprise platforms offer it natively. Salesforce, for example, documents how to activate lead-record changes to Meta CAPI. If your CRM lacks a native connection, a connector tool or custom build can fill the gap.
3. Upload a file (the manual route)
For a pilot or a small shop, the file upload is a reasonable start.
- In Events Manager, select your Dataset and choose Upload events.
- Drag in a CSV file. Meta provides a template with the expected column headers.
- Map each of your columns to Meta's data types (email, phone, event name, time, value and so on).
- Review the preview, confirm the time zone and submit.
The mapping step is where most manual uploads go wrong. A column mapped as the wrong data type produces events that upload but never match. If your Dataset offers the setting "Allow historical conversion uploads", check it before sending older records.
4. Send events through the Conversions API
When your CRM is wired to CAPI, each stage change triggers an event. Practical settings to confirm with whoever builds it:
- The
action_sourceis set appropriately for the event, such as "physical_store" for in-person or phone-closed work. - Event time reflects when the job stage changed, not when the sync ran.
- Each event has a unique order ID.
- Customer identifiers are hashed and normalized to Meta's specification.
- Failed sends are logged, so you hear about gaps within a day instead of a quarter.
5. Verify that events are arriving
Open your Dataset and look at the Event Activity graph for incoming raw events. Some integrations ask you to approve the first event before it starts flowing, as Adsquare's setup guide describes. If the graph is flat a day after you sent data, the problem is almost always connection, permissions or formatting, not Meta's attribution.
Timing rules that quietly break reporting

Offline conversions are tied to an attribution window, so late data can be ignored. LiveRamp's documentation says conversion data must be uploaded within 62 days of the conversion and 90 days of the earliest attribution event, and that the conversion must have occurred within 7 days of that attribution event. Those figures come from that program's guide, so confirm the current limits in Meta's own documentation for your setup.
What this means for a contractor:
- A roofing job sold six weeks after the first ad click is a different matter from a plumbing call booked the same afternoon. If your cycle is long, send an earlier milestone (booked or estimated) so Meta gets a signal inside its window, and send the sold event as well.
- Do not batch uploads monthly. A weekly cadence for CSV uploads, or real-time sync for CAPI, keeps you well inside the limits.
- Backfill carefully. Uploading a year of history can import events Meta cannot attribute and muddy your view.
See the results in Ads Manager
Once events match, the numbers show up where you already work:
- Open Ads Manager and choose Campaigns, Ad sets or Ads.
- Open the Columns dropdown.
- Choose Offline Conversions, as Adsquare's Meta optimization guide lays out.
Save a custom column set with spend, leads, booked jobs, sold jobs, revenue and cost per booked job. Then review it weekly, not daily. Offline events arrive with a lag, so yesterday's numbers are always incomplete.
A few honest reading tips:
- Compare campaigns by cost per sold job and revenue per dollar spent, not by cost per lead.
- Give a campaign enough time for events to land before you judge it. For long-cycle trades, that means weeks.
- Reconcile against your CRM monthly. Meta's attributed revenue will not equal your total revenue, and it should not. It only counts what it can tie to an ad.
If you are also building the downstream picture of appointments, completed work and revenue, the phone estimate best practices show how cleaner estimate handling gives your reporting something reliable to send back.
Troubleshooting: why offline conversions go missing
When events are missing or low, work through this list in order.
- Nothing in Event Activity. Check permissions, the connection and any first-event approval prompt.
- Events arrive but do not match. Look at identifiers. Missing phone numbers, typos in emails and unhashed values are common. Add click IDs where possible.
- Events arrive late and drop out. Check the timing rules above. Physical-store events should be sent within 62 days.
- Revenue looks too high. You may be sending the same job twice with different order IDs, or sending both booked and paid values as purchases. Use a distinct event name per stage.
- Revenue looks too low. Your front office may not be updating job stages. This is a process problem, not a Meta problem.
- Time zone shifts. Events stamped in local time but read as UTC can land in the wrong day or fall outside the window.
- An old integration still "works." If it was built for the retired endpoint, it is not delivering what you think. Rebuild on Datasets and CAPI.
The pattern behind almost every failure is the same: a CRM that does not reliably record what happened to each lead. That is why we start with booking discipline, as in our guide to booking rate optimization for home services.
Our perspective
Most home service owners we talk to are not short on leads. They are short on knowing which leads turned into trucks rolling. Offline conversions are the bridge, but a bridge is only as good as what crosses it.
At Leapify Media we build the CRM, the call tracking, the lead scoring and the ad management as one system, so job outcomes flow back to the ad platforms without someone exporting spreadsheets on Fridays. Our AI dispatch and intent scoring run on infrastructure we built and host ourselves, not on a third-party AI tool, and we keep your customer data proprietary and secure. That matters here, because offline conversion data is your customers' names, phone numbers and job values.
Our view is simple: send fewer events, send them faster, and make sure each one is true. When the sold and paid stages reach Meta cleanly, you can judge campaigns by revenue, cut the ones that only produce form fills, and put the budget where booked jobs come from. Our partnerships with home service companies have produced a reported 20x return on ad spend, and closing this loop is a central part of how we work.
Everson Gorski
Where Leapify Media fits
If you would rather not wire this together yourself, we handle the pieces that make offline conversions reliable: CRM integration, on-premise AI dispatch, and Meta and Google Ads management that use the outcomes you actually book.
Published pricing, in US dollars:
- Meta Ads Management: $1,500 per month
- On-Premise AI Dispatch: $1,000 per month, with a one-off $7,500 setup fee
- CRM Integration: from $3,000 one-off
- Packages: Foundation from $2,500 per month, Growth from $7,500, Scale from $15,000 and Enterprise from $25,000
See the full breakdown on our pricing page, or browse our services to see how lead generation and CRM automation connect.

We work with home service businesses doing at least $500K a year in revenue. If that is you and your ad reports still stop at the lead form, start with a conversation on our site.
If you run Facebook for a specific trade, these guides apply the same thinking: Facebook ads for plumbers and Facebook ads for roofers.
FAQ
Is the Facebook Offline Conversions API still available?
No. The standalone endpoint was discontinued in May 2025. Offline events now go to a Dataset through the Conversions API, or through a file upload in Events Manager. Integrations built on the old endpoint need to be rebuilt.
Can I upload offline conversions to Facebook without a developer?
Yes. In Events Manager you can select your Dataset, choose Upload events, add a CSV and map the columns to Meta's data types. This suits low volume, and a CAPI-ready CRM integration is the better long-term answer because it removes the weekly manual step.
How long do I have to send an offline event?
One program's guide states conversions must be uploaded within 62 days of the conversion, and within 90 days of the earliest attribution event. Send events as close to real time as you can, and confirm the current rules in Meta's documentation.
Where do I see offline conversions in Ads Manager?
Select your campaigns, ad sets or ads, open the Columns dropdown and choose Offline Conversions. Check the Dataset's Event Activity graph in Events Manager to confirm raw events are arriving before you trust the columns.
Sources
- Manage Permissions for Offline Event Sets, Meta Business Help Center
- Meta Offline Conversion Tracking: Complete Guide to CAPI & Datasets
- How to Send Offline Sales to Meta in 2026
- The Meta Conversions API Program for Offline Conversions, LiveRamp
- How to Activate Events to Meta via the Data 360 Conversions API, Salesforce
- Activate Optimization in Meta, Adsquare Help Center
- The Phone Estimate Best Practices That Actually Win Jobs
