The Workflow Library

Library / Marketing ops / marketing-ops-036

Campaign UTM format validation and marketing ops notification

Marketing opsContactData Hub ProfessionalIntermediate~40 min to buildFull spec

Outcome. Malformed UTM parameters on a new contact's tracked fields get flagged to marketing ops within a day, instead of surfacing three months later as a "why does this campaign report look wrong" investigation.

Workflow map Enrollment, branches and actions at a glance marketing-ops-036
flowchart TD
    A[UTM campaign property changes] --> B[Custom code: validate format against convention]
    B --> C{result_code ok?}
    C -->|Yes, is_valid false| D[Notify marketing ops of format issue]
    C -->|Yes, is_valid true| E[No notification]
    C -->|No| F[No notification, error logged]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse once inconsistent UTM tagging (typos, wrong casing, a missing campaign parameter) has caused a reporting problem at least once.
  • UseUse to catch format problems close to the source, while the person who built the campaign link still remembers building it.
  • SkipDo not use expecting this fiche to fix or normalize the value automatically for reporting purposes. It flags for a person to fix at the source (the ad platform or link), since silently rewriting attribution data creates the same trust problem this fiche exists to prevent.
  • SkipDo not use it as a substitute for a written UTM naming convention. Establish the convention first; this fiche only enforces catching drift from it.
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.3 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.4 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, and the custom coded action ships as a ready-to-paste .js file.PDF, Markdown, JSON, code
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.