diff --git a/_docs/_user_guide/data_and_analytics.md b/_docs/_user_guide/data_and_analytics.md index edd1807c1aa..339ade72ab9 100644 --- a/_docs/_user_guide/data_and_analytics.md +++ b/_docs/_user_guide/data_and_analytics.md @@ -5,7 +5,7 @@ page_order: 3 layout: dev_guide guide_top_header: "Data & Analytics" -guide_top_text: "Braze offers a breadth of metrics to measure your campaigns' performance. We also provide multiple reporting and tracking capabilities to ensure you get the numbers you need.

You can also leverage Braze data to augment BI and analytics efforts in other best-in-class reporting platforms using Currents, a data streaming export tool which enables your team to act on large amounts of granular customer data." +guide_top_text: "Braze offers a breadth of metrics to measure your campaign performance. We also provide multiple reporting and tracking capabilities to get you the numbers you need.

Leverage Braze data to supplement your business intelligence (BI) and analytics efforts in other best-in-class reporting platforms using Currents, a data streaming export tool that your team can use to act on large amounts of granular customer data." description: "Braze offers a wide breadth of metrics for you to use when measuring the success of your campaigns. We also provide multiple reports and tracking capabilities to ensure you get the numbers you need." guide_featured_title: "Topics" diff --git a/_docs/_user_guide/data_and_analytics/creating_a_formula.md b/_docs/_user_guide/data_and_analytics/creating_a_formula.md index 7574bd6e487..2282f2ad6ca 100644 --- a/_docs/_user_guide/data_and_analytics/creating_a_formula.md +++ b/_docs/_user_guide/data_and_analytics/creating_a_formula.md @@ -9,33 +9,33 @@ tool: Reports --- # Creating a formula -> When viewing analytics in Braze, you can combine several data points together to get valuable insights into your user data. These are referred to as formulas. Formulas allow you to normalize your time series data based on your total number of monthly active users (MAU) and daily active users (DAU). They also help you to easily understand complex relationships that exist in your data. +> When viewing analytics in Braze, you can combine multiple data points to get valuable insights into your user data. These are referred to as formulas. Use formulas to normalize your time series data based on your total number of monthly active users (MAU) and daily active users (DAU). -For example, you can compare how many custom events were completed by daily active users that qualify for a particular segment versus the general population (or against another segment). +Formulas help you understand complex relationships that exist in your data. For example, you can compare how many custom events were completed by daily active users that qualify for a particular segment versus the general population (or against another segment). ## Use cases -Formulas, especially when combined with custom events, allow you to better understand user behaviors within your app. Formulas can also lend deeper insight into segment purchasing patterns, even if your company uses paid media in conjunction with Braze, such as Google Ads or TV. +Formulas, especially when combined with custom events, can help you understand user behaviors within your app. Formulas can also lend deeper insight into segment purchasing patterns, even if your company uses paid media in conjunction with Braze, such as Google Ads or TV. The following are some examples of the kinds of behavior patterns that can be detected using formulas: -- **Ride-sharing apps:** If you have a custom event for when the user cancels a ride, configuring a function for Canceled Rides / DAU can be used to find if certain user segments tend to cancel more rides than others. -- **Ecommerce apps:** By configuring a function for purchases of a certain product ID / MAU, you can, compare the popularity of a recently promoted product between segments, even if all of the promotions couldn't be tracked using Braze. +- **Ride-sharing apps:** If you have a custom event for when the user cancels a ride, you can configure a function for Canceled Rides / DAU to find if certain user segments tend to cancel more rides than others. +- **Ecommerce apps:** By configuring a function for purchases of a certain product ID / MAU, you can compare the popularity of a recently promoted product between segments, even if all the promotions couldn't be tracked using Braze. - **Media apps using ads:** If the users' experience is interrupted by ads between video or audio clips, recording mid-ad exits as a custom event and calculating the ratio of mid-ad exits / DAU can help find the best segments to target with a campaign for ad-free premium subscriptions. ## Creating formulas -Formulas can be accessed in the statistics panels on the [Home][9], [Revenue][10] and [Custom Events][11] pages in the dashboard. To view this panel, change the **View Statistics For** dropdown to **KPI Formulas**. +Formulas can be accessed in the statistics panels on the [Home][9], [Revenue Report][10], and [Custom Events Report][11] pages in the dashboard. To view this panel, go to the **Performance Over Time** chart, change the **Statistics For** dropdown to **KPI Formulas**, and then select at least one KPI formula to populate the chart. ![View statistics for KPI formulas in the Braze dashboard][16] To create a new formula: -1. Navigate to the appropriate dashboard (Home, Revenue, or Custom Events). -2. Click **Manage KPI Formulas**. +1. Go to the appropriate dashboard (**Home**, **Revenue Report**, or **Custom Events Report**). +2. Select **Manage KPI Formulas**. 3. Enter a name for your formula. 4. Select the relevant numerators and denominators. -5. Click **Save**. +5. Select **Save**. ## Available numerators and denominators diff --git a/_docs/_user_guide/data_and_analytics/data_points.md b/_docs/_user_guide/data_and_analytics/data_points.md index bef47f508de..1021e818e6c 100644 --- a/_docs/_user_guide/data_and_analytics/data_points.md +++ b/_docs/_user_guide/data_and_analytics/data_points.md @@ -3,33 +3,37 @@ nav_title: Data Points article_title: Data Points Overview page_order: 0 page_type: reference -description: "This reference article outlines what Data Points are at Braze and how you can be aware of their usage." +description: "This reference article outlines what data points are at Braze and how you can be aware of their usage." search_rank: 6 --- # Data points -At Braze, data means action: each piece of data that arrives in Braze updates segment membership, can trigger and cancel messaging, is immediately available for messaging personalization, and more. Data points help you define the most impactful information for your business. By thoughtfully considering what information to track, you ensure that you're targeting the highest-impact data for your users' experience. +> At Braze, data means action: each piece of data that arrives in Braze updates segment membership, can trigger and cancel messaging, is immediately available for messaging personalization, and more. Data points help you define the most impactful information for your business. By thoughtfully considering what information to track, you ensure that you're targeting the highest-impact data for your users' experience. Data points define a billing and pricing structure based on information logged against user profiles. Our Customer Success team can help recommend data best practices to fit your needs. You can find a more detailed breakdown of this definition in your Braze contract. -> "Data points" shall refer to a billable unit of use of the Braze Services, measured by a session start, session end, custom event, or purchase recorded, as well as any attribute set on an end user profile. For clarity, each one of the above-mentioned data (such as session start, session end, custom event, or purchase recorded, as well as any attribute) set to an end user’s profile at one point in time shall each count as a single data point.

