Offline call attribution is frequently treated as a switch: connect a call-tracking system, import conversions, and trust the campaign report. In practice, the hard part is preserving identity and meaning from ad interaction to call, qualified conversation, opportunity, and revenue. A bounded decision record helps determine whether the current system needs a targeted repair or a clean rebuild.
1. Define the outcome and the decision
Write what the organization wants to know: which campaigns create calls, which calls are qualified, which calls become opportunities, or which calls produce revenue. Name the conversion owner, maturity window, service area, call types, and decision date.
Google describes several ways to measure the calls you receive, including duration rules and importing offline call outcomes. Use the platform description as a vocabulary reference, then define the business event separately.
2. Map the call path end to end
Draw ad, landing page, number, call platform, recording or transcript, agent disposition, CRM record, opportunity, and revenue. Include click-to-call ads, website numbers, organic listings, direct dials, referrals, and manually dialed numbers. Record where source and caller identity can be lost.
Run synthetic calls through each important path. Save timestamp, number, source parameters, call ID, CRM ID, owner, disposition, and downstream status. A call duration alone does not prove that the conversation was relevant or commercially viable.
3. Check identity and source capture
Inventory dynamic number insertion, forwarding numbers, GCLID or other click identifiers, UTM persistence, cookies, call IDs, and CRM matching rules. Record timeout, cross-device, missed-call, repeat-caller, and privacy behavior. Identify whether the same person can generate multiple events that are counted as separate conversions.
Keep source data in a durable field before a handoff or import. If the source is inferred from a reporting view after the call, mark it as an assumption. Preserve the original value and the normalized channel so future reconciliation can explain changes.
4. Validate import eligibility and data format
For each imported record, define conversion name, call time, time zone, value, currency, identifier, account, and conversion window. Google’s phone-call import guidance describes the file and account requirements and warns that imports are not a reversible substitute for correct source data.
Check formatting, account destination, duplicate key, upload schedule, error file, and approval owner. Test one known-good record, one invalid record, and one duplicate. Keep a copy of the raw file and the result report outside the article package.
5. Separate call quality from attribution quality
Create two dispositions. Call quality asks whether the caller had a supported need, location, timing, and authority. Attribution quality asks whether the source, campaign, and call identity are trustworthy. A well-attributed unqualified call is still not pipeline; a qualified call with missing source is still valuable but measurement-incomplete.
Use a consistent disposition vocabulary: wrong number, spam, support, out of area, valid inquiry, qualified conversation, opportunity, lost, and pending. Train the owner who assigns the status and record the evidence needed to change it.
Add a review rule for recordings and transcripts. If the organization stores them, define who may review them, how long they are retained, and which fields are summarized into the CRM. If recordings are unavailable, do not invent a quality score from duration alone; use the disposition and follow-up evidence that actually exists.
6. Reconcile platform, call system, and CRM counts
Compare calls, answered calls, qualified conversations, imported conversions, CRM leads, opportunities, and revenue by day, source, location, and owner. Keep time zones and call windows consistent. Investigate missing IDs, late updates, duplicate calls, manual dials, and records that never receive a disposition.
Google’s troubleshooting guidance for phone-call imports lists common mismatches such as unsupported call sources, incorrect time zones, formatting errors, and conversion-window limits. Treat each mismatch as a testable hypothesis rather than a reason to adjust numbers manually.
7. Decide whether to fix or rebuild
Fix when the business definition is shared, source identifiers survive, and one or two defects explain the gap. Rebuild when numbers are mixed across incompatible call types, ownership is unknown, identifiers were never captured, or the CRM cannot distinguish qualified outcomes. A rebuild should preserve historical records and define a transition period.
Record the evidence, affected systems, dependencies, temporary workaround, owner, and rollback. Do not rebuild because a report looks unattractive if the underlying path is still explainable.
8. Use a decision matrix
| Signal | Fix | Rebuild | | — | — | — | | definition | one unclear label or window | several meanings in one conversion | | identity | one broken field or timeout | no durable call/source key | | import | format, account or schedule defect | process cannot preserve raw evidence | | quality | disposition training gap | no consistent call outcome model | | reconciliation | isolated, explainable variance | counts cannot be joined across systems | | ownership | named technical and business owners | no owner for the measurement chain |
Attach test calls, file samples, query definitions, exception list, maturity window, and acceptance evidence. Keep a pre-change snapshot before changing tags, number pools, or imports.
9. Run a bounded repair or migration
Choose one call path, location, or campaign. Freeze the current definition, repair the smallest proven defect, and compare platform, call-system, CRM, and opportunity records after a declared window. If rebuilding, run the new path beside the old one long enough to expose missing identifiers and duplicate logic.
Plan the handover carefully. Tell every owner which number pool, conversion action, import schedule, and CRM field is active during the pilot. A technically correct rebuild can still create conflicting reports if the old process continues to upload records in parallel without a declared transition rule.
The durable artifact is an Offline Call Attribution Decision Record linking outcome definition, call path, identity, import rules, quality, reconciliation, owner, and rollback. It makes “fix or rebuild” an evidence decision rather than a reaction to a confusing dashboard.
How did this article land?
Choose one reaction. You can change it anytime.
