How to Audit HubSpot Cross-Domain Tracking Across Multiple Brand Websites

Managing several brand websites in one HubSpot portal can create a visibility problem.

A marketing team may have HubSpot forms, tracking codes, landing pages, and campaigns running across multiple domains, yet still be unsure whether visitor activity is being captured consistently. Page views may appear under one brand but not another. Form submissions may create contacts without the expected browsing history. Traffic moving between websites may be reported as referrals instead of one continuous journey.

Before building lead scoring, attribution reports, nurture workflows, or account-based campaigns, businesses need to confirm that their HubSpot cross-domain tracking foundation is reliable.

A structured HubSpot tracking audit can show whether the issue is technical, configuration-related, consent-related, or simply caused by looking at the wrong report.

Why HubSpot Tracking Across Multiple Domains Becomes Difficult

Multi-brand companies often operate websites across different domains, subdomains, content management systems, and technical teams. One site may be hosted in HubSpot, while another runs on WordPress or a custom platform.

That creates several possible points of failure:

• The HubSpot tracking code may not appear on every page.
• Different websites may use different HubSpot portal IDs.
• Additional brand domains may not be included in tracking settings.
• Cross-domain linking may not be configured correctly.
• Cookie consent rules may differ between sites.
• Embedded and non-HubSpot forms may behave differently.
• Internal traffic or browser extensions may affect testing.
• Reports may be filtered to the wrong domain, source, or date range.

HubSpot automatically includes its tracking code on HubSpot-hosted pages. Externally hosted websites must have the correct code installed, typically across every page that should contribute traffic data. 

The objective of the audit is not only to confirm that “HubSpot is installed.” It is to test whether all the websites behave as one connected tracking environment.

What a HubSpot Tracking Audit Should Validate

A complete audit should examine four connected layers:

Testing only one layer can produce misleading results. A form may successfully create a contact even though traffic attribution is incomplete. Similarly, website visits may appear in analytics while contact activity is being reviewed through the wrong CRM view.

Step 1: Confirm the HubSpot Tracking Code on Every Website

Start by creating an inventory of every domain and subdomain connected to the brand ecosystem.

This may include:

• Main corporate websites
• Separate brand websites
• Regional or franchise websites
• Campaign landing-page domains
• Blog subdomains
• Careers or resource websites
• Externally hosted pages containing HubSpot forms

For each domain, confirm that the same intended HubSpot portal ID is present and that the tracking code loads across all relevant page templates.

On an externally hosted website, HubSpot generally recommends installing the tracking code before the closing </body> tag or through a site-wide template, plugin, or tag-management system. After installation, the external domain should also be added to the relevant HubSpot analytics settings.

Do not test only the homepage. Check several page types, including:

• Service pages
• Blog posts
• Campaign landing pages
• Form pages
• Thank-you pages
• Pages built through different templates

A code installed in the global footer may still be missing from a custom template or third-party landing-page builder.

How to test the HubSpot tracking code

Use a clean browser session and load each test page. Confirm that the HubSpot script appears and that requests are being made to HubSpot tracking domains.

HubSpot’s tracking code makes asynchronous requests to its tracking infrastructure. Browser extensions, privacy settings, consent choices, and content blockers can prevent some requests from loading, so testing should cover more than one browser configuration. 

It is also useful to compare a normal browser session with an incognito window to separate existing cookie history from a new visitor journey.

Step 2: Configure HubSpot for Multiple Domains

Installing the code does not automatically mean HubSpot understands how the websites relate to one another.

Relevant external domains should be added under HubSpot’s additional site domain settings. HubSpot uses these settings to treat traffic between approved domains as movement within the same website ecosystem rather than recording the second site as a new referral source. 

For example, a visitor might:

1. Arrive on the main corporate website.
2. Move to a specialist brand website.
3. Read a service page.
4. Return to the parent company’s site.
5. Submit a consultation form.

Without properly configured cross-domain tracking, that journey may appear fragmented. The second domain can be recorded as a referral, making the original source and path harder to interpret.

Review:

• Additional site domains
• Cross-domain linking settings
• Cookie domain restrictions
• Subdomain limitations
• Secure-cookie settings
• Analytics domain filters

If Google Analytics is also used, its cross-domain settings should follow the same website structure. Otherwise, HubSpot and Google Analytics may count sessions differently because one tool treats movement between domains as a continuation while the other starts a new session. 

Step 3: Test HubSpot Form Tracking Across Every Domain

Forms are one of the clearest ways to validate whether website activity is reaching the CRM correctly.

Create a controlled test plan for every website containing a HubSpot form. Use unique test email addresses so each journey can be reviewed separately.

For each submission, verify:

• The form submits successfully.
• A new contact is created or the correct existing contact is updated.
• The form name is recorded correctly.
• The submission page is accurate.
• The submission time is correct.
• Relevant properties are populated.
• The expected workflow is triggered.
• The correct source or campaign data is retained.
• The contact is associated with the intended brand or business unit.

HubSpot forms embedded on external websites can send submissions directly into the HubSpot account, where the data can support contact management, automation, and reporting.

If the websites use non-HubSpot forms, test those separately. Their capture depends on how non-HubSpot form collection, an API, or another integration has been configured. A successful front-end submission does not always mean the record reached HubSpot with the correct attribution.

Test more than the successful submission

The audit should also review what happens after the form is submitted.

Check whether:

• The thank-you page loads correctly.
• The confirmation email is sent.
• The sales owner is assigned.
• Internal notifications reach the right team.
• Lifecycle-stage changes occur as expected.
• The contact enters the intended list or workflow.

This helps separate a tracking problem from an automation or routing problem.

Step 4: Validate Cross-Domain Visitor Journeys

Testing individual sites is not enough. You also need to test movement between them.

Create several controlled journeys, such as:

• Brand A website → Brand B website → form submission
• Parent website → regional website → form submission
• Paid landing page → main website → consultation form
• Email link → brand website → second domain → form submission

For each journey, review whether HubSpot captures the expected page activity and whether traffic between owned domains avoids appearing as a misleading self-referral.

HubSpot uses its tracking code and cookies to collect page-visit information. Consent status also affects how visitor activity can be tracked, so tests should account for both accepted and rejected cookie choices. 

Do not assume that an anonymous visitor’s entire history will immediately appear exactly as expected on a contact record. Test when the visitor becomes known, what activity is associated, and how the engagement appears in traffic analytics versus the CRM timeline.

Common HubSpot Reporting Mistakes That Look Like Tracking Failures

Sometimes tracking is working, but the team is reviewing the wrong data.

Looking only at contact records

Traffic analytics and contact timelines answer different questions. Website analytics can show overall visits, sessions, sources, and pages, while the contact record focuses on activity associated with an identifiable CRM record.

A lack of visible contact activity does not automatically mean the website received no traffic.

Using the wrong domain or date filter

Reports may exclude one of the brand domains or use a period before tracking was installed. Always verify filters before diagnosing a technical failure.

Expecting identical numbers across analytics platforms

HubSpot and other analytics platforms may process sessions, cookies, consent, and cross-domain traffic differently. Differences should be investigated, but exact numerical equality should not be the only test of success.

Testing with excluded internal traffic

If the company’s office or employee IP addresses are excluded, internal tests may not appear in traffic reporting. HubSpot allows businesses to exclude internal traffic, referrer domains, and bots from analytics. 

Ignoring cookie consent

Visitors who decline analytics cookies may not generate the same trackable journey as visitors who accept them. The audit should document expected behavior for each consent state rather than treating every missing event as a defect.

A Multi-Brand HubSpot Tracking Audit in Practice

Xgrid worked with a multi-brand staffing company that operated several separate websites and maintained approximately 20,000–30,000 contacts in HubSpot.

The marketing team wanted to know whether existing CRM contacts were visiting any of the company’s websites and whether page activity was being captured across the wider brand environment.

Xgrid tested form submissions, page visits, cookie behavior, and movement across the connected websites. The audit confirmed that the tracking foundation was operating, but the team had been reviewing activity from a view that did not provide the visibility it expected.

Xgrid then helped the company locate and interpret the relevant contact activity and created reporting views that made website engagement easier to understand. The result was not a complete replacement of the tracking setup, but greater confidence in the existing infrastructure and a clearer way to use its data.

This distinction matters. A good audit should not assume the implementation is broken. It should identify whether the gap exists in tracking, configuration, reporting, or user understanding.

HubSpot Reports to Build After the Tracking Audit

Once tracking has been validated, create reports that make the data useful.

Depending on the HubSpot subscription and setup, useful reports may include:

• Traffic and sessions by brand domain
• Form views, submissions, and conversion rates by page
• New versus existing contacts submitting each form
• Lead source and medium by brand
• Contacts engaging with high-intent service pages
• Conversion rates across regional or campaign websites
• Cross-domain journeys leading to form submissions
• Forms with traffic but low conversion rates

HubSpot provides form analytics and custom reporting options that can compare submissions by form, page, date range, source, and whether the submitter is a new or existing contact. 

The reports should answer business questions rather than simply confirm that events exist.

When to Contact HubSpot Support

Some tracking problems cannot be resolved through code checks alone.

HubSpot Support may be needed when:

• A legacy domain configuration cannot be changed.
• Several HubSpot accounts are tracking related subdomains.
• Cookie behavior differs unexpectedly between domains.
• A domain appears connected to the wrong account.
• Tracking remains inconsistent after code and settings are validated.
• Account-level domain limitations affect the planned setup.

HubSpot specifically recommends contacting Support for certain multi-account and subdomain cookie configurations. 

Before opening a support case, collect evidence including the affected URLs, portal IDs, screenshots, browser tests, example contact records, and the expected versus actual behavior.

Frequently Asked Questions About HubSpot Cross-Domain Tracking

Can HubSpot track visitors across multiple websites?

Yes. HubSpot can track activity across multiple domains when the same tracking code is installed and the domains are configured correctly.

How do I check whether HubSpot tracking is working?

Test page visits and form submissions using a unique email address, then confirm the activity appears in HubSpot analytics and on the contact record.

Why does traffic between my websites appear as referral traffic?

This usually happens when the domains are not configured for cross-domain tracking, causing HubSpot to treat movement between them as a new referral.

Does HubSpot track anonymous visitors across domains?

HubSpot can record anonymous website activity, but it only connects that activity to a specific contact after the visitor identifies themselves, such as through a form submission.

Why do HubSpot and Google Analytics show different traffic numbers?

The platforms use different methods for cookies, sessions, consent, and traffic attribution, so their totals may not match exactly.

Build a Reliable HubSpot Cross-Domain Tracking Foundation

Tracking several websites through HubSpot requires more than copying the same script onto every domain.

A reliable implementation needs:

• Complete tracking-code coverage
• Correct additional-domain settings
• Consistent cookie and consent behavior
• Tested form submissions
• Validated cross-domain journeys
• Accurate reports and filters
• Clear documentation for marketing and sales teams

Xgrid helps multi-brand organizations audit HubSpot website tracking, validate forms and cross-domain activity, resolve configuration gaps, and build reporting that turns website engagement into usable buyer insight.

Unsure whether HubSpot is tracking activity correctly across all your websites? Talk to Xgrid about a HubSpot tracking audit that identifies what is working, where visibility is breaking down, and what should be fixed before you scale new campaigns or automation.