Why HubSpot Is Not Tracking Form Submissions

1.1 HubSpot Forms Are Embedded in iFrames

When forms are embedded via iframe:

• External scripts cannot access submission events
• Google Tag Manager cannot detect form interactions
• GA4 fails to capture conversion events

This creates a major limitation when trying to track hubspot form submissions in gtm.

Fix:
Use JavaScript listeners to push submission events into the data layer and align them with your HubSpot tools.

1.2 No Event Trigger Connected to Submission

HubSpot captures submissions internally within the CRM Suite, but analytics tools require explicit triggers.

Without this:

• Submissions are visible in HubSpot but not in GA4
• Lead Conversions are underreported
• Campaign attribution breaks

This impacts Demand generation and Inbound demand generation efforts.

Fix:
Trigger a custom event on submission and align it with analytics tracking.

1.3 Workflow and Tracking Are Not Aligned

A hubspot workflow form submission may trigger actions like:

• Sending emails
• Updating lifecycle stages
• Creating support ticket entries

However, if this workflow is not connected to analytics:

• Submissions are not tracked externally
• Client opportunities are not measurable
• Reporting gaps appear

Fix:
Align workflow triggers with analytics events to maintain consistency across systems.

1.4 No Thank You Page or Confirmation State

Many implementations rely on a redirect after submission.

If the form uses inline confirmation:

• Tracking via pageviews fails
• Submissions are missed in analytics

This directly impacts visibility into customer touchpoint interactions.

Fix:
Trigger events on submission or introduce a dedicated confirmation state.

1.5 Google Tag Manager Not Configured for HubSpot

Tracking HubSpot forms requires advanced configuration in GTM.

Without it:

• Events do not fire correctly
• Submissions are not captured
• Reporting becomes inconsistent

This is especially common in environments with multiple HubSpot website agencies or fragmented delivery processes.

Fix:
Use custom triggers and data layer pushes aligned with Solutions Architecture Design.

1.6 GA4 Event Tracking Is Not Configured

Even when GTM captures events, GA4 must be configured to receive them.

If not:

• Submissions do not appear in reports
• Lead Conversions are not tracked
• Attribution across Marketing Campaigns is incomplete

Fix:
Create events in GA4 and mark them as conversions aligned with business goals.

1.7 Script Conflicts Across Platforms

Complex setups often include:

• HubSpot tracking scripts
• Analytics tools
• Third-party integrations
• Custom code

This can create:

• Duplicate tracking
• Missed submissions
• Inconsistent customer data

These issues are common in organisations managing multiple HubSpot integrations and legacy MarTech systems.

Fix:
Audit scripts and streamline tracking across platforms.

1.8 Privacy, Consent, and Data Restrictions

With evolving AI-driven discovery, privacy expectations are higher than ever.

Factors affecting tracking include:

• Consent banners
• Privacy settings
• Data protection requirements

This impacts:

• Customer experience
• Visibility into buyer persona profiles
• Accuracy of marketing benchmarks

Fix:
Ensure consent frameworks align with tracking requirements and compliance standards.

1.9 Custom Forms and API-Based Submissions

In advanced setups involving:

• Data Migration
• Custom forms
• Integrations with external platforms

HubSpot may capture submissions via API, but analytics tools may not.

This creates disconnects in:

• Revenue Operations
• Client success tracking
• Revenue growth strategy

Fix:
Trigger events manually and ensure consistency across all platforms.

1.10 Disconnected CRM and Analytics Ecosystem

In many organisations, HubSpot operates as a standalone customer platform, while analytics exists separately.

This results in:

• Fragmented Customer Journey visibility
• Incomplete Sales enablement insights
• Gaps in engagement hubs and reporting

Without alignment, even a well-implemented smart CRM cannot provide full visibility.