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.

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

Tracking audiences in a privacy-first manner #360

Closed
ramboz opened this issue Jul 15, 2024 · 1 comment · Fixed by #368 · May be fixed by adobe/helix-rum-enhancer#235
Closed

Tracking audiences in a privacy-first manner #360

ramboz opened this issue Jul 15, 2024 · 1 comment · Fixed by #368 · May be fixed by adobe/helix-rum-enhancer#235
Labels
enhancement New feature or request released

Comments

@ramboz
Copy link
Collaborator

ramboz commented Jul 15, 2024

Is your feature request related to a problem? Please describe.
In segmentation (personalization) use cases, we need to report on how each defined audience performs relative to the others. Currently, we do not have any way to track this data. This used to be tracked under the audience checkpoint, but got removed for privacy concerns.

Describe the solution you'd like
We want to re-introduce the checkpoint, and we want to be able to track this in a privacy compliant way, as discussed over slack.
Differential audiences is what we settled upon where we will randomly select whether we report the "true" audience, or pick a random one from the list. And in the reporting, we'll compute the variance from a uniform distribution to estimate the audience distribution.

@trieloff
Copy link
Contributor

🎉 This issue has been resolved in version 2.27.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment