Bluepoint's Gravity Forms were not populating HubSpot contact fields correctly due to several mapping mismatches. This article documents the root causes and the step-by-step fix applied during the 2026-01-09 check-in, which can serve as a repeatable template for fixing other Bluepoint forms and similar integrations.
Related meeting: [1]
Client: [2]
Full Name field — Gravity Forms had one combined Full Name field. HubSpot's contact object requires separate First Name and Last Name properties; there is no native mapping target for a combined name field.Product Interest dropdown in Gravity Forms used different option labels/values than the Product property in HubSpot (e.g., "Cash to Card Kiosk" vs. "Cash ATM"). HubSpot dropdown mapping requires exact string matches.Full Name into First Name + Last NameFirst Name and Last Name respectively. Mark both as required.Full Name field. Do not delete it — it holds historical entry data.Hidden (not just hide the label).Why keep the old field? Deleting it would orphan historical entries. Hiding it preserves the data without showing it to new visitors.
HubSpot's Product property had these exact values:
- Reverse ATM
- Cash ATM
- Battery Kiosk
- Digital Advertising
Product Interest (or equivalent) dropdown field.Key principle: For Gravity Forms → HubSpot dropdown mapping, the Gravity Forms choice value must be an exact string match to the HubSpot property option internal value.
| Gravity Forms Field | HubSpot Property |
|---|---|
| First Name | First Name |
| Last Name | Last Name |
| Phone | Phone Number |
| Organization Name | Company Name |
| Product Interest | Product |
| Message | Message |
Note on Company Name: HubSpot's
Companyis a separate object fromContact. TheCompany Namefield on a contact record is a text property — it does not automatically create or link a Company object. This is a known HubSpot limitation.
After saving form and feed changes, flush the site cache so visitors see the updated form:
Caution — publish date trap: During this session, saving the homepage with a future publish date (Jan 9, ~3:19 PM MT) accidentally scheduled the page offline, causing a 404. Fix: edit the page, set the publish date to a past date (e.g., Jan 8), and republish. Always verify the publish date when touching page settings.
yourname+test@domain.com) and a recognizable org name (e.g., "Test Org").Generic form names like "G Form 3" make reporting difficult. After fixing each form:
This fix was demonstrated on one form (the main contact form). The same process must be applied to all other Bluepoint Gravity Forms. Before starting each form:
Assigned to: Karly Oykhman (see [1] action items)