Add source, medium, and campaign labels to a web URL. Keep campaign naming consistent before sharing links in emails or ads.
How to use
Enter a full HTTP URL and fill in all three campaign fields. Generate the link and test the destination. Existing query parameters and fragments are retained.
Example
For a newsletter, use source newsletter, medium email, and campaign spring_launch. Reuse the same spelling in every link for that campaign.
FAQ
Does this collect analytics itself?
No. It adds labels. Your analytics setup must read them. Avoid personal data in parameters because URLs can be shared and logged.
Related tools
A practical task
Agree on campaign spelling before creating links. email and Email can become separate labels in reporting. Keep a short naming record for the source, medium, and campaign so a later newsletter uses the same convention.
Another useful question
Should I put UTM labels on internal navigation?
Usually keep campaign labels for the external promotion they describe. Internal campaign parameters can confuse attribution, so coordinate their use with your analytics design.
Settings and formats
| Field | Values |
|---|---|
| Source | Starting value: newsletter |
| Medium | Starting value: email |
| Campaign | Starting value: autumn |
Details for interpreting the result
| Detail | Explanation |
|---|---|
| Campaign labels | Campaign parameters label a visit for an analytics system. Consistent spelling is necessary for meaningful grouping. A new campaign label changes attribution data, not the underlying content or its search ranking. |
| Query values | Query separators connect parameter names and values. An ampersand inside a value must not be confused with the separator between parameters. Build the URL with correct component encoding before sharing it. |
| URL components | A URL contains structure such as scheme, host, path, query, and fragment. Characters that separate those parts differ from characters inside a value. Encode the right component rather than transforming the full address blindly. |
| Percent encoding | A percent escape represents a byte with two hexadecimal digits. It does not describe a visible character directly. Several escapes can belong to one Unicode character encoded with multiple UTF8 bytes. |
| URL fragments | A fragment points to a location within a resource and is normally not sent as part of the server request. It differs from a query parameter. Changing it does not necessarily create a different document for canonical selection. |
| Public URL data | URLs can be copied, logged, shared, and stored in analytics. Do not put passwords, private customer details, or secret access tokens in ordinary campaign fields or shareable links just because the query text is encoded. |