How Dynamic Number Insertion Works
Dynamic number insertion, usually shortened to DNI, is a call tracking method that changes the phone number a visitor sees on your website based on how that visitor arrived. The goal is attribution: when someone calls, you can connect that call to the source, campaign, keyword, or session that drove it. Google Ads describes a similar setup for website call conversion tracking, where dynamically generated forwarding numbers can replace your business number on your site so you can see which keywords, ads, ad groups, and campaigns led to calls.
“When installed on a webpage, it enables Dynamic Number Insertion (DNI).” — CallRail
What dynamic number insertion means
At a basic level, DNI uses a small JavaScript snippet on your website to swap a static phone number for a trackable one. Invoca describes DNI as a marketing technology that gives businesses attribution for phone calls driven from digital advertising and the website, while CallRail explains that its JavaScript detects phone numbers on the page and swaps them with the correct tracking number based on how the visitor came to the site.
That means two visitors can land on the same page and see different phone numbers, even though both calls still reach the same business. CallRail says each visitor can be matched to a specific tracking number, and Ringba explains that number pools let the system associate browser-session data with the caller based on the number dialed.
How dynamic number insertion works step by step
1. A call tracking script is added to the website
DNI starts with a JavaScript tag or snippet placed on the pages where your phone number appears. Google says website call conversion tracking requires a tag plus a phone snippet that replaces the number on your site with a Google forwarding number, while Ringba says its call tracking tag code snippet is placed on landing pages to replace the default number with a Ringba number.
2. The system identifies the visitor’s source or session
When a visitor arrives, the script checks how they got there. Depending on the platform, this may include source, campaign, keyword, landing page, or session context. CallRail says its script can store the visitor’s source in a cookie and continue showing the same tracking number on return visits, while Google says its setup can show which keywords, ads, ad groups, and campaigns are leading to call conversions.
3. The visible phone number is swapped
Once the source or session is identified, the script replaces the normal website number with a tracking number. CallRail describes this as detecting the numbers on the page and swapping them with the correct tracking number, and Invoca says the code dynamically replaces the phone number on each page with a unique trackable number tied to each visitor and session.
4. The caller dials the displayed tracking number
The visitor sees the swapped number and calls it like a normal business number. Behind the scenes, the platform routes the call to the real destination number. CallRail defines the destination number as the number where the phone will ring when customers dial the tracking number.
5. The platform connects the call to marketing data
Because the system knows which tracking number was shown to that visitor, it can connect the phone call back to the source that generated it. Google says this lets advertisers assess which keywords, ads, ad groups, and campaigns lead to call conversions. CallTrackingMetrics says its DNI connects session data to offline calls and texts, and Ringba says number pools help organize landing-page visitor information alongside call data for reporting.
Why marketers use DNI
The main reason is attribution. If you only display one static number everywhere, you may know that calls happened, but not what caused them. DNI closes that gap by linking calls back to campaigns and on-site activity. Google’s documentation is explicit that dynamically generated forwarding numbers on a site can show which keywords and campaigns drive calls, and CallRail says visitor-level tracking can reveal source, campaign, pages visited, and actions before and after the call.
DNI also improves optimization. When marketers know which channels and pages produce qualified calls, they can shift budget more intelligently, improve landing pages, and reduce wasted spend. Google also supports setting a minimum call length for call conversions, which helps filter out short, low-value calls from more meaningful ones.
Best practices for implementing DNI
Install the tag on every page where the phone number appears. Google says the phone snippet should be installed on site pages where your phone number appears, and Ringba says its code snippet should be pasted on each landing page where the number should appear.
Use a number pool when you want visitor-level attribution, not just basic number replacement. Ringba states that without a number pool, the tag can replace one static number with another static number, but it cannot capture browser-session data or connect that data with caller data in reporting.
Match the phone number exactly during setup. Google’s instructions for calls-from-website conversion tracking say the phone number entered needs to have the exact digits it has on the website.
Test dynamic pages and embedded elements carefully. Invoca’s support documentation notes that a tag running in the main window cannot directly manipulate the DOM of an iframe unless they share the same origin, which means some sites need extra implementation work for full number swapping coverage.
Popular brands that support dynamic number insertion
Popular platforms that support dynamic number insertion include CallRail, Invoca, CallTrackingMetrics, Ringba, and Phonexa, with each platform using DNI to improve call attribution and campaign visibility.
Read the full article about Best Call Tracking Software.
FAQ
Does dynamic number insertion change the real business phone line?
No. DNI changes the number displayed to the visitor, but the call is still routed to the destination number your business uses to receive calls.
Is DNI only for paid ads?
No. It is commonly used for paid traffic, but vendor documentation also describes using DNI for websites, landing pages, and broader source-based attribution.
Can DNI help with SEO and organic call attribution?
Yes, in the sense that it can help measure calls generated from organic visits as long as the implementation is configured correctly. Call tracking vendors describe DNI as a way to connect calls back to sources and session data from website visits, not only ads.
