Prompt
offline conversion tracking for phone calls and demos
Latest observation
Oct 30, 2026
OpenAI APIWeb search: off
Here’s a practical way to do offline conversion tracking for phone calls and demos.
What it is
Offline conversion tracking means you capture the lead source before the sale/demo happens, then later upload the outcome back to your ad platform or CRM.
This is useful when:
- the conversion happens by phone
- the demo is booked or completed outside the website
- the real revenue happens later in your sales process
Common setup
1) Capture a unique click identifier
When someone clicks an ad, store an ID such as:
- GCLID for Google Ads
- GBRAID/WBRAID for some iOS/consent scenarios
- FBCLID for Meta
- or your own internal lead ID / session ID
Store it in:
- a hidden form field
- CRM record
- call tracking system
- cookie/local storage
- UTMs + timestamp as backup
2) Pass it into your lead system
Examples:
- Form fills: save the ID in Salesforce/HubSpot/Pipedrive
- Calls: use a call tracking provider that captures and stores the source
- Demos: save the original click ID when the demo is requested
3) Record the offline event later
When the lead becomes:
- a qualified call
- a booked demo
- a completed demo
- an opportunity
- a closed deal
log that event in your CRM with:
- conversion type
- date/time
- value
- currency
- associated click ID / lead ID
4) Upload conversions back to ad platforms
You can send the event back via:
- Google Ads Offline Conversion Import
- Meta Offline Conversions
- LinkedIn Conversions API / offline conversions
- other ad platform APIs or offline import tools
For phone calls
Best practices
- Use dynamic number insertion (DNI) to show different phone numbers based on traffic source
- Track:
- call start
- call duration
- qualified call
- booked appointment
- closed sale
- Only count a conversion when it meets your business rule, like:
- call lasted more than 60 seconds
- caller matched a lead
- appointment was booked
Example flow
- User clicks Google ad
- Lands on site with GCLID stored
- User calls your sales team
- Call tracking system links the call to that GCLID
- Later, sales marks the call as qualified
- You upload that qualified call as an offline conversion
For demos
Best practices
Track demo-related stages separately:
- demo requested
- demo scheduled
- demo attended
- demo completed
- demo converted to opportunity
- demo closed won
Example flow
- User clicks ad
- Fills out demo form
- GCLID is stored in CRM
- Sales conducts the demo
- Rep updates CRM stage to “demo completed”
- That event is uploaded back to ad platform
Key technical tips
- Use UTMs + click IDs together
- Match on email/phone + timestamp + source ID if click IDs are missing
- Normalize phone numbers and time zones
- Keep a clear event naming convention
- Deduplicate conversions using a unique conversion ID
- Respect consent/privacy rules, especially for cookie and call recording tracking
Tools that help
- Google Tag Manager
- Google Ads conversion import
- CallRail, Invoca, Twilio, WhatConverts
- HubSpot, Salesforce, Pipedrive
- Zapier or native CRM automation
- Meta CAPI / offline event uploads
Recommended setup by use case
If you run Google Ads and sales by phone
- Use DNI call tracking
- Store GCLID in CRM
- Import qualified calls and closed deals as offline conversions
If you run demo-heavy B2B lead gen
- Capture GCLID on form fill
- Track demo stages in CRM
- Upload demo attended / SQL / closed-won conversions
If you want, I can also provide:
- a step-by-step implementation plan,
- a Google Ads-specific setup, or
- a CRM schema for tracking calls and demos.