<aside> 🐝 For Beehiiv-based newsletters, this step is not necessary (it’s fully automated).
</aside>
If your ESP’s API doesn’t support pulling engagement data, you can manually upload engagement data via the Subscribers tab (Upload engagement button).
You can upload a CSV file with the following columns:
email
engagement_status
with the following values:
engaged
Hard confirmation email
You don’t send your newsletter unless the subscriber confirmed their subscription explicitly.
unengaged_unconfirmed
Otherwise (most common case)
You may or may not send a confirmation or welcome email but regardless of the subscriber’s interaction, you start sending your regular email.
unengaged_no_open
: the subscriber did not open any email in their first 7 daysunengaged_unsubscribe
: the subscriber unsubscribed in their first 7 daysunengaged_bounce
: the email bounced in their first 7 days, i.e., you were not able to reach their inboxunengaged_complaint
: the subscriber sent a complaint in their first 7 daysHard confirmation email (edge case)
engagement_status | ||
---|---|---|
[email protected] | unengaged_unconfirmed | they didn’t confirm so they don’t get any content email from you |
[email protected] | unengaged_unconfirmed | they didn’t confirm so they don’t get any content email from you |
Otherwise (most common case)
engagement_status | comment | |
---|---|---|
[email protected] | unengaged_no_open | they did not open any email from d0-d7 |
[email protected] | unengaged_unsubscribe | they unsubscribed before d7 |
[email protected] | unengaged_bounce | your email bounced before d7 |
[email protected] | unengaged_complaint | they sent an email complaint before d7 |
You can upload engagement data anytime for subscribers of the current invoicing period that joined at least 7 days ago. You don’t need to upload multiple times a month – it’s enough to do it once on the 7th of the month for all subscribers of the current invoicing period.