Discord campaign tracking with UTM
Discord communities share links constantly in announcement channels, topic channels, and via bots. Discord's client opens external links in a way that typically passes little or no referrer, so untagged clicks land in direct. Tagging the URLs you post in your server lets analytics attribute Discord-driven traffic by source and campaign, while link-preview fetches stay classified as bots.
Where Discord links live
The links you control in Discord are mainly in announcement channels, pinned messages, role-gated channels, and bot embeds. All of them open in the user's browser with little referrer signal.
Apply utm_source=discord and use utm_medium to distinguish placements such as announcement, channel, or bot. Keep utm_campaign tied to the promotion so reposts stay attributed.
- utm_source=discord
- utm_medium=announcement | channel | bot
- utm_campaign for the specific drop or event
Link unfurling and bots
When you post a URL, Discord fetches it to build an embed preview. That fetch is automated and may carry the UTM; count it as bot traffic, not a click.
If you run a Discord bot that posts links, generate the UTM-tagged URL inside the bot so every automated post is consistently attributed.
How it appears in analytics and logs
A landing hit with utm_source=discord means a tagged link was opened from inside a Discord client. Without the tag the visit would be direct, since Discord generally does not pass your site a server or channel referrer.
Diagnostic use case
Attribute clicks from Discord announcement posts, community channels, and bot embeds so community engagement shows up as a named channel rather than direct traffic.
What WebmasterID can help detect
WebmasterID records UTM-tagged Discord sessions under a named source server-side, separate from direct. Discord's link-unfurling crawler fetch is treated as a bot event, not a human click.
Common mistakes
- Assuming Discord passes a referrer — it generally does not.
- Letting Discord embed-crawler fetches inflate human click counts.
- Mixing source spellings (discord, Discord, dsc) across channels.
- Not tagging bot-posted links, leaving automated shares unattributed.
Privacy and accuracy notes
UTMs describe the link and campaign, not the Discord member. You see that a tagged URL was opened, never the user, server roles, or message content. No Discord identifiers are attached to the visit.
Related pages
- Slack campaign tracking with UTM
Slack is a common internal and community distribution channel where links are pasted into channels, DMs, and posted by apps. Slack's link unfurling fetches URLs server-side, and human clicks often arrive with little referrer, so untagged Slack traffic tends to land in direct. Tagging the links you share in Slack lets analytics attribute that traffic by source and campaign while unfurl fetches stay classified as bots.
- Community campaign tracking with UTM
Community channels — owned forums, member Discords and Slacks, subreddits, and discussion boards — drive engaged traffic that is easy to lose to direct or referral noise. A consistent UTM convention across community surfaces lets you measure which communities and which posts actually send visitors, without scraping any member data. This page covers a naming approach that keeps many community sources comparable.
- Telegram campaign tracking with UTM
Telegram channels, groups, and bots are high-volume distribution surfaces where outbound links are common. Like other messaging apps, Telegram usually does not pass a useful referrer, so untagged clicks become direct. Tagging the URLs you post in Telegram channels, pin in groups, or send from a bot lets analytics attribute that traffic by source and campaign without reading any message data.
- Bot vs human
Separate Discord unfurl fetches from real community clicks.
Sources and verification notes
- Discord — Developer documentationBot and message context for links you tag with UTMs.
- Discord — Embeds and link previewsHow posted URLs are fetched to build preview embeds.
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.