Send Post to multiple Newsletters

Ideas
1

Currently, it is only possible to send a post to one newsletter. I can only divide the recipients into paid and non-paid.

However, my use case is this:

People who subscribe to my blog shall get all posts as a newsletter.
But then I have project-specific newsletters.
And some people might only be interested in that project but not all posts.

I want to send the project-specific newsletter to the project newsletter and people who have opted into the “get all news” newsletter.

Of course, there should be deduplication for those email.

There was some discussion already here:

2

I’ve voted for this because I have the exact same concept in my blog. One “all posts” newsletter, than two more specific topic-based newsletters. Most of my posts would go to 2 of the 3 newsletters.

3

I would also use this feature. While it’s possible to duplicate and send to two newsletters, it means anyone subscribed to both gets two copies.

It’d be possible to run one newsletter and mark members by label for which topics they want to receive, but there’s no built in way for a member to edit their labels, so this is not an easy workaround.

1 Like
4

I explicitly did not write how the feature should work in detail.
But yes, deduplication for emails for the same recipient should be done.

But it could be on the lower level inside the ghost code.
Their choice.

5

I voted for this because I want to offer two options on my site: get all posts, or only get the monthly digest. I should be able to send the monthly digest to both All Posts and Digest Only subscribers.

I thought perhaps I could use labels to accomplish this, but labels still only apply to subscribers of a single newsletter. Right now, it seems the only two native options are:

  • Create a duplicate monthly digest and publish it to the Digest Only newsletter. This is probably the more elegant workaround. You can publish as email only, add a link to view the All Posts version on the web, and create a Digest Only post view in the admin to avoid seeing duplicates.
  • Temporarily subscribe Digest Only members to All Posts, publish, then revert their subscriptions. This avoids duplicate posts, but at the cost of a dirty solution that involves messing with people’s preferences, and is prone to human error. Plus, it doesn’t scale well — unless you only have a handful of subscribers, you will need to develop a custom solution using the admin API.

Sending posts to multiple newsletters seems like the simplest solution to implement. You could also implement a native Digest feature with frequency and theme template support, but that is a much larger endeavor.

6

I think I’ve decided to go with labels. I’m going to write a cloud function to let my site members edit their own labels, and then I’ll choose which labels should receive my singular newsletter, instead of offering multiple newsletters for subscription.

1 Like