Validate UTM campaign naming conventions

A consistent UTM campaign name keeps analytics reports searchable, comparable, and easy to govern. This validator checks one campaign name against an explicitly selected convention and explains which rules pass or fail. Choose a supported pattern for lowercase hyphenated names, quarter suffixes, underscore-separated names, uppercase names, or compact alphanumeric identifiers. The result is deterministic, so the same name and pattern always produce the same answer. Use it before publishing a link, inside a campaign review checklist, or as a guard in an automated URL-building workflow.

Choose a convention that matches your reporting system

A naming convention is useful only when every contributor can apply it without guessing. Start by selecting the supported pattern that reflects the rule your team has documented. The lowercase-hyphenated pattern accepts names such as spring-launch and partner-webinar-2026.

It rejects spaces, underscores, uppercase letters, doubled separators, and punctuation. Choose lowercase-hyphenated-by-quarter when every name must end with q1, q2, q3, or q4, as in summer-sale-q3. The uppercase-hyphenated option serves established taxonomies such as EMEA-PRODUCT-Q4, while alphanumeric is intentionally strict and allows no separator at all.

Supplying the pattern is mandatory because a campaign name cannot be judged in isolation: summer-sale and SUMMER-SALE may each be correct under different governance rules. Make the chosen pattern part of the campaign brief, link builder, or form configuration so reviewers evaluate the same written standard rather than relying on personal preference. This also prevents a silent default from approving names under a convention that the team never intended to use.

Read the validation result and correct failures

The response includes the submitted campaign name, the normalized pattern name, an overall valid flag, a list of checks, a list of violations, and a short description of the expected format. A valid result means the complete name matches every requirement of the selected convention. A false result is deliberately more informative than a generic rejection.

For example, Summer-Sale-Q3 checked against lowercase-hyphenated-by-quarter fails the lowercase check and the quarter suffix check because the convention requires a lowercase q. A name with spaces fails the separator check, while a name ending in q5 fails the allowed quarter range. Use the violations array for concise interface messages or automated decisions, and use the checks array when a reviewer needs to see both successful and unsuccessful rules.

The validator trims surrounding whitespace before evaluation, but it does not rewrite the campaign name or guess a replacement. That behavior protects reporting identifiers from unreviewed changes. Correct the source value, run validation again, and publish only after valid becomes true.

Put validation before links enter circulation

The best place to validate a UTM campaign name is immediately before a tracking URL is generated or approved. In a campaign form, run the check when the author leaves the campaign-name field and show the failed rules beside that field. In a release pipeline, treat valid false as a review failure before URLs are copied into advertisements, newsletters, social posts, QR codes, or partner materials.

Store the selected pattern alongside internal campaign standards so future checks reproduce the original decision. The service performs bounded local string checks without network lookups, random choices, or time-dependent rules, making its results stable in tests and production.