-
Notifications
You must be signed in to change notification settings - Fork 16
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #8540 from braze-inc/bd-3090
BD-3090 Add anonymous users to Getting Started
- Loading branch information
Showing
4 changed files
with
79 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
75 changes: 75 additions & 0 deletions
75
_docs/_user_guide/data_and_analytics/user_data_collection/anonymous_users.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -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 %} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.