Delivery channels

A decision or recommendation that Personalization computes is only useful once it reaches the person it’s for. Delivery channels are the different ways that decision gets from Personalization out to a real experience — a live API call, a Flow, a batch job feeding email, an Agentforce-driven page, or a prediction from a model. Which channel you pick depends on who’s building the experience and how fast the decision needs to arrive.

Jargon check: a decision is personalization’s answer to “what should this person see right now” (see Personalization); real time means the channel calls Personalization at the moment the experience renders, while batch means decisions are precomputed ahead of time and read later.

Pick your channel

1. Call the Decisioning API — request decisions over HTTP, authenticated or unauthenticated, for any custom or real-time channel.
2. Call the Experimentation Assignment API — get a visitor’s experiment variation over the API so your channel serves a consistent experience.
3. Get decisions in Flow — bring a decision into a Salesforce Flow with an invocable action, no code required.
4. Batch personalization, DMO activation and AMPscript — precompute decisions for a segment and surface them in email or another batch destination.
5. Agentforce Adaptive Websites — bring personalization into an Agentforce-driven web experience.
6. Use Einstein Studio model predictions — feed a predictive model’s output into a recommender or decision.

Developers and integrators get the API pages; Salesforce admins building in-product automation use Flow and Agentforce; marketers running email campaigns use batch activation — most implementations end up using more than one channel.