Data Cloud Reference Guide

Data Cloud Reference Guide
Connect Data
Capture Web Interactions
Integrate Your Mobile Applications
API Reference
Initialization
Capturing Engagement Data
Capturing Profile Data
Capturing Behavior Data
Consent Management
Location Tracking
Logging and Debugging
Event Specifications
Schema Mappings
Connect MuleSoft with Data Cloud
Ingest Data
Model Data in Data Cloud
Extract Data
PDF

Capturing Profile Data

The Data Cloud Module for the Engagement Mobile SDK enables collection of profile data through the SDK’s Identity APIs.
Before profile data can be sent to Data Cloud:
  1. The Data Cloud Module for the Engagement Mobile SDK must be configured and initialized.
  2. Consent to track must be granted.

Setting Profile Attributes

iOS
Android

When a profile attribute changes, the Data Cloud Module triggers an identity profile event containing all the attributes that have been set. These attributes can be set to any name and value pair.

Supported Customer 360 Data Model

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

Each identity event contains fields that can be mapped.
  • Individual
    • firstName
    • lastName
  • Software Application
    • registrationId
    • softwareApplicationName
  • Device
    • advertiserId
    • deviceType
    • osName
  • Contact Point App
    • registrationId
Device advertiserId

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:

Contact Points
Each supported contact point has a set of required attributes that must be provided to the SDK’s Identity API. After all attributes have been provided, the Data Cloud Module triggers a profile event contacting points along with 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

Anonymous and Known Users

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”. Conversely, setting isAnonymous to “0” ensures that customers are considered known.

iOS
Android

Shared Party Identifiers

The Engagement Mobile SDK also supports sharing identifiers between modules that support other Salesforce systems for integration use cases. For example, match an individual using a mobile application that has Data Cloud and the MobilePush modules to send a push notification to a specific anonymous mobile user.

Anonymous MobilePush User
The identity event contains fields that can be mapped to the Party Identification model.
  • registrationId — Identification Number
Known MobilePush User
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 of this change and sends a partyIdentification event with these fields.
  • userId — Identification Number
  • IDName — Party Identification Name
  • IDType — Party Identification Type