How to use UTM Taxonomy Auditor
- Paste one absolute HTTP(S) campaign URL per line. Keep the original list for comparison.
- Enter allowed and required utm_ names, choose name/value case rules and decide whether unknown campaign keys should be removed.
- Review updated findings and proposed URLs. Repeated campaign names keep the complete original URL; percent-escaped or plus-containing values are not lowercased.
- Download the proposed URL list, CSV or full audit after checking every change. No saved campaign or analytics record is modified.
Example: UTM Taxonomy Auditor
Review five sample campaign URLs for case differences, a repeated source, a missing source and an unknown campaign key.
Options
- Repeated keys
- Repeated campaign parameters are reported instead of selecting a silent winner. Inspect the row before replacing the source URL.
- Value policy
- Case changes apply only where the documented raw-value policy permits them. Encoded values need explicit review; non-UTM query pairs remain intact.
- Campaign URLs
- One absolute http or https URL per line, up to 200 lines. Fragments are kept exactly; pairs after a # fragment are reported as ignored because they are not sent to the server.
- Allowed campaign parameters
- Comma-separated names. Any other utm_ parameter is reported as unknown; it is removed only when removal is switched on below.
- Required campaign parameters
- Comma-separated names that must be present on every URL. Leave blank to skip the missing-parameter check.
- Lowercase parameter names
- Turns UTM_Source into utm_source in the reviewed URL.
- Campaign value case
- Applied only to allowed campaign values that have no percent escape or plus sign, so an encoded value is never silently rewritten.
- Remove unknown utm_ parameters
- When off, an unknown utm_ key is reported and kept. Non-campaign parameters are always kept.
Supported inputs and limits
- Up to 200 HTTP(S) URLs of 2,048 characters each, without credentials.
- Allowed/required lists accept up to 40 names within 2,000 characters; campaign recognition uses literal utm_ keys in the stated ASCII subset.
- Percent-encoded key names are not decoded into campaign names.
- Repeated campaign keys withhold normalization for that complete row.
- Other query pairs and the # fragment retain their raw spelling.
More details
No analytics connection, attribution result or performance conclusion.
Where your input is processed
This tool does not upload your inputs. See the limits for anything saved on your device.
Consistent names do not establish campaign performance
The report groups naming defects and shows the reviewed URL changes. It has no analytics account connection or attribution evidence. Keep the original list and inspect repeated or unknown keys before using normalized links in a campaign.
Questions about UTM Taxonomy Auditor
Are non-UTM parameters removed?
They are preserved under the tool’s reviewed normalization policy.
Does a repeated key pick the last value?
The conflict is reported for review rather than silently resolved.
Can it tell which campaign converted best?
No. It inspects names and URL parameters, not analytics results.