---
title: Bluepoint Form Field Mapping Strategy
type: article
created: '2026-01-09'
updated: '2026-01-09'
source_docs:
- raw/2026-01-09-check-in-wkarly-113221759.md
tags:
- gravity-forms
- hubspot
- form-mapping
- bluepoint
- wordpress
- wp-engine
- crm-automation
layer: 2
client_source: null
industry_context: null
transferable: true
---

# Bluepoint Form Field Mapping Strategy

Documentation of the approach used to fix and standardize Gravity Forms → HubSpot field mapping for Bluepoint, including name field splitting, dropdown alignment, feed configuration, and testing procedures.

## Context

Bluepoint's Gravity Forms were not populating HubSpot contact records correctly. Form submissions were arriving in HubSpot with missing or misaligned fields — particularly the contact name, organization, and product interest — because the form fields and HubSpot properties were not properly mapped. This article captures the fix applied to the primary contact form and the pattern to follow for all remaining forms.

## Root Causes

1. **Single `Full Name` field** — HubSpot expects discrete `First Name` and `Last Name` properties. A combined name field cannot be mapped directly.
2. **Mismatched dropdown values** — The `Product Interest` dropdown in Gravity Forms used different option labels than the `Product` property in HubSpot (e.g., "Cash to Card Kiosk" vs. "Cash ATM"). HubSpot requires an exact string match to populate an enumeration property.
3. **No HubSpot feed configured** — The forms lacked a Gravity Forms HubSpot feed, so no field mapping existed at all.

## Fix Procedure

### 1. Split the Name Field

- Open the form in the WordPress Gravity Forms editor.
- Add two **Single Line Text** fields: `First Name` and `Last Name`.
- **Do not delete** the original `Full Name` field — it may have historical entry data attached. Instead, set its visibility to **Hidden** (under Advanced settings on the field) and drag it to the bottom of the form.
- Save the form.

### 2. Align Dropdown Options with HubSpot

- Identify the exact option values in the target HubSpot property (e.g., `Product`): navigate to HubSpot → Settings → Properties → view all contact properties → search for the field.
- Note the exact internal values: `Reverse ATM`, `Cash ATM`, `Battery Kiosk`, etc.
- In Gravity Forms, edit the `Product Interest` (or equivalent) dropdown field and replace its choices with values that **exactly match** the HubSpot property options — including capitalization and spacing. Trailing spaces will break the match.
- Save the form.

### 3. Create a HubSpot Feed

In the Gravity Forms editor for the target form:

1. Go to **Settings → HubSpot**.
2. Click **Add New** to create a feed.
3. Set **Lead Status** → `New` and **Lifecycle Stage** → `Lead`.
4. Under **Map Contact Fields**, map each form field to its HubSpot property:
   - Email → Email
   - First Name → First Name
   - Last Name → Last Name
   - Phone → Phone Number
   - Organization Name → Company Name
   - Product Interest dropdown → Product
   - Message → Message
5. Save the feed.

> **Note:** `Organization Name` on the form maps to the HubSpot contact property `Company Name` — not to a Company object. Cross-object field creation is not supported through this integration. This is a known limitation.

### 4. Flush Cache and Publish

After saving form changes, the WordPress page cache must be cleared for changes to take effect on the live site:

1. In the WordPress admin bar, go to **WP Engine → Caching → Clear All**.
2. Optionally, open a page in the editor and update its publish date to a past date, then save — this forces a page refresh.

> ⚠️ **Known Gotcha:** If you update the publish date to a *future* time, WordPress will schedule the page to go offline at that time, causing a 404. Always set the date to a past date (e.g., yesterday) when using this technique. If a 404 occurs, go back to the page editor, change the date to yesterday, and republish.

### 5. Test the Submission

1. Open the live form in a private/incognito browser window.
2. Submit a test entry using a tagged email address (e.g., `karly.oykhman+test@...`) and a recognizable organization name (e.g., "Test Org").
3. In Gravity Forms, go to **Forms → Entries** and confirm the submission appears.
4. In HubSpot, go to **Contacts** and find the test record. Verify:
   - First Name and Last Name are populated separately.
   - Company Name is populated.
   - Product field contains the correct mapped value.
5. Delete the test contact record after validation.

## Form Naming Convention

Generic form names like "G Form 1" or "G Form 3" make it impossible to identify forms in HubSpot reporting. Rename all forms to descriptive names:

**In HubSpot:**
- Navigate to **Marketing → Forms**.
- Hover over the form → click **Actions → Rename**.
- Use names like: `Website Contact Form`, `PMAX Landing Page Form`, `Quote Request Form`.

**In Gravity Forms:**
- Update the form name in the form settings to match.

## Applying to All Bluepoint Forms

This fix was validated on the primary contact form. The same procedure applies to all other Bluepoint Gravity Forms. Before working on each form:

- Identify which page the form lives on (WordPress pages vs. HighLevel landing pages — confirm with Melissa or Isak if unclear).
- Check whether a HubSpot feed already exists; if so, edit it rather than creating a duplicate.
- Verify dropdown field values match HubSpot properties for that specific form.

## Related

- [[clients/bluepoint/_index]] — Bluepoint client overview
- [[meetings/2026-01-09-check-in-wkarly]] — Source meeting where this fix was performed
- [[knowledge/crm-automation/hubspot-gravity-forms-integration]] — General integration reference
- [[knowledge/wordpress/wp-engine-cache-management]] — Cache clearing procedures