Capture Profile Data

The Data Cloud Module for the Engagement Mobile SDK enables collection of profile data through the SDK’s Identity APIs.

Before engagement data can be sent to Data Cloud:

  • The Data Cloud Module for the Engagement Mobile SDK must be configured and initialized.
  • Consent to track profile data must be granted.

When a profile attribute changes, the Data Cloud Module triggers an identity profile event containing all set attributes. You can set any name-value pair for profile attributes.

The Identity Schema provided by the recommended Mobile Connector schema for Data Cloud contains profile attributes that support identity resolution features when mapped to the appropriate Customer 360 Data Model.

Each identity event contains mappable fields.

  • Individual
    • firstName
    • lastName
  • Software Application
    • registrationId
    • softwareApplicationName
  • Device
    • advertiserId
    • deviceType
    • osName
  • Contact Point App
    • registrationId

Starting with Android 13 (API level 33), permission is required to request the device’s advertiserId. In Data Cloud 2.0.2, this permission is included by default. To prevent this permission from getting merged into your app, add this element to your AndroidManifest.xml:

Each supported contact point has required attributes that must be provided to the SDK's Identity API. After all attributes are provided, the Data Cloud Module triggers a profile event with contact points and an identity event.

The contact points and required attributes that trigger them are:

  • Contact Point Email Schema
    • email
  • Contact Point Phone Schema
    • phoneNumber
  • Contact Point Address Schema
    • addressLine1
    • city
    • postalCode
    • stateProvince
    • country

In the Data Cloud Module, all customers are considered known by default. To mark a customer as anonymous, set the isAnonymous profile attribute to "1". Setting isAnonymous to "0" ensures customers are considered known.

The Engagement Mobile SDK supports sharing identifiers between modules for integration with other Salesforce systems. For example, match an individual using a mobile application with both Data Cloud and MobilePush modules to send push notifications to specific anonymous mobile users.

The identity event contains fields that can be mapped to the Party Identification model.

  • registrationId: Identification Number

When the MobilePush module obtains a resolved identity for a mobile customer, it sets a profileId using the SDK's Identity API. The Data Cloud Module is notified and sends a partyIdentification event with these fields:

  • userId: Identification Number
  • IDName: Party Identification Name
  • IDType: Party Identification Type