Nimriz
Marketing teams

UTM management

Inconsistent UTM tagging across a team breaks campaign reporting. Nimriz gives marketing teams a structured UTM builder, reusable workspace-scoped presets, and branded short links so every placement carries the same campaign metadata.

  • Structured UTM fields as first-class link metadata - not a raw query string
  • Reusable UTM presets enforce consistent naming across the whole team (on supported plans)
  • Edit UTM state anytime: future clicks use the new values, historical attribution is preserved
Start for freeAll use cases
UTM preset library

Reusable workspace-scoped presets applied at link creation time.

On supported plans
Presets saved
12
Default preset
1
Custom params
Supported
Saved presets
Spring launch - social
source=twittermedium=socialcampaign=spring_launch_2026
Spring launch - email
source=newslettermedium=emailcampaign=spring_launch_2026
Partner referral
source=partnermedium=referralcampaign=partner_q2

The most common cause of unreliable campaign reporting is not a broken analytics tool. It is inconsistent UTM tagging. When teammates build UTM strings independently - from memory, from a shared spreadsheet, or copied from a previous campaign - small variations in casing, spelling, or field names create separate dimensions in GA4 and other analytics tools. A campaign called spring_launch in one placement and Spring-Launch in another appears as two separate campaigns in reporting, splitting attributed traffic and making channel comparisons unreliable.

Nimriz addresses this by treating UTM parameters as structured, first-class metadata on every short link rather than as part of an opaque destination URL string. The five standard fields are surfaced distinctly in the builder, keys are normalized to lowercase, and blank values are dropped automatically. This means the canonical UTM state for a link is always readable and editable as metadata, not buried in a long URL that has to be parsed to understand.

On supported plans, UTM presets take the governance angle further. A preset is a workspace-scoped reusable record that applies campaign defaults at link creation time. When a team saves a preset for a launch - with utm_source, utm_medium, utm_campaign, and any custom parameters already set - every teammate who creates a link for that launch starts from the same values. One default preset can be configured so new links are pre-populated without any extra action. The result is consistent naming across bulk creates, imports, and manual link creation.

The recommended workflow is to standardize UTMs once on the destination URL through the builder or a preset, then distribute one branded short link everywhere. The referrer dimension in click analytics still separates placements in reporting without requiring a different link per channel. For additional internal organization, pairing utm_campaign values with tags and spaces keeps the link library organized alongside attribution metadata.

Who it is for

Campaign or growth marketer

Needs consistent UTM tagging across every channel placement so campaign dimensions in GA4 and other analytics tools reflect a single coherent campaign - not multiple variants of the same string.

Marketing operations lead

Needs a governed, team-wide naming convention enforced at the moment links are created, rather than audited after the fact in a spreadsheet.

Content or social media manager

Needs to create links quickly with the right UTM values applied by default, without having to remember parameter naming conventions for every campaign.

What you get

Structured UTM builder

The five standard UTM fields - utm_source, utm_medium, utm_campaign, utm_term, and utm_content - are treated as first-class structured metadata on every link, not as a raw query string buried in the destination URL. Standard keys are normalized to lowercase and blank values are dropped automatically. Builder-managed custom query parameters are stored alongside UTMs as a distinct, explicit set.

Reusable UTM presets

On supported plans, teams save workspace-scoped preset records that apply consistent UTM defaults at link creation time. One preset can cover both standard UTM fields and builder-managed custom query parameters. A single default preset can be set so new links start pre-populated without any extra steps. Applying a preset fills in the current metadata; it does not create a live dependency between the link and future preset edits.

Editable destination state

When a destination or its UTM state is edited, the link's current metadata updates and future clicks use the new values. Historical click records keep the parameter values that were effective when those clicks happened, so past attribution is preserved after edits. This split between current state and historical click-time values keeps reporting consistent even after mid-campaign destination changes.

Link governance through presets and tagging

Shared presets mean the whole team applies the same UTM naming conventions instead of each person building strings from memory. For internal grouping, pair utm_campaign values with tags and spaces to keep the link library organized alongside attribution metadata. Consistent naming reduces broken or mismatched campaign dimensions in downstream reporting tools like GA4.

How it works

From UTM preset to branded short link

