Skip to content

Multi-language campaign tagging and attribution 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: Marketing Hub Professional.

Contact7 stepsUpdated for HubSpot seat pricing
OutcomeCampaign source values captured in different languages, such as a French landing page tagging "reseaux-sociaux" and an English one tagging "social," roll up into one normalized attribution property, so reporting shows one true channel instead of a fragmented list of language variants.
Workflow mapmarketing-ops-039
Original source drill-down changes leads to Matches a known language variant?. Matches a known language variant? leads to Yes: Set normalized_channel to matched value; No: Set normalized_channel = Other. Set normalized_channel = Other leads to Notify marketing ops: unmapped value. Yes No Original source drill-down changes Matches a known language variant? Set normalized_channel to matched value Set normalized_channel = Other Notify marketing ops: unmapped value
Original source drill-down changes leads to Matches a known language variant?. Matches a known language variant? leads to Yes: Set normalized_channel to matched value; No: Set normalized_channel = Other. Set normalized_channel = Other leads to Notify marketing ops: unmapped value. Yes No Original source drill-down changes Matches a known language variant? Set normalized_channel to matched value Set normalized_channel = Other Notify marketing ops: unmapped value

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

When to use it, when not to

Use it

  • Use on portals running campaigns across multiple languages or regional sites where the same channel gets tagged with different local-language values.
  • Use once you've noticed a channel report splitting what should be one row (Social) into several (reseaux-sociaux, soziale-medien, social) because of source language.
Read more on when to use itShow less

Skip it

  • Do not use if all campaigns already tag consistently in one language regardless of the visitor's locale. There is nothing to normalize.
  • Do not treat the normalized value as a replacement for the original. Keep the original language-specific value for local teams who need it; normalize into a separate property for portal-wide reporting.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 2 items

Every property with its label, internal name, type and options, plus the assets the workflow needs.

Enrollment · 4 parts

The trigger, the criteria as ticked in the UI, the re-enrollment rule and the suppression list.

Steps · 7 numbered actions

Each action in order with its parameters, branches and delays.

Known pitfalls · 4

Traps seen in production, each with what breaks and what to do instead.

Test plan and UAT script · 6 cases, 3 variants

How to prove it works in a test portal, one case per branch, and a sign-off sheet.

Files · PDF, Markdown, JSON, CSV

The properties JSON creates the fields in one call. The workflow JSON documents the build.

Install · 1 click, switched off

The installer creates the properties and the workflow, switched off, then opens a task for what it cannot create. Nothing is deleted, enabled or enrolled.

Unlock all 565 specs, 149 EUR

One-time, excl. VAT. 30-day refund. Installs in 3 portals. Founding price until 30 November.

Read the free Marketing ops spec

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.

149 EUR199

Full library, 565 specs
Get the full library