Loadbalancing and CM / CD environments

Umbraco setup

Make sure your Umbraco is setup according to the Umbraco best-practices. Please refer to the Umbraco documentation.

Cockpit (configuring the AuthCookieDomain cookie)

For the cockpit to function properly it is necessary that the cockpit can read the Umbraco login cookie or else the cockpit won't be visible. Umbraco and the site should run on the same domain / sub-domain. For example:

Umbraco: umbraco.domain.com
Site: domain.com

Make sure the AuthCookieDomain in your SecuritySettings of your Umbraco config is set to

"AuthCookieDomain": ".domain.com",

Also see: https://docs.umbraco.com/umbraco-cms/reference/configuration/securitysettings

Bot detection (ping)

uMarketingSuite will perform a ping (POST) to detect if the visitor is a visitor or a bot. The url umbraco/umarketingsuite/pagedata/ping should be accessible from the content delivery / front-end servers so make sure no firewall or other mechanism is blocking the POST request to umarketingsuite/pagedata/ping

Configuration

Make sure the IsProcessingServer is set to True on the content management (Umbraco) server/environment and to False on the content delivery / front-end servers in your uMarketingSuite.config (uMarktingSuite v1.x) or AppSettings.json (uMarketingSuite v2.x) file.

Sticky sessions

Sticky sessions, also known as session affinity, are essential for the proper functioning of uMarketingSuite in a load-balanced environment. Sticky sessions can be enabled using various methods such as cookie-based, IP-based, or URL-based session affinity, depending on the load balancer configuration. By enabling sticky sessions, you can ensure that user sessions remain intact and data consistency is maintained across the uMarketingSuite application so analytics, a/b testing and personalization can work properly.

Please refer to the documentation or configuration settings of your load balancer for specific instructions on enabling sticky sessions.