Save UTM presets once for a campaign, apply them at link creation time, and distribute one branded short link across every placement. Consistent metadata, no manual string assembly.

1
Plan

Create a UTM preset with the five standard UTM fields plus any builder-managed custom query parameters your campaign needs. Mark one preset as the workspace default if you want new links to start pre-populated.

2
Publish

When creating a link, apply the preset. The UTM fields populate as editable structured metadata - not as a raw URL - so you can adjust individual values before saving without affecting other links that used the same preset.

3
Measure

The final destination URL is written canonically: standard UTM fields appear first in stable key order (source, medium, campaign, term, content), followed by custom params. Blank values are excluded automatically.

  • Create a branded short link on a verified custom domain. The short code is unique per domain, so the same slug can exist across multiple branded domains without collision.
  • Distribute one short link across every channel - email, social, paid, partner content. The referrer dimension in click analytics separates placements without needing a different link per channel.
  • If the campaign parameters need to change, edit the link destination. Future clicks use the updated UTM state. Historical click records preserve the values that were effective at click time.
  • For internal campaign grouping, assign a tag or space to each link. Tags and spaces are organization metadata kept distinct from UTM attribution - they do not interfere with campaign reporting in external tools.
Explore UTM presets and APITrust and privacyFAQ
Example
UTM preset applied
source=twitter  medium=social  campaign=spring_launch_2026
Canonical destination URL
https://example.com/spring?utm_source=twitter&utm_medium=social&utm_campaign=spring_launch_2026
Branded short link
https://go.brand.com/spring26
Same link in email, paid, and social
https://go.brand.com/spring26
Referrer separates placements - no separate link per channel needed

Setup

  1. 1
    Set up UTM presets for your campaign (on supported plans)
    In the workspace preset library, create a preset for each campaign or recurring channel pattern you want to standardize. Add standard UTM fields and any builder-managed custom query parameters. Set one preset as the default if you want it pre-applied to all new links. See the UTM parameters doc for the full field list and canonicalization rules.
  2. 2
    Create a link and apply the preset
    In the link builder, paste your destination URL and select the relevant UTM preset. The UTM fields populate as editable structured metadata. Adjust any individual values needed for this specific placement before saving - the change applies only to this link, not to other links that used the same preset.
  3. 3
    Verify the canonical destination URL
    The builder writes the final destination URL in canonical order: utm_source, utm_medium, utm_campaign, utm_term, utm_content, then custom params. Keys are lowercase and blank values are excluded. This is the URL that receives clicks after the redirect resolves - the same URL your analytics tools read for session attribution.
  4. 4
    Choose your branded domain and slug
    Select a verified branded domain and set a readable slug. Slugs are unique per domain, so the same slug can appear on separate branded domains without collision. Add an expiration date and fallback destination if the link should stop redirecting at the end of the campaign window.
  5. 5
    Distribute the single branded short link everywhere
    Use the same short URL in every placement: social posts, email, paid creative, and partner content. The referrer dimension in click analytics separates channel traffic in reporting. You do not need a different link per channel.
  6. 6
    Update UTM state or destination without redistributing
    If UTM values need to change mid-campaign, edit the link. Future clicks use the updated values. Historical clicks keep their click-time attribution. The short URL stays identical across all placements already carrying it - nothing needs to be republished.

What good looks like

Before: ad-hoc UTM strings and governance debt

  • Each teammate assembles UTM strings independently from memory or a shared spreadsheet - utm_campaign ends up as spring_launch, Spring Launch, and spring-launch across different placements for the same campaign.
  • A different long URL is created for each channel, meaning a destination change requires updating every placement separately.
  • Typos and casing differences create phantom campaign dimensions in GA4, splitting attributed traffic and making channel reporting unreliable.
  • No way to tell which UTM values are in use across the link library without opening each link individually.
  • Post-campaign audits require manually correcting reporting data or rebuilding campaign views to account for naming drift.

After: shared presets, consistent tags, and one branded link per placement

  • A UTM preset captures the agreed-upon values for the campaign once. All teammates apply the same preset, so spring_launch_2026 stays spring_launch_2026 everywhere.
  • One branded short link is distributed across every channel. The referrer dimension separates placements in reporting without a separate link per channel.
  • Standard UTM keys are normalized to lowercase automatically and blank values are dropped, so canonicalization happens at creation time rather than in a post-processing step.
  • Preset names in the library make it easy to see which campaign conventions are in use workspace-wide and to update them for the next campaign.
  • For internal grouping, tags and spaces organize links alongside attribution metadata without interfering with campaign dimensions in external analytics tools.

