Sending to a random cohort of your audience

Available on Enterprise plans. Click here to upgrade your account.

Random cohort sending lets you send an email post to a randomly selected portion of your audience instead of your full list. You can cap the send at a percentage or a fixed number of recipients, and exclude anyone who already received specific past posts, making it easy to run controlled sends, test content with a sample, or reach fresh readers with each campaign.


Quick tips to get you started

  • Both controls live on the Audience page of the Post Builder, under your Email Audience selections. Learn more about the options on the Audience page of the post flow.
  • The random cohort is drawn from whatever email audience you’ve already selected, with subscriber tiers, plus any segments you’ve included or excluded. Exclusions from past posts are applied first, and the send size limit is applied to whoever remains.
  • Recipients are chosen at random each time. Two limited sends to the same audience can reach different subscribers, which is exactly what makes this useful for rotating through your list.
  • These settings only affect the email version of your post. Your web audience is not changed. If the post is published to the web, it remains visible to your selected web audience.

How to limit your send size

Use the Limit send size toggle when you want the post to go to a random sample of your audience rather than everyone in it.

  1. From your beehiiv dashboard, create a new post or open a draft. The post editor opens on the Compose page. Write your post and go through your normal workflows. 
  2. Once your post is set up as you wish, click Next to move on to the Audience page.
  3. On the Audience page, under Email Audience, select the subscriber tiers and any segments you want to include or exclude, as you would for any post.
  4. Next, toggle on Limit send size.

  5. Choose how to cap the send: Percentage of recipients or Fixed number of recipients.
  6. Enter a whole number in the field. Helper text below the field updates to show how many recipients will receive the post, as well as note if the number of recipients is too low for meaningful results.

  7. Click Next to continue through the post flow, then schedule or publish from the Review page as usual. The Email Audience summary reflects your limited send size.
Tech Note: If you enter a fixed number larger than your available audience, the post simply sends to everyone available. The helper text always shows the actual number of recipients.

How to exclude recipients of past posts

Use Exclude recipients from past posts when you don’t want to email subscribers who already received certain sends. An example would be readers who got a previous edition of the same sponsored campaign.
 

Pro Tip: Subscribers who received more than one of your selected posts are only excluded once, so you’ll never double-count exclusions.
  1. On the Audience page, toggle on Exclude recipients from past posts.
  2. Click the Published posts dropdown and select the posts whose recipients you want to exclude. You can select up to 10 posts.
  3. Review the recipient counts shown next to each selected post to confirm the impact on your audience.
  4. Continue through the post flow and publish as usual.
Tech Note: Only published posts can be selected for exclusion. Drafts and scheduled posts won’t appear in the dropdown. Exclusions are evaluated at send time, so the counts you see while drafting are estimates and the final audience is calculated when the post actually sends.

How the two controls work together

You can use either control on its own or combine them. When both are enabled, beehiiv builds the final email audience in this order:

  1. Starts with your selected Email Audience (subscriber tiers plus included/excluded segments).
  2. Removes anyone who received the posts you selected under Exclude recipients from past posts.
  3. Randomly selects recipients from the remaining audience, up to your Limit send size cap.

Example:  with an audience of 100,000 subscribers, one past post excluded that reached 40,000 of them, and a fixed send size of 10,000.  The post goes to 10,000 subscribers chosen at random from the 60,000 who didn’t receive the excluded post.


Use cases for random cohort sending

  • Rotate sponsored sends across your list:Send each sponsored campaign to a fixed number of subscribers and exclude recipients of the previous editions, so every send reaches fresh readers and your inventory stretches further.
  • Test content with a sample: Send a new format or topic to 10% of your list before committing to a full send.
  • Protect engagement on experimental sends: Limit higher-risk campaigns to a small random slice so a miss doesn’t affect deliverability across your whole audience.
  • Manage send frequency: If you publish often, cap individual sends so no single subscriber is overwhelmed while your full list still hears from you over time.

Frequently asked questions about random cohort sending 

Will the same subscribers be picked every time I limit a send?

No. Recipients are selected at random for each post. To guarantee that later sends skip earlier recipients, use Exclude recipients from past posts and select the earlier sends.

Does this affect the web version of my post?

No. Both controls apply to the email send only. Your web audience settings are unchanged.

Can I see exactly who received a limited send?

Yes. Post analytics reflect the actual recipients of the send, and you can build a segment of subscribers who received a specific post if you want to target or exclude them later.

Do saved templates keep these settings?

No. When you save a post as a template, the random cohort audience settings are not retained. Set your send size limit and post exclusions on each new post.

Why does an excluded post show 0 recipients removed?

If none of the recipients of an excluded post are part of your currently selected audience, that exclusion doesn't remove anyone. The counts on the Audience page show how many recipients each exclusion actually removes from this send.

Was this article helpful?

Related Articles