Data and events collected by default by the Braze Services, including, for example, push tokens, device information, and all campaign engagement tracking events, such as email opens and push notification clicks, are *not* counted as data points. +## Definition + +"Data points" shall refer to a billable unit of use of the Braze Services, measured by a session start, session end, custom event, or purchase recorded, as well as any attribute set on an end user profile. For clarity, each one of the above-mentioned data (such as session start, session end, custom event, or purchase recorded, as well as any attribute) set to an end user’s profile at one point in time shall each count as a single data point. + +Data and events collected by default by the Braze Services, including, for example, push tokens, device information, and all campaign engagement tracking events, such as email opens and push notification clicks, are *not* counted as data points. See this article's [Consumption count](#consumption-count) section to understand what data counts toward your data point allocation. -## Management and usage +## Viewing data point usage To view your data point usage, go to **Settings** > **Billing** and select the **Total Data Points Usage** tab. {% alert note %} -If you are using the [older navigation]({{site.baseurl}}/navigation), you can find this page by selecting your account icon > **Subscriptions and Usage** > **Total Data Points Usage**. +If you're using the [older navigation]({{site.baseurl}}/navigation), you can find this page by selecting your account icon > **Subscriptions and Usage** > **Total Data Points Usage**. {% endalert %} For more information on the data point dashboard components, refer to [Billing]({{site.baseurl}}/user_guide/onboarding_with_braze/subscription_and_usage/). {% alert tip %} **Don't waste data points. Only update changing data!**

