Showing higher audience count in destination than the Segment UI. #4900
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
## Can I reuse audience keys? Avoid using the same audience key twice, even if you've deleted the key's original audience. Downstream tools and Destinations might have trouble distinguishing between different audiences that at any point shared the same key. And may create mismatch on the audience size between Segment and Destination as the destination will be having more audience count as the users of the old audience still exist over the destination.
## Can I reuse audience keys? Avoid using the same audience key twice, even if you've deleted the key's original audience. Downstream tools and Destinations might have trouble distinguishing between different audiences that at any point shared the same key. And may create mismatch on the audience size between Segment and Destination as the destination will be having more audience count as the users of the old audience still exist over the destination.
Panandhan22
requested review from
markzegarelli,
pwseg and
rchinn1
as code owners
markzegarelli
approved these changes
Jul 18, 2023
|
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
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.
Proposed changes
How can be the audience count is high in the connected destination than the Segment UI?
This can happen only when the audiences with same name was created earlier and connected to the corresponding destination. And later if the audience was deleted and recreated with the same name is connected to the same destination. Users of the audience created previously was still available on the destination, then added to that, the audience newly created will also send the users to the destination. Hence, the audience count will be high in destination than the Segment UI.
Merge timing
Related issues (optional)