When several campaigns send callers to the same business line, the team answering the phone may have no reliable way to tell which placement prompted each inquiry. That becomes a practical problem when you need to decide which ads to keep or where to improve follow-up.
This guide covers inbound marketing calls, not private-call tracing or phone-location tracking.
How Does Call Tracking Work?
Call tracking connects incoming business calls to the ads, listings, or website visits associated with them. It uses tracking phone numbers that usually forward to the business's existing line. With website tracking enabled, a call record may also include the page visited and available campaign data.
For example, a repair company could put one tracking number on a printed flyer and another on a website campaign. Both reach the same team, but the report shows which number was dialed. This is marketing attribution: assigning a call to a source under a defined rule. To learn whether the caller booked a repair, the company also needs an appointment record.
Marketing placement or website visit
-> Tracking number shown or assigned
-> Inbound call connects to the business
-> Source and call details are recorded
-> Lead qualification and business results can be linkedThere are four jobs in that flow:
- Assign the number. Connect a tracking number to a placement, such as a flyer or listing. On a website, software can select a number using the available traffic-source or visit data.
- Connect the call. Forward it to the existing business number, a team, or an automated answering workflow.
- Log the event. Save the call's reference number, often called a call ID, plus available details such as the dialed number, time, status, and source. Logging a call doesn't necessarily mean recording its audio.
- Add the result. A person can label the lead, conversation-analysis software can classify it, or a connected customer relationship management (CRM) or booking system can supply a saved outcome.
What Is Dynamic Number Insertion?
Dynamic number insertion (DNI) is website code that changes the phone number a visitor sees according to source or visit rules.
With source-level replacement, visitors from the same traffic source may see the same number. With visitor-level tracking, the provider temporarily assigns a number to a website session, or visit, from a pool of reusable tracking numbers. It can then match the call to the data recorded for that visit. Source-level and visitor-level setups provide different detail even though both can use DNI.
The number isn't a permanent personal number for that visitor. The provider holds and reuses it under its assignment rules.
Suppose someone clicks a paid-search ad and reaches the repair company's website. The tracking code displays a number and captures the available campaign details. These might include UTM tags, which are campaign labels added to a link, or an ad platform's click identifier. A call to the assigned number can then be matched to that visit. Invoca documents this kind of website-tag implementation.
The caller can read the number on a laptop and dial it from a phone. The number still provides the match within the provider's assignment rules; it doesn't reveal all of that person's activity across devices. If visit data is missing, the call may still connect while its source remains unknown.
Static Numbers, Source-Level DNI, or Visitor-Level Tracking?
If you need to compare calls from a flyer and a directory listing, fixed numbers may be enough. If you need to connect calls to particular website visits, look at visitor-level tracking.
| Setup | What is assigned | Good starting use | What it can tell you | What it cannot tell you alone |
|---|---|---|---|---|
| Static tracking number | A fixed number for a placement, source, or campaign | Print, radio, listings, or a few campaigns | Which mapped number received the call | The caller's website session or earlier marketing contacts |
| Source-level DNI | A website number selected for a traffic source | Comparing broad website channels | The source associated with the displayed number | Which individual website visit led to the call |
| Visitor/session-level DNI | A number temporarily assigned from a pool | Connecting website visits to calls | Matched pages, campaign identifiers, and supported paid-keyword data | Every search query or a complete identity and cross-device history |
Static numbers can provide source-level attribution too. DNI describes how the website displays a number, not how much detail an attribution report must contain. Locations and service lines can be tracked within these setups; they aren't separate tracking technologies.
What to Check Before Choosing Software
- Tracking detail: Can it answer your actual question, whether that's comparing a few placements or matching individual website visits?
- Number availability and control: Are the numbers you need available? Who owns them, can you transfer them to another provider, and what happens when you cancel?
- Website coverage: Do the visible number and the click-to-call link change together on the intended pages, including mobile pages?
- Number pool: How many numbers does your website need, how long is each assigned to a visit, and what happens when all are in use? The estimate needs to account for website visits and assignment time, not just simultaneous phone calls.
- Connected records: Which source fields and call IDs can be exported? Ask for a test showing that the intended information reaches your CRM or ad platform.
- Conversation data: If you enable recording or transcription, who can access it, how long is it kept, and how can the team review it?
- Total cost: Ask about platform fees, phone numbers, call usage, and optional analysis or integration charges for your proposed setup.
You don't have to change every published business number. Start with the placements you need to measure.
Why Use Call Tracking?
Call tracking helps when the source of a call would change a business decision:
- Compare marketing channels. A service business can include phone inquiries alongside forms and online purchases when reviewing campaigns.
- Check lead quality before changing spend. An agency can separate calls about the advertised service from wrong numbers, spam, or unrelated requests.
- Find follow-up problems. A multi-location team can compare source data with answered and missed calls, then check whether someone handled the follow-up.
A campaign producing few confirmed bookings might be attracting the wrong callers. Or it might be reaching suitable prospects whose calls go unanswered. You need call-handling and outcome records alongside the source to tell the difference.
I'd start with the question you need the report to answer. If all you need is a call log, visitor-level DNI may add complexity without helping.
Call Tracking vs. Recording, Analytics, and Routing
These functions often appear in the same software, but they answer different questions.
| Function | Main question |
|---|---|
| Call tracking and source attribution | Which marketing source or website visit is associated with this call? |
| Recording or transcription | What was said, when capture is enabled? |
| Call analytics or conversation intelligence | What patterns, caller needs, or classifications appear in the data? |
| Call routing | Which team, person, or workflow should receive the call? |
| Call forwarding | To which number or destination should the call be connected? |
| Business-outcome reporting | What did the CRM, calendar, or sales system confirm afterward? |
A tracking number can forward a call, while call routing selects the destination under the business's rules. Recording and analytics may help explain the conversation. None of these functions has to be sold as a separate product.
Caller ID is different again. A caller number or label doesn't identify the marketing campaign and shouldn't be treated as verified identity.
What Can Call Tracking Tell You, and What Still Needs Proof?
For each figure in a report, ask what record supports it. A detailed website visit can lead to no sale, and a confirmed sale can lack a matched website session.
A Call Evidence Map
Use this table to check what you can conclude from the data you have.
| Question | Evidence to look for | What you can conclude | What remains unproven |
|---|---|---|---|
| Did a call occur? | Call ID, direction, timestamp, and provider status | A call event was recorded | That a person answered or a sale happened |
| Which source is associated? | Dialed number and its source mapping, or captured campaign fields | A source received credit under the chosen rule | Which other marketing influenced the caller |
| What visit data is available? | Matched session, landing page, UTM tags, or click identifiers | This recorded visit is associated with the call | Every organic search query or unrelated visits on other devices |
| Is it a qualified lead? | Written criteria and reviewable call evidence | The inquiry met those criteria | Sales acceptance, booking, or purchase |
| Was the requested action completed? | Saved booking, ticket, or CRM update confirmation | That specific action succeeded | Completion of the customer's entire request |
| Is there confirmed revenue? | Linked sales record, amount, currency, payment status, and attribution rule | The amount and status recorded for that linked sale | That an assigned lead value is cash received, or that the campaign caused the sale |
These records answer separate questions, not stages that every call must pass through. For example, Twilio's completed call status means the call was answered and ended normally. The answering destination could be a person, an IVR menu, or voicemail. That technical status doesn't mean the caller's business request was completed.
Likewise, an AI label is only useful when the team has defined what counts as a qualified lead. An inquiry can be qualified without becoming a booking.
One Call, With and Without a Confirmed Booking
Consider this hypothetical repair appointment request:
| Field | Example record |
|---|---|
| Call and source | DEMO-CALL-A; campaign repair-appointments captured by the tracking provider |
| Attribution rule | For this example, credit the latest matched paid-search visit before the call |
| Caller request | Book a repair appointment |
| Qualification | Requested repair and service address meet the team's written criteria |
| Call handling | Caller reached the booking workflow |
| Booking result | Pending until the calendar confirms a saved appointment |
| Revenue | Unknown until linked sales or payment records are available |
| Next owner | Booking team if confirmation fails |
If the calendar saves the appointment, report a confirmed booking and retain its booking reference. That confirms the slot, not payment for the repair.
If the save fails, keep the source and qualification records, leave the booking unconfirmed, and assign the booking team to follow up. You still have a qualified inquiry linked to the campaign. The requested appointment just hasn't been secured.
This is why verifying a CRM update means checking the saved record, not relying on what was said during the call.
When there isn't enough information to judge qualification, use unknown or pending. Unknown revenue isn't automatically zero either. If the team calls back, retain the callback's own call ID and link it to the original lead rather than creating another new acquisition.
An ad platform may also let you assign a value to a lead. Google, for example, accepts an advertiser-assigned conversion value. Keep that assigned value separate from confirmed sales revenue in your business reports.
How to Set Up and Test Call Tracking
Start With One Channel and One Outcome
- Choose the decision and conversion event. A conversion is the action you choose to count. Decide whether this report needs calls, qualified leads, bookings, or sales.
- List the places that display a number. Include the relevant ads, listings, print materials, landing pages, and click-to-call links. Select static or dynamic tracking for the detail you need.
- Configure each number's source and destination. For website replacement, set a working fallback number for missing script or source data. Establish whether calls to it still pass through the tracking service.
- Connect the needed records. Decide which call ID and source fields pass between systems, which source gets credit, who owns the final business result, and how repeated events are handled.
- Review data handling. Have the responsible team check website tracking, recording or transcription, applicable notices or consent, access, and retention before enabling those features.
- Make controlled test calls. Inspect the destination, source fields, and final records before extending the setup to more channels.
An End-to-End Test Matrix
Run the rows that match your setup. Transfers, business-system saves, and conversion imports need testing only if you use those workflows.
| Test | Check the call | Check attribution | Check the result |
|---|---|---|---|
| Static offline number | Correct business destination receives it | Correct flyer, listing, or other placement appears | One inbound call event is recorded |
| Tagged website visit | Visible number and click-to-call link agree | Expected campaign or visit fields appear | Call ID links to the intended record |
| Direct website visit | Approved number reaches the business | Source follows the chosen policy, including any retained earlier source | A direct visit doesn't unexpectedly replace earlier campaign credit |
| Script unavailable or source missing | Fallback number still works | Retain any known source; mark unavailable fields as unknown | If the fallback bypasses tracking, document the reporting gap |
| Return visit or saved number | Call still reaches the business | Match follows documented number-reuse and attribution-window rules | It isn't automatically treated as a new lead |
| Missed or abandoned call | Status matches what happened | Available source stays attached | Follow-up has an owner; lead quality stays unknown without evidence |
| Transfer or callback | Original call, transfer, and callback have distinct linked records where supported | Original source isn't overwritten | The record distinguishes an attempted transfer from an accepted handoff |
| Business-system save fails | Call record is retained | Original source remains available | Action stays unconfirmed and someone owns recovery |
| Existing conversion plus imported sale | Records are matched to the correct call or lead | Crediting policy is consistent | The same business event isn't counted twice in the chosen reporting or bidding goal |
For every test, note the expected result, observed result, evidence location, and responsible person. In the flyer example, expect the booking team to receive the call and the report to show the flyer source. Save the call ID so someone else can check both.
A missing-data test can pass when the caller reaches the business and the limits are clear. If the call remains tracked, preserve known source data and mark unavailable fields as unknown. If the fallback bypasses tracking, document the gap instead of expecting a call record in that report.
After launch, report calls, qualified leads, and confirmed business outcomes separately. Show unknown or unmatched records too. State the reporting period and how repeat or spam calls were handled.
Is Google Ads Call Tracking Enough?
It can be enough if you only need to measure eligible calls associated with Google Ads. To compare those calls with print, directory listings, or other channels, you'll need tracking for those sources as well.
Google's phone-call conversion overview covers several measurement options:
- Calls directly from eligible ads or call and location assets.
- Calls to a forwarding number displayed on a website after an ad interaction.
- Clicks on a phone-number link on a mobile website after an ad interaction. A tracked click alone doesn't prove a connected call.
- Call conversions imported from another system that records sales or other actions.
Check what your account counts as a conversion. Google's calls-from-ads guidance describes AI-based lead qualification from recordings where supported and enabled, with call-duration measurement when recordings are unavailable and ad-interaction data when duration is unavailable. The recording feature is currently limited to calls where both parties are in the US or Canada; account settings and eligibility still apply.
If you also import later results, review which conversion actions your reports and bidding use. Google warns against counting the same calls through overlapping conversion actions. You can measure call leads and confirmed sales separately, but don't treat two records of the same event as two business results.
Where Airsound Fits in a Tracked Call Workflow
Once a tracked call arrives, the caller still needs help. At Airsound, our AI voice agents can collect the caller's details, route the conversation, update connected CRM records, trigger SMS, and hand off to a person. Our visual workflow builder lets teams configure those steps around the request.
Use preview calls to check how the agent recognizes the request, answers from its knowledge base, and follows handoff rules. Transcripts and call outcomes give the team a record to review afterward.
Source attribution comes from the tracking setup. For a combined workflow, test that the tracking number reaches the right answering flow and that the source and call reference can be linked to the business result. Passing those fields depends on the connected systems and their configuration.
Start with one source comparison that would change a decision, then test a call through to the result you intend to count. Expand the setup once you can explain where that result came from and what supports it.
Bring one call flow to an Airsound demo and test how the agent answers, handles the requested action, and responds when that action can't be completed.
