Use this support article to learn about:
- How dynamic number insertion (DNI) works
- Cross-subdomain call tracking
- Swap precedence rules for dynamic number insertion
In order for dynamic number insertion to swap a number on your website, you’ll need to have the following in place on your website:
- A visible telephone number within HTML or an image
- A telephone number in one of the following formats:
111-222-3333, 111.222.3333, or (111) 222-3333
How Dynamic Number Insertion Works
There are several ways you can install dynamic number insertion on your website. Here are our other articles that will guide you through installing dynamic number insertion using CallRail's WordPress plugin or Google Tag Manager:
- Using CallRail’s WordPress plugin
- With Google Tag Manager
- Destination Number: The number that rings at your business when one of your tracking numbers is called. This is where your calls are routed. Usually, your business number.
- Source Tracking Number: A single, static tracking number that tracks one campaign source. For example, a billboard or a Google ad extension.
- Keyword Pool: A pool of numbers that dynamically swap based on how a lead routes to your website and is able to capture session-level data like pages visited, PPC keywords, etc. This also allows for more extensive lead reporting like CPL and Calls by Landing Page reports.
Cross-Subdomain Call Tracking
Cross-subdomain tracking allows your website visitor’s referring data to be carried across subdomains. This allows CallRail’s dynamic number insertion script to show the same tracking to a visitor as they navigate across subdomains on a website (i.e. from http://campaign.example.com to http://example.com).
By default, every CallRail account is set up to track across subdomains. If you signed up for CallRail before March 2015, contact our support team to request that cross sub-domain call tracking be turned on for your account.
Swap Precedence Rules
For example, if you have the following setups, you would want to be sure the tracking numbers were not interfering with one another:
- A source tracking phone number for "Google Ads" and another source tracking number for "All Search."
- A source tracking phone number for a landing page parameter, and a keyword-level tracking pool for "All Visitors."
The following sources are listed from highest priority to lowest priority. Earlier rules in this list take precedence over later rules.
- Landing page parameter swaps (Example: utm_campaign=mycampaign) and landing page URL options are equal (example: Visitors who land on www.landingpage.com)
- Specific referring URLs (Example: Google PPC, facebook.com, direct visitors)
- Referrer groups (Example: Google Search, All Search, Organic Search, PPC Search)
- Source tracking numbers set to "Always Swap"
- Keyword-level tracking pools
This means that any source tracking number will always take precedence over a keyword tracking pool. If you create a keyword pool to replace a source tracking number, you should set the swap setting on the original source tracking number to "offline" (or disable the unused phone number completely) to allow the keyword pool to function.