TapBaton
Start free

Free tool

See what’s inside your link.

Inspect campaign parameters before your next launch. Your link stays in this browser; the destination is never opened.

Read the campaign parameter guide

Check the link that will actually go live.

A campaign URL can contain several layers of information: the destination path, campaign tags, click identifiers and custom partner parameters. Reading each field separately makes it easier to spot a missing value before you publish.

  1. 1

    Paste the complete URL

    Use the final link you plan to put in the ad, email or placement. Include https:// and the entire query string after the question mark.

  2. 2

    Review keys and values

    Check the source and campaign names against your naming convention. A parameter with an empty value is different from a parameter that is not present at all.

  3. 3

    Look for repeated names

    Two values under the same key can mean different things to different destinations. Remove an unintended duplicate before sharing the URL.

A URL inspection is a starting point.

This tool reads the link you paste. It does not follow redirects, open the destination or verify what an ad platform adds when somebody clicks. For a complete campaign check, also inspect the final destination after a real test click and compare the identifiers with your tracking setup.

Read the campaign parameter guide

Common questions

Does the inspector open my URL?

No. The URL is parsed in your browser. The inspector does not send a request to the destination, follow redirects or ask for a TapBaton account.

Why do some characters look different in the result?

Query strings encode certain characters for use in URLs. The inspector displays decoded values, so an encoded space can appear as a space. Within a query string, a plus sign is also interpreted as a space; use %2B for a literal plus sign.

Does a UTM parameter prove that a conversion happened?

No. UTM tags describe the campaign that a link belongs to. A purchase, signup or other conversion needs its own event or postback from the destination.

What should I do with a repeated parameter?

Check the destination's expected format. Some systems accept multiple values, while others use only one. Keep repeats only when they are intentional and supported by the receiving system.