Example: what an ad click actually carried
A heating firm (fictional) gets an enquiry and the form records the landing page address. Pasting it in shows the campaign tags from a newsletter, an ad click identifier from Google and one from Facebook, plus two area values the site's own search used. Values such as Leeds%20North are decoded, and the repeated area key becomes a list.
Pressing Remove tracking parameters gives back the same address with only the area values left, which is what you would want in a link you forward to a colleague.
https://www.kitebrook.example/offers/boiler-service?utm_source=newsletter&utm_medium=email&utm_campaign=autumn&gclid=Cj0KCQ123&fbclid=IwAR0xyz&area=Leeds%20North&area=Harrogate
utm_source newsletter utm_medium email utm_campaign autumn gclid Cj0KCQ123 fbclid IwAR0xyz area Leeds North, Harrogate After Remove tracking parameters: https://www.kitebrook.example/offers/boiler-service?area=Leeds%20North&area=Harrogate
Reading a query string
Paste the link or query
A full address, or only the part starting with ?. Anything after a # is ignored, because fragments are not part of the query.
Read the table
Each key is listed once with its value decoded. When a key appears more than once, its values are joined with commas.
Copy the JSON
The same data appears as JSON underneath, with repeated keys as arrays, ready for a script, a spreadsheet import or a support ticket.
Strip tracking if needed
Remove tracking parameters deletes keys starting utm_ or mc_ and click IDs such as gclid, fbclid and msclkid. A full URL stays a full URL, with its path and any #section kept; a pasted query string stays a query string.
Parameters you will often see
| Key | Added by | Meaning |
|---|---|---|
| utm_source, utm_medium, utm_campaign | Whoever built the link | Where the visit came from, for analytics |
| utm_term, utm_content | Whoever built the link | Keyword or ad variation |
| gclid | Google Ads | Identifies the ad click |
| fbclid | Facebook and Instagram | Identifies the click from Meta's apps |
| mc_cid, mc_eid | Mailchimp | Campaign and subscriber identifiers |
| Anything else | The website | Search terms, filters, page numbers, IDs |
Questions people ask
What is a query string?
It is the part of a web address after the question mark, made of key and value pairs joined by ampersands, such as ?town=Leeds&page=2. Websites read it to know what to search for, which filters to apply or where a visitor came from. It is visible to anyone who has the link.
Why do some values contain %20 or plus signs?
Spaces and special characters are not allowed in addresses as they are, so they are percent-encoded: a space becomes %20 or, in query strings, often a plus sign. The parser decodes both, so Leeds%20North and Leeds+North both read as Leeds North in the table.
Can I remove utm tags without breaking the link?
Usually yes. UTM tags only feed analytics and the page loads the same without them. Click IDs such as gclid and fbclid are similar. Other parameters may be needed by the page itself, which is why the button removes only the recognised tracking keys and leaves the rest.
What happens to a key that appears twice?
Both values are kept. In the table they are joined with a comma, and in the JSON the key holds a list. Websites use repeated keys for multiple choices, such as several areas or product categories in a search filter.
Where your data goes
Parsing happens in your browser. The links you paste, including any tracking identifiers in them, are not sent to Map Extract or anywhere else, and nothing is opened.
Checked against the tool on