- What should be named?
- What should never be included?
- How do you verify the result?
What should be named?
Define source, medium and campaign conventions before distributing links. Use names that a future colleague can understand. Distinguish stable categories from temporary creative variants.
For illustration, an approved newsletter campaign might use a consistent email medium and a descriptive campaign name. This is a naming example, not evidence of Dappr campaign results.
What should never be included?
Do not put customer names, email addresses or sensitive information in campaign URLs. URLs can appear in browser history, logs and analytics. A tag should identify the campaign, not the individual recipient.
Avoid changing tags casually after a campaign starts. Record corrections so later analysis can reconcile the old and new labels.
How do you verify the result?
Test the full link and confirm that the destination works. Inspect the reporting setup using a controlled test, and distinguish campaign attribution from proof of causation.
Dappr can help define measurement conventions. Bring the channels and reporting questions so tagging supports decisions rather than producing a long list of inconsistent labels.
Begin with the reporting question
Decide what distinction the campaign link needs to preserve. You may want to separate an email campaign from a partner referral or distinguish two approved creative versions. Naming should support that decision rather than add parameters merely because a builder provides fields.
Identify the report and measurement setup that will receive the information. A well-formed URL does not establish that the site collects or presents its context as intended. Keep the tagging plan connected to the actual analytics implementation and its privacy choices.
Define who maintains the convention. Without an owner, different contributors may create several labels for the same source or reuse one campaign name for unrelated work. A small shared register can prevent confusion before the links are distributed.
Give each parameter a stable role
Google’s current campaign-URL guidance describes source as the referring origin, medium as the marketing channel and campaign as the campaign identifier or name. It also provides fields such as content for creative distinctions. Use the relevant parameters consistently rather than changing their meaning from one link to another.
Keep the naming readable to a future colleague. A code understood only by its creator can make a report difficult to maintain. Record any abbreviations and use a consistent approach to capitalization and separators, since parameter values are case-sensitive.
Do not place personal or sensitive information in the labels. A campaign identifier should describe the activity, not a recipient. URLs can be exposed through ordinary browsing, sharing and logging, so avoid treating a query parameter as a private storage field.
Use an original example to check the convention
Imagine a fictional business sharing a preparation guide through its monthly customer newsletter. The team chooses newsletter as the source, email as the medium and project_prep_october as the campaign name. A content label distinguishes the main guide link from a secondary placement if that distinction is useful.
The values are illustrative, not a universal naming standard or a record of a Dappr campaign. Another team may choose different labels, but it should preserve the same meaning across all links belonging to that activity. The convention should be documented before publication.
Review the resulting URL in full. Confirm the destination and each value, then ask whether the report would still make sense to someone who did not attend the planning meeting. If the label needs a lengthy explanation, improve the register or simplify the naming.
Test the complete link and its journey
Open the final link in the appropriate controlled test arrangement and confirm that the intended page loads. Check redirects and any destination behavior that may alter the URL. A parameter set copied correctly into a spreadsheet can still be attached to the wrong page.
Inspect the relevant measurement evidence under the agreed configuration. Confirm that the source, medium and campaign are represented as expected rather than assuming a visible query string proves reporting works. Record limitations caused by privacy choices or other collection conditions.
Test the distributed form of the link where practical. An email tool, advertising platform or shortening service may affect the path. The customer uses that final version, so verification should include the actual route rather than only the original builder output.
Coordinate manual tags with existing integrations
Check whether the platform already supplies campaign context through an approved integration or automated tagging arrangement. Manual values should fit the intended setup. Do not add another layer without understanding which information the reporting system will use.
Use dynamic placeholders only when the distributing platform supports them and resolves them as expected. An unresolved placeholder can become a literal report value. Verify the delivered link with the responsible platform owner instead of assuming similar syntax works everywhere.
Keep campaign acquisition labels separate from ordinary internal navigation measurement. A link between two pages on the same site serves a different purpose from an external campaign entry. Define the appropriate event or measurement need rather than tagging every internal button as a new acquisition campaign.
Correct mistakes without erasing their history
If a distributed link contains a naming error, record the old value, corrected value and effective date. Fix future use where possible, but do not pretend the earlier observations were collected under the new convention. The report may need an explicit grouping or explanatory note.
Check related links for the same source of error. A copied template can spread a misspelled label across several assets. Correct the template and the process that produced the mistake so the team does not repeat the cleanup next month.
Retain the original destination and purpose in the campaign register. This helps distinguish a typo from an intentional campaign change. Both may create a new label, but they should not be interpreted as the same business event.
Interpret campaign context within its limits
UTM information describes campaign context attached to a visit under the available measurement setup. It does not establish that the campaign caused a purchase that otherwise would not have occurred. Keep attribution, customer qualification and incremental impact distinct.
Expect incomplete information where the customer path is not fully observed. A person may return through another route or contact the business outside the website. Mark unknowns honestly instead of inventing tags or forcing every outcome into a preferred campaign category.
Dappr can help connect naming conventions, link verification and reporting decisions. Bring the channels, current integrations and questions the business needs to answer. The result should be an understandable, maintained measurement process with appropriate data boundaries, not a claim of perfect attribution.
Hand off the convention with examples
Keep an approved example for each common channel and explain which fields vary for a new campaign. Give contributors a review route for an unfamiliar situation rather than encouraging them to invent another medium label.
Review the register when the reporting model or distribution tools change. A convention that fit the previous workflow may need an explicit revision, with the reason and effective date preserved for later analysis.
Preserve the reviewer and the final approved link with the campaign record.