To create and configure a mobile property in Experience Platform Launch, complete the following steps:
Click New Property
Create a new property by providing a name and selecting Mobile as the platform.
If required, you can change Privacy and HTTPS settings later.
Find the new property in the Properties list and click to open it.
In Experience Platform Launch, click the Extensions tab. The Mobile Core and Profile extensions are installed by default.
a. Click Configure on the Mobile Core card.
b. Provide 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.
c. (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.
d. 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.
Click Catalog and install the extensions that you need.
To create a library of changes and deploy the library to a Development Environment:
In the Publishing tab, under the Development section of the publishing workflow.
click Add New Library.
Specify a name for the library and, from the Environment drop-down list, select a development environment .
Add the configuration changes to be deployed.
Click Add All Changed Resources. To add only some changes, click Add a Resource.
Click Save & Build for Development. Tip: The library builds and is displayed under the Development section of the publishing workflow.
Click on the down arrow for the library and select Submit for Approval.
The configuration in the library is deployed to the Development environment and the library is displayed under the Submitted section of the publishing workflow.