Add utm_source, utm_medium, utm_campaign, and optional utm_term, utm_content, and utm_id (GA4) to https landing URLs with correct encoding. Work happens only in your browser — no campaign data is sent to DroidXP, matching APK Analyzer and APK String Extractor. Tag a single page or batch many URLs with the same parameters.
UTM parameters (leave blank to omit)
Related: Meta Tag Generator, Schema Markup Generator, Open Graph Tag Generator.
UTM query parameters label traffic in analytics: who it came from (source), the broad channel (medium), and your initiative (campaign). Optional term and content help segment ads or creative variants; utm_id can tie to GA4 campaign definitions. Building links locally matches how APK String Extractor keeps extracted strings on your device — nothing is sent to DroidXP to compose the URL.
The page uses the browser’s URL and URLSearchParams APIs so values are encoded safely. Only parameters you fill in are set or replaced; omitted fields do not delete unrelated query keys already on the base URL. For production links, prefer
canonical https destinations.
Paste a primary URL plus additional absolute URLs (one per line) to apply the same UTM set everywhere — useful for multi-locale paths or asset variants. Invalid lines are skipped and reflected in the stats row.
Form state can persist in localStorage for convenience. It is not uploaded when you type — consistent with the client-only model of
APK Analyzer.
No. URLs are combined in your browser only — the same local-only approach as APK Analyzer and APK String Extractor. Optional localStorage saves fields on your device.
Google’s convention is utm_source (who sent the traffic), utm_medium (how: email, cpc, social), and utm_campaign (your campaign name). Omit empty fields; consistency matters more than length.
utm_id is an optional campaign identifier Google documents for GA4 and related reporting. Use short stable IDs if your org maps campaigns that way; otherwise you can leave it blank.
Yes — for any parameter you fill in the form, this tool sets (overwrites) that key on the destination URL’s query string. Blank fields are not added and do not erase existing keys.
Values are copied as you type: Campaign and campaign look like different campaigns in reports. Many teams standardize on lower case for source/medium.
The tool uses the browser’s URL APIs so spaces and symbols are percent-encoded in the final link — avoid manually double-encoding pasted values.
Those IDs are added by ads platforms when users click — they are separate from UTM. You can still use UTMs on landing-page links; do not invent click IDs yourself.
Yes — paste additional absolute URLs (one per line). Each valid line receives the same UTM set; invalid lines are skipped and counted.
Yes — values stay in your tab unless you opt into localStorage; nothing is transmitted to DroidXP to build the links.
Yes — prefer canonical https links that match production. Mixing http/https duplicates sessions in some setups and diverges from how users actually land.