loading table of contents...

Personalization Hub Manual / Version 2310

Table Of Contents Fragment Caching

Contrary to CoreMedia's Adaptive Personalization which resolves variant selection on the server side, the client-side personalization resolves everything in the client's browser. Thus, the fragments included via AJAX do not require any user specific server side processing and are cacheable for a limited time.

CAE Caching

To enable the required HTTP caching headers add the following line to the live CAE's file and adjust the cache time to your need:

Caching in a commerce-led Scenario

If you are running the client-side personalization in a commerce-led scenario, the cache headers from the CAE might not be passed through the eCommerce delivery system. To counter this, add static rules to your CDN, allowing caching and storing of fragments with the path <prefix>/dynamic/fragment/experience/item/** on the client's side.

Search Results

Table Of Contents

Your Internet Explorer is no longer supported.

Please use Mozilla Firefox, Google Chrome, or Microsoft Edge.