UTM URL Parser
UTM URL Parser extracts utm_source, utm_medium, utm_campaign, utm_term, and utm_content with URLSearchParams.get and displays a missing marker for absent or empty values. Names are case-sensitive, only the first occurrence is returned, and percent/form encoding is decoded by the URL parser. It does not validate campaign taxonomy, preserve duplicates, detect other attribution IDs, contact analytics systems, or verify that the URL resolves.
Runs locally — files stay on your deviceWhich fields are extracted?
source, medium, campaign, term, and content from their lowercase utm_ names.
UTM fields are campaign labels, not universal truth
Analytics platforms interpret campaign parameters according to their attribution logic, naming conventions, consent settings, redirects, and session state.
How it works
An absolute URL is parsed and get retrieves one value for each of five exact query keys.
Key concepts
First value only
Repeated utm_campaign entries are not all shown.
Exact lowercase names
UTM_Source is a different key.
When to use it
- Inspect a campaign URL before launch.
- Copy decoded UTM values into a review.
- Spot absent standard fields.
When not to use it
- Do not infer recorded analytics data.
- Do not expect uppercase or custom fields.
- Do not use it as a privacy or consent audit.
Worked examples
Campaign link
- Input
?utm_source=news&utm_medium=email- Expected output
source news; medium email
Other fields show missing markers.
Encoded space
- Input
utm_campaign=summer%20sale- Expected output
summer sale
URLSearchParams decodes it.
Duplicate
- Input
utm_source=a&utm_source=b- Expected output
a
get returns the first.
Common mistakes
Assuming analytics received it
No request or platform lookup occurs. Correction: Verify live collection separately.
Inconsistent casing
Keys are exact. Correction: Standardize lowercase names.
Treating missing term as error
Campaign design determines required fields. Correction: Apply your taxonomy rules.
Best practices
- Define controlled naming conventions.
- Check landing-page redirects retain intended fields.
- Validate consent and analytics behavior separately.
Related operations and differences
Canonical Tag Generator
Choose Canonical Tag Generator when you need to generate a canonical link element from a URL.; use UTM URL Parser specifically for utm parse.
External Link Extractor
Choose External Link Extractor when you need to extract links pointing away from a hostname.; use UTM URL Parser specifically for utm parse.
FAQ Schema Generator
Choose FAQ Schema Generator when you need to generate FAQPage JSON-LD from question-answer blocks.; use UTM URL Parser specifically for utm parse.
Heading Structure Checker
Choose Heading Structure Checker when you need to list H1–H6 elements from pasted HTML.; use UTM URL Parser specifically for utm parse.
Hreflang Tag Generator
Choose Hreflang Tag Generator when you need to generate language alternate tags from URL lines.; use UTM URL Parser specifically for utm parse.
HTML Link Extractor
Choose HTML Link Extractor when you need to extract href values from pasted HTML.; use UTM URL Parser specifically for utm parse.
Limitations and privacy
- Five exact lowercase keys and first value only.
- No custom IDs, duplicates, taxonomy, live analytics, redirect, reachability, consent, privacy, or attribution validation.
The pasted text or URL is processed locally in this browser and is not fetched or submitted by the tool.
Frequently asked questions
Are values URL-decoded?
Yes.
Are uppercase keys found?
No.
Are duplicate values listed?
No.
Does it send an analytics hit?
No.