To create and configure a mobile property in 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 may change Privacy and HTTPS settings later.
Find the new property in the Properties list and click to open it.
Go to the Extensions tab. You should see that Mobile Core and Profile extensions are installed by default.
Click Configure on the Mobile Core card.
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. This is typically, a 24-character, alphanumeric string followed by @AdobeOrg. If you need help finding it, contact your Adobe CSM or Customer Care.
Optionally, provide your Experience Cloud ID Server. This is an optional server value which will be used to send Visitor ID Service network requests to a custom endpoint.
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 we consider an launch a new Lifecycle session.
Click Save to confirm your settings for Mobile Core.
Click Catalog and install all the extensions you need.
Publish configuration In this step, you'll create library of changes and then deploy the library to a Development Environment.
In the Publishing tab, click on Add New Library under the Development section of the publishing workflow.
Specify a name for the library and select a development environment from the Environment dropdown.
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 will build and then show under the Development section of the publishing workflow.
Click on the down arrow for the library and select Submit for Approval.
The configuration contained in the library will then be deployed to the Development environment and the library will show under the Submitted section of the publishing workflow.