Call Tracking · Module 02

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.

Source DNI
Session DNI
Google Ads
Brand · Search · UK
Organic
SEO · Blog traffic
Social Media
Meta · Retargeting
555-666-8890
555-666-8888
555-666-8889
555-666-8895
555-666-8893
555-666-8894
555-666-8899
555-666-8897
555-666-8898
Call Attribution · Live
SourceGoogle Ads
CampaignBrand · Search · UK
Number555-666-8888
OutcomeTest drive booked
Campaign assigned · number matched · call attributed
Two modes
Source & session attribution
Campaign-level or keyword-level. Same platform, same snippet.
One snippet
Not one per channel, not one per campaign
A single JS tag handles attribution across all your sources and campaigns.
Seamless
Number swap
Works on any modern website.
Two approaches

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.

Source DNI

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
Best for: proving which campaigns drive calls
Session DNI

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
Best for: optimising paid search at keyword level
How it works

One snippet. Two attribution approaches.

1
Embed the snippet

Place a small JavaScript snippet into your website's global header to enable dynamic number tracking.

2
Link your numbers

Assign a dedicated phone number to each marketing source you want to track: Google Organic, Facebook, LinkedIn, and so on.

3
Identify the source

The script automatically detects where a visitor came from by scanning their browser's referral data or UTM parameters.

4
Swap the display

Your website instantly replaces the default phone number with the one assigned to that visitor's specific referral source.

Source vs Session

Feature comparison: Source DNI and Session DNI, side by side.

Source DNISession DNI
AttributionChannel & campaignVisitor & session
Data capturedSource, campaign, per-call attributionKeywords, UTMs, pages, visitor journey
Number poolOne per source, pools optionalPool sized to peak concurrency
Keyword trackingPossible, not cost-effective at scale
Google Ads offline conversionsNo
UTM passthrough
Setup complexityLowMedium
iovox Insights compatible
Best whenChannel and campaign ROI is the goalKeyword and journey detail matters
Customer story

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."

William Tran · Senior Program Manager · Abeille Assurances
Web
Full attribution
RFP
Selected solution
Enterprise
Insurance-grade
Analytics dashboard
Abeille Assurances

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.