CallRail

CallRail

CallRail is a call tracking and conversation intelligence platform. Scripts replace published phone numbers with dynamic tracking numbers unique to each visitor session, attributing inbound calls to specific traffic sources and ad campaigns. Call data flows into CRM platforms for marketing attribution.

Overview

CallRail is a call tracking and conversation intelligence platform used by marketing teams, agencies, and local businesses to measure the offline conversions (inbound phone calls) generated by their online and offline marketing campaigns. The platform's core mechanism is dynamic number insertion (DNI) — replacing the phone numbers displayed on a website with unique tracking numbers that are assigned per visitor session, allowing CallRail to attribute each inbound call to the specific traffic source, ad campaign, keyword, or landing page that brought the caller to the site.

CallRail is widely used in local services (HVAC, legal, healthcare, automotive), digital marketing agencies, and any business where phone calls are a significant conversion event.

What This Script Does

CallRail's script (cdn.callrail.com/companies/.../trackdynamic.min.js) implements dynamic number insertion and call attribution across the website:

Dynamic number insertion (DNI): On each page load, the CallRail script identifies all phone numbers in the page's HTML and replaces them with session-specific tracking numbers pulled from CallRail's number pool. When a visitor arrives from a Google Ads campaign, they see a different phone number than a visitor arriving from organic search or a Facebook ad — enabling CallRail to attribute each call to the correct source.

Visitor session identification: CallRail sets a first-party cookie (calltrk_session) scoped to the current session and a persistent cookie (calltrk_uuid) with a 2-year expiry for visitor identification. The calltrk_uuid links returning visitors to their previous sessions and call history, enabling attribution across multiple visits. URL parameters and referrer data are captured and stored with the visitor record.

UTM and keyword capture: The script reads UTM parameters (utm_source, utm_medium, utm_campaign, utm_term, utm_content) and Google Ads click IDs (gclid) from the URL on arrival. These are associated with the visitor's tracking number assignment so that when they call, the call record is enriched with campaign and keyword data.

Form tracking: CallRail's form tracking feature captures web form submissions alongside call events, enabling a unified view of both phone and web conversions in the CallRail dashboard and connected marketing platforms (Google Ads, HubSpot, Salesforce).

Call recording and transcription: When a tracked number is called, CallRail can record the conversation and generate an AI-powered transcript. Recordings and transcripts are stored in CallRail and can be synced to CRM platforms. This has additional legal implications in two-party consent states (California, Illinois, Florida, etc.) where recording laws require disclosure.

Keyword-level attribution: For Google Ads campaigns with keyword-level tracking enabled, CallRail assigns unique numbers at the keyword level, allowing advertisers to see which specific search terms generate phone calls and optimize bidding accordingly.

Consent & Compliance

CallRail is an analytics and marketing attribution tool with meaningful personal data collection:

  • GDPR / ePrivacy: The persistent calltrk_uuid cookie (2-year expiry) and the behavioral tracking it enables (linking multiple sessions, capturing referral and campaign data) require prior opt-in consent under the ePrivacy Directive. The DNI mechanism itself changes the website's displayed content based on tracking data, which is a consequence of the tracking infrastructure. Under GDPR, the marketing attribution purpose requires consent (Article 6(1)(a)) — legitimate interests is difficult to justify given the persistent cross-session profiling.
  • Call recording: Call recording raises additional consent issues. Under GDPR, recording calls requires informing all parties. In the US, recording laws vary by state — California, Illinois, Maryland, and others require two-party (all-party) consent for call recording.
  • CCPA: The calltrk_uuid persistent identifier and behavioral session data constitute personal information. Sharing call attribution data with advertising platforms (Google Ads auto-tagging, HubSpot) may constitute a "sale" or "sharing" under CCPA.
  • Healthcare considerations: CallRail is used by many healthcare providers. Call recordings may contain protected health information (PHI) — requiring HIPAA Business Associate Agreement (BAA) terms with CallRail.

Should You Block This Without Consent?

Yes. CallRail tracks visitors across sessions with persistent cookies, attributes phone calls to marketing campaigns, and may record call conversations. This is marketing analytics technology that requires explicit consent under GDPR and ePrivacy before activation.

Visit website

Consent Categories

Analytics
Marketing

Also Known As

call trackingdynamic number insertionDNIcall attributionCallRail scriptphone number trackingconversation intelligence

Industries

Programming and Developer SoftwareComputers Electronics and Technology

Tracked Domains (2)

cdn.callrail.comMarketing
mod.callrail.comMarketing

Frequently Asked Questions

Does CallRail require consent before its tracking script loads?

Yes. CallRail sets a persistent visitor cookie with a two-year expiry, tracks behavior across multiple sessions, and attributes phone calls to marketing campaigns. Under GDPR and the ePrivacy Directive, this cross-session profiling for marketing attribution requires explicit prior consent.

How does CallRail's dynamic number insertion work?

CallRail replaces all phone numbers on the page with session-specific tracking numbers drawn from a pool. Visitors from different traffic sources see different numbers, allowing each inbound call to be attributed to the specific campaign, keyword, or channel that drove the visit.

How does ConsentStack handle CallRail on consent-managed sites?

ConsentStack blocks CallRail's script until analytics or marketing consent is granted. Without consent, the original phone numbers display normally without dynamic replacement. Once a visitor consents, CallRail loads, numbers are swapped, and full call attribution resumes as configured.

Related Vendors

Google
Google
Google is the dominant provider of web analytics, advertising, and infrastructure tools. Scripts like Google Analytics, Tag Manager, Ads, and reCAPTCHA collect behavioral data, manage tag firing, serve targeted ads, and detect bots. Sets persistent cookies to track users and correlate activity across sites.
Google Analytics
Google Analytics
Google Analytics is the world's most widely deployed web analytics platform. Scripts track page views, sessions, user demographics, traffic sources, and conversion events. Drops cookies to identify returning visitors and attribute user journeys across sessions.
Firebase
Firebase
Firebase is Google's mobile and web application development platform offering authentication, real-time database, cloud functions, and analytics. Web SDK scripts initialize Firebase services and may track app events via Firebase Analytics, which is powered by Google Analytics 4. Widely used in single-page apps and PWAs for backend infrastructure and usage tracking.
Microsoft
Microsoft
Runs Clarity (session recording and heatmaps), the Microsoft Advertising UET tag (conversion tracking), and Bing's remarketing pixel. Clarity injects a recording script that captures mouse movements, clicks, and rage clicks. The UET tag fires conversion events to tie ad clicks to on-site actions across Microsoft's ad network.
Microsoft Dynamics 365
Microsoft Dynamics 365
Microsoft Dynamics 365 is a suite of CRM and ERP applications that integrates with websites through tracking scripts and embedded forms. Web tracking code captures visitor behavior, page views, and form submissions to build customer profiles and score leads. Sets cookies to identify returning visitors and attribute marketing touchpoints across sessions.
LinkedIn Insight Tag
LinkedIn Insight Tag
LinkedIn Insight Tag is a JavaScript tracking pixel for LinkedIn's advertising and analytics platform. The tag fires on every page view to collect URL, referrer, IP address, and device data for conversion tracking, website demographics reporting, and retargeting audience building. Sets cookies to identify LinkedIn members across advertiser websites.

Manage consent for CallRail

ConsentStack automatically detects and manages CallRail trackers so your site stays compliant with global privacy regulations.