Choose a naming convention before creating links
Google Analytics documents source, medium and campaign as the core campaign parameters, with content available to distinguish creatives. Its guidance also notes that parameter values are case sensitive. A team using CreatorLaunch and creatorlaunch will not get one consistent campaign label.
For this template, use a stable platform value for utm_source, an agreed channel value for utm_medium, and a public-safe campaign code for utm_campaign. Put the creator or placement code in utm_content. This is a suggested convention, not a universal Google-required influencer taxonomy. Check how the chosen medium maps to the property’s channel groups.
Do not put emails, customer identifiers, private contract data or secret tokens in a URL. Parameters can appear in browser history, logs and shared messages. Use an internal lookup to connect a public placement code to the contract record.
Copy these fields into the campaign link worksheet
Keep one row per publishing surface that needs separate measurement. A description link and a pinned comment can receive distinct content values when the team needs that comparison. Avoid creating more labels than someone will use in a decision.
A public code such as creator07 need not reveal the creator’s identity. Keep the lookup durable, especially when a creator changes their handle between briefing and reporting.
| Field | Illustrative value | Rule |
|---|---|---|
| Destination | https://example.com/demo/ | Confirmed permitted landing page |
| utm_source | youtube | One platform spelling |
| utm_medium | creator | Agreed reporting channel |
| utm_campaign | product-demo-oct | Shared campaign name |
| utm_content | creator07-description-v1 | Placement and creative identity |
| Owner | Campaign operations | Person who validates the link |
| QA status | Pending or passed | Evidence before distribution |
Build the URL without losing existing parameters
An illustrative tagged URL is https://example.com/demo/?utm_source=youtube&utm_medium=creator&utm_campaign=product-demo-oct&utm_content=creator07-description-v1. The example.com address is a reserved example, not a live campaign destination.
Use a URL builder that encodes values and preserves any existing query string. Add a question mark only when the destination has no query. Separate additional parameters with ampersands, and place a fragment after the query. A hand-edited link can appear plausible while dropping the route’s existing product selection.
Do not add these campaign parameters to internal navigation just to track movement within the website. Use the analytics team’s event approach for those interactions. The task here is to identify incoming campaign visits without changing the meaning of later reporting.
The attribution plan defines the accepted outcome behind a tagged visit. Carry the same definitions into the campaign reporting framework rather than rebuilding them after launch.
Test the complete visitor path
Use a test campaign code that the analytics owner can exclude from business reporting. Do not submit a live customer registration or deposit merely to prove tracking. A link and a permitted test event usually give enough evidence for this check.
If an app installation or deep link sits in the journey, involve the app measurement owner. A web UTM visit does not automatically survive the transition into an app. Record any unverified segment instead of declaring the entire funnel measured.
| Check | Action | Accept when |
|---|---|---|
| Destination | Open the untagged URL | Intended page and permitted offer appear |
| Redirects | Follow the tagged link | Relevant values survive the path |
| Browser context | Test mobile and in-app browser | Journey remains usable |
| Collection | Inspect a permitted test visit | Expected campaign fields appear |
| Consent | Test configured consent states | Observed behaviour matches the setup |
| Publishing surface | Check the final post link | Exact approved URL is present |
Explain what a tagged visit can and cannot prove
A session associated with a creator link shows a recorded acquisition path under that analytics setup. It does not prove that the creator caused every later conversion or that untagged visitors never saw the content. Screenshots, code usage and self-reported discovery each add evidence with different limitations.
Keep a conversion definition beside the campaign label: account creation, qualified signup or another agreed action. Distinguish a visit from a customer and distinguish a platform click count from a web session count. The systems can differ because of timing, collection rules, redirects and consent.
If no conversion access exists, report link visits and delivery honestly. Do not reverse-engineer revenue from views using an unsourced industry conversion rate.
Reconcile names after the first posts go live
Inspect the first real placement in the reporting interface before handing out another batch of links. Check the actual source, medium, campaign and content values, not only whether the page loaded. A template error multiplied across twenty creators is much harder to clean up.
When a typo appears, preserve the original value and document a mapping for analysis. Changing the link affects future visits; it cannot guarantee that earlier data is rewritten. Keep the reporting note clear enough that another analyst can reproduce the reconciliation.
At close, archive the worksheet, final URLs, live-post references, test results and measurement caveats. Those records let the next campaign reuse a convention that has been tested in the brand’s own setup.
Sources and further reading
Prepared with AI assistance using the linked references. Planning tables and worked scenarios are illustrative, not client results. Check current product, platform and market requirements before using them.
