Practical Mesh
← Tools

Utility

UTM Naming Convention Builder

Build a reusable team UTM convention with controlled source and medium lists, campaign field order, examples and a local JSON export.

Include campaign exactly once. Optional fields: objective, product, region, date. Every included field needs a value; omitted fields are ignored.

How it works

Choose a team naming policy, then build a reusable specification and complete example URL. Required fields and normalized vocabulary collisions are surfaced before export. Everything runs locally; campaign inputs are not uploaded or stored.

Example

Campaign Spring Sale, objective Awareness and region UK become spring-sale-awareness-uk under the lowercase hyphen policy. Change the field order to match your workflow.

Limitations

This is a team-defined convention, not a universal GA4 requirement. Use ASCII letters and numbers for portable labels. Separators within a field can make reverse parsing ambiguous; compare generated names across campaigns. Date labels are text, not validated calendar dates. Never include personal data.

FAQ

Can I export the rules?

Copy or download the JSON specification, including allowed values and a complete example URL. No account is needed.

What happens to empty fields?

Fields included in your order must be non-empty. Fields omitted from the order do not affect the generated name.

Check actual campaign links with the UTM QA & Normalizer.