Personalization rollouts are multi-month projects. Technical setup is a few weeks; campaign and personalization design takes longer.
- Provision the dataset
Coordinate with the Salesforce account team to provision a Personalization dataset (formerly known as a Mass account).
- Deploy the JavaScript tag
Add the Personalization JavaScript tag to every page on the website. The tag captures page views and events.
- Add mobile SDKs
Install the iOS and Android SDKs in the mobile app. They send the same event stream as the web tag.
- Connect to CRM and Marketing Cloud
Configure the Salesforce connector for known-user identity sync. Plan Data Cloud integration where applicable.
- Design personalization campaigns
Build campaigns that decide what each visitor sees. Start simple (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 baselines exist.
- The Interaction Studio name persists in older documentation. Treat Interaction Studio and Marketing Cloud Personalization as synonyms.
- Visitor profile volume drives licensing cost. High-traffic sites can blow through licensed volume; size the contract with realistic forecasts.
- JavaScript tag deployment requires coordination with the web team. Missed tags miss events, producing under-personalized experiences.
- Data Cloud is the strategic direction. New deployments should evaluate the Data Cloud-first architecture.