From a913abd7a62b7a1cc97f6fc82ad4fb92be2dfefa Mon Sep 17 00:00:00 2001 From: Lydia Xie Date: Fri, 13 Jan 2023 14:57:03 -0800 Subject: [PATCH 1/3] Data doc edits pt. 3 --- _docs/_api/data_retention.md | 4 +++- _docs/_user_guide/onboarding_with_braze/data_points.md | 4 ++-- 2 files changed, 5 insertions(+), 3 deletions(-) diff --git a/_docs/_api/data_retention.md b/_docs/_api/data_retention.md index a0f3729dfec..4c7fc801c21 100644 --- a/_docs/_api/data_retention.md +++ b/_docs/_api/data_retention.md @@ -36,6 +36,8 @@ A User may have multiple profiles, and you may need to delete multiple profiles ## Data Retention Handled by Braze +The below retention policies pertain to Braze's compliance with GDPR and privacy regulations and are regarding transient data storage as it passes through our internal systems. These retention policies do not impact the Braze Services and are informational for your legal and privacy teams. + #### Braze Database: Automatic Archiving/Deletion of Churned Users Each week, Braze runs a process to remove Inactive and Dormant Users from the Braze Services. In general, these are users who are not reachable (e.g., have no email address, no phone number, no push token, do not use your apps or visit your websites), have had no activity recorded on their user profile, and have not been messaged or engaged with using Braze. This is done to adhere to GDPR principles and best practices. You can read more about this process on our [user archival definitions]({{site.baseurl}}/user_guide/data_and_analytics/user_data_collection/user_archival/) page. @@ -44,7 +46,7 @@ Each week, Braze runs a process to remove Inactive and Dormant Users from the Br #### Braze Servers: Short-term Retention for Recovery Purposes -Data sent from the Braze Services to Braze’s Snowflake Data Lake via Braze servers is retained in such Braze servers for up to 90 days for recovery purposes. +Data sent by Braze to certain subprocessors may still exist in Braze's internal systems for up to 90 days. #### Braze Data Lake Data Retention diff --git a/_docs/_user_guide/onboarding_with_braze/data_points.md b/_docs/_user_guide/onboarding_with_braze/data_points.md index 7b4b0fd1d83..2c99566098e 100644 --- a/_docs/_user_guide/onboarding_with_braze/data_points.md +++ b/_docs/_user_guide/onboarding_with_braze/data_points.md @@ -11,9 +11,9 @@ description: "This reference article outlines what Data Points are at Braze and 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. As such, data points are Braze’s way of defining a billing and pricing structure, based on pieces of information logged against user profiles. See the [Consumption count](#consumption-count) section of this article to understand what data counts toward your data point allocation. -Our Customer Success team can help recommend data best practices to fit your specific needs. You can find a more detailed breakdown of this definition in your Braze contract. +Our Customer Success team can help recommend data best practices in order to make your costs/entitlements highly predictable by accounting for seasonality and sized correctly with plenty of headroom and options for flexibility. 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. 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. For clarity, the setting of an End User’s profile information at one point in time shall count as a single Data Point. +"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. Your contracted MAU volume determines your allotment of Data Points, with flexibility as to the appropriate ratio based on your business and/or user needs. 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. For clarity, the setting of an End User’s profile information at one point in time shall count as a single Data Point. ## Management and usage From 71e041f5ba8eb838653d25eb4370144ae9fc1239 Mon Sep 17 00:00:00 2001 From: Lydia Xie Date: Fri, 13 Jan 2023 16:16:42 -0800 Subject: [PATCH 2/3] Edit for data points usage in CSV imports --- _docs/_user_guide/onboarding_with_braze/data_points.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_docs/_user_guide/onboarding_with_braze/data_points.md b/_docs/_user_guide/onboarding_with_braze/data_points.md index 2c99566098e..cd65c8d4169 100644 --- a/_docs/_user_guide/onboarding_with_braze/data_points.md +++ b/_docs/_user_guide/onboarding_with_braze/data_points.md @@ -126,7 +126,7 @@ table td { #### CSV -Custom attributes uploaded via CSV count towards your data points, however CSV imports for segmentation purposes (imports made with `external_id` as the only field) will not consume data points. +Custom attributes uploaded via CSV count towards 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. #### Arrays From 5b60e42a86a897624c96b1fe852b22028bfcc552 Mon Sep 17 00:00:00 2001 From: Lydia Xie Date: Tue, 17 Jan 2023 08:28:13 -0800 Subject: [PATCH 3/3] Data point consumption for user imports --- .../data_and_analytics/user_data_collection/user_import.md | 1 + 1 file changed, 1 insertion(+) diff --git a/_docs/_user_guide/data_and_analytics/user_data_collection/user_import.md b/_docs/_user_guide/data_and_analytics/user_data_collection/user_import.md index 334229cb976..9e3071d9b5e 100644 --- a/_docs/_user_guide/data_and_analytics/user_data_collection/user_import.md +++ b/_docs/_user_guide/data_and_analytics/user_data_collection/user_import.md @@ -93,6 +93,7 @@ Braze accepts user data in the standard CSV format from files up to 500MB in siz Each piece of customer data imported via CSV will overwrite the existing value on user profiles and will count as a data point, except for external IDs and blank values. - External IDs uploaded via CSV will not consume data points. If you are uploading a CSV to segment existing Braze users by uploading only external IDs, this can be done without consuming data points. If you were to add additional data like user email or phone number in your import, that would overwrite existing user data, consuming your data points. + - 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. - Blank values will not overwrite existing values on the user profile, and you do not need to include all existing user attributes in your CSV file. - Updating `email_subscribe`, `push_subscribe`, `subscription_group_id`, or `subscription_state` will not count towards data point consumption.