
A healthy email list is the key to ensuring your newsletters land in your readersβ inboxesβ¦but manually pruning inactive subscribers can be both time-consuming and tedious.
Today we launched several powerful automation features to help you build a more robust newsletter operation.
With the new featuresβyou can build a fully automated re-engagement campaign to proactively remove dormant subscribers and keep your list squeaky clean π§½π«§.
The result: boost the deliverability and engagement of your newsletter.
And Iβll show you exactly howβ¦

Unengaged Trigger
Quick notice on terminologyββtriggersβ are conditions that start automations.
And we just added a new one to the repertoire: the Unengaged Trigger.
Youβll need to determine the length of time without any engagement (opens or clicks) required for a subscriber to be considered unengaged.

This will vary per newsletter. For example:
Daily newsletters may consider readers who havenβt engaged in 45 days to be inactive
Weekly newsletters may consider readers who havenβt engaged in 90 days to be inactive
Every day, readers who meet the criteria will be automatically enrolled into this automation at the exact same time of day as their most recent engagement (open or click).
Note: Automations are only available to users on Scale or Enterprise plans. You can learn more and/or upgrade here.

Send Email
To be fair this isnβt a new featureβ¦youβve always been able to build automations to send emails π.
But for the completeness of walking you through how to create an automated re-engagement campaignβyes, the next step is to send an email to those unengaged readers asking if they still want to receive your newsletter.
Typically I recommend copy similar to this:


Branch Node
Now the Branch Node is a new feature we introduced today. It allows you to set certain conditions, and readers will continue down either one of two possible paths depending on whether or not they meet the conditions.

These conditions could be any sort of engagement metric or subscription attribute. You can even group multiple conditions together. Some examples:
Are they a paying subscriber?
Does their email contain β@gmailβ?
Does their acquisition source include βfacebookβ?
In this example for the automated re-engagement campaigns, perhaps youβll give the reader 48 hours to open and click the email in the previous step.
So for the branch node youβll want to create a condition checking if the subscriber has clicked on any email in the past 48 hours.
If yesβthen they have technically been re-engaged and youβll want to keep them on your list.
If noβthen they have been both inactive for X period of time AND did not opt back in with your final chance email in the previous step. Youβll want to remove these subscribers.
Which leads us to the final stepβ¦
Note: Automations are only available to users on Scale or Enterprise plans. You can learn more and/or upgrade here.

Update Subscription Node
The all new Update Subscription Node allows you to automatically update the status and custom attributes associated with a subscription.
For exampleβitβs common practice to append custom fields to subscriptions when they complete an automation to indicate they have already completed it for future use.
You can also add a condition to the automation trigger to filter and prevent people with said custom field from re-entering a similar automation in the future.
Continuing our example with the automated re-engagement campaign, youβll want to do two things:
1. For those who did NOT click on the re-engagement emailβ¦
Use the update subscription node toβ¦
transition their subscription status β Inactive
add a custom field re-engaged = false

2. For those who DID click on the re-engagement emailβ¦
Use the update subscription node toβ¦
add a custom field re-engaged = true
This will allow you to track these newly engaged subscribers over time


Tying it all togetherβ¦
The purpose of the re-engagement automation is to proactively churn inactive subscribers and keep the quality of your list high. You set it up once and itβll run on autopilot indefinitely.
Create a new automation
Select the Unengaged Trigger and specify the # of days of inactivity required to be enrolled
Send a re-engagement email encouraging them to opt-in by clicking a button
Add a Branch Node to send subscribers down either one of two paths depending if they engaged with the email in step #3
Use Update Subscription Nodes to either remove the subscriber from your list (via status β Inactive) or add a custom field to re-engaged subscribers

You can watch a full video tutorial on this below π
Note: Automations are only available to users on Scale or Enterprise plans. You can learn more and/or upgrade here.

What did you think about these product updates?
P.S. I ended up autocorrecting and enhancing this post a ton using our new AI features in the text editor. You can learn more about those here.


