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.
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]

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.
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.





