Sync Mobile app AEPSDK from Launch technical workflow

After creating and configuring your mobile property in the Data Collection UI, the Sync Mobile app AEPSDK from Launch technical workflow will now synchronize the tag mobile properties imported in Adobe Campaign Standard.

By default, the technical worflow starts every 15 minutes. If needed, it can be manually restarted:

  1. In Adobe Campaign Standard, from the advanced menu, select Administration > Application Settings > Workflows.

  2. Open the Sync Mobile app AEPSDK from Launch (syncWithLaunch) workflow.

  3. Click on the Scheduler activity.

  4. Select Immediate execution.

Your workflow will now restart and synchronize the tag mobile properties imported in Adobe Campaign Standard.

Setting up your application in Adobe Campaign

To use a tag mobile property in Campaign, you must also configure this property in Adobe Campaign. In Adobe Campaign, ensure that the IMS user is part of the Standard User and Administrator Product Profiles.

You must wait for the technical workflow to run and sync the tag mobile property to Adobe Campaign. You can then configure it in Adobe Campaign.

For more information on Sync Mobile app AEPSDK from Launch technical workflow, refer to this section.

NOTE
By default, administrators with organizational unit set to ALL can edit the mobile application.
  1. From the advanced menu, select Administration > Channels > Mobile app (AEP SDK).

  2. Select the mobile application that you created in the Data Collection UI.
    Its Property Status should be Ready to configure.

    NOTE
    By default, to retrieve the list of mobile applications created in the Data Collection UI, Campaign Standard uses the value defined in the NmsServer_URL option to look for matching properties.
    In some cases, the Campaign endpoint for a mobile application may be different from the one defined in NmsServer_URL. In that case, define the endpoint in the Launch_URL_Campaign option. Campaign will use the value from this option to look for matching properties in the Data Collection UI.

  3. You can change the organizational unit of your mobile application under the Access Authorization section to limit access to this mobile application to specific organization units. For more information, refer to this page.

    Here, the administrator can assign sub organizational units by selecting them from the drop-down.

  4. To make the connection between Campaign and tags in Adobe Experience Platform, click Save.

  5. Verify that the status of the mobile app has changed from Ready to Configure to Configured.

    When the Campaign extension shows that the pkey has been set up successfully, you can also verify that the property has been set up successfully in Campaign.

  6. For this configuration to take effect, the changes need to be published in the Data Collection UI.

    For more information, see Publish configuration