CallRail & HubSpot Integration

Overview

CallRail and HubSpot can be connected to pass full call attribution data — including source, keyword, and landing page — directly into HubSpot contact and deal records. This closes the loop between paid media activity and CRM-tracked leads, making phone calls a first-class attribution event alongside form fills and chat.

The integration is most valuable when CallRail is running ^[1], because DNI-enriched calls carry granular metadata (GCLID, keyword, session) that flows into HubSpot automatically.

How the Integration Works

CallRail offers a native HubSpot integration (no Zapier required). When a call comes in through a tracked CallRail number:

1. CallRail captures call metadata: source, keyword, landing page, caller ID, call recording, duration, and talk-time ratios.
2. The HubSpot integration fires and creates or updates a contact record in HubSpot.
3. Call data is logged as an activity on the contact timeline — including a link to the recording.
4. If DNI is active, the GCLID is included, enabling Google Ads conversion import from HubSpot.

This means a sales rep opening a HubSpot contact can see exactly which ad, keyword, and page drove the inbound call — without leaving the CRM.

Setup Requirements

• CallRail account with at least one active tracking number or DNI pool
• HubSpot account (any tier with API access)
• The HubSpot integration enabled in CallRail under Settings → Integrations → HubSpot
• CallRail JavaScript snippet installed on the website (required for DNI)

Once connected, the integration is largely automatic. CallRail will match callers to existing HubSpot contacts by phone number, or create new ones if no match is found.

When to Use This Integration

Use CallRail + HubSpot together when:

• The client runs paid search (Google Ads) and needs keyword-level call attribution in their CRM
• Sales reps need call recordings attached to contact records for coaching or handoff context
• The client wants to report on lead source across both form and phone channels in one place
• You need to trigger HubSpot workflows based on call events (e.g., enroll a contact in a nurture sequence after a first call)

When HubSpot Alone Is Sufficient

CallRail is not always necessary. If a client's primary need is outbound call recording or basic inbound logging — and they are not running paid search — HubSpot's native calling feature may be a better fit:

• HubSpot calling allows reps to dial directly from a contact record
• Calls are recorded and logged automatically
• No additional tool, cost, or JavaScript installation required

Decision rule: If the client needs inbound attribution tied to ad spend, use CallRail + HubSpot. If the client just needs a call log and outbound recording, use HubSpot native calling.

This distinction came up directly during the ^[2] CallRail planning session, where Mark noted that a client focused purely on outbound recording "would be better off with HubSpot phone numbers" rather than requiring agents to use the CallRail mobile app.

Alternative Integration Paths

If HubSpot is not the client's CRM, CallRail supports several other integration methods:

For clients on less common CRMs, Zapier is the recommended fallback. If Zapier cannot bridge the gap, a custom webhook or AI-assisted integration can be explored.

Practical Notes

• Client communication: When DNI is active, the phone number visible on the website will change per visitor session. Clients often notice this and become alarmed. Explain DNI proactively before go-live so they understand the number rotation is intentional and all calls still route correctly.
• Pool number validation: Ensure all numbers in a DNI pool are tested and routing correctly before launch. A misconfigured pool number that goes nowhere is a silent lead loss. (This issue was encountered on a Bluepoint setup referenced in the source meeting.)
• Call recording consent: CallRail's inbound recording prompt ("this call may be recorded") handles consent for inbound calls. Outbound recording via the CallRail app requires more care — some states require two-party consent, meaning the rep must verbally disclose recording at the start of the call.

Related

• ^[1]
• ^[3]
• ^[2]
• ^[4]