URL Tracking Cleaner

Turn Campaign Links Back Into Destination Links

Tracking parameters are useful to marketers but noisy in documentation, tickets, chat, and test fixtures. A product link may carry a short, meaningful parameter such as id=123 alongside several attribution identifiers. The URL Tracking Cleaner removes a defined set of common campaign and click-tracking keys while leaving the destination and unrelated parameters intact.

Paste this exact example into Dirty URL (with tracking tokens):

https://example.com/product?id=123&utm_source=twitter&utm_medium=social&utm_campaign=summer_sale&fbclid=IwAR1

The cleaned result retains id=123 and removes utm_source, utm_medium, utm_campaign, and fbclid. This distinction is central to the tool: it does not erase the entire query string. Application state, product identifiers, filters, referral codes, and other unknown keys remain because deleting them could change what the link does.

Exactly Which Parameters Are Removed

The cleaner targets these names:

• utm_source, identifying the traffic source
• utm_medium, identifying a channel such as email or social
• utm_campaign, naming a campaign
• utm_term, often carrying paid-search terms
• utm_content, distinguishing creatives or links
• fbclid, the Meta/Facebook click identifier
• gclid, the Google Ads click identifier
• yclid, the Yandex click identifier

Removal is performed through the browser’s URLSearchParams API. Every occurrence of a listed key is deleted, including duplicates. Other keys are not evaluated or guessed. For example:

https://docs.example.org/guide?lang=en&utm_content=footer&session=demo#install

becomes a URL with lang=en, session=demo, and #install still present. The scheme, hostname, port, path, and fragment are preserved by the parsed URL, although serialization may normalize their textual form.

Cleaning a Link Step by Step

1. Paste one complete absolute URL into the dirty URL area.
2. Read the cleaned output immediately; conversion happens as the input changes.
3. Compare the remaining query parameters with the destination’s documented requirements.
4. Open or test the clean link when preserving application behavior matters.
5. Select Copy to place the displayed result on the clipboard.

There are no rule toggles or custom parameter fields in this implementation. That makes routine cleaning fast and predictable: the same eight names are always removed. It also means you should inspect the output rather than assuming every analytics vendor’s token has disappeared.

A Documentation Workflow

Consider a support engineer copying a link from a campaign email:

https://app.example.com/invoices/INV-104?view=print&utm_source=newsletter&utm_medium=email&utm_campaign=august#totals

The invoice path and view=print affect the destination. The UTM fields describe attribution rather than application state. Run the URL through the cleaner, confirm that /invoices/INV-104, view=print, and #totals remain, then use the copied result in the support article. The published link is shorter, less distracting, and less likely to attribute future readers to an unrelated campaign.

The same approach works for test cases. Clean a captured URL before adding it to a fixture, but review retained values for user IDs, access tokens, or personal data. A tracking cleaner is not a general-purpose secret scrubber.

Functional Parameters Versus Tracking Parameters

A query parameter’s name does not always reveal its effect. utm_source is conventionally attribution metadata, while id, page, filter, and redirect commonly influence application behavior. This cleaner uses an explicit allow-to-delete list precisely to avoid making broad assumptions.

Unknown tracking keys therefore survive. A link may still contain mc_cid, msclkid, _hsenc, a vendor-specific campaignId, or a custom analytics token. Conversely, a system could intentionally use a UTM-named parameter for server behavior. The cleaner will remove it regardless because matching is based on the key, not the destination’s semantics.

For high-impact links, compare the original and cleaned versions in a safe environment. Confirm that both resolve to the same resource and that authentication, locale, cart, feature flag, and redirect behavior remain correct. This is especially important when links are signed: changing any query component can invalidate a signature even when the deleted field appears informational.

What Happens to URL Formatting

The input is trimmed and parsed as an absolute URL. The output comes from URL.toString(), so it is a normalized serialization. Depending on the input, the browser may add a trailing slash to a bare origin, normalize a default port, or represent encoded query data consistently. The tool’s promise is semantic cleaning through the browser URL model, not byte-preserving text deletion.

