Home / Fundamentals / Dynamic number insertion: setup and pitfalls

Fundamentals · US-focused guide

Dynamic number insertion: setup and pitfalls

Understand website number swapping.

The essential answer

Dynamic number insertion (DNI) swaps a displayed phone number based on a visitor’s marketing source. CallRail documents a JavaScript snippet used for this purpose.

What to check before acting

Install the vendor-provided script according to its current instructions, ensure the intended numbers are eligible for swapping and test mobile click-to-call links. Check consent and privacy requirements for your implementation.

Practical next step

Run a test visit from each tagged campaign and confirm the correct number appears.

Implementation acceptance tests

Visit the site using tagged and untagged URLs, check the visible number and tel: link, place a call, and verify attribution. Repeat on mobile and after a consent choice where applicable.

Common failure points

Caching, script conflicts, insufficient number pools, hard-coded phone links, and redirect-stripped campaign tags can all undermine measurement. Use the vendor’s current installation instructions.

A worked example

A visitor arrives from paid search and sees a tracking number. The same page opened directly should display the appropriate number for that source. On mobile, tapping the number must dial the displayed number rather than an unchanged hard-coded link.

Choose the right level of attribution

Campaign-level numbers answer which placement or channel generated a call. Website visitor attribution can provide more detailed session context but requires a properly configured number pool and website script. The additional detail is worthwhile only if someone will use it to improve a decision. Define whether the outcome is calls, answered calls, qualified inquiries, appointments, or sales; these are not interchangeable.

Test the experience a caller actually has

Open the relevant page from a tagged campaign, a normal search visit, and a direct visit. Confirm the visible number, the mobile dial link, and the destination that answers the call. Repeat after changes to templates, consent settings, caching, or redirects. Check that the tracking system associates the test call with the expected source. If any link in that chain fails, fix the implementation before presenting the numbers as evidence.

Maintain a useful measurement record

Keep a simple inventory of tracking numbers, the campaign or page using each number, routing destination, owner, and date last tested. Document how repeat callers and spam are handled. Review a sample of records against the team’s actual lead outcomes. A small, regularly checked setup is often more useful than a large configuration nobody maintains.

The decision to take away

Verify visible text, tel links, forwarding and source records on each important device and channel.

A useful reporting template

For dynamic number insertion: setup and pitfalls, create a weekly report with five separate columns: marketing source, incoming calls, answered calls, qualified inquiries, and confirmed next steps. Add a notes column for routing failures, missing campaign labels, and unusual spikes. The source tells you where the interaction was attributed; the outcome tells you whether it was useful. If your organization cannot reliably record the last two columns yet, begin with a small manually reviewed sample rather than pretending the data is complete.

Questions to settle with your team

Before changing your setup for dynamic number insertion: setup and pitfalls, agree on who owns the tracking numbers, who may update forwarding destinations, and who checks that the reports match real conversations. Decide what to do with returning callers and contacts who use more than one channel. Ask whether your team needs campaign-level information or visitor-level detail, and document the trade-off between implementation complexity and the decision that extra detail would enable.

When to revisit the setup

Recheck the dynamic number insertion: setup and pitfalls workflow whenever campaigns, landing pages, staffing, business hours, or connected systems change. Place a controlled call, confirm the destination, inspect the source record, and verify the downstream outcome. Keep a brief log of the date and result. If a report changes sharply, first rule out a broken script, altered tags, duplicate imports, or a routing change before attributing the movement to marketing performance.

Related guides

• What is call tracking?
• How call tracking works from click to call
• Call tracking numbers: pools, forwarding and costs
• Call recording for marketing: responsible use
• CallRail pricing and usage

Editorial research updated September 17, 2026. This is not a hands-on review.

Sources and editorial standards

This guide explains a measurement workflow, not a claim of firsthand testing. For product-specific details, consult CallRail’s current US plan information and its call-tracking setup documentation. For our approach to commercial content, see our editorial policy.