The score for each segment can vary at runtime depending on the current normalization. The actual scores used in each request can therefore be logged.
To enable segment score explanation logging, set the 'explanation' log to INFO level. For example, add the following to your log4j2.xml file:
<Logger name="com.onehippo.cms7.targeting.explanation.Explanation" level="info" additivity="false"> <AppenderRef ref="site"/> </Logger>
By default, the explanations will be added to the log file of the CMS. Use the 'appender-ref' configuration option to change this.
Each request to the site will now log all global segments and all component-specific configurations that are used in the current channel. For each of these variants the following data is shown:
- the normalized score (which is used to determine the best matching configuration per component)
- the raw score (the score as calculated by the engine without being normalized)
- whether this variant is used in some component configuration in the current page or the current channel
- whether this variant is a global segment or a component-specific configuration
+ http://localhost:8080/site/news + Prospective reseller | - normalized score: 0.0 | - raw score: 0.0 | - on current page: true | - on current channel: true | - is global persona: true + Returning visitor ( normalization : 0.49900049999999996 ) | - normalized score: 2.004006008010012 | - raw score: 1.0 | - on current page: false | - on current channel: true | - is global persona: false + Monday - normalized score: 0.0 - raw score: 0.0 - on current page: false - on current channel: true - is global persona: false