Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BD-3648 Add email conversion events #8454

Merged
merged 2 commits into from
Nov 20, 2024
Merged

BD-3648 Add email conversion events #8454

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a9c9d3d
BD-3648 Update conversion events
rachel-feinberg Nov 14, 2024
e5c4550
BD-3648 Add email conversion events
rachel-feinberg Nov 19, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions .../_user_guide/engagement_tools/campaigns/building_campaigns/conversion_events.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,10 +42,12 @@ We highly recommend using as many conversion events as you feel is necessary bec
For each conversion event you want to track, select the event and conversion deadline.

1. Select the general type of event you'd like to use:
- **Opens App**: A user is counted as having converted when they open any one of the apps that you specify (defaults to all apps in the workspace).
- **Starts Session**: A user is counted as having converted when they open any one of the apps that you specify (defaults to all apps in the workspace).
- **Makes Purchase**: A user is counted as having converted when they purchase the product you specify (defaults to any product).
- **Performs Custom Event**: A user is counted as having converted when they perform one of your existing custom events (no default, you must specify the event).
- **Upgrade App**: A user is counted as having converted when they upgrade the app version on any one of the apps that you specify (defaults to all apps in the workspace). Braze will perform a best-efforts numerical comparison to determine if the version change was an upgrade. For example, a user would convert if they upgrade from version 1.2.3 to 1.3.0 of the application, but Braze wouldn't register a conversion if a user downgrades from 1.2.3 to 1.2.2. However, if the app's version name contains strings, such as "1.2.3-beta2", then Braze will not be able to determine if a version change was an upgrade. In this situation, Braze will count it as a conversion when the user's most recent app version changes.<br><br>
- **Upgrade App**: A user is counted as having converted when they upgrade the app version on any one of the apps that you specify (defaults to all apps in the workspace). Braze will perform a best-efforts numerical comparison to determine if the version change was an upgrade. For example, a user would convert if they upgrade from version 1.2.3 to 1.3.0 of the application, but Braze wouldn't register a conversion if a user downgrades from 1.2.3 to 1.2.2. However, if the app's version name contains strings, such as "1.2.3-beta2", then Braze will not be able to determine if a version change was an upgrade. In this situation, Braze will count it as a conversion when the user's most recent app version changes.
- **Opens email**: A user is counted as having converted when they open the email (only for email campaigns).
- **Clicks email**: A user is counted as having converted when they click a link within the email (only for email campaigns).<br><br>
2. Set your conversion deadline. This is the maximum amount of time that may pass to consider a conversion. You have the option of allowing up to a 30-day window during which the conversion will be counted if the user takes the specified action.

![The "Makes Purchase" conversion event type as an example to record conversions for users who make any purchase. This has a conversion deadline of 12 hours.][2]
Expand Down