- How should your team agree on UTM naming before sharing campaign links?
- Who should approve parameters and handle exceptions without rewriting history?
Solve the naming disagreement before building links
When an Egyptian marketing team, an agency, and a sales coordinator all distribute campaign links, inconsistent naming can fragment reporting. One person writes LinkedIn, another writes linkedin, and a third uses a nickname for the same campaign. The immediate problem is not the dashboard. It is the absence of an agreed vocabulary.
Google's custom campaign URL guidance explains manual campaign parameters and notes that parameter values are case-sensitive. Establishing lowercase values is therefore a useful internal convention, not a requirement that Google imposes on every campaign.
Give each parameter one job
Create a shared dictionary with approved values and examples. Let utm_source identify the referring platform or publisher, utm_medium describe the marketing mechanism, and utm_campaign identify the initiative. Use utm_content to distinguish creative or placement variants within that initiative.
Avoid letting one field carry several competing meanings. If the campaign value sometimes means a product, sometimes a city, and sometimes a salesperson, comparisons become unreliable. Agree which information belongs in the campaign name and which belongs in a separate campaign register.
For an Egyptian business with Arabic and English assets, keep a stable machine-readable vocabulary across teams. Record human-friendly Arabic and English campaign names alongside it in the register. Choose a convention everyone can reproduce; do not depend on individuals transliterating the same Arabic phrase differently.
A blank campaign-link specification
Maintain an unfilled record for destination URL, source, medium, campaign, content, language, owner and approval status. Populate values from your agreed naming dictionary, not from a fictional promotion. Use placeholders in the working sheet until the actual initiative and asset are approved; do not distribute a link with unfilled fields.
The source identifies the origin you have chosen to record, medium describes the agreed traffic classification and campaign groups the real initiative. Content distinguishes the actual asset where needed. These editorial choices should be documented consistently; they are not automatically platform-mandated labels or a guarantee of channel classification.
Validate the completed destination, encoding and parameter values before sharing it. Check redirects and confirm that the landing page still serves the intended language and offer. Where several assets belong to the same initiative, review campaign consistency without copying a value blindly. Store the approved link in the register and retire obsolete versions through a named owner.
Put approval before distribution
Maintain a link register containing the destination, complete tagged URL, approved values, owner, distribution location, creation date, and status. A lightweight form or controlled spreadsheet can be enough if it prevents unofficial values from entering circulation.
Use a naming QA checklist:
- Confirm the destination is correct for the advertised language and offer.
- Match each value against the dictionary, including letter case.
- Check separators, spelling, duplicate parameters, and URL encoding.
- Open the final distributed link, including any shortened version.
- Verify redirects preserve the intended parameters.
- Test measurement in the applicable consent state and document the outcome.
Keep personal information, customer identifiers, and free-text messages out of campaign URLs. Links may be copied, logged, and shared beyond their original audience.
Handle exceptions without rewriting history
Do not add campaign tags to ordinary internal navigation to describe acquisition. Use an event plan for on-site interactions instead. Also check existing advertising integrations before adding manual tags; they should follow a deliberate measurement design rather than competing conventions.
If an old link uses the wrong case, record the exception and correct future distribution. Reporting normalization may help analysis, but it does not retroactively change the original collected values. Explain any grouping rule to dashboard users.
Make link QA part of your broader conversion tracking checks. Ask Kitely to build a practical dictionary and approval workflow that your internal team, agency, and distribution partners can all follow.
