Standard Amazon Pinpoint analytics metrics
You can use Amazon Pinpoint Analytics APIs to query analytics data for a subset of standard metrics that apply to Amazon Pinpoint projects, campaigns, and journeys. These metrics, also referred to as a key performance indicators (KPIs), are measurable values that can help you monitor and assess the performance of projects, campaigns, and journeys.
Amazon Pinpoint provides programmatic access to analytics data for several types of standard metrics:
-
Application metrics – These metrics provide insight into trends for all the campaigns and transactional messages that are associated with a project, also referred to as an application. For example, you can use an application metric to get a breakdown of the number of messages that were opened by recipients for each campaign that's associated with a project.
-
Campaign metrics – These metrics provide insight into the performance of individual campaigns. For example, you can use a campaign metric to determine how many endpoints a campaign message was sent to or how many of those messages were delivered to endpoints.
-
Journey engagement metrics – These metrics provide insight into the performance of individual journeys. For example, you can use a journey engagement metric to get a breakdown of the number of messages that were opened by participants in each activity of a journey.
-
Journey execution metrics – These metrics provide insight into participation trends for individual journeys. For example, you can use a journey execution metric to determine how many participants started a journey.
-
Journey activity execution metrics – These metrics provide insight into participation trends for individual activities in a journey. For example, you can use a journey activity execution metric to determine how many participants started an activity and how many participants completed each path in an activity.
The topics in this section list and describe the individual metrics that you can query for each type of metric.
Topics
Application metrics for campaigns
The following table lists and describes standard application metrics that you can query to
assess the performance of all the campaigns that are associated with an Amazon Pinpoint project. To query
data for these metrics, use the Application metrics
resource of the Amazon Pinpoint API. The kpi-name column in the table
indicates the value to use for the kpi-name parameter in a query.
| Metric | Kpi-name | Description |
|---|---|---|
Delivery rate |
|
For all the campaigns that are associated with a project, the percentage of messages that were delivered to recipients. This metric is calculated as the number of messages that were sent by all the campaigns for a project and delivered to recipients, divided by the number of messages that were sent by all of those campaigns. |
|
Delivery rate, grouped by date |
|
For all the campaigns that are associated with a project, the percentage of messages that were delivered to recipients, for each day in the specified date range. This metric is calculated as the number of messages that were sent by all the campaigns for a project and delivered to recipients, divided by the number of messages that were sent by all of those campaigns, for each day in the specified date range. The query results for this metric are grouped by calendar day, in extended ISO 8601 format. |
Email open rate |
|
For all the campaigns that are associated with a project, the percentage of email messages that were opened by recipients. This metric is calculated as the number of email messages that were sent by all the campaigns for a project and opened by recipients, divided by the number of email messages that were sent by all of those campaigns and delivered to recipients. |
|
Email open rate, grouped by campaign |
|
For each campaign that's associated with a project, the percentage of email messages that were opened by recipients. This metric is calculated as the number of email messages that were sent by a campaign and opened by recipients, divided by the number of email messages that were sent by the campaign and delivered to recipients. The query results for this metric are grouped by campaign ID ( |
|
Endpoint deliveries |
|
For all the campaigns that are associated with a project, the number of unique endpoints that messages were delivered to. |
Endpoint deliveries, grouped by campaign |
|
For each campaign that's associated with a project, the number of unique endpoints that messages were delivered to. The query results for this metric are grouped by campaign ID ( |
|
Endpoint deliveries, grouped by date |
|
For all the campaigns that are associated with a project, the number of unique endpoints that messages were delivered to, for each day in the specified date range. The query results for this metric are grouped by calendar day, in extended ISO 8601 format. |
|
Messages delivered, grouped by campaign |
|
For each campaign that's associated with a project, the number of messages that were delivered to recipients. This metric is calculated as the number of messages that were sent by a campaign, minus the number of messages that were sent by the campaign and couldn't be delivered to recipients due to a hard bounce. The query results for this metric are grouped by campaign ID ( |
|
Push open rate |
|
For all the campaigns that are associated with a project, the percentage of push notifications that were opened by recipients. This metric is calculated as the number of push notifications that were sent by all the campaigns for a project and opened by recipients, divided by the number of push notifications that were sent by all of those campaigns and delivered to recipients. |
|
Push open rate, grouped by campaign |
|
For each campaign that's associated with a project, the percentage of push notifications that were opened by recipients. This metric is calculated as the number of push notifications that were sent by a campaign and opened by recipients, divided by the number of push notifications that were sent by the campaign and delivered to recipients. The query results for this metric are grouped by campaign ID ( |
Application metrics for transactional email messages
The following table lists and describes standard application metrics that you can query to
monitor trends for all the transactional email messages that are associated with an Amazon Pinpoint
project. To query data for these metrics, use the Application metrics
resource of the Amazon Pinpoint API. The kpi-name column in the table
indicates the value to use for the kpi-name parameter in a query.
Note that these metrics don't provide data about email messages that were sent by campaigns. They provide data about transactional email messages only. To query data for messages that were sent by one or more campaigns, use a campaign metric or an application metric for campaigns.
| Metric | Kpi-name | Description |
|---|---|---|
Clicks |
|
The number of times that recipients clicked links in the messages. If a single recipient clicked multiple links in a message, or clicked the same link more than once, each click is included in the count. |
Clicks, grouped by date |
|
The number of times that recipients clicked links in the messages, for each day in the specified date range. If a single recipient clicked multiple links in a message, or clicked the same link more than once, each click is included in the count. The query results for this metric are grouped by calendar day, in extended ISO 8601 format. |
Complaint rate |
|
The percentage of messages that were reported by recipients as unsolicited or unwanted email. This metric is calculated as the number of messages that were reported by recipients as unsolicited or unwanted email, divided by the number of messages that were sent. |
Complaint rate, grouped by date |
|
The percentage of messages that were reported by recipients as unsolicited or unwanted email, for each day in the specified date range. This metric is calculated as the number of messages that were reported by recipients as unsolicited or unwanted email, divided by the number of messages that were sent, for each day in the specified date range. The query results for this metric are grouped by calendar day, in extended ISO 8601 format. |
Complaints |
|
The number of messages that were reported by recipients as unsolicited or unwanted email. |
Complaints, grouped by date |
|
The number of messages that were reported by recipients as unsolicited or unwanted email, for each day in the specified date range. The query results for this metric are grouped by calendar day, in extended ISO 8601 format. |
Deliveries |
|
The number of messages that were delivered to recipients. This metric is calculated as the number of messages that were sent, minus the number of messages that couldn't be delivered due to a soft or hard bounce or because they were rejected. A message is rejected if Amazon Pinpoint determines that the message contains malware. Amazon Pinpoint doesn't attempt to send rejected messages. |
Deliveries, grouped by date |
|
The number of messages that were delivered to recipients, for each day in the specified date range. This metric is calculated as the number of messages that were sent, minus the number of messages that couldn't be delivered due to a soft or hard bounce or because they were rejected, for each day in the specified date range. A message is rejected if Amazon Pinpoint determines that the message contains malware. Amazon Pinpoint doesn't attempt to send rejected messages. The query results for this metric are grouped by calendar day, in extended ISO 8601 format. |
Delivery rate |
|
The percentage of messages that were delivered to recipients. This metric is calculated as the number of messages that were sent and delivered to recipients, divided by the number of messages that were sent. |
Delivery rate, grouped by date |
|
The percentage of messages that were delivered to recipients, for each day in the specified date range. This metric is calculated as the number of messages that were sent and delivered to recipients, divided by the number of messages that were sent, for each day in the specified date range. The query results for this metric are grouped by calendar day, in extended ISO 8601 format. |
Hard bounces |
|
The number of messages that couldn't be delivered to recipients due to a hard bounce. A hard bounce occurs if a persistent issue prevents a message from being delivered—for example, if a recipient's email address doesn't exist. |
Hard bounces, grouped by date |
|
The number of messages that couldn't be delivered to recipients due to a hard bounce, for each day in the specified date range. A hard bounce occurs if a persistent issue prevents a message from being delivered—for example, if a recipient's email address doesn't exist. The query results for this metric are grouped by calendar day, in extended ISO 8601 format. |
Opens |
|
The number of messages that were opened by recipients. |
Opens, grouped by date |
|
The number of messages that were opened by recipients, for each day in the specified date range. The query results for this metric are grouped by calendar day, in extended ISO 8601 format. |
Sends |
|
The number of messages that were sent. |
Sends, grouped by date |
|
The number of messages that were sent, for each day in the specified date range. The query results for this metric are grouped by calendar day, in extended ISO 8601 format. |
Soft bounces |
|
The number of messages that couldn't be delivered to recipients due to a soft bounce. A soft bounce occurs if a temporary issue prevents a message from being delivered—for example, if a recipient's inbox is full or the receiving server is temporarily unavailable. |
Soft bounces, grouped by date |
|
The number of messages that couldn't be delivered to recipients due to a soft bounce, for each day in the specified date range. A soft bounce occurs if a temporary issue prevents a message from being delivered—for example, if a recipient's inbox is full or the receiving server is temporarily unavailable. The query results for this metric are grouped by calendar day, in extended ISO 8601 format. |
Unique user click events |
|
The number of unique recipients (endpoints) who clicked links in messages. Unlike the Clicks metric, this metric reports the number of unique recipients who clicked links, not the number of click events that occurred. For example, if a single recipient clicked multiple links in the same message, or clicked the same link more than once, this metric reports only one click event for that recipient. |
Unique user click events, grouped by date |
|
The number of unique recipients (endpoints) who clicked links in messages, for each day in the specified date range. Unlike the Clicks, grouped by date metric, this metric reports the number of unique recipients who clicked links, not the number of click events that occurred. For example, if a single recipient clicked multiple links in the same message, or clicked the same link more than once, this metric reports only one click event for that recipient. The query results for this metric are grouped by calendar day, in extended ISO 8601 format. |
Unique user open events |
|
The number of unique recipients (endpoints) who opened messages. Unlike the Opens metric, this metric reports the number of unique recipients who opened messages, not the number of open events that occurred. For example, if a single recipient opens the same message multiple times, this metric reports only one open event for that recipient. |
Unique user open events, grouped by date |
|
The number of unique recipients (endpoints) who opened messages, for each day in the specified date range. Unlike the Opens, grouped by date metric, this metric reports the number of unique recipients who opened messages, not the number of open events that occurred. For example, if a single recipient opens the same message multiple times, this metric reports only one open event for that recipient. The query results for this metric are grouped by calendar day, in extended ISO 8601 format. |
Application metrics for transactional SMS messages
The following table lists and describes standard application metrics that you can query to
monitor trends for all the transactional SMS messages that are associated with an Amazon Pinpoint project.
To query data for these metrics, use the Application metrics
resource of the Amazon Pinpoint API. The kpi-name column in the table
indicates the value to use for the kpi-name parameter in a query.
Note that these metrics don't provide data about SMS messages that were sent by campaigns. They provide data about transactional SMS messages only. To query data for messages that were sent by one or more campaigns, use a campaign metric or an application metric for campaigns.
| Metric | Kpi-name | Description |
|---|---|---|
Average price per message, grouped by country |
|
The average cost of sending each message, for each country or region that messages were sent to. The price is shown in thousandths of a United States cent. For example, if the value of this attribute is 645, then we charged you 0.645¢ to send the message (645 / 1000 = 0.645¢ = $0.00645). This metric is calculated as the total cost of all the messages that were sent to recipients in each country or region, divided by the number of messages that were sent to recipients in each of those countries and regions. The query results for this metric are grouped by country or region, in ISO 3166-1 alpha-2 format. |
Average price per message part, grouped by country |
|
The average cost of sending each message part, for each country or region that messages were sent to. A message part is a portion of an SMS message. The price is shown in thousandths of a United States cent. For example, if the value of this attribute is 645, then we charged you 0.645¢ to send the message (645 / 1000 = 0.645¢ = $0.00645). This metric is calculated as the total cost of all the message parts that were sent to recipients in each country or region, divided by the number of message parts that were sent to recipients in each of those countries and regions. The query results for this metric are grouped by country or region, in ISO 3166-1 alpha-2 format. |
Deliveries |
|
The number of messages that were delivered to recipients. |
Deliveries, grouped by country |
|
The number of messages that were delivered to recipients, for each country or region that messages were sent to. The query results for this metric are grouped by country or region, in ISO 3166-1 alpha-2 format. |
Deliveries, grouped by date |
|
The number of messages that were delivered to recipients, for each day in the specified date range. The query results for this metric are grouped by calendar day, in extended ISO 8601 format. |
Delivery errors |
|
The number of times that an error occurred while attempting to deliver the messages, for each type of error that occurred. The query results for this metric are grouped by error code, for each type of error that occurred. |
Delivery rate |
|
The percentage of messages that were delivered to recipients. This metric is calculated as the number of messages that were sent and delivered to recipients, divided by the number of messages that were sent. |
Delivery rate, grouped by date |
|
The percentage of messages that were delivered to recipients, for each day in the specified date range. This metric is calculated as the number of messages that were sent and delivered to recipients, divided by the number of messages that were sent, for each day in the specified date range. The query results for this metric are grouped by calendar day, in extended ISO 8601 format. |
Message parts delivered |
|
The number of message parts that were delivered. A message part is a portion of an SMS message. If an SMS message contains more characters than the SMS protocol allows, Amazon Pinpoint splits the message into as many message parts as necessary to send the message to a recipient. |
Message parts delivered, grouped by country |
|
The number of message parts that were delivered, for each country or region that messages were sent to. A message part is a portion of an SMS message. The query results for this metric are grouped by country or region, in ISO 3166-1 alpha-2 format. |
Message parts sent |
|
The number of message parts that were sent. A message part is a portion of an SMS message. If an SMS message contains more characters than the SMS protocol allows, Amazon Pinpoint splits the message into as many message parts as necessary to send the message to a recipient. |
Message parts sent, grouped by country |
|
The number of message parts that were sent, for each country or region that messages were sent to. A message part is a portion of an SMS message. The query results for this metric are grouped by country or region, in ISO 3166-1 alpha-2 format. |
Messages sent |
|
The number of messages that were sent. |
Messages sent, grouped by country |
|
The number of messages that were sent, for each country or region that messages were sent to. The query results for this metric are grouped by country or region, in ISO 3166-1 alpha-2 format. |
Messages sent, grouped by date |
|
The number of messages that were sent, for each day in the specified date range. The query results for this metric are grouped by calendar day, in extended ISO 8601 format. |
Total price, grouped by country |
|
The total cost of sending the messages, for each country or region that messages were sent to. The price is shown in thousandths of a United States cent. For example, if the value of this attribute is 645, then we charged you 0.645¢ to send the message (645 / 1000 = 0.645¢ = $0.00645). The query results for this metric are grouped by country or region, in ISO 3166-1 alpha-2 format. |
Campaign metrics
The following table lists and describes standard campaign metrics that you can query to
assess the performance of an individual campaign. To query data for these metrics, use the Campaign metrics resource of the Amazon Pinpoint API. The kpi-name column in the table indicates the value to use for the
kpi-name parameter in your query.
| Metric | Kpi-name | Description |
|---|---|---|
|
Bounce rate |
|
For all campaign runs, the percentage of email messages that couldn't be delivered to recipients. This metric measures only hard bounces—that is, messages in which the recipient's email address had a permanent issue that prevented the message from being delivered. This metric is calculated as the number of bounced email messages that were sent by all the campaign runs, divided by the number of email messages that were sent by all of those campaign runs. |
|
Bounce rate, grouped by campaign run |
|
For each campaign run, the percentage of email messages that couldn't be delivered to recipients. This metric measures only hard bounces—that is, messages in which the recipient's email address had a permanent issue that prevented the message from being delivered. This metric is calculated as the number of bounced email messages that were sent by a campaign run, divided by the number of email messages that were sent by the campaign run. The query results for this metric are grouped by campaign activity ID
( |
|
Delivery rate |
|
For all campaign runs, the percentage of messages that were delivered to recipients. This metric is calculated as the number of messages that were sent by all the campaign runs and delivered to recipients, divided by the number of messages that were sent by all of those campaign runs. |
|
Delivery rate, grouped by campaign run |
|
For each campaign run, the percentage of messages that were delivered to recipients. This metric is calculated as the number of messages that were sent by a campaign run and delivered to recipients, divided by the number of messages that were sent by the campaign run. The query results for this metric are grouped by campaign activity ID
( |
Delivery rate, grouped by date |
|
For all campaign runs, the percentage of messages that were delivered to recipients during each day in the specified date range. This metric is calculated as the number of messages that were sent by all the campaign runs and delivered to recipients, divided by the number of messages that were sent by all of those campaign runs, for each day in the specified date range. The query results for this metric are grouped by calendar day, in extended ISO 8601 format. |
Email open rate |
|
For all campaign runs, the percentage of email messages that were opened by recipients. This metric is calculated as the number of email messages that were sent by all the campaign runs and opened by recipients, divided by the number of email messages that were sent by all of those campaign runs and delivered to recipients. |
|
Email open rate, grouped by campaign run |
|
For each campaign run, the percentage of email messages that were opened by recipients. This metric is calculated as the number of email messages that were sent by a campaign run and opened by recipients, divided by the number of email messages that were sent by the campaign run and delivered to recipients. The query results for this metric are grouped by campaign activity ID
( |
Emails opened, grouped by campaign run |
|
For each campaign run, the number of email messages that were opened by recipients. The query results for this metric are grouped by campaign activity ID
( |
|
Endpoint deliveries |
|
For all campaign runs, the number of unique endpoints that messages were delivered to. |
|
Endpoint deliveries, grouped by campaign run |
|
For each campaign run, the number of unique endpoints that messages were delivered to. The query results for this metric are grouped by campaign activity ID
( |
|
Endpoint deliveries, grouped by date |
|
For all campaign runs, the number of unique endpoints that messages were delivered to, for each day in the specified date range. The query results for this metric are grouped by calendar day, in extended ISO 8601 format. |
|
Links clicked, grouped by campaign run |
|
For each campaign run, the number of times that recipients clicked links in the email message. If a single recipient clicked multiple links in the message, or clicked the same link more than once, each click is included in the count. The query results for this metric are grouped by campaign activity ID
( |
|
Messages delivered, grouped by campaign run |
|
For each campaign run, the number of messages that were delivered to recipients. This metric is calculated as the number of messages that were sent by a campaign run, minus the number of messages that couldn't be delivered to recipients of the run due to a hard bounce. The query results for this metric are grouped by campaign activity ID
( |
|
Messages sent, grouped by campaign run |
|
For each campaign run, the number of messages that were sent. The query results for this metric are grouped by campaign activity ID
( |
|
Push open rate |
|
For all campaign runs, the percentage of push notifications that were opened by recipients. This metric is calculated as the number of push notifications that were sent by all the campaign runs and opened by recipients, divided by the number of push notifications that were sent by all of those campaign runs and delivered to recipients. |
Push open rate, grouped by campaign run |
|
For each campaign run, the percentage of push notifications that were opened by recipients. This metric is calculated as the number of push notifications that were sent by a campaign run and opened by recipients, divided by the number of push notifications that were sent by the campaign run and delivered to recipients. The query results for this metric are grouped by campaign activity ID
( |
Total push opened, grouped by campaign run |
|
For each campaign run, the number of push notifications that were opened by recipients. The query results for this metric are grouped by campaign activity ID
( |
| Total SMS spend | sms-spend |
For all campaigns, the total amount of money, in milicents, spent on sending SMS. |
Journey engagement metrics
The following table lists and describes standard journey engagement metrics that you can
query to monitor trends for all the email messages that were sent by an Amazon Pinpoint journey. To query
data for these metrics, use the Journey
engagement metrics resource of the Amazon Pinpoint API. The kpi-name column in the table indicates the value to use for the
kpi-name parameter in a query.
| Metric | Kpi-name | Description |
|---|---|---|
Clicks |
|
The number of times that participants clicked links in the messages. If a single participant clicked multiple links in a message, or clicked the same link more than once, each click is included in the count. |
Clicks, grouped by activity |
|
For each activity in the journey, the number of times that participants clicked links in the messages. If a single participant clicked multiple links in a message, or clicked the same link more than once, each click is included in the count. The query results for this metric are grouped by activity ID
( |
Complaints |
|
The number of messages that were reported by participants as unsolicited or unwanted email. |
Complaints, grouped by activity |
|
For each activity in the journey, the number of messages that were reported by participants as unsolicited or unwanted email. The query results for this metric
are grouped by activity ID ( |
Deliveries |
|
The number of messages that were delivered to participants. This metric is calculated as the number of messages that were sent, minus the number of messages that couldn't be delivered due to a soft or hard bounce, or because they were rejected. |
Deliveries, grouped by activity |
|
For each activity in the journey, the number of messages that were delivered to participants. This metric is calculated as the number of messages that were sent, minus the number of messages that couldn't be delivered due to a soft or hard bounce, or because they were rejected, for each activity in the journey. The query results for this metric are grouped by activity ID
( |
Hard bounces |
|
The number of messages that couldn't be delivered to participants due to a hard bounce. A hard bounce occurs if a persistent issue prevents a message from being delivered—for example, if a participant's email address doesn't exist. |
Hard bounces, grouped by activity |
|
For each activity in the journey, the number of messages that couldn't be delivered to participants due to a hard bounce. A hard bounce occurs if a persistent issue prevents a message from being delivered—for example, if a participant's email address doesn't exist. The query results for this metric are grouped by activity ID
( |
Opens |
|
The number of messages that were opened by participants. |
Opens, grouped by activity |
|
For each activity in the journey, the number of messages that were opened by participants. The query results for this metric are grouped by activity ID
( |
Rejections |
|
The number of messages that weren't sent to participants because they were rejected. A message is rejected if Amazon Pinpoint determines that the message contains malware. Amazon Pinpoint doesn't attempt to send rejected messages. |
Rejections, grouped by activity |
|
For each activity in the journey, the number of messages that weren't sent to participants because they were rejected. A message is rejected if Amazon Pinpoint determines that the message contains malware. Amazon Pinpoint doesn't attempt to send rejected messages. The query results for this metric are grouped by activity ID
( |
| Sends |
|
The number of messages that were sent. |
Sends, grouped by activity |
|
For each activity in the journey, the number of messages that were sent. The query results for this metric are grouped by activity ID
( |
Soft bounces |
|
The number of messages that couldn't be delivered to participants due to a soft bounce. A soft bounce occurs if a temporary issue prevents a message from being delivered—for example, if a participant's inbox is full or the receiving server is temporarily unavailable. |
Soft bounces, grouped by activity |
|
For each activity in the journey, the number of messages that couldn't be delivered to participants due to a soft bounce. A soft bounce occurs if a temporary issue prevents a message from being delivered—for example, if a participant's inbox is full or the receiving server is temporarily unavailable. The query results for this metric are grouped by activity ID
( |
Unsubscribes |
|
The number of times that participants clicked unsubscribe links in the messages. If a single participant clicked the same unsubscribe link more than once, each click is included in the count. |
Unsubscribes, grouped by activity |
|
For each activity in the journey, the number of times that participants clicked unsubscribe links in the messages. If a single participant clicked the same unsubscribe link more than once, each click is included in the count. The query results for this metric are grouped by activity ID
( |
Journey execution metrics
The following table lists and describes standard execution metrics that you can query to assess the status of participants in an Amazon Pinpoint journey. To query data for these metrics, use the Journey execution metrics resource of the Amazon Pinpoint API. The Field column in the table identifies the name of the field that appears in the query results for each metric.
| Metric | Field | Description |
|---|---|---|
|
Active participants |
|
The number of participants who are actively proceeding through the activities in the journey. This metric is calculated as the number of participants who started the journey, minus the number of participants who left the journey and the number of participants who were removed from the journey. |
|
Participant cancellations |
|
The number of participants who didn't complete the journey because the journey was cancelled. |
|
Participant departures |
|
The number of participants who left the journey. |
|
Participant entries |
|
The number of participants who started the journey. |
|
Participant exceptions, reentry limits |
|
The number of participants who didn't complete the journey because they would have exceeded the maximum number of times that a single participant can re-enter the journey. |
|
Participant exceptions, rejections |
|
The number of participants who can't start the journey because they are already active participants in the journey. A participant is rejected if they start a journey and you subsequently update their endpoint definition in a way that affects their inclusion in a segment (based on segment criteria) or the journey (based on activity conditions). |
Journey activity execution metrics
The following table lists and describes standard execution metrics that you can query to assess the status of participants in each type of individual activity for an Amazon Pinpoint journey. To query data for these metrics, use the Journey activity execution metrics resource of the Amazon Pinpoint API. The Metrics column in the table lists the fields that appear in the query results for each type of activity. It also provides a brief description of each field.
| Activity type | Metrics |
|---|---|
|
Yes/No split ( |
The metrics are:
Additional metrics are available for the activity on each path. For information about those metrics, see the row in this table for that type of activity. |
|
Holdout ( |
The metrics are:
|
Email ( |
The metrics are:
|
Multivariate split ( |
For each path of the activity, the number of participants who proceeded to the activity on the path. The query results for this metric are grouped by path,
Additional metrics are available for the activity on each path. For information about those metrics, see the row in this table for that type of activity. |
Random split ( |
For each path of the activity, the number of participants who proceeded to the activity on the path. The query results for this metric are grouped by path,
Additional metrics are available for the activity on each path. For information about those metrics, see the row in this table for that type of activity. |
Wait ( |
The metrics are:
|
Contact Center ( |
The metrics are:
|
Journey and campaign execution metrics
You can query standard execution metrics to assess the status of participants in each type of individual activity for an Amazon Pinpoint journey or campaign. To query data for these metrics, use the Journey run activity execution metrics or Campaign Metrics resource of the Amazon Pinpoint API. The following table lists the fields that appear in the query results for each type of activity.
| Metric Name | Applies to Journeys, Campaigns, or Both | Description |
|---|---|---|
| ENDPOINT_PRODUCED | Both | The number of endpoints initially produced from the segment or event before any filtering. |
| ENDPOINTS_FROM_USER | Both | If the customer has a user-id only segment, then all the endpoints of those users will be added. This metric measures the number of endpoints added in this way. |
| ENDPOINT_OPT_OUT | Both | The endpoint was opted out and didn't enter the campaign or journey. |
| ENDPOINT_INACTIVE | Both | The endpoint was inactive and didn't enter the campaign or journey. |
| FILTERED_OUT_BY_SEGMENT | Both | Endpoint didn't match segment filters and didn't enter the campaign or journey. |
| ENDPOINT_MISSING_ADDRESS | Both | Endpoint was missing an address and didn't enter the campaign or journey. |
| ENDPOINT_MISSING_CHANNEL | Both | Endpoint was missing a channel and didn't enter the campaign or journey. |
| ENDPOINT_MISSING_TIMEZONE | Both | Endpoint was missing a value for timezone and was filtered out. This only happens when a timezone value is required. |
| ENDPOINT_TIMEZONE_MISMATCH | Both | Endpoint was in a timezone that wasn't included in the execution at that time. |
| ENDPOINT_CHANNEL_MISMATCH | Campaigns | The campaign doesn't have a message configured for this endpoint's channel type. |
| DUPLICATE_ENDPOINT | Both | Duplicate endpoints were found and de-duped. |
| DUPLICATE_USER | Both | Duplicate users were found and de-duped from a user-id only segment. If they have the same user id, a metric of 1 will be emitted. |
| PAUSED | Journeys | Removed from execution because the journey was paused. |
| ENDED | Journeys | Removed from execution because the journey was ended. |
| TREATMENT_HOLDOUT | Campaigns | This is emitted in A/B campaigns, for endpoints whose cohorts don’t match the current treatment. For example in a 50/50 A/B split, 50% of the endpoints will emit this metric for each treatment |
| ENDPOINT_ESTIMATED_TIMEZONE | Journeys | Time zone estimation was able to estimate a time zone for the endpoint. |
