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 vs. pro-code

	Low-code	Pro-code
Rendering	Built-in (Banner, Recommendations) or custom components	Fully custom - you build the UI
Engagement tracking	Automatic for out-of-the-box components, assisted for custom components (the SDK provides tracking APIs)	Manual
Setup effort	Lower	Higher
Flexibility	High - override any component or build your own, and change the personalization point or content served at any time without code changes, within the components allowed by that zone	Full control
Best for	Standard content zones, rapid integration - custom components can also handle highly custom layouts	Multiple personalization points in a single request, or a zone lifecycle that isn’t tied to UI rendering

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

Build your own UI by implementing the Component interface, backed by a transformer with a distinct component name:

Clone an out-of-the-box transformer. In the backend, duplicate the Salesforce_Banner or Salesforce_Recommendations transformer, assign it a new component name, and adjust the model to taste. Avoid reusing the same name for what’s actually a different (custom) component, which gets confusing fast.
Define a fully custom transformer with your own fields and component name. You implement engagement tracking manually if needed.

Either way, give your custom component its own name.

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.