Pro-Code Mobile Personalization

Pro-code mobile personalization gives you full control over the Decisioning API. Instead of using a pre-built SDK plugin, you call fetchDecisions() directly, parse the response, and render personalized content in your own UI - and you’re responsible for reporting engagement yourself.

How It Works

The host app initializes the native Data 360 and Personalization modules of the Unified SDK on startup.
You call fetchDecisions() with the personalization point name(s) you want content for.
The SDK requests a decision from the backend and returns a DecisionsResponse.
You parse the response and render your own UI with the returned content.
You report View and Click engagement manually using the SDK’s tracking APIs.

Prerequisites

Pro-code integration depends on the same underlying native SDKs as the low-code path. Before integrating:

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 and CDP_ENDPOINT from your Data Cloud administrator.

Platform Guides

When to use pro-code vs. low-code

Pro-code integration is best when you need multiple personalization points in a single request, or a zone lifecycle that isn’t tied to UI rendering. If your use case fits standard content zones or rapid integration, consider the low-code path instead. For a full comparison, see When to use low-code vs. pro-code.