Create personalization points and decisions
A personalization point is the “where” — a slot on a page or app, like a homepage banner, that can request content. A decision is the “what” — the logic that decides, for each visitor, whether they qualify and what content or recommendation to serve. One point can hold several decisions, prioritized so only one wins.
How a point gets served
- 1 Page loads Visitor opens the page or app
- 2 Personalization point The slot on the page requests a decision
- 3 Decision request Sent to the Decisioning API
- 4 Decision logic Targeting rules pick the top eligible decision
- 5 Content served The point renders the returned response
Build points and decisions
- Create a personalization point with a type and a response template that matches where it renders.
- Add one or more decisions to the point — each is a candidate response.
- Add targeting rules to each decision so it only serves visitors who qualify.
- Attach a recommender or static content, then use merge fields to populate the response.
- Prioritize decisions on the point so a qualifying visitor receives exactly one.
Discussion
Comments are not configured for local development. They appear once the site owner connects GitHub Discussions (Giscus).