Offline Conversion Tracking for Google Ads and Meta: A Practical Guide
Offline conversion tracking sends verified CRM outcomes, such as qualified leads, attended appointments and sales, back to Google Ads and Meta.
It connects advertising to business value when you preserve matching identifiers, define consistent stages, record consent and upload each eligible outcome reliably.
- Keep the matching identifiers
- Record real outcomes
- Verify the feedback loop
Start with the revenue journey
A form submission is an enquiry, not a sale. Campaigns can appear successful while sales staff handle duplicates, unsuitable enquiries and no-shows if bidding only sees form fills.
Document your journey: enquiry, qualified lead, appointment booked, visit attended, deal won and cash collected. Assign an owner and timestamp to every stage you intend to measure.
| Outcome | Verify before uploading |
|---|---|
| Qualified lead | The contact meets a documented sales criterion, rather than simply submitting a form. |
| Appointment | Distinguish a booking from an attended visit; record cancellations and no-shows separately. |
| Revenue | Use the agreed value basis and currency; separate booked value from collected cash. |
Avoid adding every stage together as separate customers. Keep diagnostic stages separate from the primary bidding outcome you want the platform to optimise.
Preserve click IDs at lead capture
Click IDs connect eligible ad interactions to later outcomes. Capture them on arrival, retain them through navigation where permitted, and pass them through forms or booking systems into the CRM.
- GCLID is Google’s click identifier. Preserve its original value and case; avoid rewriting it or keeping it only in a temporary spreadsheet.
- GBRAID and WBRAID support Google’s privacy-preserving measurement paths, including iOS-related journeys. Capture them when present; they are not interchangeable fields.
- For Meta, preserve available click and browser signals such as fbc and fbp when permitted. Do not manufacture identifiers for traffic that never supplied them.
- Keep UTMs for descriptive source context. A campaign name helps reporting but does not replace platform matching identifiers.
Google’s offline import guidance covers identifiers and upload fields. Meta defines matching fields and hashing requirements in customer information parameters.
Use enhanced conversions for leads
Enhanced conversions for leads supplements offline matching with permitted first-party contact information. Configure the Google tag and later CRM upload as one measurement flow.
Normalise and hash supported contact fields according to the integration instructions. Check whether the connector hashes automatically; hashing twice breaks matching, and hashing does not create consent.
Check Google’s current offline conversion documentation: since 15 June 2026 it directs new API implementations to Data Manager API. Eligible existing Google Ads API integrations have separate migration guidance.
- Create clearly named conversion actions, such as Qualified lead or Attended visit, and agree which are primary for bidding.
- Map the actual outcome time, with timezone, to the correct conversion action and advertising account.
- Include supported matching data, a stable event or order identifier, and value plus currency where appropriate.
- Monitor accepted, rejected and unmatched records. Resolve errors and retry without creating another conversion for the same outcome.
Send CRM events through Meta CAPI
Meta’s Conversions API connects server and CRM data to Meta, including offline outcomes. Configure the correct dataset and map CRM stages to supported events.
Include the event name, actual event time, matching data and accurate action_source. A conversion completed by phone is not a website conversion merely because a server uploads it.
Follow Meta’s server event definitions and current event-age limits. Upload promptly; a valid CRM event can still be too old for the destination.
When Pixel and server report the same action, use matching names and IDs for deduplication. Later qualification is a separate event, not a duplicate of the initial enquiry.
Use Events Manager diagnostics and test events before production. An accepted upload, a matched person and an attributed conversion are different states; none guarantees improved bidding performance.
Make consent part of the data
Record what the person agreed to, when, through which form and under which notice. Supplying a phone number for a visit is not automatically permission for advertising matching.
Google Consent Mode communicates choices through ad_storage, analytics_storage, ad_user_data and ad_personalization. It adjusts tags; it does not collect consent or independently enforce every CRM upload.
Carry applicable choices into server processing, access rules, retention and withdrawal handling. Upload only eligible records; a server-side integration does not bypass a visitor’s choice.
India’s DPDP Act and 2025 Rules have phased commencement. As of 16 November 2026, check the applicable provisions rather than claiming the entire framework is already in force.
Agree purpose-specific notices, access, retention and deletion with your privacy or legal owner. For healthcare, exclude diagnoses, treatment details and sensitive free text from advertising payloads; check platform restrictions.
Match leads to collected revenue
Use a stable internal ID through capture, CRM, booking and billing. Resolve duplicates without discarding the original source history or consent record.
- Keep an event ledger: lead ID, stage, outcome time, source identifiers, permitted matching fields, consent status, value and currency.
- Separate won deals from paid invoices. Define whether reported return uses booked revenue or collected cash.
- Use an idempotent upload key per real outcome. Record destination, response, retry status and later corrections.
- Reconcile CRM, billing and uploads. Platform totals can differ because of attribution windows, matching availability and reporting dates.
Speed to lead: measure the delay
Speed to lead is the time from an enquiry arriving to a meaningful first response. Measure it alongside qualification and attendance; an automatic acknowledgement does not prove follow-up happened.
Record arrival, assignment and first-response times under a clear working-hours policy. Review unassigned leads, overdue follow-ups and response-time distributions by source and owner.
Use your conversion history to investigate rupee impact. Keep sample size, assumptions and uncertainty visible; correlation between slow replies and lost sales does not establish causation.
Common failures and how to check
| Failure | Practical check |
|---|---|
| Lost click IDs | Trace a tagged visit through redirects, navigation, form submission and the CRM record. |
| Broken forms or webhooks | Submit a controlled lead; verify delivery, identity, consent and source context. |
| No CRM stages | Require evidence and an owner for qualification, attendance, won and collected outcomes. |
| Duplicate or rejected uploads | Inspect IDs, timestamps, timezones, accounts, hashing and destination responses. |
| Totals disagree | Compare the same outcome, date basis, attribution window and revenue definition. |
How XGI closes the loop
XGI, Xynexia Growth Intelligence, connects enquiries through collected cash. Its documented feedback loop sends qualified leads, visits and revenue to Google Ads through offline/enhanced conversions and Meta through Conversions API.
Revenue Truth distinguishes observed, inferred and unknown attribution. Leak Radar shows estimated rupee impact with confidence and evidence; governed actions use permissions, approvals and a tamper-evident Proof Trail.
Eligible events and permissions are agreed during onboarding. Explore analytics and attribution services for implementation and XGI lead management for capture and follow-up.
Frequently asked questions
What is offline conversion tracking in Google Ads?
Offline conversion tracking links later outcomes to eligible Google Ads interactions. A CRM sends qualified leads or sales with supported identifiers, timestamps and conversion actions, subject to consent and matching requirements.
Can Meta track conversions recorded in a CRM?
Yes, Meta Conversions API can receive eligible CRM and offline outcomes. Configure the correct dataset, supported events, matching data, accurate timestamps and deduplication while respecting consent and platform restrictions.
Do enhanced conversions for leads replace click IDs?
They supplement matching with permitted first-party data rather than making captured click IDs useless. Preserve GCLID, GBRAID and WBRAID when available and follow the integration’s supported field combinations and hashing instructions.
Should I upload leads, appointments or revenue?
Upload the verified stages that reflect your sales process, keeping each event distinct. Choose primary bidding goals deliberately and avoid treating every stage as additive revenue; bookings and attended visits are different outcomes.
Does Consent Mode make offline uploads compliant?
No, Consent Mode communicates signals and changes Google tag behaviour. Your CRM and upload system must still enforce applicable permissions, notices, retention and withdrawal handling, including the DPDP provisions in force for your operation.
How does speed to lead affect tracking?
Speed to lead reveals response delays between advertising and sales outcomes. Recording arrival, assignment and response times helps diagnose missed opportunities without assuming delay alone caused a loss.