Campaign links
When you publish links across paid and organic channels, consistency and trustworthy reporting inputs matter. Nimriz keeps links branded, redirects predictable, and analytics private by default.
- Branded short domains on every placement - social, email, paid, and partners
- Bot-filtered click analytics with referrer, geography, and device breakdown
- Update destinations anytime without republishing or breaking active links
Link-level breakdown of referrers, geography, and device mix.
Most campaign link problems trace back to two separate issues that get conflated: inconsistent UTM parameters scattered across channels, and generic redirect URLs that erode brand trust at the moment of sharing. Fixing one while ignoring the other leaves campaign reporting unreliable or links that look untrustworthy, or both.
The recommended pattern is to standardize UTM parameters once on the destination URL, then shorten that destination to a single branded short link distributed everywhere. The referrer dimension in click analytics separates placements in reporting without requiring a separate link per channel. This keeps the link catalog manageable and keeps UTM attribution consistent regardless of where a click originates.
Nimriz captures referrer, country, device, and bot signals for every click event. Raw IP and full User-Agent values are never stored in redirect analytics. Bot signals are flagged separately so teams can filter noise when reviewing paid-media click counts. The result is campaign link analytics data that is more trustworthy as a reporting input, without storing fields your privacy posture does not require.
Because destinations are editable anytime without changing the short URL, campaigns can be updated mid-flight - swapping landing pages, extending expiry windows, or adjusting UTMs on the destination - without breaking every placement that already carries the link.
Who it is for
Needs consistent UTM attribution across paid, owned, and earned channels so campaign reporting in analytics tools reflects actual channel mix rather than UTM drift between placements.
Needs every link distributed in press, social, and partner content to appear on a verified branded domain rather than a generic redirect host, supporting link trust and brand recognition.
Needs to run multiple client brands from one workspace with isolated domains, bulk-create links for campaign launches, and hand off branded short links without exposing other clients or internal infrastructure.
What you get
Every placement - social, email, paid, and partner - carries a link on your own verified domain rather than a generic redirector. Branded short domains are scoped per (domain_id, short_code) so the same slug on different domains never collides. Visitors and click-trackers see a URL that looks intentional, which supports link trust at the moment of sharing.
Click events carry referrer, country, and device context. Bot signals are flagged separately so campaign click counts reflect real human traffic instead of mixing in prefetch or automation noise. Raw IP and full User-Agent values are never stored in redirect analytics.
Standardize UTM parameters once on the destination URL and distribute one branded short link across every channel. The referrer dimension in click records then separates placements without requiring a different link per channel. On supported plans, UTM presets let teams apply reusable UTM defaults at link creation time so campaign metadata stays consistent across bulk creates and imports.
Change where a link points anytime without breaking the short URL already distributed across placements. Extending an expiry, swapping a destination, updating a password gate, or removing protection all happen on the same link record. The short URL never changes, so there is nothing to republish in past emails, paid creative, or printed materials.
How it works
From raw URL to branded short link
Standardize UTM parameters once on the destination URL, shorten to a branded domain, and distribute the same link across every channel. One link, unified reporting.
Build the destination URL with UTMs using the UTM builder or by pasting a pre-built URL. Standard UTM fields are stored as editable first-class metadata, not buried in an opaque raw URL string.
Create a branded short link on a verified custom domain. Strict host matching means the short code is scoped to that domain, so cross-brand collisions are structurally impossible.
Distribute one short link across every channel. The referrer dimension in click records separates placements so channel mix stays visible without requiring a different link per placement.
- Redirects default to 302 (change-friendly). Choose 301 per link only when you want a permanent, cached redirect.
- Standard privacy-aware analytics is the default; raw IP and full User-Agent values are never stored.
- Bot signals are flagged separately so paid-media click counts reflect real human traffic.
- Add an expiration date so traffic past a campaign window lands on a branded fallback instead of a broken redirect.
Setup
- 1Verify your branded domainAdd a DNS record to confirm ownership. Nimriz validates the record and enables the domain for your workspace. Strict host matching applies immediately: apex and www are treated as separate records with no silent aliasing between them. See the custom domain setup guide for DNS record details.
- 2Build your destination URL with UTMsUse the UTM builder to set utm_source, utm_medium, utm_campaign, utm_term, and utm_content as structured fields on the link. UTM presets (on supported plans) let you apply reusable campaign defaults so every link in a launch uses consistent parameter values. Standard UTM keys are normalized to lowercase and blank values are dropped automatically.
- 3Create the branded short linkChoose your verified domain and set a readable slug. The short code is unique within that domain - the same slug can exist on a separate domain without collision because lookups are keyed by host plus short code. Add an expiration date and a branded fallback destination if the link should stop redirecting after the campaign window.
- 4Distribute one link across every channelCopy the branded short URL and use it in every placement: social posts, email, paid creative, partner content, and QR assets. You do not need a different link per channel. The referrer dimension in click analytics separates placements in reporting.
- 5Review analytics and filter bot signalsOpen link analytics to see referrer mix, country, and device breakdown. Bot-flagged clicks are separated from human traffic so campaign click counts are more useful as reporting inputs. Raw IP and full User-Agent values are never stored in redirect analytics.
- 6Update the destination or expiry anytimeIf the campaign landing page changes, update the destination. If the campaign window extends, update or remove the expiry. Neither change requires redistributing the short URL - it stays identical across all placements that already carry it.
What good looks like
Before: scattered UTMs and generic redirect URLs
- Different teammates build UTM strings independently - utm_source values vary across channels for the same campaign.
- Each channel placement uses a different long URL with embedded UTMs, making edits require updating every placement separately.
- Generic redirect URLs (third-party shortener or raw long URLs) appear in social, email, and partner content.
- Click counts include bot and prefetch traffic mixed in with human clicks, making paid-media reporting harder to trust.
- No fallback when a campaign link expires - visitors land on a broken redirect.
After: one branded short link with consistent UTMs
- UTM parameters are standardized once on the destination URL using the builder. All placements carry the same branded short link.
- The referrer dimension in click analytics separates channel performance without requiring a separate link per placement.
- Every link appears on a verified branded domain. Strict host matching keeps cross-brand collisions structurally impossible.
- Bot signals are flagged separately. Campaign click counts reflect human traffic and can be used as cleaner reporting inputs.
- Expiration date routes post-campaign traffic to a branded fallback page instead of a broken redirect.
One branded short link, consistent UTMs on the destination, privacy-aware bot-flagged analytics across every channel.
Frequently asked questions
Does Nimriz replace UTM parameters, or does it work alongside tools like GA4?
Nimriz does not replace UTM parameters. The recommended approach is to keep UTMs on the destination URL so tools like GA4 continue to attribute sessions normally. Nimriz shortens that UTM-tagged destination to a branded short link and provides click-level analytics (referrer, country, device, bot signals) as a separate reporting layer. GA4 sees the UTMs in the destination URL when the redirect resolves, so attribution in GA4 is unaffected. See the UTM parameters doc for implementation details.
Why does Nimriz use 302 redirects by default instead of 301?
302 is the default because it is change-friendly: browsers and caches do not store the redirect destination permanently, so if you update the destination or expiry, visitors see the updated behavior immediately. 301 (permanent) is a deliberate per-link choice that tells browsers and search engines to cache the redirect. Choose 301 only when you are certain the destination will not change and you want that caching behavior. See 301 vs 302 for a fuller explanation.
How does bot filtering work? Can I trust the click counts for paid media?
Nimriz applies bot flagging based on bot signals in click events. Bot-flagged clicks are recorded separately so you can view human-only traffic in analytics rather than having automation and prefetch traffic mixed into campaign counts. This makes click counts more useful as paid-media reporting inputs. Nimriz uses "bot flagging" and "bot signals" - it does not claim perfect bot removal or guarantee that every non-human click is identified.
Can I change where a link points after it has already been distributed?
Yes. You can update the destination URL, expiration date, password gate, or UTM parameters on a live link at any time. None of these changes affect the short URL itself, so all existing placements - emails, social posts, paid creative, printed materials - continue to work and route to the updated destination. Future clicks use the new destination; historical click attribution is preserved from the click-time values.
What do standard and strict privacy store and omit?
Raw IP addresses and full User-Agent strings are never stored in redirect analytics. Standard privacy-aware analytics may use daily-salted hashes for per-day deduplication, while strict privacy omits those hashes and reduces selected granular fields. Click events still record approved referrer host, country, device category, and bot signals where available. See analytics and privacy for more detail.
Can I use the same short slug on different branded domains without collision?
Yes. Slugs are unique per (domain_id, short_code), which means the same slug can exist on two separate verified domains and resolve to different destinations with no collision. Lookups are keyed by host plus short code, so apex and www are also treated as distinct records. An agency running multiple client domains from one workspace can reuse readable slugs like /launch across all of them without interference.
What happens to campaign traffic after a link expires?
You can set a branded fallback destination on any link with an expiration date. After the expiry time passes, visitors who click the link are routed to that fallback page - a product page, a waitlist, a holding page of your choice - instead of landing on a broken redirect or a platform error page. You can extend the expiry or update the fallback destination on the live link without changing the short URL. See link protection for details on expiry and fallback behavior.
Are UTM presets available on all plans?
UTM presets are plan-gated. The UTM builder itself (adding standard UTM fields to a destination URL) is available for link creation, but reusable preset records that apply campaign defaults at link creation time are available on supported plans. Refer to the UTM parameters doc or the pricing page for current plan details.
Related use cases
Deeper reading
Ready to get started?
Create your account and start with the Starter workflow. Compare plans when you need higher limits or supported-plan capabilities.