Various statistics and reports are available in Blueshift via the UI, Insights reports, Campaign APIs or Amazon S3.
In addition to the core metrics, you can create compound metrics that are based on core metrics or custom goals to use in reports.
Create a compound metric
You can create a compound metric from the Campaign Dashboard. You can also create a compound metric when you create an Insights report. This compound metric will then be available for use in all reports.
To add a compound metric, complete the following steps:
- Click the gear icon on the Campaign Dashboard.
- Go to the Compound Metrics tab.
- Click Edit Metrics and then + Add Metric.
- Add a Name for the metric.
- Select Format as Ratio or Percentage.
- Select a metric for the Numerator and Denominator.
- Click Create Metric.
You can now use the compound metric in your reports.
Core Metrics
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 | The in-app message is displayed in the host application. | |||
| Unique Impressions1 |
Unique users that opened an email. If a user X opens an email multiple times, it will be counted as a single unique impression regardless of the time duration between two opens.2 |
If the in-app message is displayed multiple times in the host application, it will be counted as a single unique impression. | |||
| 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 and clk_elmt) that tells us on which element did the user click. Does not include clicks for Dismiss actions. |
|
| Unique Clicks1 | 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). | |
| Dismiss | The customer closed or dismissed the in-app message. | ||||
| 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. 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). |
Delivered = Sent - Bounced A message is considered as delivered if a bounce is not received from APNS or FCM for a specific send. |
Messages delivered to users (not bounced). Available only for some of Blueshift's native integrations. |
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 users from subsequent sends. |
Invalid Tokens (will be removed for subsequent sends). | Invalid Tokens (will be removed for subsequent sends). |
Messages not delivered to users (bounced). Available only for some of Blueshift's native integrations. |
|
| 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:
Available only for some of Blueshift's native integrations. |
|||
| 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. | The number of mobile devices to which we could not deliver an in-app message. | ||
| Drops | Messages to a specific email address that an ESP drops in order to protect your sender reputation. | ||||
Note:
1 Blueshift uses the HyperLogLog algorithm for estimating unique impressions and unique clicks. This algorithm has an accuracy of 98%, which means that results will be within a 2% error margin.
2 For a campaign, if you consider the uniqueness counts for a single day, these are calculated independently for each day, without any influence from other days. For example, for a campaign, one user clicks on the same message in their inbox every day for 7 days. If you generate a daily time series, you will see this unique click in the report for each day. But if you generate a report for 7 days, you will see a single click.
Comments
0 comments