-To ensure you minimize data point consumption, we recommend setting up a program to prevent sending the same unchanging data and only passing new and relevant data to Braze. Braze will work with you to establish this best practice during onboarding. +To minimize data point consumption, we recommend setting up a program to prevent sending the same unchanging data and only passing new and relevant data to Braze. Braze will work with you to establish this best practice during onboarding. {% endalert %} ## Consumption count @@ -57,7 +61,7 @@ If you set the whole array at once, it will count as a single data point. As suc #### CSV -Custom attributes uploaded via CSV count toward your data points. However, CSV imports for segmentation purposes (imports made with `external_id`, `braze_id`, or `user_alias_name` as the only field) will not consume data points. +Custom attributes uploaded through CSV import count toward your data points. However, CSV imports for segmentation purposes (imports made with `external_id`, `braze_id`, or `user_alias_name` as the only field) will not consume data points. Also, as subscription state changes do not consume data points, updating the `email_subscribe`, `push_subscribe`, `subscription_group_id`, or `subscription_state` fields in your CSV file will not incur charges. @@ -66,7 +70,7 @@ Also, as subscription state changes do not consume data points, updating the `em {% tabs %} {% tab Non-billable %} -#### Non-billable data points (out of the box) +#### Non-billable data points (default)
diff --git a/_docs/_user_guide/data_and_analytics/report_metrics.md b/_docs/_user_guide/data_and_analytics/report_metrics.md index 3e0d42c8c17..2a6e890cc4f 100644 --- a/_docs/_user_guide/data_and_analytics/report_metrics.md +++ b/_docs/_user_guide/data_and_analytics/report_metrics.md @@ -36,7 +36,7 @@ The total number of users who clicked into the AMP version of your AMP HTML Emai All {% endapitags %} -Percentage of users who received a particular message. This number is received from Braze. +The percentage of users who received a particular message. This number is received from Braze. {% endapi %} @@ -48,7 +48,7 @@ Percentage of users who received a particular message. This number is received f Email, Web Push, iOS Push {% endapitags %} -The total number of messages that were unsuccessful. This could occur because there is not a valid push token, the email addresses were incorrect or deactivated, or the user unsubscribed after the campaign was launched. An email bounce for customers using SendGrid consists of hard bounces, spam, and emails sent to invalid addresses. +The total number of unsuccessful messages. This could occur because there isn't a valid push token, the email addresses were incorrect or deactivated, or the user unsubscribed after the campaign was launched. An email bounce for customers using SendGrid consists of hard bounces, spam, and emails sent to invalid addresses. Calculation: (Bounces) / (Sends) @@ -93,7 +93,7 @@ Occurs when someone clicks on any of the following in-app message types: In-App Message {% endapitags %} -Total number of clicks on Button 1 of the message. +The total number of clicks on Button 1 of the message. Calculation: (Button 1 Clicks) / (Impressions) @@ -107,7 +107,7 @@ Total number of clicks on Button 1 of the message. In-App Message {% endapitags %} -Total number of clicks on Button 2 of the message. +The total number of clicks on Button 2 of the message. Calculation: (Button 2 Clicks) / (Impressions) @@ -121,7 +121,7 @@ Total number of clicks on Button 2 of the message. In-App Message {% endapitags %} -Total number of choices selected when the user clicks the submit button on the survey question page of a [simple survey]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/templates/simple_survey/). +The total number of choices selected when the user clicks the submit button on the survey question page of a [simple survey]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/templates/simple_survey/). {% endapi %} @@ -173,7 +173,7 @@ The percentage of confidence that a certain variant of a message is outperformin In-App Message {% endapitags %} -Total clicks on the call to action button on the confirmation page of a [simple survey]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/templates/simple_survey/). +The total clicks on the call to action button on the confirmation page of a [simple survey]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/templates/simple_survey/). {% endapi %} @@ -185,7 +185,7 @@ Total clicks on the call to action button on the confirmation page of a [simple In-App Message {% endapitags %} -Total clicks on the close (x) button on the confirmation page of a [simple survey]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/templates/simple_survey/). +The total clicks on the close (x) button on the confirmation page of a [simple survey]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/templates/simple_survey/). {% endapi %} @@ -197,7 +197,7 @@ Total clicks on the close (x) button on the confirmation page of a [simple surve Content Cards, Email, In-App Message, Web Push, iOS Push, Android Push, Webhook, SMS {% endapitags %} -Additional conversion events added after the Primary Conversion Event. The number of times a defined event occurred after interacting with or viewing a received message from a Braze campaign. This defined event is determined by the marketer when building the campaign. For Email, Push and Webhooks, we start tracking conversions after the initial send. For Content Cards and In-App Messages, this count begins when they view a Content Card or Message for the first time. +Additional conversion events added after the primary conversion event. The number of times a defined event occurred after interacting with or viewing a received message from a Braze campaign.

