Version 2.0 of Optimizely Personalized Search & Navigation adds support for _EPiServer.Personalization_ 2.0. For more information, see _EPiServer.Personalization_ [breaking changes](🔗).

Because of breaking changes from _EPiServer.Personalization_, _EPiServer.Find.Personalization_ does not provide settings related to the Personalization service. All settings are provided by _EPiServer.Personalization_. For more information, see [Using scopes in a multisite installation](🔗).

## API changes

### EPiServer.Find.Personalization.Api.RefreshPreferenceCommand

The following properties and fields were removed from the `RefreshPreferenceCommand`:

• `BaseApiUrl`

• `ClientToken`

• `Site`

To access these settings in the new version, look at the `RefreshPreferenceCommand`'s `ScopeConfiguration` property. This `ScopeConfiguration` instance contains the properties listed above.

### EPiServer.Find.Personalization.Conventions.IPersonalizationClientConventions

The following properties and fields were removed from `IPersonalizationClientConventions`:

• `BaseApiUrl`

• `ClientToken`

• `Site`

If you need to get these properties and fields in any custom implementation using the new version, implement the `GetPersonalizationConfiguration` property. This property is a function that returns a `PersonalizationConfiguration` instance that has the `GetConfiguration(scope)` and GetConfiguration() methods. These methods return a `ScopeConfiguration` instance that contains the properties listed above. For more information, see [Using scopes in a multisite installation](🔗).

## Configuration changes

See [Personalization.Commerce 2.0 breaking changes](🔗) and [Personalization.Commerce 3.0 breaking changes](🔗)