Native Integration Issue: HubSpot Custom Properties appearing as Labels or Empty in Brevo

Hi everyone,

I am currently working on a bidirectional integration between HubSpot and Brevo using Brevo’s native integration service (not a manual CSV import). My goal is to sync custom contact properties, but I am facing an unexpected behavior regarding data mapping.

Problem Description: Although the connection between both platforms is successful, the values for several custom fields (e.g., Property Type, Business Segment) are not displaying correctly in Brevo contacts:

  • In most cases, the fields remain empty.
  • In other instances, the value displayed in Brevo is the internal attribute name (e.g., PROPERTY_TYPE) instead of the actual data value (e.g., “Residential Landlord”).

Technical Details:

  1. Source Data (HubSpot): The fields are Dropdown Select properties. Upon inspecting the DOM, I confirmed these are TypeaheadResultsItem components with specific internal values and labels.
  2. Destination Data (Brevo): I have configured the attributes in Brevo as Text type (to avoid validation restrictions) and also tried Category type, but the result remains the same.
  3. Sync Report: The synchronization report shows a high number of “invalid contacts,” mostly due to missing primary keys (Email). However, even for successfully synced contacts, the custom fields mentioned above do not pull the information.
  4. Frequency: I am currently using “On-demand” (A la carta) synchronization for controlled testing.

Steps Taken So Far:

  • Manually re-mapped the fields in the “Map your data” step within the Brevo integration setup.
  • Verified that there are no conflicting special characters in the internal names of the Brevo attributes.
  • Confirmed that the test contacts have unique emails and populated fields in HubSpot.

Questions:

  • Has anyone encountered issues mapping Dropdown Select properties from HubSpot to Brevo?
  • Is there a known limitation regarding HubSpot’s “Internal Values” vs. “Labels” that prevents the native integration from reading the value correctly?
  • Does the native integration support HubSpot properties that contain dots or special characters in their internal name (e.g., property_type_act.)?

I would appreciate any technical guidance or workarounds you can provide. Thanks in advance!

Hey @NCUERVORIOS - thanks for posting in the Community!
This is an interesting use case I’d like to tag in some Community experts on. @Phil_Vallender, @TomM2, and @jolle - any thoughts here?
Shane, Senior Community Moderator

If this is the native integration offered by Brevo, have you already contacted their support to help troubleshoot this?
If you’re mapping HubSpot dropdowns to Brevo dropdowns, thereis a higher risk of issues due to API changes or simple bugs. I’d suggest mapping the HS dropdown to a Brevo text field to see whether this helps with getting the data syncing.

When syncing an internal attribute name rather than a field value, HubSpot custom dropdown properties expose internal values via the API, and labels are only available by separately retrieving the property definition endpoint. Any third-party integrations that consume property values via API may only see the internal value unless they specifically convert it using the property definition. Again, this may be a bug or an issue caused by API changes.

Finally, if you’re open to using 3rd party integrations platforms, then we at Outfunnel also offer a HubSpot-Brevo integration (that most probably doesn’t have the same issues).

Thanks for the suggestion. I actually reached out to Brevo, but they gave me a response similar to yours. In the end, the only way I could solve this was by manually cleaning all the existing data. For new contacts, I’ve set up an n8n automation that cleans the data automatically as it comes in.

Out of curiosity — when you had to manually clean the data, was that because the dropdown internal values didn’t match exactly what Brevo expected?

And was that happening during import/export prep, or purely inside the API sync layer?