Introduction
This tutorial aims to clarify the distinction between 'Unsubscribed' and 'Email Unsubscribed' as recorded in the Journey Message Metrics via Data Pipelines connected to Amplitude.
Problem
There may be some confusion involving the difference between 'Unsubscribed' and 'Email Unsubscribed' within the Journey Message Metrics. Specifically, there could be uncertainty about whether 'Email Unsubscribed' captures cases in which a person unsubscribes from a specific type of email, and does not resort to a general unsubscribe.
Solution
The term 'unsubscribed' records general unsubscribes, which can be activated through any message channel, an API call on the backend to update the 'unsubscribed' attribute, or manual modification in the User Interface (UI). On the other hand, 'email unsubscribed' tracks when someone unsubscribes via a link in a specific email. These two terms represent distinct activities, as outlined below:
- Unsubscribe via link in an email: This is captured under 'email unsubscribed'. When a user clicks on the unsubscribe link within a particular email, this action is recorded as 'email unsubscribed'.
- Unsubscribe from the subscription center: This action is classified under 'unsubscribed'. If a user chooses to unsubscribe from messages through any other channel, be it an API call, the UI, or the subscription center, this is depicted as an 'unsubscribed' event.
Below, you will find screenshots that visually depict the difference between these two sets of activities:
Gaining a deeper understanding of this area can help to ensure that the data being used from the message metrics is accurate and reflective of actual user behavior.