-
Notifications
You must be signed in to change notification settings - Fork 46
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
Added "defaultPersonalizationEnabled" option to the sendEvent command to control requesting the page-wide scope and default surface #1011
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like the name requestPersonalizations
instead of initializePersonalizations
@@ -34,7 +34,8 @@ export default ({ options }) => { | |||
}), | |||
datasetId: string(), | |||
mergeId: string(), | |||
edgeConfigOverrides: validateConfigOverride | |||
edgeConfigOverrides: validateConfigOverride, | |||
initializePersonalization: boolean() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it more like disablePersonalization
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, it will disable personalization for that event. But I would like us to take an approach that can be extensible in future.
We have the personalization
object as an option to sendEvent
command, we could move the cache initialization flag there, which is on by default for the first event and can be disabled/enabled per event.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jonsnyder looks good with one comment: should move the flag inside personalization
object.
Description
This adds an option to the sendEvent command called "initializePersonalization". This option controls whether or not the default scope is initialized and whether or not to request the default surface.
I'm not really happy with this naming. I'm open to different names.
Related Issue
https://jira.corp.adobe.com/browse/PDCL-10626?
Motivation and Context
Screenshots (if appropriate):
Types of changes
Checklist: