Offline conversion tracking bridge sending a CRM sale back to an ad platform

Offline Conversion Tracking: 5 Easy Signs You Need a Bridge

Facts checked in November 2026. Statements about what Google and Meta accept come from their official documentation, linked where they appear. Practical advice is marked as advice, and anything that is my own reasoning is marked as such.

An ad platform sees the click and the form submission. The sale that matters often happens later, in a CRM stage, on a phone or on an invoice, and the platform never hears about it. Offline conversion tracking closes that gap, but a bridge is not always the right answer. This guide shows when you need one, when you do not, and what it must get right.

What an Offline Conversion Bridge Is

In practice, a bridge is the working part of offline conversion tracking. It is any setup that takes a sale or qualified lead that happened outside the browser and sends it back to an ad platform as a correct conversion event. It can be a native CRM integration, a middleware tool or a custom script. What matters is that the event arrives with the right identifier, the right time, a stable ID and, where it applies, the right consent.

5 Signs You Need Offline Conversion Tracking

These are signs, not rules. Each one points to a gap that a bridge can close, and the more of them apply to you, the more likely it is that your offline conversion tracking is worth setting up properly.

1. The sale closes by phone, in person or by invoice

When a customer pays an invoice or signs a contract in a showroom, no thank you page loads, so a browser pixel has nothing to fire on. Meta’s Conversions API has action source values for exactly these cases: phone_call for conversions over the phone and physical_store for conversions in person. If your real revenue sits in these channels, the platform only learns about it when something sends it.

2. Lead and sale are days or weeks apart

A lead arrives today and the CRM stage changes to won three weeks later. For offline conversion tracking, time rules matter here. Meta’s server event documentation says event_time can be up to 7 days before you send the event, and that a single event older than that makes the whole request fail. Meta’s Conversions API guide gives physical store transactions a longer window, 62 days from the conversion. Advice: send each stage change soon after it happens, and know which limit applies to your events.

3. The CRM knows the deal value, but the ad platform only sees leads

A lead event tells the platform that someone filled in a form. It does not tell it that the lead became a paying customer worth a specific amount. Sending the closed deal back with its value lets reporting reflect revenue instead of form fills, which is the main job of offline conversion tracking. Google’s Data Manager API also lets you restate a conversion value later, although the conversion count stays the same.

4. A chat or messaging channel closes the deal

Chat deals have their own setup, which is covered on my WhatsApp conversion tracking service page.

5. Ads Manager and the CRM disagree

A mismatch is a symptom to investigate, not proof that you need a bridge. Platforms and CRMs count different things on different dates, so some gap is normal. Advice: take a set of recently closed deals and check whether each one reached the platform. If most are missing, a bridge is the likely fix. If they arrived but the numbers still differ, look at event times, duplicate events and attribution settings first.

When You Do Not Need a Bridge

Offline conversion tracking adds moving parts, so skip the bridge when a simpler setup already does the job.

Web purchases already tracked by pixel and server events

If the purchase happens on your site and both the browser event and the server event reach Meta with the same event name and event ID, Meta’s documentation says it keeps the first event it receives and ignores the duplicate, provided they arrive within 48 hours of each other. Nothing offline is missing, so there is nothing to bridge.

Very low volume

Advice: if you close only a handful of deals in a month, a manual upload from a spreadsheet may be enough, and a bridge may cost more attention than it saves. Check the current upload options inside your ad account before deciding.

A native CRM integration that already covers your events

Advice: if your CRM’s built in integration already sends the stages you care about, with the click ID, the value and a stable ID, you already have a bridge. Check which events it sends, which identifiers it includes and whether it sends the deal value. Build something custom only for what it leaves out.

What an Offline Conversion Bridge Must Get Right

Platform rules below come from the official documentation. The checklist, and every note marked as advice, is my own recommendation.

Capture the click ID when the lead arrives

Google’s send events guide says each event needs at least one identifier: a gclid, gbraid or wbraid, session attributes, user data, or an IP address. Meta’s fbc and fbp values are separate identifiers that must not be hashed. Advice: save these values on the CRM record when the form is submitted, because by the time the deal closes there is no browser left to read them from.

