Dynamic Number Insertion: A Practical Guide for Marketers

Dynamic number insertion (DNI) swaps the phone number displayed on your website in real time based on how each visitor arrived, so every inbound call gets tied to the campaign, keyword, or channel that drove it. If you run Google Ads, SEO, or any mix of paid and organic traffic, and phone calls matter to your business, the immediate next step is simple: confirm you have a call-tracking provider and add the DNI JavaScript snippet to every page of your site.

DNI works the same way a cookie tracks a form fill, except it closes the loop on phone leads. Without it, every call that comes in looks like it came from nowhere, and you are making budget decisions blind.

Key Takeaways

Dynamic number insertion closes the attribution gap between your marketing spend and your inbound phone calls, making it one of the highest-leverage tracking setups a phone-dependent business can run.

Point	Details
DNI definition	DNI swaps your displayed phone number per visitor session so every call maps to its originating campaign or keyword.
Pool sizing matters most	Size your pool using peak concurrent visitors times session duration, then add a safety buffer to avoid exhaustion.
Test before you go live	Run private-window UTM tests, a gclid simulation, and image-swap verification before declaring the setup complete.
U.S. compliance is not optional	Call recording rules vary by state; all-party consent states require a disclosure message, and TCPA governs automated callbacks.
Tradewindsunitedmedia	Tradewindsunitedmedia implements the full DNI stack, including site updates, analytics wiring, and Google Ads conversion import, for small businesses.

How does dynamic number insertion actually work?
What do marketers actually gain from DNI?
When should you use DNI, and when should you skip it?
How to implement DNI: a step-by-step checklist
What integrations and reports should you build?
How do you test and troubleshoot DNI?
What U.S. privacy and compliance rules apply to DNI?
How much does DNI cost, and how do you size your number pool?
What does an agency DNI implementation actually look like?
The DNI detail most agencies get wrong
Tradewindsunitedmedia handles the setup so you can focus on the calls
Sources

How does dynamic number insertion actually work?

The technical flow is straightforward, even if you are not a developer. Here is what happens from the moment a visitor lands on your page to the moment their call is logged:

Referrer and parameter detection. The DNI script fires on page load and reads the visitor’s traffic source: UTM parameters, gclid (Google Ads click ID), organic referrer, or direct.
Session lookup or creation. The script checks whether this visitor already has an active session (stored in a cookie or local storage). If yes, it retrieves the number already assigned. If no, it requests a new one.
Number assignment from the pool. The platform pulls an available tracking number from your pre-provisioned pool and reserves it for this session.
DOM swap. The script finds every phone number on the page that matches your configured swap-target selectors (CSS classes, data attributes, or specific text patterns) and replaces the default number with the assigned tracking number.
Call routing and logging. When the visitor calls, the platform routes the call to your real business number and simultaneously logs the session metadata: source, medium, campaign, keyword (if gclid is present), landing page, and pages visited.

Session persistence is what separates DNI from simple page-level swaps. According to CallRail’s implementation documentation, the tracking number stays assigned to the visitor for the full session duration, even across subdomains, so a visitor who browses three pages before calling sees the same number throughout.

Pro Tip: Configure your swap targets using a dedicated CSS class (e.g., .dni-phone) on every phone number element in your HTML rather than relying on text-pattern matching. Text-pattern matching can break when number formatting varies across your site.

What do marketers actually gain from DNI?

The short answer: you stop guessing which campaigns generate phone leads and start knowing.

Primary benefits:

Campaign-to-call attribution. Every call maps to a specific source, medium, and campaign. You can see that your Google Ads campaign drove several calls last month while your organic traffic drove some.
Keyword-level insights. When DNI captures gclid values and integrates with Google Ads, you can trace a call back to the exact search term that triggered the click. That is the kind of data that justifies pausing a keyword or doubling a bid.
Budget reallocation. DNI is a direct tool for budget optimization: agencies use call attribution to identify high-performing channels and cut spend on sources that generate clicks but no calls. Pair this with a data-driven marketing strategy and the decisions practically make themselves.

Secondary benefits worth noting:

Caller context reaches your sales team before they pick up (source, landing page, prior visits).
Call recordings and transcripts feed creative and landing-page tests.
DNI data feeds CRM lead records automatically, so sales and marketing share the same picture of lead quality.

