Create personalization points and decisions

Updated Nov 8, 2026 Based on web research, 2026-11-08

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. 1 Page loads Visitor opens the page or app
  2. 2 Personalization point The slot on the page requests a decision
  3. 3 Decision request Sent to the Decisioning API
  4. 4 Decision logic Targeting rules pick the top eligible decision
  5. 5 Content served The point renders the returned response

Build points and decisions

  1. Create a personalization point with a type and a response template that matches where it renders.
  2. Add one or more decisions to the point — each is a candidate response.
  3. Add targeting rules to each decision so it only serves visitors who qualify.
  4. Attach a recommender or static content, then use merge fields to populate the response.
  5. Prioritize decisions on the point so a qualifying visitor receives exactly one.
Personalization point with prioritized decisions, targeting rules, and a recommender attached
Screenshot: Points and decisions

Discussion

Comments are not configured for local development. They appear once the site owner connects GitHub Discussions (Giscus).

Support SF Guide

SF Guide is a free, independent guide to Salesforce Personalization, built and maintained in the open. If it saved you time on an implementation, a small contribution helps keep it current and ad-light.