utm_source review
Use this tool to clean formatting, then confirm the cleaned value exists in your approved source list.
facebookCore tool · normalize inputs before build
UTM Naming Generator
Normalize messy UTM inputs into cleaner candidate values before final build.
Use the generator to clean formatting, surface ambiguity, and stop risky inputs before they move into build and release.
<>Normalize raw values before they move downstream
Paste the raw values people are actually using. Clean what is safe to standardize, flag what still needs human review, and stop inputs that should not move into build.
Raw inputsWhat people type under launch pressure
Required. Source should describe where the click came from, not whatever alias someone likes this week.
Required. Medium should match your reporting contract, not ad-hoc team slang.
Required. Campaign names need to stay readable, scoped, and versionable later.
Optional. Use when creative, placement, or CTA detail genuinely improves reporting.
Optional. Reserve for keywords, audience labels, or targeting detail with real analysis value.
Normalized outputsWhat is safe to copy forward
utm_sourcefacebook
safeutm_mediumpaid-social
safeutm_campaignspring-sale-2026
safeutm_contenthero-cta
reviewutm_termbrand-keyword
safeWhat changed automatically
- Lowercase, spacing, repeated separators, and disallowed characters are tracked here after each run.
Needs policy review
- Alias drift, ambiguous mediums, and overstuffed campaign labels should show up here.
Stop and rewrite
- Dangerous inputs like URLs, missing required values, or strings that collapse into junk should be blocked here.
review
utm_medium review
Blended medium labels should still be checked against your conventions before launch.
paid-socialutm_campaign review
The generator can tidy raw text, but campaign structure still needs naming discipline and versioning rules.
spring-sale-2026utm_content review
Optional fields should only survive when they add meaningful analysis value instead of vanity detail.
hero-ctautm_term review
Keep term inputs for keyword or audience detail that your reporting actually reads later.
brand-keyword
Copy normalized values
Copy review handoff
What the generator can clean — what it should reject
Keep normalization honest. Formatting can be cleaned here. Policy choices and weak inputs still need to be reviewed or stopped.
Safe to normalize
- Lowercase, spacing, repeated separators, and obvious character cleanup.
- Readable candidate values that still preserve the original intent.
- Consistent formatting before the row moves into build.
Needs policy review
- Alias drift that may hide the wrong approved value.
- Medium labels that blur paid, owned, and referral traffic.
- Campaign names that are readable but still structurally weak.
Reject until rewritten
- Inputs that lose meaning once cleaned.
- Values that bundle multiple ideas into one field.
- Anything the team would not want preserved in reporting history.
Start with the naming problem
Rules are unclear
Fix the naming pattern before you try to normalize more rows.
Approved values are drifting
Lock the dictionary before the generator keeps producing different candidates.
Rows still need control
Move into the operating sheet when ownership, approvals, or exceptions still matter.
Inputs are clean and ready
Assemble the final candidate URL once the naming layer is stable.
Build is complete
Use the human release gate before anything is approved for launch.
Go deeper in naming control and build
Naming conventions
Use the rule page when the writing pattern itself needs to be set or cleaned up.
Taxonomy design
Use the approved-value page when the real problem is dictionary control, aliases, or rollup drift.
Naming template
Use the operating sheet when rows still need ownership, status, approvals, and exception handling.
UTM Builder
Move into final URL assembly only after the candidate values are clean enough to build.
UTM QA Checklist
Use the human release gate after build to confirm approval, proof, and launch readiness.