Personalization
This is where connected data becomes a personalized experience. By the time you reach this section, Data 360 has the right data, identity resolution has unified it, and calculated insights have summarized it — now you turn that into recommendations, targeted content and decisions that reach your channels.
Jargon check: a decision is personalization’s answer to “what should this person see right now”; a recommender is the model or rule set a decision can call to choose items; a personalization point is the place in an experience where a decision can run.
Build in this order
Work through these eight pages in order — each builds on the one before it.
- Set up the content schema — define the items and attributes a decision can return.
- Create experience templates — start recommenders and decisions from a preconfigured pattern instead of building from scratch.
- Build recommenders — create objective-based and rule-based recommenders, apply filters, then simulate, train and set a fallback.
- Configure engagement signals and metrics — tell recommenders what counts as interest so models train on the right behavior.
- Create personalization points and decisions — define where personalization applies and what it returns, with targeting rules and merge fields.
- Use the Web Personalization Manager — place, preview and publish on-page personalization without a developer for each change.
- Organize work with campaigns — group related points and decisions so you manage a coordinated experience as one unit.
- Localize personalized experiences — serve the right language and locale variant to each audience.
Discussion
Comments are not configured for local development. They appear once the site owner connects GitHub Discussions (Giscus).