Language and locale property normalization
One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.
Professional
Seat pricing: Professional edition. To build it, a GTM Seat or an Ops Seat (an Ops Seat cannot create marketing emails or sequences). Per-hub plans: Data Hub Professional.
OutcomeA contact's preferred language always reads as one of a small, standard set of values, instead of a mix of raw locale codes, free-text guesses, and inconsistent casing that no email personalization rule or list segmentation can reliably filter on.
Workflow mapdata-quality-040
When to use it, when not to
Use it
- Use it when a raw locale code, from a browser's language header captured by an integration, a form field, or an import, needs to become a clean, standard picklist value used for segmentation and email personalization.
- Use it when the set of locales you actually operate in is small enough to map explicitly, a handful of languages, not the full space of every possible browser locale variant.
Read more on when to use itShow less
Skip it
- Do not use it to infer language from country alone. A contact's country and preferred language are related but not the same thing, a French-speaking contact in Belgium, an English-speaking expat in Germany. Keep them as separate properties.
- Do not use it if the raw source already writes a clean, standard value directly. Check the actual raw values you receive before building a mapping for variants that do not occur in practice.
Read more on when to skip itShow less
The rest of this spec
Not the workflow you needed?
More in Data quality
50 specs in this section
Read 12 complete specs before you pay.
One per category, same format as the paid ones. Email only, no card.
We email the link, then a short note when specs change. Nothing else.
Here it is. Download the pack now (.zip) The link is in your inbox too.
Read the free Data quality spec