Set up a mobile property

A property is a container that you fill with extensions, rules, data elements, and libraries. To use these resources, you need to create and configure a mobile property in the Data Collection UI. You will typically create a mobile property for each mobile application you want to manage.

Before you start

Before you can set up your mobile property, complete the following prerequisites:

Set up groups and users

The Data Collection UI is fully integrated with your Adobe ID. User permissions are managed through the Admin Console with other Adobe products and solutions from the Creative Cloud, Document Cloud, and Experience Cloud.

For detailed instructions on how to create groups and add users in the Data Collection UI, see user permissions.

Log in to the Data Collection UI

After Data Collection UI rights have been added to your Adobe ID, log in to the Data Collection UI. You can do this by going to the Data Collection UI directly or by logging in to the Experience Cloud, navigating to the Activation page, and selecting the Data Collection UI.

Create a mobile property

Log in to the Data Collection UI.
On the main page, review the list of existing mobile and web properties.
Select New Property.
Type a name for the property and select Mobile as the platform.
If necessary, you can change the Privacy setting later.
Select Save to create the mobile property.
Search for the property you just created and select it to open it.

The default privacy status is set to opted in and might impact data collection. For more information, see Privacy and GDPR.

Setting default privacy status

Install your extensions

An extension is an integration built by Adobe or an Adobe partner that adds new options you can use in your apps. By default, all new mobile properties come with the Mobile Core and Profile extensions installed.

The Mobile Core extension provides a robust default set of functionality, including lifecycle events and conditions. The Profile extension allows storing of data into a client-side profile. Additional functionality for Analytics, Target, and so on will come from extensions that you install from the catalog. For more information, see the document on adding a new extension.

Set up your extensions

In the Data Collection UI, on the details page for your mobile property, select the Extensions tab.
The Mobile Core and Profile extensions are installed by default.
On the Mobile Core card, select Configure to open the extensions detail page.
Check your Experience Cloud Org ID.
By default, this value is auto-populated using the currently signed-in Organization ID. This is a required identifier for your Experience Cloud Organization and is typically a 24-character, alphanumeric string followed by @AdobeOrg. If you need help finding it, contact your Adobe CSM or Customer Care.
(Optional) Provide your Experience Cloud ID Server.
This is an optional server value that is used to send Visitor ID Service network requests to a custom endpoint. If this property is not set, the visitor identifiers sync requests are sent to dpm.demdex.net when the Identity extension is registered.
(Optional) Change the Session Timeout value.
A default value of 300 seconds is already set. This timeout value indicates the number of seconds that must pass after a user backgrounds the app before a launch is considered to be a new Lifecycle session.
Select Save to confirm your settings for Mobile Core.

Publish the configuration

Before the mobile application can access the configuration, it needs published to an environment. For now, we need to publish the Mobile Core and Profile extension configurations.

To deploy your configuration to a development environment for testing:

In the Data Collection UI, on your mobile property's details page, select the Publishing Flow menu.
Under the Development section of the publishing workflow, select Add New Library.
Specify any name for the library Name.
From the Environment drop-down list, select Development as the environment.
Select Add All Changed Resources to add the configuration changes to be deployed. You will see the Mobile Core and Profile extensions listed as changes to be published.
Select Save & Build for Development.
The library builds and is displayed under the Development section of the publishing workflow.
On the library card, select the ellipsis (...) to see a dropdown list.
Select Submit for Approval and then Submit.

The library of changes are then published to the Development environment and the library is displayed under the Submitted section of the publishing workflow.

Testing can be done using the configuration in the Development environment. The library can later be deployed to the Staging and Production environments by using the rest of the publishing workflow. For more information, see the documentation on publishing in the Data Collection UI.

Now that you published your configuration, get the Adobe Experience Platform SDK for your application. For more information, see tutorial on getting the Experience Platform SDKs.