3

Looking at the 8.5 documentation for XO, there is a cartridge which is responsible for putting all the defined triggers from the trigger-types.xml to a claim in ADF, the Experience Optimization cartridge.

The Claim Processors used in the Experience Optimization cartridge are packaged in the smarttarget_cartridge.jar

Before an XO query is executed, the entire content of the Claim Store is cross referenced against the claim containing the triggers, and and only the matching ones are sent to FH.

This makes perfect sense, yet I cannot find anything similar in Sites 9's XO (using ElasticSearch). Is this filtering now built into the system or where is it?

Below is a screenshot of the documentation comparing the "XO cartridge reference" sections of 8.5 and 9, and there is no mention of anything similar for 9. Am I missing something?

enter image description here

4

The cartridge is indeed no longer needed as the problem it was solving (URL size) doesn't exist in the new version with Elasticsearch.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.