Bluepoint Gravity Forms → HubSpot Duplicate Submission Issue

Overview

During a pre-call sync, a suspected double-counting issue was identified in Bluepoint's form submission data. The call tracking dashboard showed 99 form entries over 30 days, but the actual volume of unique inquiries is estimated at roughly ~50 — suggesting each submission is being logged twice.

The leading hypothesis is that both Gravity Forms and HubSpot are independently capturing and forwarding form submissions to the reporting layer, resulting in duplicate records for every inquiry.

This is an open investigation with a fix pending confirmation.

Symptoms

The duplication was first noticed visually during a screen-share review of the conversion dashboard — entries appeared to repeat in pairs.

Root Cause Hypothesis

Bluepoint's form stack connects Gravity Forms (WordPress) to HubSpot via an integration. The suspected flow:

1. A visitor submits a form on the Bluepoint website (Gravity Forms).
2. Gravity Forms logs the entry locally and fires a submission event to the reporting/tracking system.
3. HubSpot, also connected to the same form or tracking layer, independently logs the same submission.
4. The dashboard counts both events, inflating totals by ~2×.

This is a common failure mode when two systems with overlapping scope (form capture + CRM) are both treated as sources of truth for the same event.

Impact

• Reporting accuracy: Lead volume metrics are overstated by approximately 2×. Any conversion rate or lead-gen reporting shared with Bluepoint is currently unreliable.
• Lead prioritization: AI-generated intent classifications (appointment, pricing inquiry, sales-ready, etc.) may appear duplicated, creating noise in follow-up queues.
• Client trust: Bluepoint is an attentive, detail-oriented client. If they audit the numbers independently, inflated figures could raise credibility concerns.

Even at half the reported volume (~50 unique inquiries in 30 days), lead generation is healthy and consistent with Bluepoint's own report of being "really busy." The duplication does not indicate a lead gen problem — only a data integrity problem.

Action Items

• [ ] Investigate whether Gravity Forms and HubSpot are both emitting submission events to the tracking dashboard (@Mark Hope)
• [ ] Identify the exact integration path (native GF-HubSpot plugin, Zapier, webhook, etc.) to find where deduplication should be applied
• [ ] Fix by either: (a) disabling one source from reporting to the dashboard, or (b) implementing deduplication logic keyed on email + timestamp
• [ ] Update Karly with findings before or after the Bluepoint call so she can speak to the corrected numbers if asked

Related Context

• This issue surfaced during a sync focused on ^[1] account health ahead of a client call.
• The call tracking analysis (separate from forms) showed a 55% answer rate on qualified calls — see ^[2] for that issue.
• Bluepoint's website backend is in strong technical health (A+ SSL, 100% Ahrefs score) despite client concerns about front-end maintenance — see ^[3].

General Pattern: Gravity Forms + HubSpot Double-Counting

This issue is not unique to Bluepoint. Any WordPress site using Gravity Forms with a HubSpot integration risks duplicate event logging when:

• Both systems are configured to push data to a shared analytics or call-tracking layer
• The integration uses both a native plugin and a HubSpot tracking script on the same page
• Webhooks are set up redundantly at the form level and the CRM level

Best practice: Designate a single system of record for form submission events. If HubSpot is the CRM, route Gravity Forms data to HubSpot only, and pull reporting from HubSpot — do not also count raw Gravity Forms entries as separate conversion events.