Free UTM checker

Audit UTM links and match decisions to your campaign sheet.

Check links from ads, emails, and partners in one batch. Keep each placement with its original link, proposed change and outstanding decisions in the review CSV.

See a campaign handoff example · Read the 14 protection cases

Originals → findings → review CSV

Review campaign links

Paste links to start. IDs and platform templates are protected.
Import a local CSV, TSV or text file
Preview the placement CSV
Review naming policy and field-specific aliases

Source aliases never rename campaigns or IDs. Existing campaign, content, term and platform values are kept by default. A naming suggestion needs a campaign-owner decision; edit the input and check again after approval.

Rules stay on this device. Review the selected policy before saving.

Match review results to a sorted campaign sheet

Include a unique placement_id and a url for each placement. Add channel and owner if they help a teammate route decisions. The checker carries these columns into the review CSV when present. Placement IDs belong to the sheet. The URL’s utm_id remains a separate campaign parameter.

Three rows from the 24-placement sample under factory rules
Placement IDChannel / ownerDecision in the review CSV
MAIL-04Email / Newsletter QAReview. Confirm the missing medium before use.
MAIL-06Email / Campaign QAReview. Compare Newsletter with the proposed newsletter.
MAIL-08Email / Newsletter QAReview. Shares a URL with MAIL-07 and keeps its own placement ID.

Run the placement sample above or download the sample CSV. Expect 24 records, 19 ready for destination testing and 5 for review. After sorting by channel or owner, use placement_id to match the review back to the source sheet. In your spreadsheet, import numeric placement IDs as text to keep leading zeros.

Reimport a review CSV to inspect proposed URLs while retaining the original links and outstanding decisions. To clear a decision, confirm it with the owner, update the source sheet and check again. Read the placement handoff comparison.

What this UTM checker tests

Structural proposals and campaign-owner decisions

Source and medium aliases are field-specific. Campaign IDs always retain their original values; campaign, content, term and platform names are preserved by default. Naming changes need campaign-owner approval. Recognized key typos and identical duplicate keys can be repaired; conflicting duplicates stay in manual review. Unresolved templates and signature-like destinations remain unchanged. Fragment changes require a route test.

This is a URL and naming audit. It does not request the destination page or claim that the page is online.

Why batch-level checks matter

A single link can be syntactically valid while still damaging reporting. A batch audit reveals variants such as paid_social, paid-social, and Paid Social that would otherwise split one channel into several report rows.

UTM audit workbook: 14 reproducible review decisions

These fictional examples test both repairs and deliberate non-changes. They include field-scoped aliases, protected IDs, unexpanded templates, signatures and invalid input. They are not customer campaigns or measured traffic. Factory policy uses lowercase naming suggestions, hyphens and source/medium allowlists; existing campaign names are retained.

Download the 14-row input CSV · Download the answer key and review decisions

A ready proposal has no unresolved checks under this policy. It still needs a destination and attribution test. Naming changes, app-route changes, templates and signatures require a human decision.

Reproduce the workbook

  1. Use “Run protection workbook” above. Factory rules apply to this run only; your saved policy is not changed.
  2. Expect 14 retained input records: 13 unique URLs and 1 invalid row, with 5 ready and 9 requiring review. No duplicate input is included in this workbook.
  3. Compare originals, proposals, field changes and remaining decisions below or in the downloaded review CSV.
  4. Normal checks use your saved policy. Changing the separator or allowlists can intentionally change the findings. Compare the policy before reporting a discrepancy.
1. Keep the destination query and anchor Passes default policy

Original URL

https://example.com/pricing?plan=pro&utm_source=newsletter&utm_medium=email&utm_campaign=fall-launch#details

Expected proposal

https://example.com/pricing?plan=pro&utm_source=newsletter&utm_medium=email&utm_campaign=fall-launch#details

The plan=pro query belongs to the destination, and #details selects an anchor. Neither is a campaign field. A link can already meet the naming policy; an audit should not rewrite it just to produce a change.

Remaining findings: None under the default policy; destination and attribution are not tested.

Campaign-owner decision: Keep this URL. Verify the pricing page and anchor in the actual destination before release. A passing URL audit does not test either.

2. Review source aliases without migrating campaign history Manual review

Original URL

https://example.com/demo?utm_source=fb&utm_medium=Paid_Social&utm_campaign=Fall%20Launch

Expected proposal

https://example.com/demo?utm_source=facebook&utm_medium=paid-social&utm_campaign=Fall%20Launch

Source and medium aliases produce review proposals. The existing campaign name is retained, even though the local convention suggests a different spelling. Source aliases never apply to campaign names.

Remaining findings: naming-change-review, naming-policy-choice

