📞 CallRail Debug

Live view of what swap.js is rendering + the attribution captured for this session. Hit this page from different ad URLs to confirm each pool routes correctly.

Phone number on this page

847-279-0028

↑ This is what swap.js produced. The HTML source has 847-279-0028 hardcoded.

Swap status did CallRail replace the number?

CallRail script loaded ⏳ Checking…

CallTrk session ID Not yet available

Number swapped from 847-279-0028

Number swapped to Waiting for swap…

Source pool name Unknown — will populate from CallRail context

Attribution this session sees what the contact form will send

utm_source

utm_medium

utm_campaign

utm_content

utm_term

gclid (Google)

fbclid (Facebook)

msclkid (Microsoft)

Landing page

Referrer

First seen

Raw signals what CallRail saw at swap time

URL

document.referrer

User-Agent

Cookies set by CallRail

Test routes click to test a specific pool

Each link reloads this page with synthetic UTM/click-id params. The swap result should reflect the source pool you've configured for that attribution in CallRail's admin.

🟦 Google Ads 🟦 Facebook Ads 🟪 Instagram Ads 🟦 Bing Ads 🟢 Google Organic ⚪ Direct (no params) 🧹 Clear stored attribution

What you should see configuration sanity

Direct visit (no params): Swapped number should be your main pool or fallback static line.
Google Ads test link: Should land on a number from your Google Ads pool. Different from the direct number.
Facebook Ads test link: Should land on a number from your Facebook Ads pool. Different again.
"Swapped from" → "Swapped to": If these are the same, swap.js didn't run or no pool is configured for this source.
Session ID: Should be a 32-character hex string once CallRail finishes loading. If always blank, the script is blocked.

Page is noindex,nofollow so it won't appear in search results. Safe to leave deployed. Inspect window.CallTrk in DevTools for the full session payload.