State/province normalization to a standard two-letter code
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.
Per-hub plans: also Marketing Hub Professional
On per-hub plans, one of its steps belongs to another subscription: add to static list needs Marketing Hub Professional. Both are required to build it as written. On seat pricing the edition covers both.
When to use it, when not to
Use it
- Use it when
State/Regionis, or was, free text, and existing data has many spellings for the same state or province. - Use it before territory-based lead routing that filters on state, since inconsistent spellings silently miss records that should match.
Read more on when to use itShow less
Skip it
- Do not use it on portals operating only outside the United States and Canada, where "state" is not the relevant administrative unit. Adapt the lookup table to the country's actual regions, or skip this workflow entirely.
- Do not use it to normalize country values. See data-quality-004 for
that; run it first, since state normalization here assumes a clean
Country/Regionto pick the right lookup table (US versus Canada).
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