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 Experience Platform Launch. You will typically create a mobile property for each mobile application you want to manage.
Before you can set up your mobile property, complete the following prerequisites:
Launch 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 for Launch, see User permissions.
After Experience Platform Launch rights have been added to your Adobe ID, log in to Launch. You can do this by going to https://launch.adobe.com or by logging in to the Experience Cloud (https://experiencecloud.adobe.com), navigating to the Activation page, and clicking on Launch.
Log in to Experience Platform Launch.
On the main page, review the list of existing mobile and web properties.
Click New Property.
Type a name for the property and select Mobile as the platform.
If necessary, you can change the Privacy setting later.
Click Save to create the mobile property.
Search for the property you just created and click to open it.
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 Add a new extension.
In Experience Platform Launch, on the details page for your mobile property, click the Extensions tab.
The Mobile Core and Profile extensions are installed by default.
On the Mobile Core card, click 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.
Optionally, 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.
Click Save to confirm your settings for Mobile Core.
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 Experience Platform Launch, on your mobile property's details page, click the Publishing Flow menu.
Under the Development section of the publishing workflow, click Add New Library.
Specify any name for the library Name.
From the Environment drop-down list, select Development as the environment.
Click 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.
Click Save & Build for Development.
The library builds and is displayed under the Development section of the publishing workflow.
On the library card, click ... to see a drop-down 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.
Now that you published your configuration, get the Adobe Experience Platform SDK for your application. For more information, see Get the Experience Platform SDKs.
To learn more about getting access to Launch, see User Permissions.
To learn more about Experience Platform Launch's publishing workflows, watch this video.