Every web call attributed, from channel level to exact keyword.
One JavaScript snippet. Two levels of attribution. Campaign-level source tracking for channel and campaign ROI. Keyword and session-level tracking for full visibility into the customer journey. The right choice depends on what you need to know.
What is dynamic number insertion?
Dynamic number insertion (DNI) shows each website visitor a tracking number tied to how they arrived. With iovox, each call can be attributed down to the keyword, landing page and journey before the phone even rings.
Dynamic Numbers for channel and campaign attribution, or the entire customer journey.
Both approaches run on the same iovox infrastructure. The right fit depends on your attribution goals, and you can move between them without re-implementing.
Campaign & channel attribution
One tracking number per source: per channel, campaign, or ad group. JavaScript swaps it in based on where the visitor came from. Pools are optional for teams managing large campaign counts.
- One number per campaign or channel
- Channel and campaign ROI without keyword granularity
- Pools optional. Scale to large campaign counts when needed.
- Right-sized for channel and campaign attribution goals
Visitor & keyword attribution
A pool of numbers rotates per visitor session. Every call is pre-attributed to the exact keyword, UTM, landing page, and visitor journey, before the phone rings.
- Keyword, page, and UTM attribution per call
- Full GCLID passthrough for offline conversions
- Google Ads, GA4, and Meta native integrations
- Pool auto-sized to peak concurrent sessions
One snippet. Two attribution approaches.
Place a small JavaScript snippet into your website's global header to enable dynamic number tracking.
Assign a dedicated phone number to each marketing source you want to track: Google Organic, Facebook, LinkedIn, and so on.
The script automatically detects where a visitor came from by scanning their browser's referral data or UTM parameters.
Your website instantly replaces the default phone number with the one assigned to that visitor's specific referral source.
Feature comparison: Source DNI and Session DNI, side by side.
| Source DNI | Session DNI | |
|---|---|---|
| Attribution | Channel & campaign | Visitor & session |
| Data captured | Source, campaign, per-call attribution | Keywords, UTMs, pages, visitor journey |
| Number pool | One per source, pools optional | Pool sized to peak concurrency |
| Keyword tracking | Possible, not cost-effective at scale | ✓ |
| Google Ads offline conversions | No | ✓ |
| UTM passthrough | ✓ | ✓ |
| Setup complexity | Low | Medium |
| iovox Insights compatible | ✓ | ✓ |
| Best when | Channel and campaign ROI is the goal | Keyword and journey detail matters |
The WebCallBack & Dynamic Numbers combination that won the RFP.
"We found the Dynamic Number call tracking and WebCallBack solutions from iovox were the best fit to meet our needs and help us achieve our goals."
Frequently asked questions
What is the difference between Source DNI and Session DNI?
Source DNI gives one tracking number per channel, campaign or ad group, for channel and campaign ROI. Session DNI rotates numbers per visitor, attributing each call to the exact keyword, UTM, landing page and journey.
How do I set up dynamic number insertion?
Place one small JavaScript snippet in your website's global header. It detects where each visitor came from and swaps in the matching tracking number.
Does iovox dynamic number insertion work with Google Ads and GA4?
Yes. Session-level tracking integrates natively with Google Ads, GA4 and Meta, with full GCLID passthrough for offline conversions.
Can I switch between the two approaches later?
Yes. Both run on the same iovox infrastructure, so you can move between them without re-implementing.
See every conversation attributed, at the level that fits your business.
30 minutes with an iovox specialist. We'll show you source DNI, session DNI, and which one makes sense for your business today.