Offline Conversions

Offline conversions are sales that happen away from your website, in a store, over the phone, or inside your CRM, fed back to Meta so it can attribute and optimize toward them.

You run ads that drive real business the pixel never sees. Someone taps your ad, then calls to book, walks into the shop, or gets closed by your sales team a week later. To Meta, that sale simply never happened, so it keeps optimizing toward whatever it can measure, like form fills, instead of the deals that actually pay you. Offline conversions close that loop by sending those real-world sales back to Meta and tying them to the people who saw or clicked your ads.

You should know the plumbing has changed. The old standalone offline event sets have been deprecated, and offline events now flow through a Meta dataset and the Conversions API, the same pipe your web events use. In practice you upload or connect your sales data, mark the action source as a physical store or other offline source, and Meta matches those records back to user profiles to assign credit and feed its optimization. You do this so the system learns from money, not proxies: once Meta can see which clicks became phone bookings or closed deals worth real rupees, it can chase more of those people instead of the cheap leads that never turn into anything.

The honest catch is that match quality depends entirely on the customer data you upload, so weak or messy fields mean fewer matched sales and shakier credit, and offline events arrive with a delay that muddies same-day reporting. It rewards real setup discipline and punishes a sloppy export.

If your best sales close offline, a system that cannot see them is optimizing toward your worst ones.