This defined event is determined by the marketer when building the campaign. For email, push, and webhooks, we start tracking conversions after the initial send. For Content Cards and in-app messages, this count begins when they view a Content Card or message for the first time. {% endapi %} @@ -235,7 +235,7 @@ The number of days after receiving the message during which user actions are tra Email, Web Push, iOS Push, Android Push, WhatsApp {% endapitags %} -The total number of message requests that are accepted by the receiving server. This does not mean the message was delivered to a device, only that the message was accepted by the server. +The total number of message requests that are accepted by the receiving server. This doesn't mean the message was delivered to a device, only that the message was accepted by the server. Calculation: Count @@ -289,7 +289,7 @@ The number of errors returned by webhook events (incremented during the sending WhatsApp {% endapitags %} -The WhatsApp message could not send because the Internet Service Provider returned a hard bounce. A hard bounce signifies a permanent deliverability failure. +The WhatsApp message couldn't send because the internet service provider returned a hard bounce. A hard bounce signifies a permanent deliverability failure. {% endapi %} @@ -315,7 +315,7 @@ The total number (and percentage) of users who opened the app after the push not Email {% endapitags %} -The number of requests that were temporarily rejected, by the receiving server, but still attempted for re-delivery by the ESP. The ESP will retry delivery until a timeout period is reached (typically after 72 hours). +The number of requests that were temporarily rejected, by the receiving server, but still attempted for re-delivery by the email service provider (ESP). The ESP will retry delivery until a timeout period is reached (typically after 72 hours). {% endapi %} @@ -327,7 +327,7 @@ The number of requests that were temporarily rejected, by the receiving server, Content Cards, Email, In-App Message, Web Push, iOS Push, Android Push, Webhook, SMS, WhatsApp {% endapitags %} -The number of times a defined event occurred after interacting with or viewing a received message from a Braze campaign. This defined event is determined by the marketer when building the campaign. For Email, Push, and Webhooks, we start tracking conversions after the initial send. For Content Cards and In-App Messages, this count begins when they view a Content Card or Message for the first time. +The number of times a defined event occurred after interacting with or viewing a received message from a Braze campaign. This defined event is determined by the marketer when building the campaign.

