Outcome. Campaign 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 map
Enrollment, branches and actions at a glance
marketing-ops-039
flowchart TD
A[Original source drill-down changes] --> B{Matches a known language variant?}
B -->|Yes| C[Set normalized_channel to matched value]
B -->|No| D[Set normalized_channel = Other]
D --> E[Notify marketing ops: unmapped value]
When to use it, when not to
- UseUse on portals running campaigns across multiple languages or regional sites where the same channel gets tagged with different local-language values.
- UseUse 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.
- SkipDo not use if all campaigns already tag consistently in one language regardless of the visitor's locale. There is nothing to normalize.
- SkipDo 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.
The preview ends here. Six sections are in the library.
counted, not blurred
PrerequisitesEvery property with its label, internal name, type and options, plus the assets the workflow needs before you start.2 items
EnrollmentThe trigger, the criteria exactly as they are ticked in the UI, the re-enrollment rule and the suppression list.4 parts
StepsEach action in order with its parameters, its branches and its delays, written as you tick them.7 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.4 pitfalls
Test plan, variants and build specHow to prove it works in a test portal, where to look when it does not, the variants for other objects or tiers, and the YAML build spec.3 variants, 3 sections
FilesThe properties JSON creates the fields in one API call, the workflow JSON documents the build.PDF, Markdown, JSON
Install1 click. The installer creates the properties this spec declares and the workflow itself, switched off, then opens a task for the prerequisites that are assets rather than properties, such as a team, a static list or a marketing email. What it created is listed on the install page.1 click, switched off
Unlock the full library,
149 EUR
or the marketing ops pack, 39 EUR
One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.
