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

Added "defaultPersonalizationEnabled" option to the sendEvent command to control requesting the page-wide scope and default surface #1011

Merged
merged 6 commits into from
Oct 24, 2023

Conversation

jonsnyder
Copy link
Contributor

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

  1. Be able to record a display notification as the first request on the page without requesting new personalization.
  2. Be able to refresh the cache of page-wide scope propositions.

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Improvement (non-breaking change which does not add functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • I have signed the Adobe Open Source CLA or I'm an Adobe employee.
  • I have made any necessary test changes and all tests pass.
  • I have run the Sandbox successfully.

@jonsnyder jonsnyder requested a review from ninaceban July 14, 2023 22:53
Copy link
Contributor

@carterworks carterworks left a 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()
Copy link
Contributor

@jfkhoury jfkhoury Jul 22, 2023

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?

Copy link
Contributor

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.

Copy link
Contributor

@ninaceban ninaceban left a 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.

@jonsnyder jonsnyder merged commit b8369b2 into main Oct 24, 2023
1 check passed
@jonsnyder jonsnyder deleted the initializePersonalizationOption branch October 24, 2023 14:54
@jonsnyder jonsnyder changed the title Add option to sendEvent command of whether or not to request the page-wide scope Added "requestPersonalizationEnabled" option to sendEvent to control requesting the page-wide scope and default surface Nov 1, 2023
@jonsnyder jonsnyder changed the title Added "requestPersonalizationEnabled" option to sendEvent to control requesting the page-wide scope and default surface Added "requestPersonalizationEnabled" option to the sendEvent command to control requesting the page-wide scope and default surface Nov 1, 2023
@jonsnyder jonsnyder changed the title Added "requestPersonalizationEnabled" option to the sendEvent command to control requesting the page-wide scope and default surface Added "defaultPersonalizationEnabled" option to the sendEvent command to control requesting the page-wide scope and default surface Nov 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants