• beehiiv Blog
  • Posts
  • beehiiv's Powerful Attribution Engine Helps You Grow

beehiiv's Powerful Attribution Engine Helps You Grow

We've been hard at work making updates to how we collect and surface useful data about subscribers.

Background

As part of our ongoing efforts to provide the most powerful tools to help creators grow, we recently released updates to our subscriber attribution tools within the Beehive platform.

You may not have seen them as they are deep within the platform, but these are some of the most valuable metrics for creators intent on growing their following.

Before we get into how to use these data, it's important to provide context as to where these updates are coming from and where they're leading.

From the beginning, it's been our goal here at beehive to provide the most functional platform for growing and scaling your newsletter. That begins with a clear understanding of where your audience finds you and where they're coming from when they subscribe to a publication. Over the next few months will be rolling out updates like allowing creators to segment audiences with greater granularity.

Updated beehiiv Attribution Framework:

channel: source / medium

Channel: The method by which a subscriber is added to a publication

Source: Where a subscriber came from before subscribing

Medium: How a subscriber came to a publication

How it Works

UTM parameters are commonly used to track links to understand how users arrive on a website. These are created by taking a URL, say beehiiv.com, and adding a “?” to the end followed by up to five standard UTM Parameters, each separated by a “&”:

  • utm_source

  • utm_medium

  • utm_campaign

  • utm_content

  • utm_term

To learn more about how these are used, here’s an article that goes into deeper detail.

The important part is how these are used. If we wanted to tag a link to this blog’s subscription page from an organic post on Twitter, the URL might look like this:

https://blog.beehiiv.com/subscribe?utm_source=twitter&utm_medium=organic

Importantly, there is no required way to set UTM parameters, they can be set to anything, however, to provide some standardization, we’ve provided examples of common UTM sources and mediums at the end of this article.

It’s useful to note that for links that are not tagged explicitly with UTM parameters, our platform automatically collects data about the user’s visit and sets source and medium data based on the data we piece together about the visit.

Once this data is collected, we surface this information at the Subscriber level, which can be viewed by logging into your beehiiv account, navigating to Subscribers, and selecting a specific user.

Example 1

What you see in beehiiv:

[email protected] - website: direct / (none)

Would be read as:

[email protected] was added to Publication XYZ from the publication’s beehiiv website (channel). They signed up after navigating to the publication by typing in the URL to their browser (source, medium.)

Example 2

What you see in beehiiv:

[email protected] - import: google / organic

Would be read as:

[email protected] was added to Publication XYZ via a direct list upload (channel). They signed up after navigating to the publication by searching Google (source) and navigating to the publication organically (medium).

Example 3

What you see in beehiiv:

[email protected] - website: twitter.com / (none)

Would be read as:

[email protected] was added to Publication XYZ from the publication’s beehiiv website (channel). They found the sign-up after clicking on a link in their Twitter (source) feed (medium).

Example 4

What you see in beehiiv:

[email protected] - embed: facebook / cpc

Would be read as:

[email protected] was added to Publication XYZ with an embed form (channel). They found the sign-up after clicking on a Facebook (source) ad (medium). In this case, the UTM parameters from the Facebook ad would have been manually set in the ad campaign to be utm_source=facebook and utm_medium=cpc

Common Channels, Sources, and Mediums

Channel / Description

website

The user was added from a publication’s beehiiv website

embed

The user was added from an embedded subscribe form, which you can create in your account under settings

import

The user was added by a subscriber import upload

api

User was added via API directly, or through a Zapier connection

 

Source / Description

direct

The user came directly to the landing page via an untracked link, typing in the publication URL, or, in the case of uploads, without a source defined.

google, bing, yahoo, duck duck go

The user came to the landing page from a search engine platform.

facebook, twitter, linkedin, instagram

The user came to the landing page via a social media platform.

[website] i.e. wikipedia.org

The user came to the landing page from a link contained on another website.

pollinate

User came from the pollinate app

[custom]

This could be anything, a one-off promotion, a unique platform that you’re testing, and more.

 

Medium / Description

(none)

The default medium if no parameters are present or if a user typed in the URL to their browser

organic

The user interacted with an organic search listing

cpc, ppc, paid, display

The user interacted with a paid ad or link

referral

The user clicked a link on an organic link within a website 

[custom]

This could be anything, a one-off promotion, a unique platform that your testing, and more.

Join the conversation

or to participate.