Mobile handover checklist

Updated Nov 8, 2026 · Based on Salesforce Data Cloud docs and Apple/Google developer docs reviewed 2026-11-08

Before your app developers build the Unified Mobile SDK into a release, confirm these items with the implementation team. Working through them first avoids rework after the SDK ships in a build.

Before the app team integrates the SDK Copy list

• Mobile event schema is finalized: the engagement and profile data lake objects (DLOs) are mapped to their data model objects (DMOs). See Configure the mobile schema.
• A test engagement event sent from a build through the Unified Mobile SDK reaches Data 360 and lands on the expected DMO.
• The identifier your app sends (for example, a device ID) is confirmed against your identity resolution rules, so mobile activity joins the unified profile.
• The mobile connector's in-app preview URL is set, so the app team can preview personalization on a device before release.
• Each platform team (iOS, Android, Flutter, React Native) knows which SDK package or dependency to add and has initialized it with the connector configuration.
• App store privacy disclosures are reviewed for the new SDK before submitting the updated build.
• The app's consent or opt-out flow matches how the SDK collects and sends data.

For the schema and identity items, see Configure the mobile schema.