Add details on how Page/Screen name property surface in Audience builder #7412
Conversation
This file contains hidden or 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
… the audience builder In the audience builder, the name property for page and screen calls will show up as page_name and screen_name, respectively. This update is to call out to customers about this distinction.
SethNuteTwilio
previously approved these changes
Jan 30, 2025
pwseg
changed the title
pwseg
approved these changes
Jan 30, 2025
pwseg
added
the
content-update
|
Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the audience builder, the name property for page and screen calls will show up as page_name and screen_name, respectively, instead of name (which is what shows up in the actual event). This update is to call out to customers about this distinction.
Merge timing