Dynamic Number Insertion for Visitor-Level Call Tracking

What is dynamic number insertion?

Dynamic number insertion (DNI) is a technique that automatically swaps phone numbers on your website based on how each visitor found you. A visitor from Google Ads sees one number, a visitor from Facebook sees another, and an organic search visitor sees a third. This happens invisibly through a JavaScript snippet. When any of these visitors call, you know exactly which channel, campaign, and even keyword drove the call.

How DNI works technically

You add a lightweight JavaScript snippet to your website (or use Google Tag Manager). When a page loads, the script checks the visitor's referral source, captures click parameters like gclid, fbclid, and UTM tags, and assigns a unique tracking number from your number pool. That number is displayed everywhere on the page, replacing your default business number. The assignment is tied to the visitor's session, so if they browse multiple pages and call later, the attribution still holds.

DNI vs. static call tracking

Static call tracking assigns one number per campaign. If you run 10 Google Ads campaigns, you use 10 numbers. This tells you which campaign drove the call, but not which keyword or which specific visitor. DNI goes further by assigning numbers per visitor session, capturing the full click path including keyword, landing page, and device. For most businesses running online ads, DNI is essential for accurate ROI measurement.

Impact on page speed and SEO

CallScaler's DNI snippet loads asynchronously and weighs under 5KB. It does not block page rendering or affect Core Web Vitals. The number swap happens after the page paints, so there is no layout shift visible to users. Search engines see your original number in the HTML source, which is the correct behavior for local SEO. The swap is JavaScript-only, meaning Googlebot indexes your real business number while visitors see tracking numbers.

Setting up DNI for the first time

Create a number pool in CallScaler with at least 5-10 tracking numbers. Set the target number (the real number DNI should replace on your site). Copy the one-line JavaScript snippet and add it to your website header or via Google Tag Manager. The script automatically detects your phone number formats on the page and replaces them. No code changes to your site templates are needed. The whole setup takes about 5 minutes.

Best practices for DNI number pools

Optimize your DNI setup with these tips:

• Start with 8-12 numbers and add more if pool utilization exceeds 80 percent
• Use local area codes that match your business region for higher answer rates
• Set session duration to 20-30 minutes for most business websites
• Monitor the pool analytics dashboard weekly to right-size your pool

Troubleshooting common DNI issues

If numbers are not swapping on your site, check these common causes:

• The tracking script must load before the page finishes rendering — place it in the head tag
• The target number on the page must exactly match the format configured in CallScaler
• Phone numbers inside images or iframes cannot be swapped — use text-based numbers
• Ad blockers in your own browser may block the script — test in incognito mode

How DNI works with Google Tag Manager

If your site uses Google Tag Manager, you can deploy the DNI snippet as a custom HTML tag that fires on all pages. This avoids editing your site code directly and lets your marketing team manage the tracking script without developer involvement. Set the tag to fire on DOM Ready for the fastest number swap. GTM deployment works identically to a direct script install — same attribution, same speed, same results.

Using DNI alongside form tracking

The same tracking.js snippet that powers DNI also captures form submissions on your site. When a visitor fills out a form, it gets the same source attribution as a phone call — UTM parameters, gclid, landing page, and referrer. This means you can compare call and form conversion rates by source in a single dashboard without adding any extra code.