Consistent UTM naming enforced at creation time, one branded link per placement, and clean campaign dimensions in downstream reporting.

Frequently asked questions

What is a UTM preset and how is it different from the UTM builder?

The UTM builder is the structured form in the link creation flow where you fill in utm_source, utm_medium, utm_campaign, utm_term, utm_content, and any custom query parameters. A UTM preset is a saved, reusable workspace record that pre-populates those fields when you create a link. The builder is always available; presets are a convenience layer on top of it, available on supported plans, that let the whole team apply the same values without manual entry. See the UTM parameters doc for details.

Are UTM presets available on all plans?

UTM presets are available on supported plans. The UTM builder itself - adding standard UTM fields to a destination URL as structured metadata - is available when creating links, but saving reusable preset records that can be applied at creation time is plan-gated. Check the pricing page or the UTM parameters doc for current plan details.

Does editing a UTM preset update all links that used it?

No. Applying a preset is a one-time convenience action that fills in the current metadata on a link at creation time. Once the link is saved, it has no live relationship to the preset. Editing the preset later does not change the UTM values on links that previously used it. This is intentional: it means a preset update does not silently alter active campaign links or their historical attribution.

If I edit a link's UTM values after it is live, what happens to existing click data?

Historical clicks keep the parameter values that were effective when those clicks happened. Editing a link's UTM state updates the current link metadata and affects future clicks only. This split between current state and historical click-time attribution means past reporting stays consistent even after destination or UTM edits. The short URL itself never changes, so all existing placements continue to work.

Why should I use one branded short link instead of a different URL per channel?

Using one branded short link and letting the referrer dimension separate placements keeps the link catalog smaller and makes destination updates simpler - one edit applies everywhere the link is used. A different long URL per channel means any destination change requires updating every placement separately. The referrer data that click analytics captures (the domain that sent the visitor) provides the same channel-level visibility without multiplying links. See the campaign links use case for more on this pattern.

How do UTM parameters and tags or spaces relate to each other?

UTM parameters are attribution metadata attached to the destination URL and consumed by external analytics tools like GA4. Tags and spaces are internal link organization labels used for filtering and grouping links within Nimriz. They are kept deliberately separate: tags and spaces do not appear in the destination URL and do not affect how external analytics tools attribute sessions. For internal campaign grouping, you can use a tag that matches your utm_campaign value to keep the link library organized without creating any dependency between the organization metadata and the attribution metadata. See the link organization use case for more on tags and spaces.

Does Nimriz replace GA4 or my analytics tool for campaign reporting?

No. Nimriz provides click-level analytics - referrer, country, device, and bot signals - as a layer on top of your branded short links. Your existing analytics tool (GA4, Plausible, or similar) continues to attribute sessions using the UTM parameters in the destination URL after the redirect resolves. The two reporting layers are complementary: Nimriz click data shows what happened at the link level, your analytics tool shows what happened on the destination after the click. See the analytics integration use case for how they work together.

Can I use custom query parameters alongside UTMs?

Yes. The UTM builder supports builder-managed custom query parameters in addition to the five standard UTM fields. Custom params are stored as a distinct, explicit set - separate from the standard UTM fields and separate from any opaque query params already present in a pasted destination URL. They appear after the standard UTM fields in the canonical destination URL. A preset can include both standard UTM fields and custom params, so a team that uses a custom tracking dimension alongside UTMs can encode both in one reusable preset.

Related use cases

Campaign links
Branded campaign links across every channel.
Organize links with spaces and tags
Organize links with tags and spaces alongside UTM metadata.
Analytics integration
Connect Nimriz click data with your analytics stack.

Deeper reading

UTM parameters docSpaces and tags docAPI, automation, and UTM presets featureBranded links and domainsUTM best practicesGlossary: UTM parameters

Ready to get started?

Create your account and start with the Starter workflow. Compare plans when you need higher limits or supported-plan capabilities.

Start for freeView pricing