CallRail Number Swapping via JavaScript

Overview

When implementing CallRail dynamic number swapping on WordPress sites, the CallRail WordPress plugin is unreliable and should be replaced with the direct JavaScript snippet. The plugin can silently fail or conflict with the snippet, preventing number swaps from occurring even when the CallRail account and pool configuration are correct.

The Problem

Dynamic number swapping may appear to be configured correctly in CallRail — pool defined, swap target set, numbers assigned — but the banner or header phone number never changes for new visitors. The CallRail diagnostic test returns: "The wrong code snippet was installed."

Root cause: The WordPress CallRail plugin either fails to inject the tracking script correctly or conflicts with a separately added JS snippet, causing neither to function properly.

The Fix

Replace the WordPress plugin with the direct JavaScript snippet injected via a code snippet manager (e.g., WPCode, Insert Headers and Footers, or similar).

Steps

1. Get the JavaScript snippet from CallRail:
   - In CallRail, go to Integrations (puzzle piece icon in the left nav)
   - Find JavaScript Snippet at the top of the list
   - Click Copy to Clipboard

2. Deactivate the CallRail WordPress plugin:
   - In WordPress admin, go to Plugins
   - Find the CallRail phone tracking plugin (e.g., "AB Call Rail Phone Tracking")
   - Click Deactivate

3. Add the snippet directly to the site header:
   - Open your code snippet manager
   - Create a new snippet named "CallRail"
   - Paste the JavaScript
   - Set location to Header (before </head>)
   - Save and activate

4. Clear site cache — cached pages may still serve the old (non-swapping) number. Clear all caches before testing.

5. Verify with an incognito window — use a browser profile that has never visited the site, as CallRail sets a cookie and will not swap the number for returning visitors.

Confirming It Works

• Run the CallRail diagnostic test (Integrations → JavaScript Snippet → Test)
• The snippet ID in the test output should match the last characters of your account's snippet (e.g., ...7856)
• Open the site in an incognito window — the banner number should display a CallRail pool number (e.g., a local 303 number) rather than the original static number

Why the Plugin Fails

The WordPress plugin is a wrapper around the same JavaScript snippet, but it can:
- Inject the script at the wrong position in the DOM
- Conflict with a separately installed snippet, causing duplicate or malformed script tags
- Fail silently without surfacing errors in the WordPress admin

Injecting the snippet directly via a header code manager bypasses all of these failure modes.

Important Notes

• Incognito testing is required. CallRail drops a cookie on first visit. Any browser that has previously visited the site will not see the swap until the cookie expires.
• Cache clearing is required after the change. If the site uses a caching plugin or CDN, the old page (with the static number) may be served to new visitors until caches are purged.
• Static footer numbers are separate. If some numbers are configured as static CallRail numbers (not pool/swap), they are unaffected by this change and do not require swapping logic.
• All visible numbers should ideally route through CallRail to ensure complete call attribution. Direct-dial numbers that bypass CallRail will not appear in reporting.

Evidence

Confirmed during a ^[1]. The CallRail plugin was deactivated, the JS snippet was added to the site header via a code snippet manager, and an incognito window test confirmed the swap was working. Cache clearing was queued as a follow-up step.

Related

• ^[2]
• ^[3]