Set Up Mobile Personalization

Setting up mobile personalization requires configuration across your mobile app code, the Data 360 connector, and the Salesforce Personalization app. Developers complete the technical setup first. You then create and publish experiences.

• Phase I: App and Connector Setup
  • What's involved: Integrate Data 360 and Salesforce Personalization modules of the Marketing Cloud Unified Mobile SDK into your app and send engagement and profile data to Data 360. Set the in-app URL on your mobile connector for preview support. Register the components and content zones your app supports in connector setup. Define the matching components and content zones in your app code so the native app knows how to render personalized content and where to display it.
  • Outcome: Your mobile app connector is ready to serve personalized experiences. The registered components and content zones are available when developers build templates and users create experiences. QR code preview is enabled via the in-app URL.

  Step	Goal
  Configure Your Mobile App for Personalization	Initialize the SDK, send engagement and profile data to Data 360, and set the in-app URL for preview.
  Register and Define Mobile Personalization Components	Register each component in connector setup and define it in your app code.
  Register and Define Mobile Content Zones	Register each content zone in connector setup, connect its allowed components, and define it in your app code.

• Phase II: Personalization Engagement Tracking
  • What's involved: Configure engagement tracking on the connector so that view, click, and dismiss events are sent to Data 360 when users interact with personalized content. Tracking is configured once per content schema and applies automatically to every personalization point that uses that schema.
  • Outcome: User interaction data flows into Data 360, giving you the measurement foundation to improve future personalization.

  Step	Goal
  Track Engagement with Personalized Content	Add tracking events to the connector for each content schema you use.

• Phase III: Experience Templates
  • What's involved: Create experience templates for the mobile channel. A mobile template references a component from connector setup instead of defining HTML. The template carries the content data that the component renders natively in the app.
  • Outcome: Active templates are available in the template picker when you create personalization experiences.

  Step	Goal
  Create a Mobile Experience Template	Build and activate a template that references a mobile component and maps content schema variables.

• Phase IV: Personalization Experiences
  • What's involved: Create experiences from a personalization point, select an experience template, choose the content zone where the experience appears, preview the experience by scanning a QR code on a device, and then publish it.
  • Outcome: The experience is live in your mobile app, delivering personalized content to customers in the right app location.

  Step	Goal
  Create a Mobile Personalization Experience	Configure the experience properties, template, and content zone location.
  Preview a Mobile Personalization Experience with a QR Code	Verify the experience renders correctly in your app before publishing.
  Publish a Mobile Personalization Experience	Set the experience to Active to make it live for all customers.