A UTM builder appends campaign parameters (utm_source, utm_medium, utm_campaign, and optional term/content) to a landing URL so analytics tools can attribute traffic. OmniKit builds and decodes links in your browser, with lowercase normalization and bulk CSV export for marketers running multi-channel tests.
Build GA4 campaign URLs without leaving the tab. Required: utm_source, utm_medium, utm_campaign. Optional: term and content. Values lowercase and hyphenate. Existing query keys stay. Decode a tagged link, export bulk CSV, save presets locally. Do not put emails or names in UTMs.
Required fields on the left
Optional. Leave this empty unless you are splitting an existing tagged link back into the fields above.
Appears after you run
https://omnikitapp.net/tools?utm_source=newsletter&utm_medium=email&utm_campaign=spring-launch
Values are lowercased. Existing query keys stay. Do not put emails or names in UTMs — GA4 will store whatever you send.
A UTM builder appends campaign parameters (utm_source, utm_medium, utm_campaign, and optional term/content) to a landing URL so analytics tools can attribute traffic. OmniKit builds and decodes links in your browser, with lowercase normalization and bulk CSV export for marketers running multi-channel tests.
GA4 still reads those five keys. Existing query strings are kept. Values are lowercased and spaces become hyphens so spreadsheet exports stay consistent.
OmniKit’s UTM Builder requires utm_source, utm_medium, and utm_campaign. Optional keys are utm_term and utm_content. Values are lowercased in the browser. Existing query parameters are preserved. Campaign tags are not a place for emails or names.
Enter a landing URL and the required trio. Optional term and content fill paid-search and creative slots. Decode pastes a tagged URL back into fields. Bulk accepts one URL per line and downloads CSV. Presets save in localStorage on this device.
Paste the landing URL and the required trio.
Add optional term/content. Apply a preset or save one to this browser.
Copy the tracked URL, or paste many landings and download CSV.
utm_source, utm_medium, and utm_campaign. utm_term and utm_content are optional. OmniKit will not emit a link until the trio is present.
No. Campaign tags are stored in analytics. Emails, phone numbers, and names are personal data. This page warns when a field looks like an email or phone.
No. It only adds query parameters to an http(s) URL you already control. javascript: and other unsafe schemes are rejected.
A UTM builder appends campaign parameters (utm_source, utm_medium, utm_campaign, and optional term/content) to a landing URL so analytics tools can attribute traffic. OmniKit builds and decodes links in your browser, with lowercase normalization and bulk CSV export for marketers running multi-channel tests.
utm_source, utm_medium, and utm_campaign. Term and content are optional.
No. Google’s builder is the official product. This page is a local OmniKit helper with decode, CSV, and presets. Use either; keep one naming sheet.
You should not. Analytics will store the string. This tool warns on email-like and phone-like values.
Keep measuring in the same cluster — or jump to the next decision.
Use this when you are tagging a newsletter, LinkedIn post, paid click, or GEO experiment. After the click lands, preview the SERP snippet and OG card. Measure whether assistants mention you on GEO Brand Audit — UTMs do not create citations by themselves.
