Low-Code Mobile Personalization

Low-code mobile personalization uses pre-built SDK plugins that render personalized content for you. Instead of calling the Decisioning API directly and building your own UI, you use a ContentZone element in your app with a list of allowed components, and the SDK fetches content, matches the backend’s component name, and renders the result automatically.

How It Works

The host app initializes the native Personalization Module of the Unified SDK on startup.
You place a ContentZone in your UI and specify which components it may render.
The SDK fetches a personalization decision from the backend.
The matching component is rendered. If no match is found, an optional fallback is shown.

When to use

Low-code integration is best for standard content zones and rapid integration, and custom components can also handle highly custom layouts. For a full comparison, see Low-Code vs. Pro-Code.

Out-of-the-Box Components

The low-code SDKs ship two ready-to-use components on each platform (packaged differently per platform):

SalesforceBanner - A single card with image, title, subtitle, and a CTA. Backed by the Salesforce_Banner template.
SalesforceRecommendations - A scrollable list of recommendation cards. Backed by the Salesforce_Recommendations template.

Out-of-the-box components track View and Click engagement automatically.

Custom Components

By implementing the Component interface, you can build your own UI component backed by an experience template with a distinct component name.

Whether you use an out-of-the-box (Salesforce_Banner or Salesforce_Recommendations) or fully custom experience template to create a custom component, you assign each custom component a new component name and handle these tasks in the app:

Parse the decision JSON
Render the UI
Report View and Click engagement using the SDK’s engagement tracking APIs

For implementation details, see the platform guides.

Prerequisites

The low-code plugins depend on the same underlying native SDKs as the pro-code path. Before integrating a plugin:

Complete the Data 360 Engagement Mobile SDK setup for identity, consent, and behavioral data collection.
Configure a Mobile Connector in Data 360 and obtain your CDP_APP_ID, CDP_ENDPOINT, CDN_URL, and DATASPACE from your Data Cloud administrator.
For the live previews functionality, configure a custom URL schema in your application.