Various statistics and reports are available in Blueshift via UI, Campaign APIs or Amazon S3. The table below provides a brief overview of all metrics captured in Blueshift by channel.
| Push(SDK) | Push(non-SDK) | SMS | In-app | ||
|
Sends |
Emails sent to ESP (not delivered yet) | Messages sent to GCM/APNS |
Messages sent to SMS Service Provider (not delivered to users) |
Messages sent to SMS Service Provider (not delivered to users) | In-app messages sent to customer devices |
Note: Sends is referred to as users in the campaign activity report and other reports exported from the platform. |
|||||
| Impressions | Total emails opened | ||||
| Unique Impressions | Unique users that opened an email. Uniqueness is maintained in a 7 day window. So if user X opens an email in two subsequent days, it will be counted as a single unique impression. If the user X opens the email twice in two weeks apart, it will count as two impressions | ||||
| Clicks | All the clicks recorded for a tracking link. Note: If a user clicks 5 times on a tracking link, the servers will record 5 total clicks and 1 unique click | All the clicks recorded for a tracking link. Note: If a user clicks 5 times on a tracking link, the servers will record 5 total clicks and 1 unique click | App opened and an event was generated within 15 minutes of send, relies on mobile app sending events to Blueshift. | The customer clicked on a clickable element (buttons, links etc...) on the in-app message. This event has additional data (clk_url & clk_elmt) that tells us on which element did the user click. |
|
| Unique Clicks | Number of unique users that clicked on a tracking link | Number of unique users that clicked on a tracking link | Number of unique users that clicked on a tracking link | Number of unique users that clicked on a tracking link (only if the SMS contains a link and Shorten & Track Links is enabled on the template) | |
| Visits | New session created from a campaign click. We will generate a new session after 30 minutes of inactivity | New session created from a campaign click. We will generate a new session after 30 minutes of inactivity. | New session created from a campaign click. We will generate a new session after 30 minutes of inactivity. | ||
| Orders | Orders created via a campaign (and as defined by attribution settings | Orders created via a campaign (and as defined by attribution settings) | Orders created via a campaign (and as defined by attribution settings) | Orders created via a campaign (and as defined by attribution settings) | |
| Activations | First purchase (and as defined by attribution settings) | First purchase (and as defined by attribution settings) | First purchase (and as defined by attribution settings) | First purchase (and as defined by attribution settings) | |
| Delivered | Emails delivered to users (not bounced). | sent-bounce=delivered |
|
The in-app message payload is fetched from the API and stored locally. | |
| Revenue | Total revenue resulting from the campaign (and as defined by attribution settings) | Total revenue resulting from the campaign ( and as defined by attribution settings) | Total Revenue | ||
| Bounces |
Includes both hard and soft bounces. Soft bounces will be retried for up to 72hrs. However, whenever we receive a hard bounce, we will update the user attribute - email_hard_bounced to true and exclude user(s) from subsequent sends |
Invalid Tokens (will be removed for subsequent sends) | Invalid Tokens (will be removed for subsequent sends) | ||
| Spam Reports | Triggered when a customer clicks the spam button or puts your email in their spam folder within their email client such as Yahoo, Google, Outlook, etc. We also store this as a custom attribute - email_spam_reported | ||||
| Unsubscribes | Unique user who unsubscribed via the unsubscribe link in the email template or from the email header. |
Unique user who uses one of the following unsubscribe keywords (if Twilio is used to send an SMS):
|
|
||
| Devices sent | The number of mobile devices a push or in-app message was sent to. | The number of mobile devices to which a push or in-app message was sent to. |
|
The number of mobile devices a push or in-app message was sent to. |
|
| Devices bounced | The number of mobile devices to which we could not deliver a push message. | The number of mobile devices to which we could not deliver a push message. |
|
|
|
| Drops | Messages to a specific email address that an ESP drops in order to protect your sender reputation. |
|
|
||
|
|
The in-app message is displayed in the host application. |
||||