Parameter values remain subject to normal URL encoding. A value containing a space or Unicode character may be serialized in encoded form. Fragments are preserved because they are separate from searchParams. Path segments are not decoded, rewritten, or cleaned.

Parameter name matching uses the exact keys passed to search.delete(). Do not rely on variants such as uppercase UTM_SOURCE being removed; normalize or review unusual casing manually. Keys that merely contain a listed term, such as original_utm_source, are different names and remain.

Invalid URL Guidance

If the output reads Invalid URL format, the browser could not construct a URL from the trimmed input. Unlike the URL Parser, this cleaner does not automatically add https://. Enter a complete address such as:

https://example.com/page?utm_source=test

rather than example.com/page?.... Also check for a malformed port, broken IPv6 brackets, invalid percent escapes, pasted prose, or line breaks inside the address. Only one URL is accepted at a time; a newline-separated batch is not interpreted as multiple links.

Do not click Copy while an invalid-input message is displayed if you expect a usable URL. The copy action writes whatever currently appears in the output, including that error text. Correct the input and verify the resulting link first.

Privacy and Security Boundaries

The cleaning logic runs in the page through standard browser APIs; the component does not fetch the destination as part of cleaning. That avoids following redirects or contacting the host merely to rewrite the string. Clipboard access occurs only when you press Copy and is subject to browser permission and secure-context rules.

Local processing does not make sensitive URLs harmless. The input can still be visible on screen, in browser state, or to anyone with access to the device. Remove session identifiers, signed tokens, email addresses, and private resource IDs separately before sharing. The retained query parameters deserve at least as much scrutiny as those removed.

The tool also does not classify destination safety. A cleaned phishing URL remains a phishing URL. Check unfamiliar hostnames and redirect targets through appropriate security controls rather than treating shorter output as trusted output.

Good and Bad Fits

Use the cleaner for making campaign links suitable for notes, reducing attribution noise in bug reports, preparing readable examples, and comparing destination behavior without common ad identifiers. It is particularly effective when a URL mixes necessary state with standard UTM or click IDs.

Do not use it as a full privacy audit, URL validator, redirect expander, malware checker, or link shortener. It cannot discover parameters hidden after a redirect because it makes no request. It cannot remove tracking embedded in a pathname, subdomain, fragment, or opaque encoded payload. It does not know whether the server records other identifiers such as cookies or IP addresses.

For repeatable engineering cleanup beyond the eight built-in keys, define a reviewed policy in application code or a proxy. Decide whether matching is case-sensitive, whether unknown parameters should be dropped, and how signed URLs are handled. This small tool is intentionally conservative about everything it does not recognize.

URL Tracking Cleaner FAQ

Will id=123 or page=2 be removed?

No. Only the eight listed tracking names are deleted. Other parameters remain even if they look analytics-related, so inspect the output.

Are all duplicate UTM parameters removed?

Yes. Calling URLSearchParams.delete() for a key removes every value associated with that exact key.

Why did UTM_SOURCE remain?

The built-in key is lowercase utm_source, and parameter names are treated as distinct strings. Unusual capitalization should be removed manually if appropriate.

Does cleaning follow redirects?

No. The tool rewrites the supplied URL without requesting it. Tracking added by a redirect or encoded in the eventual destination cannot be seen.

Can I add msclkid or a custom key to the removal list?

Not in the current interface. It has a fixed list and no custom-rule control. Remove unsupported keys with a URL editor or an application-specific cleanup policy.

Why does a bare domain show an error?

The cleaner requires an absolute URL that the browser can parse directly. Include the scheme, for example https://example.com/.

Does a clean URL guarantee no tracking?

No. Tracking can use retained parameters, redirects, cookies, path segments, account state, or server-side signals. The result only excludes the named query keys.