diff --git a/_docs/_user_guide/data_and_analytics/user_data_collection.md b/_docs/_user_guide/data_and_analytics/user_data_collection.md index 40c5a1a1ef1..245c010c17b 100644 --- a/_docs/_user_guide/data_and_analytics/user_data_collection.md +++ b/_docs/_user_guide/data_and_analytics/user_data_collection.md @@ -26,6 +26,9 @@ guide_featured_list: - name: User Import link: /docs/user_guide/data_and_analytics/user_data_collection/user_import/ image: /assets/img/braze_icons/users-01.svg + - name: Anonymous Users + link: /docs/user_guide/data_and_analytics/user_data_collection/anonymous_users/ + image: /assets/img/braze_icons/user-circle.svg - name: User Language Codes link: /docs/user_guide/data_and_analytics/user_data_collection/language_codes/ image: /assets/img/braze_icons/globe-04.svg diff --git a/_docs/_user_guide/data_and_analytics/user_data_collection/anonymous_users.md b/_docs/_user_guide/data_and_analytics/user_data_collection/anonymous_users.md new file mode 100644 index 00000000000..1f276fba996 --- /dev/null +++ b/_docs/_user_guide/data_and_analytics/user_data_collection/anonymous_users.md @@ -0,0 +1,75 @@ +--- +nav_title: Anonymous users +article_title: Getting Started: Anonymous Users +page_order: 0 +page_type: reference +description: "This article provides an overview of anonymous users and user aliases, outlining their significance and how they can be leveraged in your messages." + +--- + +# Anonymous users + +> Users who visit your website or application without logging in, like a guest visitor, are recognized as anonymous users. These users don't have `external_ids`, which are used to update user profiles with the Braze API, but they still have [data points]({{site.baseurl}}/user_guide/data_and_analytics/data_points/) assigned to them and can be targeted in your segments. + +When an anonymous user visits your website or application, the Braze SDK creates and assigns them to an “anonymous” user profile. While the user browses, the SDK automatically captures data for their anonymous user profile, such as usage information, device information, and more if you’ve set up custom attributes and custom events. + +You can do the following with captured anonymous users: + +- Message users before they log in +- Collect a user’s profile before they log in, so you don’t miss out on relevant data +- Encourage profile completion with a message when a user only partially completes their profile +- Complete a user’s profile when they log in, so that you can cancel messaging on other platforms (such as not sending a “free shipping on 1st app order” message when the user already has made app orders) +- Engage with users who show an intent to exit by encouraging them to create a profile, checkout their cart, or take another action + +## Assigning user aliases + +Anonymous users don’t have `external_ids`, but you can assign anonymous user profiles with an alternative identifier: user aliases. This allows you to take the same actions on an anonymous user profile as if they were identified by `external_ids`. For example, you can use the Braze API to log events and attributes associated with anonymous users, and target those users in your messaging with the segmentation filter [External User ID is blank]({{site.baseurl}}/user_guide/engagement_tools/segments/segmentation_filters#external-user-id). + +## Merging anonymous users + +Sometimes anonymous user profiles are duplicates that have the same phone number or email address as other user profiles. One of the duplicates may even be an identified user profile. These duplicates can be merged into one user profile by using the [POST: Merge Users endpoint]({{site.baseurl}}/api/endpoints/user_data/post_users_merge/) or one of the merge tools on the Braze platform, such as [rules-based merging]({{site.baseurl}}/user_guide/engagement_tools/segments/user_profiles/duplicate_users/#rules-based-merging). + +## Use cases + +### Target anonymous users in your segment + +Because anonymous users don't have an `external_id`, you can target them in bulk by using the segmentation filter **External User ID is blank**. For further accuracy, you can add a custom attribute to the anonymous users you want to target and filter for that. + +Let's say you assign the custom attribute "is_lead_profile" to each anonymous user profile. You could target these profiles with one or both of these filters: + +- **External User ID is blank** +- "is_lead_profile" **is true** + +![Segment filters for a blank external user ID and a true "is_lead_profile" custom attribute.][1] + +### Capture checkout data from an anonymous user + +You can capture checkout data from an anonymous user (or guest visitor) by creating a user aliased profile during the checkout process. When an anonymous user checks out by using a web capture form, have an API call trigger to create a user aliased profile and log a purchase event. You'll then be able to update the created user profile through the Braze API. + +Here is an example payload that will generate when the web capture form is submitted: + +{% raw %} +```json +{ + "purchase":[ + { + "user_alias": {"alias_name": "Joedoe", "alias_label": "full_name"}, + "app_id": "11dk3k9d-2183-3948-k02b-kw3938109k12od", + "product_id": "jacket", + "currency": "USD", + "price": 80.00, + "time": "2025-01-05T19:20:30+01:00", + "properties": { + "color": "brown", + "monogram": "ABC", + "checkout_duration": 180, + "size": "Small", + "brand": "Natural Essence" + } + } + ] +} +``` +{% endraw %} + +[1]: {% image_buster /assets/img/getting_started/anonymous_users.png %} diff --git a/_docs/_user_guide/getting_started/users_segments.md b/_docs/_user_guide/getting_started/users_segments.md index 2c2424edd02..85866e14bf0 100644 --- a/_docs/_user_guide/getting_started/users_segments.md +++ b/_docs/_user_guide/getting_started/users_segments.md @@ -19,7 +19,7 @@ In Braze, information about your audience is stored in user profiles. A [user pr By understanding user profiles, you can gain insights into your audience and engage with them on a personalized and targeted level. A user's profile contains a lot of information, but here are some of the key parts: -- **User Identifier:** Each user profile is uniquely identified by a user ID, called an `external_id`. This identifier allows Braze to track and associate user data across different channels and devices, providing a unified view of each user's interactions with your brand. +- **User Identifier:** Each user profile is uniquely identified by a user ID, called an `external_id`. This identifier allows Braze to track and associate user data across different channels and devices, providing a unified view of each user's interactions with your brand. [Anonymous user profiles]({{site.baseurl}}/user_guide/getting_started/users_segments/anonymous_users/) (users who visit your website or application without logging in) don't have an `external_id`, but can be assigned [user aliases]({{site.baseurl}}/user_guide/getting_started/users_segments/anonymous_users/#assigning-user-aliases) as an alternative identifier. - [Attributes](#attributes)**:** These are specific pieces of information about the user, such as their name, age, location, or any other demographic information. You can use these attributes to segment your audience and personalize your messaging. - [Events](#events)**:** These are actions that the user takes, like making a purchase, clicking on a link, or opening an app. Braze tracks these events to help you understand the user’s behavior and engagement. Similar to attributes, you can also use events to segment and personalize. - **Purchases:** This section records the user's purchase history. It's crucial for understanding the user's buying habits and preferences. diff --git a/assets/img/getting_started/anonymous_users.png b/assets/img/getting_started/anonymous_users.png new file mode 100644 index 00000000000..6c143b69da1 Binary files /dev/null and b/assets/img/getting_started/anonymous_users.png differ