The CallRail HubSpot integration can send selected calls, text messages, and form submissions into HubSpot contact activity timelines. It can also create a contact when no match exists if you enable that setting. The result depends on your CallRail tracking setup, the identifiers available for each interaction, and the options selected during connection.
Product documentation checked September 8, 2026. The setup and testing recommendations below are our guidance, not a guarantee of a particular result.
That is useful, but it is not the same as perfect attribution. A phone call may carry a marketing source, landing page, campaign, keyword, recording, or other detail when CallRail captured that information. Missing cookies, small number pools, duplicate call sources, field mismatches, and contact-creation rules can change what appears in HubSpot.
CallRail’s integration documentation lists inbound calls, outbound calls, text messages, and forms as the interaction types you can select.
You choose which interaction types to send. When an interaction is enabled, CallRail can add an activity to a matching HubSpot contact. Depending on your settings, it can also create a contact when it cannot find one.
The connection is configured for each CallRail company. If you manage more than one company in CallRail, confirm the HubSpot account and interaction settings for each one rather than assuming a single authorization covers every company.
The fields available depend on the interaction and the CallRail products in use. CallRail’s call and text documentation and form-submission documentation describe the available activity data:
Do not interpret this as a guarantee that every activity will contain every field. A visitor-level tracking number, source tracking number, text conversation, and external form do not begin with the same data. Your dashboard and reporting definitions should preserve those differences.
Start with the decision you want the data to support. Examples include:
The integration should answer a defined question. If the team begins by syncing every available field, the result is often a crowded timeline with unclear ownership.
Record the exact CallRail company and HubSpot account you intend to connect. A user with access to multiple HubSpot accounts must select the correct one during authorization. A mistaken connection can send customer activity to the wrong portal.
CallRail warns that insufficient numbers in a website pool can cause attribution errors when capturing the HubSpot tracking cookie.
List the website pools, source tracking numbers, destination numbers, and campaigns in scope. Confirm which numbers use dynamic number insertion and which numbers appear directly in an ad, listing, or offline placement.
CallRail documents a choice between creating a contact when no match is found and limiting activity posting to existing contacts.
CallRail also offers placeholder @call.com emails when your configuration needs an email value. Its current setup guidance adds an important exception: a new contact created through a HubSpot cookie may still receive a placeholder email even when that option is disabled. Test that path too. Placeholder emails can satisfy a technical requirement while creating work for deduplication, segmentation, consent, and later identity resolution.
If your business relies on email as the unique contact key, document how phone-only leads should be handled before enabling automatic contact creation.
Call recordings, transcripts, text messages, and form submissions can contain personal or sensitive information. Decide what CallRail should collect, what HubSpot should receive, who can access it, and how long it should remain available.
Before enabling recording, follow CallRail’s notice to check applicable requirements with your legal or compliance owner. Have that owner define collection, access, retention, and consent requirements for your use case. A software setting does not replace that review.
CallRail's current setup flow begins in the Integrations area for a selected company. The administrator chooses HubSpot, selects the interaction types, authorizes the correct HubSpot account, and configures contact creation and phone formatting.
Because interface labels can change, use the current CallRail HubSpot integration instructions while you perform the setup. Record the date, administrator, CallRail company, HubSpot account, enabled interaction types, contact-creation rule, and E.164 formatting choice in your implementation notes.
CallRail’s JavaScript snippet supports website call and form tracking. Confirm that it loads on the intended pages under the consent choices you intend to honor. Do not bypass a visitor’s consent choice to recover tracking data.
CallRail’s call-matching documentation describes checking for a HubSpot cookie first, then a matching phone number when no cookie is found. When no match exists, the configured contact-creation rule determines whether CallRail creates a record.
This creates several identity cases to test:
| Scenario | What to verify |
|---|---|
| Known visitor with a HubSpot cookie | Activity reaches the intended existing contact. |
| Caller whose phone already exists on one contact | Phone matching selects the expected record. |
| Shared business or household phone number | The activity does not attach to the wrong person. |
| New caller without an email address | Contact creation follows the chosen rule, including the cookie-based placeholder exception. |
| Returning caller after an email is learned | The process resolves or merges the earlier phone-only record safely. |
Do not test identity resolution with a real customer first. Use controlled records and numbers, then document what the integration actually does in your portal.
CallRail can send first-touch and last-touch details, campaign information, landing-page data, keywords, and other fields when those values are available. CallRail also documents mapping its first-touch source to a standard HubSpot Original Source value.
That mapping is an interpretation, not a raw event log. Preserve the original CallRail activity and document which HubSpot property a report uses. Before a stakeholder calls a dashboard "revenue attribution," confirm that the report connects contacts, calls, deals, and revenue using the intended model. HubSpot’s attribution definitions distinguish contact creation, deal creation, and revenue attribution; available reports depend on your subscription.
A practical HubSpot operations framework should define:
Export or record the current integration settings, relevant HubSpot properties, active workflows, and one controlled test contact. Note whether the CallRail script and HubSpot tracking code load on the test page.
Begin with one enabled interaction and a known expected result. A focused test makes it easier to identify whether a failure came from tracking, matching, field mapping, or workflow automation.
Complete an interaction as a person who already has a controlled HubSpot record. Confirm that the activity appears on the correct timeline and that no duplicate contact is created.
Complete an interaction with a new test phone number or email. Confirm whether CallRail creates a contact, which identifiers it writes, and whether any placeholder email is introduced.
Compare the CallRail interaction with the HubSpot activity. Check the source, medium, campaign, landing page, keyword, duration, recording, tags, and qualification data expected for that test.
If call activity starts a workflow, test enrollment and suppression rules separately. Make sure a repeat call, internal test, spam call, or duplicate activity does not create an unintended customer communication.
Save the test case, expected result, actual result, date, and owner. A passing test is evidence for that configuration at that time, not a guarantee that every future interaction will carry the same data.
Check whether the call used a visitor tracking number or source tracking number, whether the JavaScript snippet was active, whether the website pool had sufficient numbers, and whether the expected HubSpot properties use compatible field types.
Review the contact-creation setting, phone formatting, placeholder-email behavior, and any other integration that sends the same call to HubSpot. CallRail specifically recommends checking whether the destination number also sends call data to HubSpot.
Check CallRail’s external-form requirements against your form and script location. Its standard tracking excludes iframe forms, with a documented Typeform integration exception. For individual contact fields, its HubSpot form guidance requires corresponding single-line-text custom properties; otherwise data may remain in the submission or form-capture block.
Review the connected-app status in both systems, the authorizing user's permissions, and any recent account or security changes. Reauthorization should follow a documented test instead of an assumption that reconnecting alone solved the issue.
These tools answer different questions.
CallRail focuses on tracking and analyzing calls, texts, forms, and their marketing context. HubSpot calling supports different calling paths. HubSpot-provided numbers can support inbound and outbound calls; registering an existing outbound number does not bring its callbacks into HubSpot. Third-party providers have their own capabilities. Check the applicable subscription, seat, and regional requirements.
Some teams use both. Others need only one. Choose from the workflow and reporting requirement, not from a generic feature list. If the main goal is campaign-level call tracking, CallRail may provide relevant context. If the main goal is rep calling inside HubSpot, begin with the current HubSpot calling options.
It can. CallRail documents a setting that creates a new contact when no match exists and a setting that limits activities to existing contacts. Choose and test the behavior that fits your identity and consent process.
Selected calls, text messages, and forms can become HubSpot contact activities. Available details can include marketing source, campaign, landing page, keyword, call duration, recording, tags, qualification, and interaction-specific data.
CallRail documents matching through an available HubSpot cookie or phone number. Identity can be ambiguous when numbers are shared or differently formatted, so controlled testing is essential.
CallRail documents mapping its first-touch source to a closely matching standard HubSpot Original Source value. Review that mapping before using it in attribution reports.
@call.com email addresses?CallRail offers a placeholder-email option, but new contacts created through a HubSpot cookie may still need a placeholder even with that option off. Review both paths and how those records will be identified, segmented, and resolved.
Not by itself. The integration can add call and marketing context to HubSpot. Revenue reporting still depends on contact identity, deal associations, source definitions, qualification rules, and the reporting model.
The connection is only one part of the work. A reliable implementation defines identity rules, source ownership, consent, workflow behavior, report logic, and a repeatable test before the data reaches a live dashboard.
If you need help planning or repairing the connection, Selworthy can review the integration within your broader HubSpot onboarding and training, paid media, and reporting setup. Talk with Selworthy about the exact process you need to support.