Quick answer
Use a controlled naming dictionary rather than letting each creator invent tracking tags. Keep platform, channel, campaign and placement in separate fields, give every published link an owner, and test the final destination. UTMs describe campaign traffic in analytics; they do not independently establish affiliate commission ownership or prove that a viewer was eligible for an offer.
Acquisition managers standardizing creator links across platforms and reporting teams.
Decide what each field means
Google’s campaign URL documentation identifies source, medium, campaign and content as distinct reporting inputs, and notes that values are case-sensitive. Build your own dictionary around those roles. Our editorial convention uses platform as source, the approved marketing channel as medium, a stable campaign name, and a non-personal placement code as content.
Choose the convention with the analyst who maintains your channel reports. A technically valid value can still land in an unexpected reporting group. Do not promise that a custom label such as creator_sponsorship automatically belongs to a particular default channel. Check the actual report and document any custom grouping your team chooses to maintain.
References: Google Analytics — Campaign URL builders
Separate permanent IDs from editable names
Creators can change handles and campaign names can change after approval. Keep a stable internal creator code in your registry and map it to the current display name there. A placement code can combine that creator code, format and version without carrying a private person’s name or contact details. This is an editorial data-management choice, not a Google-required syntax.
Freeze the values used in published links. If someone corrects a typo later, record the old value as an alias instead of silently rewriting your historical dictionary. Otherwise the same campaign can appear to improve merely because one reporting filter stopped including its earlier traffic. Keep the change date and affected placements with the correction.
Use a small synthetic naming example
The table is a synthetic naming example for an approved hypothetical campaign, not a recommendation to advertise gambling in a particular market. Campaign and placement labels are illustrative. The important property is that each field answers a different question and the values remain consistent across a team’s link inventory.
Store the full destination and its approved market beside the tags. If the destination already contains a query string, add parameters with a URL-aware builder that preserves existing fields and fragments. Avoid appending a second question mark or replacing an affiliate identifier. Open the generated result and inspect the final destination after redirects before giving it to a creator.
| Field | Synthetic value | Purpose |
|---|---|---|
| utm_source | youtube | Platform |
| utm_medium | creator_sponsorship | Approved internal channel label |
| utm_campaign | pilot_2026_09 | Stable campaign |
| utm_content | cr014_description_v1 | Creator and placement code |
Protect the fields from personal information
Google’s guidance prohibits sending information it can recognize as personally identifiable information to Analytics, including through campaign parameters. Do not put an email address, phone number or customer name into a tracking value. A public URL is also an unsuitable place for a private commercial note or account secret.
Use the registry for internal context and restrict access according to your organization’s rules. If the requested label seems to need individual customer information, stop and ask the analytics owner to design a different measurement path. Naming convenience is not a reason to expose personal data. Review destination query fields as well as the five familiar UTM fields.
References: Google Analytics — Avoid personally identifiable information
Test the published placement, not only the builder
A clean generated URL can still be changed by a link hub, shortener, description editor or redirect. Test the exact link from the creator’s approved draft or a controlled preview. Confirm its destination, retained campaign fields, affiliate identifiers and permitted content. Record the device and test time so the team can reproduce a failure.
Have an analyst confirm that the intended source and campaign appear in the appropriate acquisition report after its normal processing period. Keep this separate from a server-to-server conversion test. Both can pass independently while the commercial attribution remains wrong. Record which system answers traffic questions and which system governs settlement under the signed agreement.
Maintain the registry through the campaign
Give one owner permission to issue new campaign names and allow trained operators to create placements inside that dictionary. Use a status field such as draft, approved, published or retired. Before a weekly reporting review, group unexpected values and assign someone to resolve them against the registry instead of casually merging everything that looks similar.
Retain retired links so old videos and archived descriptions remain explainable. If a destination must change, check the replacement’s eligibility and repeat the redirect test. Download the registry worksheet and use the UTM tool with synthetic or approved destinations. The tool formats a link; your team still owns approval, reporting interpretation and the accuracy of every input.
Build a campaign tracking link
Use your own assumptions. Calculations stay in your browser; nothing is submitted.
Complete the required fields to see your result.
UTMs label traffic; they do not create affiliate click IDs, server postbacks or guaranteed attribution. Keep personal data out of URLs. Existing query parameters and fragments are preserved; all existing UTM parameters are removed and replaced with the fields above. Test the final destination before use.
Working template
| Decision or test | Evidence or value | Responsible owner |
|---|---|---|
| Approved destination URL | — | Campaign owner |
| Platform/source dictionary value | — | Analyst |
| Medium and reporting group checked | — | Analyst |
| Campaign stable name | — | Campaign owner |
| Creator code and placement | — | Creator manager |
Frequently asked questions
Should every creator be a different utm_source?
In this editorial convention, source is the platform and a stable creator code belongs in content. A different existing convention can work if it is documented and consistently reported.
Can UTMs replace affiliate tracking IDs?
No. Keep the affiliate identifier required by your agreed integration. UTMs provide an analytics label and may not control the contractual attribution decision.
Should internal site links have campaign tags?
Avoid reusing this external campaign convention for internal navigation. Ask your analyst to measure internal placements separately so acquisition reporting remains interpretable.
Sources and scope
Sources checked September 22, 2026. Numerical examples are illustrative unless explicitly identified otherwise.
- Google Analytics — Campaign URL builders — Defines campaign parameters, case sensitivity and acquisition reporting. Checked September 22, 2026.
- Google Analytics — Avoid personally identifiable information — Explains restrictions on personal information in Analytics URLs and campaign fields. Checked September 22, 2026.
Related reading
Plan your next campaign with us
Tell us the market, platform and decision you need to resolve.
Discuss your campaign with Octo Media