Page tree
Skip to end of metadata
Go to start of metadata

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)

(plus) Could be used for Channel/Device
(minus) AS is already packed
(minus) Some code would have to go in core?

TraitCollector

(plus) Injectable anywhere
(plus) Installed in p13n module
(minus) Less explicit
(question) Lifecycle

Decision

It was decided to use a @LocalScoped TraitCollector

  • No labels