Free UTM Builder for BlueSky

BlueSky (decentralized social platform) routes to "Organic Social" for organic posts. As a newer, Twitter-like platform, utm_source=bluesky helps you track its performance separately. BlueSky emphasizes open protocols and algorithmic choice, so content engagement can vary significantly—utm_content helps identify what resonates.

Organic BlueSky

Source: bluesky
Medium: social
GA4 Channel: Organic Social

Paid BlueSky

Source: bluesky
Medium: paid_social
GA4 Channel: Paid Social

Worked Examples

Build Your BlueSky UTM Link

Common utm_content Values for BlueSky

postthreadreplyprofile-linkcustom-feed

Common Pitfalls

Using app domain variants in utm_source

BlueSky can be accessed via bsky.app or other instances. Always normalize to utm_source=bluesky regardless of the domain to keep reporting unified.

Treating BlueSky like Twitter without differentiation

While similar to Twitter, BlueSky has unique community norms. Use distinct utm_campaign values to compare BlueSky vs X (Twitter) performance accurately.

Not leveraging custom feeds for tracking

BlueSky's custom feeds are a unique feature. Use utm_content=custom-feed-[name] to track which feeds drive traffic to your content.

BlueSky UTM FAQs

Should I use "bluesky" or "bsky" for utm_source?

Use "bluesky" for clarity and consistency. While "bsky" is the app domain, "bluesky" is the platform name and more recognizable in reports.

How do I track BlueSky threads vs single posts?

Use utm_content=thread for multi-post threads and utm_content=post for single posts. BlueSky threads can go viral, so tracking them separately helps measure their impact.

Can I compare BlueSky and X (Twitter) performance?

Yes! Use utm_source=bluesky for BlueSky and utm_source=x for Twitter. Keep the same utm_campaign name if it's a cross-platform effort, and you can compare source performance in GA4.

Related BlueSky Resources