How Dynamic Number Insertion Works (And What Operators Actually Look For)

1. What Is Dynamic Number Insertion?

Dynamic number insertion is a JavaScript-based technology that detects a website visitor's traffic source and replaces the static phone number on the page with a unique tracking number assigned to that source. Every call is then tied to the campaign, keyword, or channel that drove the visit.

Dynamic number insertion solves a problem that has existed since the first business ran a print ad and a radio spot simultaneously: which one drove the call?

The mechanism is straightforward. A small JavaScript snippet loads on your website. When a visitor arrives, the script reads session data, including UTM parameters, referrer, and keyword, and swaps the displayed phone number for a tracking number mapped to that source.

The visitor sees a real, callable number. You see exactly where they came from.

Here's what that looks like in practice.

• A visitor arrives from a Google Ads campaign for "emergency HVAC repair." They see tracking number A.
• A visitor arrives from organic search for the same query. They see tracking number B.
• A visitor arrives from a Facebook retargeting ad. They see tracking number C.

All three numbers route to the same destination. But each call is logged separately, with its source, duration, recording, and outcome.

That's the core function. But DNI is not just a marketing attribution tool.

When DNI is paired with conversation analysis, every attributed call becomes a data point about what was said, whether the call was answered, and whether it converted. That's the difference between knowing a campaign drove 40 calls and knowing it drove 40 calls, 28 of which were answered, 14 of which converted, and 6 of which mentioned a competitor by name.

Convirza builds DNI as the attribution layer inside a broader call intelligence infrastructure. The number swap is the entry point. What happens to the data after the call ends is where the revenue signal lives.

I've worked with operators who had DNI running for two years before they realized they were only using 10% of what the data could tell them. The number swap was working. The downstream analysis was not.

That gap, between capturing the call and acting on what's inside it, is the problem worth solving.

The Bureau of Labor Statistics data on customer service occupations shows frontline phone staff represent one of the largest labor cost centers in service businesses.

DNI is the only way to measure whether that labor investment is converting, by channel, by campaign, and by agent.

2. Why Do Multi-Location Businesses Lose Revenue on Calls?

Why most multi-location businesses cannot see the revenue they are losing on every call.

Multi-location businesses lose call revenue because they have no visibility into what happens between a campaign driving a call and a sale closing. Without dynamic number insertion, there is no attribution. Without attribution, there is no accountability. The result is marketing spend optimized for clicks, not conversions.

The villain here is not a bad campaign or an undertrained agent.

It is measurement blindness.

When you cannot see which campaigns drive calls that convert, you optimize for the wrong signals. You cut the campaign that drove 20 calls and keep the one that drove 200 clicks, not realizing the 20-call campaign had a 60% conversion rate and the click campaign had a 4% rate.

That is not a hypothesis. I have seen this exact pattern across dozens of multi-location operators.

Here is what the data shows about the structural problem.

20 to 30% of inbound calls never connect to a live person, according to Convirza data. That is not 5%. That is not a rounding error.

At 500 calls per month, that is 100 to 150 calls going unanswered. Every month. Per location.

If your average call represents $300 in potential revenue, that is $30,000 to $45,000 in invisible revenue leakage. Per location. Per month.

Multiply across 10 locations and the number becomes $3.6 million annually. From one fixable problem.

But here is the compounding issue: without DNI, you do not even know which campaigns are driving the calls that go unanswered. You cannot fix what you cannot see.

The performance variance data makes this worse. The delta between the best and worst performing location in a multi-location business is 3x, according to Convirza data. Same market. Same product. Same campaigns.

Three times the conversion rate. From one location to another.

That variance is not random. It is a data problem. The top location is doing something differently. Without call-level attribution tied to source data, you cannot identify what that is or replicate it.

There is also the after-hours problem. 28% of bookable demand arrives after business hours, according to Convirza data.

That demand is not being lost because of bad agents. It is being lost because no one is there to answer.

DNI does not solve the after-hours gap by itself. But it identifies which campaigns are driving after-hours calls, so you can make an informed decision about staffing, routing, or automated response.

Without DNI, that 28% is invisible. You see a missed call. You do not see that it came from your highest-converting campaign at 7:14 PM on a Tuesday.

3. What Does the Industry Benchmark Data Show?

Every proprietary Convirza benchmark, contextualized and applied to DNI decisions.

Convirza's benchmark data, drawn from 25 years of proprietary call data, shows that call attribution failures are systematic, not isolated. The numbers reveal a consistent pattern: businesses invest in driving calls, then lose the revenue signal the moment the call arrives. DNI is the fix for the first failure in that chain.

Let me walk through what the data actually shows, and what it means for how you should think about DNI deployment.

Start with the most fundamental benchmark. 96% of inbound calls are analyzed by zero humans.

Reference: U.S. Census Bureau small business data.