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.
A shared convention for many communities
Pick utm_medium=community as the umbrella, then set utm_source to the specific community (for example a forum domain or server name) and utm_campaign to the thread or initiative. This keeps dozens of community sources comparable in one view.
Because community links get quoted and reposted, embed the campaign so the attribution travels with the link.
- utm_medium=community
- utm_source = the specific community
- utm_campaign = the thread, AMA, or initiative
Why this is a pattern, not a fixed spec
There is no single official standard for a community taxonomy — it depends on which communities you are active in. This entry documents a convention to apply consistently rather than a vendor-published value, which is why it is marked as not yet verified against a primary source.
Write the convention into your UTM governance doc so everyone tags community posts the same way.
How it appears in analytics and logs
Visits with utm_medium=community signal a click from a community surface you tagged. The utm_source then tells you which community, letting you rank communities by engagement rather than guessing from referrers that are often missing.
Diagnostic use case
Measure traffic from the communities you participate in or operate — forums, chat servers, member areas — using one UTM convention so cross-community comparison is meaningful.
What WebmasterID can help detect
WebmasterID records community-tagged sessions under their named source server-side, so you can see community engagement as a channel alongside search and social, with bots filtered out.
Common mistakes
- Using utm_medium=referral for community links, mixing them with uncontrolled referrers.
- Inventing a new source name per post instead of per community.
- Skipping a governance entry, so teammates tag communities inconsistently.
- Forgetting reposts spread the link beyond the original thread.
Privacy and accuracy notes
Community UTMs describe the link and the community as a source, never individual members. No usernames, profiles, or message contents are captured — only that a tagged URL was opened.
Related pages
- 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.
- 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.
- UTM governance and templates
UTM data degrades when everyone builds links by hand. This page covers the governance that prevents it: a shared builder or spreadsheet, documented allow-lists for source and medium, and a review step so new values are deliberate rather than ad-hoc.
- Campaign links docs
Apply one community convention across all your communities.
Sources and verification notes
- Google Analytics Help — Collect campaign data with custom URLsReference for utm_source/medium/campaign you map to communities.
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.