Metrics DNI directly feeds:

Calls by source and campaign
Cost-per-call by channel
Call-to-lead conversion rate
Revenue per call (when CRM is connected)

DNI improves offline-to-online attribution for phone leads the same way cookies do for form fills. The difference is that it adds operational overhead, including number provisioning, routing configuration, and ongoing pool monitoring, that teams need to budget for alongside the platform cost.

When should you use DNI, and when should you skip it?

DNI adds real value in specific situations. It is not the right tool for every business.

DNI makes sense when:

You run multiple active campaigns simultaneously (paid search, SEO, social, display) and need to separate their call contributions.
Phone calls represent a meaningful share of your leads, not just an occasional inquiry.
You have mixed online and offline channels and need a unified attribution picture.
You want keyword-level data from Google Ads to inform bid strategy.

DNI is probably overkill when:

Your site generates fewer than a handful of calls per week. The operational overhead outweighs the insight.
You run a single static campaign with one traffic source. A dedicated static tracking number is simpler and cheaper.
Brand consistency is a hard requirement and your legal or franchise agreements prohibit displaying numbers other than the registered business number.

Known limitations to plan around:

Pool exhaustion. If your pool is undersized for peak traffic, some visitors will see the default number and those calls go unattributed.
Image-embedded numbers. Phone numbers baked into banner images or CTA graphics will not swap unless the script is specifically configured to target those elements.
Cross-device attribution. A visitor who researches on mobile and calls from a desktop is treated as two separate sessions.
Direct and returning visitors. Organic returning visitors who clear cookies or use a new device lose their session history, creating attribution gaps.
NAP consistency for SEO. Search engines crawl your site and may index the tracking number instead of your real number, which can hurt local SEO if not handled correctly.

How to implement DNI: a step-by-step checklist

This checklist is ordered the way an agency would actually run the project. Work through it top to bottom, or hand it to your developer.

Pre-implementation

Audit every phone number placement. Check HTML, header, footer, sidebar, CTA buttons, images, and pop-ups. List every location and its format.
Estimate your pool size. Use peak concurrent visitors, average session duration, and a safety buffer (covered in the costs section below).
Confirm destination routing. Identify the real phone number(s) calls should forward to and any IVR or call-routing rules you need to preserve.
Choose a call-tracking provider. Select a platform that supports DNI, GA4 integration, Google Ads gclid capture, and CRM export.

Installation

Add the JavaScript snippet sitewide. Installing DNI works like adding Google Analytics: paste the provider’s script tag into the <head> of every page, or deploy it via Google Tag Manager.

A minimal swap example looks like this:

<!-- DNI Swap Script (example structure) -->
<script>
  (function() {
    var defaultNumber = '(555) 123-4567';
    var trackingNumber = getTrackingNumberFromPool(); // provider API call
    document.querySelectorAll('.dni-phone').forEach(function(el) {
      el.textContent = trackingNumber || defaultNumber;
    });
  })();
</script>

Configure swap-target selectors. Add the .dni-phone class (or your provider’s equivalent) to every phone number element in your HTML. For anchor tags, update both the visible text and the href="tel:..." attribute.
Set session duration. Match your session window to your typical sales cycle. Most platforms default to 30 minutes; extend it if visitors commonly research for longer before calling.

Number provisioning

Create your tracking pools. Provision separate pools for each campaign source you want to track independently (e.g., one pool for Google Ads, one for organic).
Choose local vs. toll-free numbers. Local numbers tend to get higher answer rates for service-area businesses. Toll-free numbers signal national reach.
Set number reuse timing. Configure how long after a session ends before a number returns to the pool. Thirty minutes is a common default.

Analytics wiring

Enable gclid capture in your call-tracking platform and confirm Google Ads auto-tagging is on.
Connect to GA4. Push call events as GA4 conversions so calls appear alongside form fills in your reports.
Import call conversions into Google Ads. Map the gclid from each call back to the originating click so Smart Bidding can factor in phone leads. This is the step that makes Google Ads management genuinely data-driven.
Map call metadata to CRM fields. Push source, medium, campaign, keyword, and landing page into the lead record at the moment the call comes in.

Pro Tip: For phone numbers embedded inside images or CTA graphics, coordinate with your designer to add a data-dni-target attribute to the image container. Without a consistent hook in the markup, the script cannot find or replace those numbers.