Campaign-owner decision: Confirm source and medium with the campaign owner. Edit the input after approval and recheck. Keep the established campaign spelling unless a migration was agreed.

3. Repair a recognized parameter-key typo Passes default policy

Original URL

https://example.com/guide?utm_sorce=google&utm_medium=cpc&utm_campaign=fall-launch

Expected proposal

https://example.com/guide?utm_source=google&utm_medium=cpc&utm_campaign=fall-launch

utm_sorce is a recognized typo for utm_source. The proposal corrects the key while retaining google, cpc and the campaign value. The typo finding comes from a small explicit dictionary, not a guess about every unknown parameter.

Remaining findings: None under the default policy; destination and attribution are not tested.

Campaign-owner decision: Compare the corrected source with the original ad placement. Retest attribution in the analytics property; this repair cannot recover visits already recorded with the typo.

4. Remove an identical duplicate without choosing a new channel Passes default policy

Original URL

https://example.com/a?utm_source=newsletter&utm_medium=email&utm_campaign=fall-launch&utm_medium=email

Expected proposal

https://example.com/a?utm_source=newsletter&utm_medium=email&utm_campaign=fall-launch

Both utm_medium values are exactly email, so reducing them to one does not choose between different channel values. Compare this with the conflicting duplicate in case 5.

Remaining findings: None under the default policy; destination and attribution are not tested.

Campaign-owner decision: Review and accept the single email value. Check the source campaign template too, so later links do not reintroduce the duplicate.

5. Leave conflicting duplicate values for the campaign owner Manual review

Original URL

https://example.com/b?utm_source=linkedin&utm_medium=paid-social&utm_campaign=fall-launch&utm_medium=social

Expected proposal

https://example.com/b?utm_source=linkedin&utm_medium=paid-social&utm_campaign=fall-launch&utm_medium=social

paid-social and social describe different placements. Choosing the first or last value would hide the conflict. Both remain in the proposal and the URL is excluded from the passing-proposals list.

Remaining findings: duplicate-key

Campaign-owner decision: Check whether this is a paid ad or an organic post. Remove the unintended medium in the input and rerun. Do not publish the unchanged proposal while it still contains both values.

6. Move campaign fields out of a fragment while retaining app state Manual review

Original URL

https://example.com/app#details?view=grid&utm_source=newsletter&utm_medium=email&utm_campaign=fall-launch

Expected proposal

https://example.com/app?utm_source=newsletter&utm_medium=email&utm_campaign=fall-launch#details?view=grid

This URL has campaign fields inside the # fragment. The proposal moves only recognized campaign fields into the query and keeps details?view=grid as fragment state. The proposal requires a route test and is excluded from automatic copying.

Remaining findings: fragment-review

Campaign-owner decision: Open the proposal in the real app and verify the details route and grid view, then check attribution. A custom router may need a different URL structure even when the proposal passes this audit.

7. Do not invent a missing campaign name Manual review

Original URL

https://example.com/c?utm_source=newsletter&utm_medium=email

Expected proposal

https://example.com/c?utm_source=newsletter&utm_medium=email

Source and medium are present, but the default policy also requires campaign. Nothing in the URL reveals which campaign name was approved, so the tool leaves the URL unchanged and requires review.

Remaining findings: missing-required

Campaign-owner decision: Get the campaign value from the approved campaign sheet, add it to the original URL and rerun. Do not copy a campaign name from a different launch just to clear the finding.

8. Treat an unknown source as a policy decision, not an invalid URL Manual review

Original URL

https://example.com/d?utm_source=partner-acme&utm_medium=referral&utm_campaign=fall-launch

Expected proposal

https://example.com/d?utm_source=partner-acme&utm_medium=referral&utm_campaign=fall-launch

partner-acme is outside the default source allowlist. It may be an intentional partner name. The tool retains it; replacing every partner with partner would remove a distinction the report may need.

Remaining findings: unknown-source

Campaign-owner decision: Confirm the partner vocabulary with the campaign owner. If approved, add partner-acme to your local source allowlist and rerun using your saved rules. This warning alone does not establish a GA4 error.

9. Review an existing campaign before changing its separator Manual review

Original URL

https://example.com/e?utm_source=newsletter&utm_medium=email&utm_campaign=fall_launch

Expected proposal

https://example.com/e?utm_source=newsletter&utm_medium=email&utm_campaign=fall_launch

The hyphen convention suggests fall-launch, but existing campaign names are preserved by default. A naming mismatch is an organizational decision, not proof that the existing URL is broken.

Remaining findings: naming-policy-choice

Campaign-owner decision: Retain the underscore convention or agree a migration date. Adjust the local separator if the established vocabulary is intentional; then recheck without rewriting campaign history.

10. Keep a campaign called fb separate from the source alias Passes default policy

