
Optimizely Data Platform Visitor Groups now supports multiple instances
This module adds additional visitor groups, allowing personalised content based on real-time segments, profile data and other metrics from the Optimizely Data Platform (OPD).
The latest update (V2.0) includes support for multiple Optimizely Data Platform instances, which is useful when data residency rules need to be supported on large multi-region sites.
This version has added support for .NET7 and .NET8 and dropped support for CMS11.
Upgrading from previous versions
If you are upgrading from a previous version, be aware of several breaking changes.
The configuration must be updated to match the new schema.
Any existing Visitor Groups must be resaved, as you must now specify the OPD instance.
Configuration
The configuration schema allows for a collection of endpoints to be added; each one must have a unique name.
1{
2 "EPiServer": {
3 //Other config
4 "OdpVisitorGroupOptions": {
5 "OdpCookieName": "vuid",
6 "CacheTimeoutSeconds": 10,
7 "SchemaCacheTimeoutSeconds": 86400,
8 "PopulationEstimateCacheTimeoutSeconds": 4320,
9 "OdpEndpoints": [
10 {
11 "Name": "US", //Unique name for the instance
12 "BaseEndPoint": "https://api.zaius.com",
13 "PrivateApiKey": "..."
14 },
15 {
16 "Name": "EU",
17 "BaseEndPoint": "https://api.zaius.eu",
18 "PrivateApiKey": "..."
19 }]
20 }
21 }
22}
Visitor Groups
When creating a visitor group, you must specify the ODP instance, which is implemented in two different ways.
The ODP instance is prefixed to the property/segment name, or
An additional drop-down property that requires you to specify the ODP instance to use.

If you are upgrading from a previous version, then it is recommended that you modify the existing Visitor Groups to select the ODP instance.
More information
More information is available on the project GitHub page: https://github.com/unrvld/ODP.VisitorGroups. This includes instructions on how to install and configure the module.