Marketing · Tool
URL Parameter Inspector
Parse URLs and decode every query parameter at a glance.
What is URL Parameter Inspector
Long URLs hide a lot. The inspector splits any URL into its parts — protocol, host, path, and every query parameter — and URL-decodes the values so you can read what is actually being sent. Use it to audit campaign tags, debug redirects, or just understand what a tracking link is doing.
The URL Parameter Inspector is a browser-based parser that takes any URL and breaks it down into its component parts: protocol, host, path, base URL, and a fully decoded table of every query parameter. It handles repeated keys, percent-encoded characters, and unusual delimiters without losing data.
It's the tool you reach for when a tracking link looks fine on the surface but the analytics report disagrees with reality. Paste the URL in, and the table tells you exactly what the platform sees — every utm value, every fbclid, every appended ad-network parameter — without the noise of the encoded string.
It's useful for paid media analysts auditing inbound traffic, lifecycle marketers verifying email links, SEO specialists checking canonical and tracking parameter handling, and engineers debugging redirects or third-party integrations.
How to use URL Parameter Inspector
- 1Paste the full URL.
- 2Review the parsed host, path, and query parameters.
- 3Use the decoded values to audit tracking or debug redirects.
- 4Copy the cleaned URL without parameters when needed.
Why URL Parameter Inspector matters
A URL is a contract between your site and the platforms that send traffic to it. When that contract is broken — by stray ampersands, missing parameters, duplicate keys, or values that were encoded once too many times — analytics platforms misclassify the click, attribution windows fail, and downstream automation (like CRM enrichment or audience targeting) silently produces wrong segments.
Inspecting URLs by hand catches the failure mode before it propagates. Good practice is to spot-check every tracked link before launch, especially links generated by third parties or assembled by spreadsheet macros, and to keep a clean diff of what the URL actually sends versus what you intended.
URL Parameter Inspector use cases
Auditing a campaign URL before it goes live
Before publishing a paid placement, paste the final tracking URL into the inspector to confirm utm_source, utm_medium, and utm_campaign are spelled the way you expect. It's cheaper to catch a typo here than to discover the campaign aggregated incorrectly two weeks into a flight.
Debugging email click tracking
ESPs wrap your destination URLs in their own redirect handlers. Paste the wrapped link into the inspector to see exactly what the final destination URL will look like once the wrapper resolves, and confirm your UTMs survive the rewrite.
Investigating unexpected traffic in analytics
If you see a flood of traffic with an odd source or medium, copy the referring URL out of analytics and inspect it. The parameter table often reveals which platform's auto-tagging system (fbclid, gclid, msclkid, ttclid) is generating the entries.
Sharing clean URLs
Strip a URL down to its base form before sharing it in docs or chat. Inspecting the URL gives you the clean version with one click — useful when you want to share the page without leaking session tokens, tracking IDs, or A/B test variants.
Example
Pasting a long affiliate redirect URL surfaces hidden referral codes, click ids, and analytics tags so you can verify what tracking is actually active.
FAQ
- Does this send the URL anywhere?
- No. Parsing happens entirely in your browser — the URL never leaves your machine.
- Can I paste shortened links?
- Short links need to be expanded by their provider first. Paste the resolved URL (after the redirect) for accurate parameter parsing.
- Why are some values still URL-encoded?
- The tool decodes one layer. If a value was double-encoded (common in chained redirects) you may need to decode it again.