Keep a stable event or transaction ID

On Google, transactionId is optional and used for deduplication. Google Ads keeps the first event received for a given ID within a conversion action, and later events with the same ID are treated as adjustments. On Meta, event_id and event_name are used to deduplicate a browser event and a server event that describe the same action, and only when both arrive within 48 hours of the first one. Meta’s deduplication page does not state that two server events with the same ID are removed, so a bridge should not rely on it. Advice: use the CRM deal ID as the stable ID and keep a record of what you have already sent, so a retry never creates a second event.

Normalize and hash personal data before sending

Google requires identifiers such as email and phone to be hashed with SHA-256, encoded as hex or Base64, after normalization. In its examples, an email is trimmed and lowercased and a phone number is written in E.164 format. Meta’s customer information parameters list the fields that must be hashed, including email and phone, and say phone numbers need a country code to be used for matching. Meta says fbc, fbp, client_ip_address and client_user_agent must not be hashed.

Check consent per contact at upload time

Google’s request has a consent object with adUserData and adPersonalization, described as consent settings under the Digital Markets Act. Advice: store the consent status with each contact, send the status that is current at upload time, and decide in advance what happens to contacts without consent. This post is not legal advice.

Respect each platform’s time and size rules

Meta accepts up to 1,000 events per request, as its Conversions API guide explains, and fails the whole request if any event_time is older than 7 days. Google accepts up to 2,000 events per IngestEvents request, and its Data Manager API uses a fast-fail model and does not support conversion retractions. You can restate a value, but the count stays the same. Advice: decide before building how you treat cancelled deals, because you cannot remove a conversion once it is recorded.

Test before sending live

Google’s validateOnly flag checks a request without ingesting it. Meta’s Test Events tool gives you a test ID that you send as test_event_code, and Meta says to remove it from the production payload. If your deals come from chats on Meta ads, my CAPI debugger checks Conversions API events for those chats. For the Google side in more depth, see my post on the Data Manager API for offline conversions.

A Short Worked Example

This made up lead shows offline conversion tracking from click to import, in order. A visitor clicks a Google ad and lands on a quote form. The form saves the gclid and the visitor’s email on the new CRM record, together with a note that the visitor agreed to ad personalization. Nine days later a salesperson marks the deal as won after the invoice is paid.

The bridge reads the record and uses the deal ID as the transaction ID. It trims and lowercases the email, hashes it with SHA-256, adds the deal value and the time the deal was won, and sets the consent fields. It sends the request once with validateOnly set to true. When that returns no errors, it sends the real request. If the same deal is sent twice by mistake, the transaction ID means Google keeps the first event and treats the later one as an adjustment.

For a Meta ad, the record would need the fbc value saved at form submission, and the event would go out as soon as the deal closes.

FAQ

What is offline conversion tracking?

Offline conversion tracking means sending a sale or qualified lead that happened outside the browser back to an ad platform as a conversion event. The event needs an identifier that links it to the ad click or the person, a time, and usually a value. Without it, the platform only sees the click and the form.

Do I need a bridge if my CRM already has an integration?

Not necessarily. If the built in integration sends the stages you care about, with the click ID, the value and a stable ID, it already works as a bridge. Check what it sends before building anything custom.

How old can an offline event be when I send it to Meta?

Meta’s documentation says event_time can be up to 7 days before you send the event, and that one older event makes the whole request fail. Its Conversions API guide gives physical store transactions a longer window of 62 days from the conversion.

Can I remove an offline conversion from Google when a deal is cancelled?

Not with the Data Manager API, which does not support conversion retractions. You can restate the value of a conversion, but Google says the conversion count stays the same. Decide how to treat cancelled deals before you build.

What should I store when the lead arrives?

Advice: store the click ID (gclid, gbraid or wbraid for Google, and the fbc and fbp values for Meta), the contact details you will need to match the person, the consent status and a stable deal ID. Google needs at least one identifier on each event, and the click ID is the one that is hardest to recover later.

If you are not sure which of these cases fits your setup, send a short description of your offline conversion tracking setup to contact@alfahadhridoy.com and I will reply by email. Include your CRM, the ad platforms you use and how deals close.