Intro
For the personalization feature we have to store traits of visitors somewhere "accessible" in a unified manner.
Initially, the AggregationState was selected, but suggestions were made, to use a different approach, especially considering that the module will be EE only.
AggregationState (AS)
Could be used for Channel/Device
AS is already packed
Some code would have to go in core?
TraitCollector
Injectable anywhere
Installed in p13n module
Less explicit
Lifecycle
Decision
It was decided to use a @LocalScoped TraitCollector
Overview
Content Tools