For email, push, and webhooks, we start tracking conversions after the initial send. For Content Cards and in-app messages, this count begins when they view a Content Card or message for the first time. {% endapi %} @@ -339,7 +339,7 @@ The number of times a defined event occurred after interacting with or viewing a WhatsApp {% endapitags %} -When a WhatsApp message is read by the end user. The end user's read receipts must be "On" for Braze to track reads. +When the user reads the WhatsApp message. The user's read receipts must be "On" for Braze to track reads. {% endapi %} @@ -355,7 +355,7 @@ Email, Content Cards, In-App Message, Web Push, iOS Push, Android Push, SMS, Wha - Push: Received when messages are sent from the Braze server to the push provider. - Email: Received when messages are sent from the Braze server to the email service provider. - SMS/MMS: "Delivered" after the SMS provider receives confirmation from the upstream carrier and destination device. -- In-App Message: Received at the time of display based on the trigger action defined. +- In-app message: Received at the time of display based on the trigger action defined. - WhatsApp: Received at the time of display based on the trigger action defined. {% endapi %} @@ -368,7 +368,7 @@ Email, Content Cards, In-App Message, Web Push, iOS Push, Android Push, SMS, Wha SMS {% endapitags %} -The SMS has been rejected by the carrier. This can happen for a number of reasons, including carrier content filtering, availability of the destination device, the phone number is no longer in service, etc. As a Braze customer, rejections are charged toward your SMS allotment. +The SMS has been rejected by the carrier. This can happen for several reasons, including carrier content filtering, availability of the destination device, the phone number is no longer in service, and similar. As a Braze customer, rejections are charged toward your SMS allotment. Calculation: Count @@ -382,7 +382,7 @@ The SMS has been rejected by the carrier. This can happen for a number of reason Content Cards, Email, In-App Message, Web Push, iOS Push, Android Push, Webhook, SMS, WhatsApp, LINE {% endapitags %} -*Sends*, or *Messages Sent*, is the total number of messages sent in a campaign. Upon launching a scheduled campaign, this metric will include all messages sent, regardless of whether they have been sent out yet due to rate limiting. This does not mean the message was received or delivered to a device, only that the message was sent. This metric is provided by Braze. +*Sends*, or *Messages Sent*, is the total number of messages sent in a campaign. After launching a scheduled campaign, this metric will include all messages sent, regardless of whether they have been sent out yet due to rate limiting. This doesn't mean the message was received or delivered to a device, only that the message was sent. This metric is provided by Braze. {% alert tip %} For Content Cards, this metric is calculated differently depending on what you selected for **Card creation**. See [Card creation]({{site.baseurl}}/user_guide/message_building_by_channel/content_cards/create/card_creation/) for details. @@ -404,7 +404,7 @@ SMS *Sends to Carrier* is deprecated, but will continue to be supported for users that already have it. {% endalert %} -This stat is the sum of Confirmed Deliveries, Rejections, and Sends where delivery or rejection was not confirmed by the carrier. There are instances where carriers do not provide delivery or rejected confirmation, as some carriers do not provide this confirmation or were unable to do so at the time of send. +The sum of Confirmed Deliveries, Rejections, and Sends where delivery or rejection wasn't confirmed by the carrier. This includes instances where carriers don't provide delivery or rejected confirmation, as some carriers don't provide this confirmation or can't do so at the time of send. Calculation: Count @@ -432,7 +432,7 @@ The total number of emails delivered that were marked as "spam." In-App Message {% endapitags %} -Total clicks on the close (x) button on the survey question page of a [simple survey]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/templates/simple_survey/). +The total clicks on the close (x) button on the survey question page of a [simple survey]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/templates/simple_survey/). {% endapi %} @@ -444,7 +444,7 @@ Total clicks on the close (x) button on the survey question page of a [simple su In-App Message {% endapitags %} -Total clicks on the submit button of a [simple survey]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/templates/simple_survey/). +The total clicks on the submit button of a [simple survey]({{site.baseurl}}/user_guide/message_building_by_channel/in-app_messages/templates/simple_survey/). {% endapi %} @@ -543,7 +543,7 @@ The total revenue in dollars from campaign recipients within the set primary con Email, Content Cards, LINE {% endapitags %} -Distinct number of recipients who have clicked within a message at least once. This is tracked over a 7-day period for Email. Note that clicks on Braze-provided unsubscribe links are counted as unique clicks. +The distinct number of recipients who have clicked within a message at least once. This is tracked over a 7-day period for Email. This includes clicks on Braze-provided unsubscribe links. For LINE, this is tracked after a minimum threshold of 20 messages per day has been reached. @@ -595,7 +595,7 @@ The total number of users who received and viewed a given in-app message or card Email, LINE {% endapitags %} -For emails, this is the total number of delivered emails that have been opened by a single user at least once. This is tracked over a 7-day period for Email. For LINE, this is tracked after a minimum threshold of 20 messages per day has been reached. +This is the total number of delivered emails that have been opened by a single user at least once and are tracked over a 7-day period. For LINE, this is tracked after a minimum threshold of 20 messages per day has been reached. Calculation: (Unique Opens) / (Deliveries) @@ -609,7 +609,7 @@ For emails, this is the total number of delivered emails that have been opened b All {% endapitags %} -Unique Daily Recipients. The number of users who received a particular message in a day. This number is received from Braze. +The number of unique daily recipients, or users who received a particular message in a day. This number is received from Braze. Calculation: Count diff --git a/_docs/_user_guide/personalization_and_dynamic_content/catalogs.md b/_docs/_user_guide/personalization_and_dynamic_content/catalogs.md index 84950268e9f..3c1bda13bad 100644 --- a/_docs/_user_guide/personalization_and_dynamic_content/catalogs.md +++ b/_docs/_user_guide/personalization_and_dynamic_content/catalogs.md @@ -5,9 +5,9 @@ page_order: 6 layout: dev_guide guide_top_header: "Catalogs" -guide_top_text: "Catalogs allow you to access data from imported CSV files and API endpoints to enrich your messages, similar to how you'd access custom attributes or custom event properties through Liquid." +guide_top_text: "Catalogs access data from imported CSV files and API endpoints to enrich your messages, similar to how you'd access custom attributes or custom event properties through Liquid." -description: "This landing page is home to Catalogs. With catalogs and filtered sets, you can leverage non-user data in your Braze campaigns to send personalized messages." +description: "This landing page is home to catalogs. Use catalogs and filtered sets to leverage non-user data in your Braze campaigns to send personalized messages." guide_featured_title: "Section articles" guide_featured_list: diff --git a/assets/img_archive/kpi_forms.png b/assets/img_archive/kpi_forms.png index 14fa1bdc27e..0aad495da8a 100644 Binary files a/assets/img_archive/kpi_forms.png and b/assets/img_archive/kpi_forms.png differ