Standing up Personalization is a configuration and integration project, not a single record you create. The high-level path takes you from account access through tag deployment, catalog and sitemap setup, and a first live campaign. The steps below outline that path; the detailed field-level work lives in the Salesforce Help implementation guide.
- Get account access and plan the data
Confirm your Personalization dataset is provisioned and decide which channels you will track first. Map the visitor attributes, catalog categories, and key actions you care about before touching code, so the implementation has a clear target.
- Deploy the tag and SDKs
Add the Personalization JavaScript tag to every web template and integrate the mobile SDKs for app coverage. Verify the tag fires on each page type, because a missed template creates a permanent blank spot in the profile.
- Build the sitemap and catalog
Configure the sitemap so Personalization understands your page structure and content zones, and load the product or content catalog that recipes will recommend from. Keep the catalog feed in sync with the live site.
- Define segments and a first campaign
Create a starter segment from real behavior, then build one campaign, such as a recommendation strip or an exit-intent banner, targeted at that segment. Launch small, measure, and expand once the data looks clean.
Web content zones, mobile app SDK, open-time email, or server-side API; pick the surfaces you will personalize first.
The recommendation algorithm, configured with ingredients, inclusions and exclusions, boosters, variations, and fallbacks.
Web template using sitemap content zones, or server-side template using ContentZoneLookup for promotion assets.
Optional data stream that ingests engagement data into Data Cloud and activates unified segments back into Personalization.
- In server-side Einstein Decisions campaigns only view logs are tracked automatically; clicks must be tracked manually through the API.
- Anonymous visitors count toward profile-based licensing, so high-traffic catalogs can exceed expected profile volume.
- Documentation and community posts written before late 2022 call the product Interaction Studio; it is the same tool.
- Missing tags on any template leave gaps in the visitor profile that degrade every downstream recommendation and decision.