Personalize Mobile Experiences
The Personalization module of the Engagement Mobile SDK enables you to query the Personalization service and receive targeted content within your iOS and Android applications.
While the Personalization module processes these requests to return personalized content, the Data 360 module handles the capture of customer interactions. By integrating both modules, you can send engagement data to Data 360 to build behavior profiles and use that data to drive real-time personalization decisions in your app.
The Personalization module depends on the underlying Data 360 module for identity resolution, consent management, and behavioral data collection. Therefore, integrate your mobile app with the Data 360 module. For procedure, see Data 360 Engagement Mobile SDK.
The Engagement Mobile SDK provides methods to capture interactions and personalize content. Call these methods in your application’s code at the appropriate moments in the user journey to track events and retrieve personalized experiences.
Pro-code integration gives you full control over the Decisioning API. You write native iOS or Android code to call fetchDecisions() directly, parse responses, track engagement, and render personalized content in your own UI components. For more information, see Pro-Code Mobile Personalization.
Low-code integration uses pre-built SDK plugins that handle fetching, rendering, and engagement tracking for you. Drop a ContentZone component into your app, configure it with the content zone identifier, and the SDK takes care of the rest for out-of-the-box components. Custom components and custom styling require additional setup. For more information, see Low-Code Mobile Personalization.
Both paths build on the same underlying SDKs. Use this comparison to choose the approach that fits your use case:
| 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 at code time, but low flexibility at runtime |
| 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 |