Batch personalization, DMO activation and AMPscript
For channels that don’t call the API in real time — like email — precompute decisions in batch for a segment, write them to a DMO, and read them where you need them, for example with AMPscript in a Marketing Cloud Engagement email send.
Run batch and activate
- Create a Batch Personalization for a Data 360 segment.
- It writes decisions to the Batch Personalization Output DMO.
- Activate the DMO to your destination (Marketing Cloud Engagement, GCP, Amazon S3, or Azure).
- In the email, read the activated row’s decision fields with AMPscript.
%%[
var @decisionContent
set @decisionContent = Lookup(
"Personalization_Activation",
"ContentValue",
"SubscriberKey",
_subscriberkey
)
]%%
%%=v(@decisionContent)=%%
Discussion
Comments are not configured for local development. They appear once the site owner connects GitHub Discussions (Giscus).