What integrations and reports should you build?

DNI data is only as useful as what you connect it to. The platform logs the call; your job is to route that data somewhere it can drive decisions.

Essential integrations:

GA4 event export. Send call events with source/medium/campaign dimensions so calls appear in the same reports as form fills and purchases.
Google Ads conversion import. Use gclid mapping to import calls as conversions. Smart Bidding will use this data to optimize toward callers, not just clicks. See how Google Ads drives results when conversion data is complete.
CRM lead creation. Create a new lead record on call start or call end (your choice), pre-populated with UTM values, landing page, and call duration.
Call recording storage. If you record calls, store recordings in a compliant location and link them to the CRM record for sales coaching and quality review.
Call flow optimization. Platforms like Callflow can help you design and test the routing logic that handles calls after DNI assigns them, which matters when you have multiple departments or locations.

Reports to build from day one:

Report	Primary metric	Decision it drives
Calls by source/medium	Call volume per channel	Budget reallocation across channels
Calls by keyword	Call volume per search term	Bid adjustments and negative keywords
Cost-per-call by campaign	Spend divided by calls	Campaign pause or scale decisions
Call-to-lead conversion rate	Calls that become CRM leads	Landing page and offer testing
Revenue per call	Pipeline value per call	Channel-level ROI calculation

Push UTM values, the landing page URL, pages visited during the session, and any agent notes into the CRM record. That combination gives sales context before the follow-up call and gives marketing a feedback loop on lead quality.

How do you test and troubleshoot DNI?

Get this right before you go live. A broken DNI setup is worse than no DNI at all because you will collect data you cannot trust.

Functional tests to run before launch

Private browsing with UTM parameters. Open an incognito window, navigate to yoursite.com?utm_source=google&utm_medium=cpc&utm_campaign=test, and confirm the phone number on the page changes from the default.
Simulated gclid test. Append ?gclid=test to your URL and verify the platform logs a paid-search session with the tracking number displayed.
Cookie-clearing test. Clear cookies, revisit the site, and confirm a new tracking number is assigned. Then revisit without clearing cookies and confirm the same number persists.
Image and CTA swap verification. Manually check every image-embedded number and CTA button to confirm the swap is working, not just the HTML text nodes.
Cross-subdomain test. If your site uses subdomains (e.g., shop.yoursite.com), navigate between them and verify the same tracking number follows the session.

Common failure modes

Failure	Symptom	Fix
Pool exhaustion	Visitors see the default number	Expand pool size; monitor utilization
Wrong swap-target selector	Number does not change	Audit CSS classes; use browser inspector
Script race condition	Number flickers or reverts	Load DNI script earlier in `<head>`; defer conflicting scripts
Cross-subdomain session break	New number assigned on subdomain	Configure shared cookie domain
gclid not captured	Calls show as direct in reports	Confirm auto-tagging is on in Google Ads

Pro Tip: Open your browser’s developer console (F12) and filter network requests for your call-tracking provider’s domain. You should see an API request on page load that returns the assigned tracking number. If you see a 4xx or 5xx error, the pool assignment is failing server-side.

What U.S. privacy and compliance rules apply to DNI?

DNI touches three distinct compliance areas for U.S. businesses. None of them are optional.

Cookie consent:

DNI relies on cookies or local storage to persist session assignments. Some providers classify these as strictly necessary cookies, but you, as the site owner, are responsible for your cookie notice and disclosure.
U.S. federal law does not currently require opt-in consent for cookies the way GDPR does, but California (CCPA/CPRA) and other state privacy laws may affect how you categorize and disclose tracking cookies. Review your consent banner configuration with legal counsel.

Call recording and state wiretapping laws:

Recording laws vary by state. Federal law and most states require only one-party consent (the business can record without notifying the caller). California, Florida, Illinois, and several other states require two-party (all-party) consent.
Configure your call-tracking platform to play a recording disclosure message before calls connect in all-party consent states. Document that configuration.

TCPA considerations:

If your DNI setup triggers automated outbound callbacks or SMS follow-ups, the Telephone Consumer Protection Act (TCPA) applies. Automated outbound contact to cell phones without prior express written consent carries significant liability.
Get legal review before enabling any automated callback or SMS workflow connected to your DNI data.

Practical compliance steps:

