Call Tracking Marketing Dynamic Number Insertion 3

Question 1

What is 'source-level' DNI as opposed to 'session-level' DNI?

Accepted Answer

Assigning one tracking number per traffic source (e.g., Google, Facebook)

Answer

Source-level DNI assigns a single unique number to each traffic source channel, rather than to each individual visitor session, providing channel-level attribution.

Question 2

Why might a marketer choose session-level DNI over source-level DNI?

Accepted Answer

Session-level provides visitor-level attribution including keyword and ad data

Answer

Session-level DNI captures granular data including which specific keyword, ad, or landing page each caller came from, providing much deeper insight than source-level.

Question 3

What does 'swap target' mean in a DNI configuration?

Accepted Answer

The specific phone number on the webpage that the DNI script replaces with a tracking number

Answer

The swap target is the specific phone number (or HTML element) on the page that the DNI JavaScript identifies and replaces with the appropriate tracking number.

Question 4

How does DNI help optimize Google Ads bidding strategies?

Accepted Answer

By feeding call conversion data back into Google's Smart Bidding algorithms

Answer

DNI-attributed call conversions imported into Google Ads give Smart Bidding algorithms real call data to optimize bids toward campaigns and keywords that drive calls.

Question 5

What type of website visitors would a 'direct' DNI number pool be assigned to?

Accepted Answer

Visitors who typed the URL directly or had no trackable referrer

Answer

A 'direct' pool captures visitors with no identifiable referrer—those who typed the URL, used bookmarks, or came from untracked sources.

Call Tracking Marketing Practice Test

Call Tracking Marketing Practice Test

Call Tracking Marketing Dynamic Number Insertion 3