Personalization rollouts are multi-month projects. The technical setup is a few weeks; the campaign and personalization design takes longer.
- Provision the dataset
Coordinate with the Salesforce account team to provision a Marketing Cloud Personalization dataset (formerly known as a Mass account in Interaction Studio).
- Deploy the JavaScript tag
Add the Personalization JavaScript tag to every page on the website. The tag captures page views, click events, and form submissions automatically.
- Integrate mobile SDKs
Add the iOS and Android SDKs to the mobile app. The SDKs send the same event stream as the web tag.
- Connect to CRM and Marketing Cloud
Configure the Salesforce connector to sync known-user identity from Service Cloud and Marketing Cloud Engagement. Configure Data Cloud integration if used.
- Design personalization campaigns
Build campaigns that decide what each visitor sees. Start with simple use cases (recommended products, content rotation) before complex orchestration.
- Pilot, measure, expand
Launch one campaign at a time. Measure lift via A/B testing. Expand to more campaigns once a baseline is established.
- The Interaction Studio name persists in older documentation. The modern product is Marketing Cloud Personalization; treat both names as the same product.
- Visitor profile volume drives licensing cost. High-traffic sites can blow through the licensed volume; size the contract with realistic forecasts.
- JavaScript tag deployment requires coordination with the web team. Mis-deployed tags miss events, producing under-personalized experiences.
- Data Cloud integration is the strategic direction. New deployments should evaluate the Data Cloud-first architecture rather than the legacy standalone Personalization model.