Original URL

https://example.com/f?utm_source=newsletter&utm_medium=email&utm_campaign=fb

Expected proposal

https://example.com/f?utm_source=newsletter&utm_medium=email&utm_campaign=fb

The source alias fb=facebook is scoped to utm_source. It has no authority to rename a campaign, term, content value or ID.

Remaining findings: None under the default policy; destination and attribution are not tested.

Campaign-owner decision: Keep the campaign name. If fb is an approved activity code, no source-alias repair belongs in this field.

11. Preserve a case-sensitive campaign ID Passes default policy

Original URL

https://example.com/g?utm_source=newsletter&utm_medium=email&utm_campaign=launch&utm_id=ACME_Q4_A

Expected proposal

https://example.com/g?utm_source=newsletter&utm_medium=email&utm_campaign=launch&utm_id=ACME_Q4_A

Campaign IDs are identifiers. Lowercasing or changing separators can break matching with campaign-data imports. The ID is kept as supplied, even when other naming suggestions use lowercase and hyphens.

Remaining findings: None under the default policy; destination and attribution are not tested.

Campaign-owner decision: Compare the ID with the campaign-data record. This tool does not access or validate that record.

12. Do not rewrite an unresolved platform template Manual review

Original URL

https://example.com/h?utm_source=newsletter&utm_medium=email&utm_campaign={{Campaign.Name}}

Expected proposal

https://example.com/h?utm_source=newsletter&utm_medium=email&utm_campaign={{Campaign.Name}}

The braces identify an unresolved template, not a final visitor URL. The exact spelling is preserved; the checker does not claim that this placeholder is valid for any particular ad platform.

Remaining findings: dynamic-template

Campaign-owner decision: Use the platform preview or test workflow, then check the expanded visitor URL. Do not publish a rewritten macro from a generic URL tool.

13. Retain an input row that contains no valid URL Manual review

Original URL

not a URL

Expected proposal

This input cannot be interpreted as a web URL. It remains a numbered invalid record in the report and CSV; it does not disappear from the batch.

Remaining findings: invalid-url

Campaign-owner decision: Find the intended URL in the source sheet, correct the row and rerun. Row counts must reconcile before the sheet is handed off.

14. Keep a signed destination unchanged Manual review

Original URL

https://example.com/i?token=a%20b~&signature=ExampleOnly&utm_source=newsletter&utm_medium=email&utm_campaign=launch

Expected proposal

https://example.com/i?token=a%20b~&signature=ExampleOnly&utm_source=newsletter&utm_medium=email&utm_campaign=launch

A signature-like parameter can depend on the exact destination query. The original is retained and requires platform review. This fictional signature is a detection example, not a test of a real signing system.

Remaining findings: signed-url

Campaign-owner decision: Use the destination platform to add tracking or issue a new signed URL. Do not assume that unchanged decoded values preserve a signature.

Check the full 30-row review task

This fictional benchmark adds duplicates, invalid protocols, source conflicts, field-isolation checks and byte-sensitive queries to the workbook. Download the 30-row input and independently specified expected decisions. Factory policy retains all 30 records: 25 unique URLs, 2 duplicates and 3 invalid rows. Expect 9 ready and 21 review records. Expected results describe this policy; they do not establish real-world attribution.

Use the report as a review queue

  1. Collect expanded links from the actual ad, email, or partner sheet. A template containing unresolved platform macros is not the final URL a visitor receives.
  2. Run the audit and compare each original with its proposal. The tool rechecks the proposal and displays anything still unresolved.
  3. Download the review CSV. original_url preserves your input; proposed_url holds the edit; review_status separates passing proposals from manual review. The UTM columns describe the proposal. input_row preserves the starting line of a CSV record, including multiline records. input_status and duplicate_of_row account for invalid and repeated inputs; field_changes lists actual value changes, not merely suggestions. Reimporting a manual-review report retains its unresolved decision; it does not approve the proposed changes.
  4. Approve any naming changes, resolve missing values and conflicting duplicates with the campaign owner, edit the input, then audit again. Copy passing proposals only after confirming the naming policy.
  5. Test the final destinations and analytics behavior before replacing live links. This tool does not edit ads or retroactively repair past analytics data.

What passing this audit does not establish

A structurally consistent URL can still lead to an unavailable page, lose tags during a redirect, or reach a site without analytics. This checker does not load destinations, inspect GA4 data, validate auto-tagging integration, or guarantee a default channel classification. It supports seven common UTM fields; other parameters are preserved, not interpreted. Treat HTTP, unsupported dynamic placeholders, and unknown sources as manual checks.

For new campaigns, start with the bulk UTM builder. To define which values your team should accept, use the naming convention guide. Refer to Google's campaign parameter documentation for field meanings.