Insights / Growth, Search & Measurement · · Updated · 14 min read
UTM standards across brands: one naming convention for a group of companies
A practical UTM naming convention for company groups, with GA4 session rules, channel checks, privacy limits and examples of Oryvelon portfolio links.
Campaign reports can fragment when different people label the same source as “Facebook”, “facebook” or “fb”. The same problem occurs when “email” and “Email” coexist, or when “launch” means different initiatives in different companies. A naming convention makes those choices explicit before links are distributed.
The fix is a UTM standard: a short, written naming convention that everyone uses. For a single company it is good hygiene. For a group that runs several independent companies, a parent site and founder authority sites, it is the difference between readable data and noise.
This guide proposes a convention for a company group. It distinguishes examples observed on the Oryvelon homepage on September 30, 2026 from hypothetical campaigns and recommended processes. It does not establish that every company has implemented the same register, analytics configuration or privacy controls.
What UTM parameters do — and don't do
UTM parameters are key–value pairs appended to a URL. A configured destination analytics tool can collect them and use them in campaign reporting. The reported result depends on collection, processing and the dimension being viewed; a tag does not guarantee that a visit was measured.
Five commonly used fields are shown below. Google also documents additional fields, including utm_id and utm_source_platform, in its campaign URL guide.
| Parameter | Answers | Example |
|---|---|---|
utm_source |
Where did the link live? | oryvelon, newsletter, instagram |
utm_medium |
What kind of channel is it? | portfolio, email, social, cpc, referral |
utm_campaign |
Which initiative is it part of? | merchnivo, founder, spring_launch |
utm_content |
Which specific link or creative? | hero_button, footer_link |
utm_term |
Which paid keyword? | a keyword label for manual tagging; check the advertising integration |
Two points are often misunderstood.
First, campaign labels are not a privacy control. They should describe an initiative or placement, not identify a recipient. Free-text values can contain personal information if someone inserts it, and the receiving tool may collect other identifiers independently. Consistent naming does not establish anonymous measurement.
Second, a destination must actually collect the parameters before they can appear in its reports. An outbound click recorded on oryvelon.com cannot establish what a company recorded after arrival. See outbound clicks, destination sessions and leads for that distinction, and Analytics without surveillance for measurement limits.
Core rules for a proposed convention
A proposed convention can be short enough to use while still making exceptions explicit:
- Lowercase values. GA4 treats campaign parameter values as case-sensitive. Choose a consistent form to avoid splitting the same source between labels such as
Emailandemail. - One word separator. This example uses underscores:
spring_launch. Hyphens are also a valid naming choice; consistency is the reason to choose one. Spaces require URL encoding, which a URL builder should handle. - A documented spelling for each brand. For example, use
kesifatlasiconsistently for KeşifAtlası. An ASCII vocabulary can simplify manual entry; it is a naming choice, not a claim that other characters cannot be encoded. - Source is where, medium is what kind. Never put a channel type in source or a platform name in medium.
- A fixed list of mediums. New mediums are added to the list deliberately, not invented on the fly.
- Campaign names come from a register. Anyone creating a new campaign adds it to the shared register first.
- No personal data, ever. No emails, names, phone numbers, customer IDs or order numbers in any UTM value.
- Avoid UTMs on internal navigation. Measure placements within a continuous journey with events. A different domain alone is not a reason to treat a link as a new acquisition campaign; first establish the intended measurement boundary.
The medium list
The table is an illustrative vocabulary, not a list of GA4 default channel definitions or a verified policy across all Oryvelon companies. Validate source and medium together in the receiving property:
| Medium | Used for |
|---|---|
portfolio |
Links from oryvelon.com to a company's own website |
referral |
Contextual links from founder sites, partners or other non-portfolio properties |
email |
Newsletters, lifecycle emails, transactional emails with links |
social |
Organic posts and profile links on social platforms |
paid_social |
Paid ads on social platforms |
cpc |
Paid search |
affiliate |
Partner programmes with commission |
print |
QR codes on packaging, cards, event materials |
app |
Links from inside a product to its own marketing site |
If a new kind of channel appears, the question is always "does this fit an existing medium?" before "should we add one?"
In GA4, default channels follow Google’s channel rules, which can depend on the source, medium and advertising integration. A custom medium such as portfolio or print may appear as Unassigned when no rule matches. Inspect source/medium directly, and consider a documented custom channel group if needed. Do not assume that choosing a familiar medium guarantees the intended default channel.
How links between the group and the companies are tagged
For a company group, distinguish the link actually published from the reporting behaviour expected at its destination. Shared ownership does not establish a shared measurement setup.
From oryvelon.com to a company
The portfolio links inspected on the Oryvelon homepage on September 30, 2026 use this pattern. The MerchNivo link is:
https://merchnivo.com/?utm_source=oryvelon&utm_medium=portfolio&utm_campaign=merchnivo
utm_source=oryvelon— the link lives on the group site.utm_medium=portfolio— the channel is the group's portfolio of companies.utm_campaign=<company key>— a fixed campaign key per company.
The checked homepage links use campaign keys including merchnivo, castlyra, edurelia, zodivela, kesifatlasi, noveniq and sinemkeser_beauty_academy. The WeAreMedia link uses services. This is an observation of those public links, not evidence of receiving-site traffic or product availability.
Check each published link and its final destination after redirects. A naming pattern on one page does not establish that every link throughout the group follows it.
If the destination collects the labels correctly, its reports can help distinguish group-site referrals. The tag itself does not prove that the destination loaded, that analytics ran, or that user data is isolated between companies. Verify those questions separately.
From founder sites
A hypothetical founder-site link could use the founder site as source and referral as medium. The following example illustrates a naming choice; it is not a claim about a link currently published on that founder site:
https://oryvelon.com/?utm_source=ugurkeser_art&utm_medium=referral&utm_campaign=founder
For the reverse direction, a possible convention is utm_source=oryvelon, utm_medium=referral and utm_campaign=founder. A contextual article link could instead use a campaign label describing that initiative. Confirm the actual published URL before reporting it as an implemented pattern.
How those founder sites relate to the group, and why their links stay contextual, is in Founder authority sites.
Between companies
A contextual link between companies should help the reader. For example, a hypothetical commerce article might link to a relevant retail example. Shared ownership alone is not a reason to add promotional links or claim an operating relationship that has not been verified.
For separately measured destinations, one possible convention is the linking company as source, referral as medium and the initiative as campaign. Exclude recipient identifiers from campaign URLs. Naming rules alone cannot establish whether companies share user data; that requires a separate review of systems and access.
Campaign names that stay readable
utm_campaign is where most conventions break down, because campaigns are created constantly by different people.
A proposed campaign-name format uses only the parts needed to distinguish the initiative:
<initiative>_<yyyy>_<mm>
Hypothetical names include spring_launch_2026_03 and onboarding_series_2026_09; they do not announce actual campaigns. If dates are used, document whether they mean the initiative’s start month. Evergreen links can use a stable name with no date.
A few habits make a large difference:
- Name the initiative, not the channel. The channel is already in medium.
spring_launchis good;spring_launch_instagramduplicates information and breaks cross-channel reporting. - Add company context when needed. In a property or report limited to one company, repeating its name may be unnecessary. In shared exports, retain a company field or explicit prefix so identical campaign labels are not merged accidentally.
- Use
utm_contentfor variants. Two buttons in the same email areutm_content=hero_buttonandutm_content=footer_link, not two campaigns. - Keep names short. They appear in reports, dashboards and exports. Long names get truncated.
The campaign register
Keep a shared register with one row per campaign. The illustrative row below is a template, not evidence of a current EduRelia campaign or an existing internal register:
| Column | Example |
|---|---|
| Campaign name | onboarding_series_2026_09 |
| Company | EduRelia |
| Owner | the person responsible |
| Mediums used | email, app |
| Start / end | dates |
| Purpose | one sentence |
| Destination URLs | the landing pages |
Before distributing a new campaign, assign an owner and add its agreed label to the register. This reduces the risk of people independently inventing launch, launch_v2 and newlaunch for the same initiative.
The register also answers questions months later. "What was promo_q3 for?" becomes a lookup, not an archaeology project.
A small link builder can offer allowed mediums, validate naming rules and warn about unregistered campaign names. Preserve the destination URL and encode parameter values correctly; do not blindly lowercase the entire URL, because its path may be case-sensitive. This is a recommended helper, not a claim that Oryvelon has deployed one.
What never goes in a UTM
Personal information in a campaign URL can reach analytics or other systems that handle that URL. Google’s PII guidance explicitly covers URL paths, parameters, titles and campaign dimensions. Keep personal information out of these fields; cleaning one field does not clean the rest.
Exclude email addresses, names, phone numbers and recipient-specific identifiers from UTM values. Also review customer, order, student or school identifiers for whether they identify or can be connected to a person. These are recommended safeguards, not a verified group-wide implementation claim.
Do not assume an email platform keeps recipient identifiers out of URLs. Inspect generated links and the receiving measurement configuration separately. A generic campaign label is usually enough for campaign-level reporting; any individual tracking needs its own justified design and applicable consent handling. For related design questions, see Data minimisation for children in edtech and Marketing consent vs product consent.
The public Oryvelon click script inspected on September 30, 2026 removes the query string from its custom outbound event’s link_url. It also sends link text. That limited transformation does not sanitise destination paths, link text or other automatically collected fields. It is not evidence that all unexpected data is excluded.
Common mistakes and how to avoid them
- Tagging internal links. In GA4, encountering new campaign values during an existing session does not start a new session or replace that session’s source. Those values can affect event-based attribution. Avoid using acquisition tags to label internal navigation; use an appropriate event instead. See Google’s campaigns and traffic sources explanation.
- Mixing case.
Newsletterandnewsletterbecome two rows. Lowercase everything. - Inventing mediums.
insta,ig,instagram_storyandsocialall describe organic social. Use the fixed list. - Putting the platform in medium.
utm_medium=facebookhides the channel type. Platform goes in source, type goes in medium. - Ignoring advertising integrations. Check how the relevant platform’s auto-tagging and manual campaign fields interact. Document which fields each reporting use needs, test the final URL and avoid duplicate or contradictory values. There is no universal rule that every integration must use manual tags alone.
- Forgetting redirects. Some redirects drop query strings. Test the final landing URL, not just the link.
- Letting partners improvise. Give partners and affiliates their exact links, not the convention.
Reporting across companies
Consistent labels make reports easier to interpret, but comparable naming does not make metrics interchangeable. Agree on the counting unit, completed period, reporting time zone and measurement scope before comparing companies.
For example, a proposed monthly report could show destination sessions by Session source/medium, alongside separately defined lead events. GA4 distinguishes first-user, session and event scopes; their dimensions answer different questions. Do not sum originating clicks and destination sessions as if they were the same people, or call every recorded event a verified enquiry.
A group report can use aggregated figures without including individual records. That is a reporting choice, not proof that underlying systems cannot identify users. Document data access, collection limits and missing values separately, and leave unavailable figures unavailable rather than replacing them with zero.
Rolling out a convention in an existing company
If you are introducing a standard into a company with years of messy data, do not try to fix history. Instead:
- Write the convention on one page.
- Set a start date; everything before it is "legacy".
- Update evergreen links first — email footers, social bios, partner links — because they generate traffic continuously.
- Build the register and the link builder before the next campaign.
- In reports, add a simple mapping for legacy values where it matters, and leave the rest.
Review newly collected values after rollout. Judge improvement by fewer unexplained labels and verified reporting behaviour, not by a promised number of weeks. Preserve a note of the change so legacy and new periods are interpreted consistently.
A worked example: one campaign, four channels
Hypothetical example: suppose a product team plans a campaign for an additional reading format. The following ZodiVela-labelled examples illustrate a naming convention only; they do not announce a feature, launch date or live campaign. An example register entry could be new_reading_2026_10, with email, social, paid social and app placements.
The links then look like this:
| Placement | source | medium | campaign | content |
|---|---|---|---|---|
| Newsletter to subscribers who opted in | newsletter |
email |
new_reading_2026_10 |
hero_button |
| Organic post | instagram |
social |
new_reading_2026_10 |
carousel |
| Paid ad | meta |
paid_social |
new_reading_2026_10 |
video_a |
| App placement sending to a separately measured destination | zodivela_app |
app |
new_reading_2026_10 |
home_banner |
After checking collection, use matching manual campaign dimensions to compare the recorded labels. Verify the scope and channel classification before interpreting results. Campaign and content labels can distinguish placements, but they do not prove that a creative caused an outcome or that every interaction was captured.
Without a convention, labels such as Newsletter, NewReading and ig can fragment the intended grouping. A missing tag means the intended campaign label may be absent; it does not establish that the visit itself is invisible. Investigate the recorded source rather than inventing a value.
A short convention and register reduce preventable naming errors. Testing the receiving reports is what establishes whether the labels are useful in that particular setup.
QR codes, print and offline
Tags can help distinguish links intended for printed materials. They cannot prove that a visitor scanned the original item, because a URL can be copied or forwarded. Keep the campaign label tied to the intended placement and interpret it accordingly.
Hypothetical example: a package-insert QR code for Noveniq could point to the following URL. This is an illustrative path, not a verified live care page or a claim about current packaging:
https://noveniq.com/care/?utm_source=package_insert&utm_medium=print&utm_campaign=care_guide
Two practical rules help here. Keep the printed URL short by pointing the QR code at a clean redirect on the company's own domain, which then forwards to the tagged URL; if the campaign name ever needs to change, the redirect changes and the printed material does not. And test the redirect preserves the parameters before anything goes to print, because fixing a printed QR code means reprinting.
The same design could be used for hypothetical Sinem Keser Beauty Academy course or event materials: a label for the material, a campaign name for the initiative and a tested channel grouping. This does not assert that such materials or an event currently exist.
Auditing the convention
Review the convention when new sources, team members, partners or platform settings are introduced. A periodic check can also fit into a quarterly tool review. This is a suggested cadence, not a record of checks performed across the group.
Export distinct source, medium and campaign values for a completed period. Investigate unexpected spellings, mediums outside the agreed vocabulary and unexplained campaigns. Trace each issue to a published link or integration before changing it. Record approved exceptions so a legitimate value is not mistaken for an error.
Summary
A useful UTM standard separates source, medium and campaign, uses stable labels and keeps personal information out of URLs. Oryvelon’s checked homepage portfolio links provide one concrete naming example. Broader campaign and founder-link examples here are proposals. Test destination collection, GA4 reporting scope and channel classification separately; a naming convention cannot establish user anonymity, product availability or business results.
Questions and answers
What are UTM parameters?
UTM parameters are campaign labels added to a URL, such as utm_source, utm_medium and utm_campaign. Analytics tools can use them to describe traffic sources when collected. They are not a privacy guarantee: values must not contain personal information.
How does Oryvelon tag links to its companies?
The portfolio links checked on the Oryvelon homepage on September 30, 2026 use utm_source=oryvelon, utm_medium=portfolio and a company campaign key, such as utm_campaign=merchnivo. This observation does not verify receiving analytics or every link across the group.
Should UTM parameters be used on internal links?
Avoid UTMs on internal navigation. In GA4, a new campaign encountered during an existing session does not start a new session or overwrite its source, but it can affect event-based attribution. Use events to measure internal placements and verify the intended measurement boundary.