LOCAL FILES. REAL POSSIBILITIES.

UTM campaign link builder

Create campaign-tagged HTTP(S) links locally, one URL at a time or from CSV records.

YOUR WORKSPACEProcessed on your device

Add campaign parameters locally to one URL or up to 200 CSV records. Destination URLs are never visited by this builder. Source, medium and campaign are required; values preserve your capitalization.

Campaign report title

Input method

Destination URLAbsolute HTTP(S) URL. Existing unrelated parameters and the fragment are retained.

Source

Medium

Campaign

Campaign ID (optional)

Source platform (optional)

Term (optional)

Content (optional)

Existing managed UTM parameters are replaced, including uppercase spellings. Blank optional tags remove stale values. Other query values are preserved; URL encoding may be normalized.

Google Analytics campaign parameter guidance. Keep naming consistent: analytics treats parameter values as case sensitive. This tool creates links; it does not collect clicks or configure destination analytics.

Nothing is saved automatically. JSON backups are readable, unencrypted files. Export before closing.

Import JSON backup

Processed on your device. Your files are never uploaded by Justility.

How privacy works

How it works

Enter an absolute destination URL and source, medium and campaign values, or import a campaign CSV. Build the links, review each encoded URL, then copy the single result or download the CSV. Save JSON to retain editable inputs.

Supported formats

HTTP(S) URLs up to 2,048 characters; seven tag values up to 200 characters each. Batch UTF-8 CSV/TSV up to 200 records, 1 MB and 150,000 characters. Headers url,source,medium,campaign required; id,platform,term,content optional. CSV and JSON exports.

Good to know

No link shortening, destination requests, click tracking or analytics configuration. Managed UTM tags are replaced case-insensitively; blank optional tags remove older values. Unrelated query values and fragments remain, but encoding may normalize.

Worked example

Before

https://example.com/pricing?plan=basic#details; source newsletter, medium email, campaign spring_launch

After

https://example.com/pricing?plan=basic&utm_source=newsletter&utm_medium=email&utm_campaign=spring_launch#details

The plan query value and details fragment survive. Values retain capitalization, so Newsletter and newsletter can become separate analytics values.

Use a naming convention before generating batches

Choose consistent source and medium names, then use content for placements such as header_button. Every CSV row supplies its own tags. Optional source platform maps to utm_source_platform, while campaign ID maps to utm_id. Links are built locally and never opened automatically.

Content calendar builder

Troubleshooting

Why did an old utm_content value disappear?

The builder replaces its seven managed parameters rather than stacking stale tags. A blank optional content field removes the old utm_content; fill it if you want to retain that placement label.

Common questions

Will generating a URL make Google Analytics record campaign visits?

No. The destination must have its own correctly configured analytics, and a visitor must follow the link. The builder only adds parameters.

Can I use this without an internet connection?

Yes, after you prepare this tool from Offline help and the browser retains its assets. Installation is optional. All processing dependencies are bundled locally.