Keep a written record of your consent flow and cookie disclosure.
Store only the minimum PII needed in your analytics platform (avoid logging full caller phone numbers in GA4 where possible).
Audit your data-retention settings annually.

How much does DNI cost, and how do you size your number pool?

Pricing across call-tracking platforms typically combines three components: a monthly platform fee, a per-number monthly charge for each tracking number in your pool, and per-minute fees for call duration. Some enterprise plans bundle minutes; entry-level plans charge separately.

Pool sizing: the practical approach

Pool sizing is the most common operational failure point.

Example: 200 peak concurrent visitors × 0.5-hour session = 100 numbers needed at peak.

Source: VeloCalls DNI sizing guidance

Cost control tips:

Start with a conservative pool and expand based on real utilization data, not estimates.
Use local numbers for service-area businesses. They cost less per month than toll-free numbers and typically perform better for local calls.
Set number reuse timing as short as your session window allows. A 30-minute reuse window on a 30-minute session means numbers cycle back quickly, keeping your pool smaller.
Monitor utilization weekly for the first 60 days. If utilization regularly exceeds 80%, expand the pool before you hit exhaustion.

What does an agency DNI implementation actually look like?

Here is the workflow Tradewindsunitedmedia runs for a typical small-business client, from first conversation to reporting handoff.

Project phases

Discovery (Week 1). Audit the client’s site for all phone number placements, confirm the call-tracking provider, document destination routing, and establish baseline call volume from existing records.
Configuration (Week 1–2). Provision tracking pools by campaign source, add CSS swap-target classes to the site’s HTML, install the DNI script via Google Tag Manager, and configure gclid capture.
Analytics wiring (Week 2). Connect GA4 event export, import call conversions into Google Ads, and map call metadata fields to the CRM.
Testing (Week 2–3). Run the full QA checklist: private-window UTM tests, gclid simulation, cookie-clearing tests, image-swap verification, and cross-subdomain checks.
Launch and monitoring (Week 3). Go live, monitor pool utilization daily for the first two weeks, and confirm call attribution is appearing correctly in GA4 and Google Ads.
Reporting handoff (Day 30). Deliver the first monthly report showing calls by source, cost-per-call, and call-to-lead conversion rate. Walk the client through interpreting the data.

What the client needs to provide:

Access to Google Tag Manager (or site FTP/CMS access for direct script install)
Google Ads account access for conversion import
CRM admin credentials for field mapping
Confirmation of destination phone number(s) and any IVR rules

What to expect in the first 30–90 days:

Days 1–30: Data collection. Call volume by source starts populating. Expect some gaps as the system calibrates.
Days 30–60: First optimization decisions. Identify which campaigns are generating calls and which are generating clicks with no calls. Pair this with budget allocation guidance to make the first real spend adjustments.
Days 60–90: Pool right-sizing. Adjust pool size based on real utilization data. Refine session duration settings. Begin keyword-level bid adjustments using call conversion data.

The DNI detail most agencies get wrong

The most overlooked part of a DNI setup is not the script install. It is the swap-target audit combined with pool sizing. Most teams add the JavaScript, test one phone number in the header, declare it working, and move on. Then three months later, the footer number, the mobile CTA button, and the contact page are all still showing the default number, and a third of calls are unattributed.

The fix is straightforward: before you touch the script, build a complete inventory of every phone number on the site, including images, PDFs linked from the site, and any third-party widgets. Assign a consistent CSS class to every one of them. Then size the pool based on real traffic data, not a gut estimate, and set a calendar reminder to review utilization at 30 and 60 days.

Tradewindsunitedmedia handles the setup so you can focus on the calls

Most small businesses that try to implement DNI on their own get the script installed and stop there. The attribution gaps from missed swap targets, undersized pools, and disconnected Google Ads conversions quietly cost them the insight they were trying to gain in the first place.

Tradewindsunitedmedia handles the full DNI implementation stack: site updates to add swap targets, script deployment via Google Tag Manager, GA4 and Google Ads conversion wiring, CRM field mapping, and a 30-day monitoring period to confirm the data is clean. You get a working attribution setup and a monthly report that shows exactly which campaigns are driving calls, what those calls cost, and which ones are converting. No guesswork, no half-finished setup sitting in your tag manager. Book a brief discovery call and we will scope the implementation and send a proposal within 48 hours.