UTM Campaign URL Builder
Compose Google Analytics / GA4 UTM-tagged URLs.
- Web & Network
- Free to use
- Runs in your browser
Your input
Set your options
Run UTM Campaign URL Builder
Private by default. Runs entirely in your browser — files never uploaded.
Three steps
How to use UTM Campaign URL Builder
- Step 01
Pick your input
Paste your text into the box above.
- Step 02
Configure & run
Adjust the options (base url, source, medium, campaign, term, content) and click Run. Everything happens in your browser via WebAssembly.
- Step 03
Download the result
A JSON document is downloadable below.
This tool runs entirely in your browser. Your file is never uploaded to our servers.
About utm campaign url builder
Compose Google Analytics / GA4 UTM-tagged URLs. It sits in the web & network shelf alongside 64 other web & network tools, needs no account, and keeps the same behaviour whether you open it here or call it through the REST API.
It works from what you type in rather than a file and gives back JSON. The work happens in your browser, so nothing is sent to us at all and the tool keeps working offline. The same operation is available programmatically at POST /v1/web/utm-builder.
UTM Campaign URL Builder questions
Does UTM Campaign URL Builder upload my file?
No. UTM Campaign URL Builder runs as WebAssembly inside this browser tab: the file is read from your disk by the page, processed on your own machine, and handed straight back. It is never sent anywhere, so there is nothing for us to store or delete.
Do I need an account to use UTM Campaign URL Builder?
No. UTM Campaign URL Builder works without signing in, and that is not a trial — it is how the free tier works. An account only matters for things that need one to exist at all: larger server jobs against your quota, API keys, saved workflows and billing.
Can I run UTM Campaign URL Builder from my own code?
Yes. Every tool on the site is reachable from the REST API with the same slug — `utm-builder` — and the same options as this page, so anything you can do here you can automate against your own files.
Related tools
- CORS Header BuilderCompose Access-Control-* headers and validate against a request.
- otpauth:// URI & QR BuilderBuild the otpauth:// URI for Google Authenticator / 1Password / Authy.
- Cache-Control Header BuilderCompose Cache-Control with presets for static / API / dynamic content.
- Content Security Policy BuilderBuild a CSP header from drop-down policies for each directive.
- CSS Animation Keyframes BuilderBuild @keyframes from from/to declarations.
- Data URI BuilderEncode/decode data: URIs with proper MIME and base64 handling.