Fediverse campaign tracking with UTM
Federated microblogging is decentralised: links are posted across thousands of independent instances, so referrer hostnames vary and link previews are fetched by instance servers. UTM parameters on the link itself are the reliable way to attribute this traffic, since they travel with the URL regardless of which instance a click came from.
Why the fediverse needs UTM
Federated microblogging has no single domain. A post can be boosted across many instances, each with its own hostname, so referrer-based attribution scatters your traffic across dozens of rows. A UTM parameter on the link travels with the URL through every boost and reply, giving you one consistent channel value.
Set a stable convention, for example a coarse social source plus utm_medium=social, so the channel groups cleanly no matter which instance forwarded the click.
- No single fediverse domain — referrers vary per instance
- UTM on the link survives boosts across instances
- Use a coarse source value, not the instance name
Preview fetches vs human clicks
When a link is posted, instances fetch it server-side to build a link preview card. These automated fetches are bot traffic and should not be counted as campaign clicks. The exact fetch behaviour varies by instance software and version, so it is described as a pattern rather than a fixed signature, which is why this entry is marked partially verified.
Measure the human click on the tagged URL, and keep the preview fetches in your bot view so the campaign number stays clean.
How it appears in analytics and logs
A tagged fediverse link arriving with utm_source set to your chosen value identifies federated microblogging traffic regardless of the originating instance. Server-side preview fetches from instances are bots, not human clicks, and should not be counted as campaign visits.
Diagnostic use case
Attribute clicks from the fediverse to a single campaign by tagging the shared URL, instead of relying on referrer hostnames that differ per instance.
What WebmasterID can help detect
WebmasterID separates server-side link-preview fetches from fediverse instances (bot events) from real human clicks on tagged links, so your campaign count reflects people, not federation crawlers.
Common mistakes
- Relying on referrer hostnames, which differ for every instance.
- Encoding the specific instance or a user handle in utm_source.
- Counting server-side preview fetches as human campaign clicks.
- Using inconsistent source values across posts so the channel splits.
Privacy and accuracy notes
Use a coarse channel label in utm_source; do not encode the specific instance or any user handle. UTM values describe the campaign, not the individual sharer or reader.
Related pages
- Bluesky campaign tracking with UTM
Bluesky, built on the AT Protocol, can be accessed through the main app and third-party clients, so referrer hostnames vary and link cards are fetched server-side. UTM parameters on the shared link are the reliable way to attribute Bluesky traffic across the app and alternative clients.
- Threads campaign tracking with UTM
Threads is a mobile-first app where most clicks open in an in-app browser, so referrer data is often missing or shows a generic value. UTM parameters on the shared link are the dependable way to attribute Threads traffic, since they travel with the URL through the in-app webview.
- UTM parameters and bot traffic
Tagged URLs get fetched by more than humans: crawlers, link-preview unfurlers, security scanners, and uptime monitors all follow UTM links. Counting them as campaign clicks inflates results. This page explains why bots hit tagged URLs and how to separate automated traffic from human campaign visits.
- Fediverse referrer traffic (decentralised social)
The fediverse microblogging network is decentralised: there is no single canonical host, but thousands of independent instances, each on its own domain. Web reads commonly pass that instance's domain as the referrer, so this traffic is often identifiable yet spread across many hosts. Recognising the federation pattern is key to attributing it.
- Bot vs human
Separate instance preview fetches from real clicks.
Sources and verification notes
- Fediverse documentation — federation and link previewsDecentralised instances fetch link previews; no single referrer domain.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.