Works with your stack
Cookie consent for CallRail Phone Call Tracking
one number per source
CallRail Phone Call Tracking adds CallRail’s swap.js script to every page. The script replaces your phone number with a tracking number chosen from the visitor’s source, and sets cookies to show the same number on the next visit.
By CallRail · callrail.com · WordPress.org
Is this your product? Tell us if anything here is out of date. Write to us
What matters for consent with CallRail Phone Call Tracking
What CallRail says
CallRail’s help centre describes the cookies of its dynamic number insertion as strictly necessary and says they need no consent under the GDPR. Cookie Rocks still waits for marketing consent. In European guidance, a cookie is strictly necessary only when what the visitor asked for cannot work without it: the site and the phone number work without this one. Its job is to link a call to the advert or source that brought the visitor, for up to 6 months renewed at each visit, sometimes with other tools’ identifiers such as _ga.
One script on every page
The plugin loads swap.js from cdn.callrail.com and writes a small marker, window.crwpVer, in the page. Cookie Rocks recognises CallRail by either of them.
Cookies set by a request
The plugin’s changelog says the cookies are set over HTTP, by a request that swap.js sends to CallRail, rather than written by the script itself.
Six months by default
CallRail keeps its cookies for six months by default. You can choose 30, 60 or 90 days instead, and the time starts again at each return visit.
Shared across subdomains
Tracking across subdomains is on by default. The cookie is then set on your parent domain, so every subdomain reads it.
It can read other cookies
With Custom Cookie Capture, CallRail can read cookies set by other tools, such as Google Analytics’ _ga, and send them with the call. This is why keys such as calltrk-_ga appear in local storage.
Analytics and ad pixels
Other plugins of the same kind.
Questions
What do visitors see before they accept?
The phone number written in your page. swap.js replaces it only once it runs.
My site loads swap.js from its own domain. Is that a problem?
Versions of the plugin before the removal of its first-party mode could serve swap.js from your own site. Update the plugin, which now loads it from CallRail, so the script can be recognised by its address.
How does CallRail suggest waiting for consent?
CallRail’s help centre gives two ways: fire its tag in Google Tag Manager from the banner, with a required consent type, or load swap.js from your theme only after the visitor accepts. It does not set up a banner itself.
What happens after the 30-day trial?
The banner, your visitors’ choices and your proofs of consent keep working. Without a key, most settings lock, updates and support stop. Take a key at any time and everything opens again.
For CallRail users
Track your calls, ask first.
same number, after the choice
Every feature of the complete plugin for 30 days, no card.
- During the trial: everything, including the full settings and the scans
- After 30 days without a key: the banner, your visitors’ choices and your proofs of consent keep working
- What waits for a key: most settings, updates and support

Get your trial key
Your e-mail and your site. Your key arrives as soon as you confirm your e-mail.