How offline sales join online ads

Which sales belong offline#

Any revenue the browser never sees belongs here: till sales, phone closes, showroom orders, field-sales contracts and CRM-qualified deals that started as ad clicks or leads. If the outcome lands days after the click in a different system, offline uploads are the only bridge back to the auction. Start at the Meta Ads hub for the family view.

Draw the boundary crisply: online-confirmed orders stay in Pixel plus CAPI, everything confirmed elsewhere goes offline. Blurred boundaries double-count the same sale in both streams. CAPI setup covers the online half, and Meta own offline conversions guide sets the upload rules.

Event sets and upload paths#

Offline events land in offline event sets inside Business Manager: named containers that group uploads by business, region or funnel stage. Create one set per reporting unit that needs its own optimisation signal, attach it to the ad account, and grant upload access to the system or person running the cadence. Manual CSV uploads suit monthly volumes; scheduled file transfers and CRM integrations suit weekly or daily flows.

Choose the path your team will sustain, because stale uploads decay into misleading history within weeks. Automate wherever volume justifies it; calendar-block manual uploads where it does not. Event naming follows standard events so online and offline vocabularies agree.

Matching on customer data#

Uploads match to people on hashed customer fields: name, email, phone, postcode, town and country plus order timestamps. Capture these at enquiry time with consent captured alongside; the click ID captured on the form doubles match strength where available. Every field you collect honestly lifts match rate, and match rate decides how much offline revenue optimisation can see.

Hash before or during transit so raw customer data never rests in logs or spreadsheets longer than needed. Agree retention windows with whoever owns compliance, and document them beside the upload log. Developer field detail is at offline parameters.

Frequency and freshness#

Upload on a rhythm the auction can learn from: daily for high-volume retail, weekly for considered B2B, never quarterly dumps that arrive as history lessons. Events timestamped within roughly two months of occurrence stay eligible; older outcomes inform finance but not delivery. Freshness is a feature, so schedule uploads like media, not like admin.

Monitor match rate and upload diagnostics each cycle: falling match rates name data-capture decay at the till or in the form, not auction faults. Fix capture first, then re-upload the affected window with corrected files. Attribution windows still govern how matched outcomes credit.

Dedup across online and offline#

One sale, one counted event across all three streams: where an online lead becomes an offline close, the offline upload must carry the same order or lead ID discipline as the browser and server copies. Re-uploading a period without replacing the prior file doubles the count; overlapping online Purchase plus offline Purchase for one order does the same. Keep a single event ledger with owners per source.

Reconcile monthly: platform totals against the order book and CRM, with the gap tracked as its own metric. A widening gap names capture or dedup faults before it names creative ones. Dedup rules govern the online pair; extend the same discipline offline.

Optimising on offline outcomes#

Attach the offline event set to campaigns once uploads run clean for several cycles, and optimise lower-funnel activity toward qualified closes rather than raw leads. Lead quality transforms overnight: delivery stops chasing form-fillers and starts hunting buyers. Budget with the longer feedback loop in mind, because offline signal arrives days late and reacts slowly to edits.

Pair offline optimisation with consolidated structure so each ad set still clears roughly 50 events a week. Lead ads routing feeds the top of this funnel, and our team reviews offline wiring before you optimise on it.

Frequently asked questions#