---
title: BluePoint HubSpot Product Field Sync Failure
type: article
created: '2026-01-21'
updated: '2026-01-21'
source_docs:
- raw/2026-01-21-bluepoint-atm-marketing-call-116086857.md
tags:
- hubspot
- lead-routing
- bluepointatm
- forms
- integration
layer: 2
client_source: null
industry_context: null
transferable: true
---

# BluePoint HubSpot Product Field Sync Failure

## Overview

During a January 2026 review call, BluePoint discovered that the **Product** field submitted via website forms was not syncing to HubSpot. This field is the linchpin of BluePoint's lead routing logic — without it, new leads land in a general contact pool of thousands and are never assigned to the correct salesperson.

The root cause appears to be a mismatch between the field option values defined in HubSpot and the values being submitted by the website forms.

## Impact

Lead routing was broken for all form submissions that included a Product selection:

| Product Value | Routes To |
|---|---|
| Cash ATM | Wade Zirkle |
| Reverse ATM | Mike Stebbins |
| Other Kiosk | (unassigned / general pool) |

Without the field syncing, leads fell into the general HubSpot contact pool and risked being lost among thousands of existing contacts.

## Root Cause

The HubSpot **Product** property had four options defined:

- `Reverse ATM`
- `Cash ATM`
- `Battery Kiosk`
- `Digital Advertising`

The website forms were updated to use slightly different naming conventions, and `Digital Advertising` was never included as a form option. The mismatch between form-submitted values and HubSpot property options caused the field to fail silently — all other fields (name, phone, email, company) synced correctly.

This was confirmed via a test submission on the Reverse ATM landing page on the morning of 2026-01-21.

## Resolution

Two parallel actions were agreed upon:

### 1. Asymmetric: Troubleshoot the sync
Investigate why the mapped field is not writing to HubSpot even when a matching value is submitted. Retest after HubSpot-side changes are made and confirm resolution to Wade and Mike.

### 2. BluePoint: Consolidate HubSpot Product field options
Reduce the four existing options to three, aligned exactly with the website form values:

| New Option | Replaces |
|---|---|
| `Cash ATM` | `Cash ATM` (unchanged) |
| `Reverse ATM` | `Reverse ATM` (unchanged) |
| `Other Kiosk` | `Battery Kiosk` + `Digital Advertising` (merged) |

Any existing leads currently categorized as `Battery Kiosk` will be migrated to `Other Kiosk` during the consolidation. BluePoint confirmed this is acceptable.

## Key Decisions

- **Three-option model adopted.** `Battery Kiosk` and `Digital Advertising` are early-stage products not yet actively sold; merging them into `Other Kiosk` keeps the routing model clean without losing the category.
- **Exact string matching required.** HubSpot dropdown property values must match form-submitted values character-for-character. Any future form or CRM changes must be coordinated to keep these in sync.
- **Migration approved.** Existing leads tagged `Battery Kiosk` will be re-categorized to `Other Kiosk` without manual review.

## Action Items

- [ ] Troubleshoot and fix the HubSpot Product field sync; retest with a live form submission (@Karly Oykhman / Asymmetric)
- [ ] Consolidate HubSpot Product property to three options: `Cash ATM`, `Reverse ATM`, `Other Kiosk` (@BluePoint — Mike Stebbins)
- [ ] Migrate any existing `Battery Kiosk` leads to `Other Kiosk` during consolidation (@BluePoint)
- [ ] Confirm fix to Wade and Mike once retested (@Karly Oykhman / Asymmetric)

## Related

- [[clients/bluepointatm/_index]]
- [[knowledge/hubspot/form-field-mapping]]
- [[meetings/2026-01-21-bluepoint-marketing-call]]