ÃÛ¶¹ÊÓƵ

DocumentationCampaignCampaign Standard Documentation

Configuring a mobile application configuring-a-mobile-application

Last update: Sat Mar 23 2024 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • Experienced
  • Admin

Configuring a mobile application using ÃÛ¶¹ÊÓƵ Experience Platform SDKs using-adobe-experience-platform-sdk

IMPORTANT
ÃÛ¶¹ÊÓƵ Experience Platform Launch has been rebranded as a suite of data collection technologies in ÃÛ¶¹ÊÓƵ Experience Platform. Several terminology changes have rolled out across the product documentation as a result. Please refer to the following document for a consolidated reference of the terminology changes.

Note that Push notification and In-App implementations have to be performed by expert users. For assistance, contact your ÃÛ¶¹ÊÓƵ Account executive or Professional services partner.

To send push notifications and In-App messages with Experience Platform SDK application, a mobile application has to be set up in the Data Collection UI and configured in ÃÛ¶¹ÊÓƵ Campaign.

Once a mobile application is set up, you can retrieve the PII data it collected to create or update profiles from your database. For more on this, refer to this section: Creating and updating profile information based on mobile application data.

To learn more on the different mobile use cases supported in ÃÛ¶¹ÊÓƵ Campaign Standard by using the ÃÛ¶¹ÊÓƵ Experience Platform SDKs, refer to this page.

To complete the configuration, complete the following steps:

  1. In ÃÛ¶¹ÊÓƵ Campaign, ensure that you can access the following:

    • Push notification
    • In-App message
    • ÃÛ¶¹ÊÓƵ Places

    If not, contact your account team.

  2. Check that your user has the necessary permissions in ÃÛ¶¹ÊÓƵ Campaign Standard and tags in ÃÛ¶¹ÊÓƵ Experience Platform.

    • In ÃÛ¶¹ÊÓƵ Campaign Standard, ensure that the IMS user is part of the Standard User and Administrator Product Profiles. This step allows the user to log in to ÃÛ¶¹ÊÓƵ Campaign Standard, navigate to the Experience Platform SDK mobile app page, and view the mobile app properties that you created in the Data Collection UI.

    • In the Data Collection UI, ensure that your IMS user is part of a Experience Platform Launch product profile.
      This step allows the user to log in to the Data Collection UI to create and view the properties. For more information about product profiles in the Data Collection UI, see Create your product profile. In the product profile, there should be no permissions set on the company or the properties, but the user should be able to still log in.

    To complete additional tasks like installing an extension, publishing an app, configuring environments, and so on, you need to set permissions in the product profile.

  3. In the Data Collection UI, create a Mobile property. For more information, see .

  4. In the Data Collection UI, click the Extensions tab, go to Catalog, and search for the ÃÛ¶¹ÊÓƵ Campaign Standard extension. For more information, see .

  5. To support location use cases in Campaign Standard, install the Places extension in the Data Collection UI. Refer to this .

  6. In ÃÛ¶¹ÊÓƵ Campaign Standard, configure the mobile property that you created in the Data Collection UI. Refer to Setting up your ÃÛ¶¹ÊÓƵ Experience Platform Launch application in ÃÛ¶¹ÊÓƵ Campaign.

  7. Add the channel-specific configuration to your mobile application set up.
    For more information, see Channel-specific application configuration in ÃÛ¶¹ÊÓƵ Campaign.

  8. If required, you can delete your tag property.
    For more information, see Deleting your application.

Sync Mobile app AEPSDK from Launch technical workflow aepsdk-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 ÃÛ¶¹ÊÓƵ Campaign Standard.

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

  1. In ÃÛ¶¹ÊÓƵ 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 ÃÛ¶¹ÊÓƵ Campaign Standard.

Setting up your application in ÃÛ¶¹ÊÓƵ Campaign set-up-campaign

To use a tag mobile property in Campaign, you must also configure this property in ÃÛ¶¹ÊÓƵ Campaign. In ÃÛ¶¹ÊÓƵ 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 ÃÛ¶¹ÊÓƵ Campaign. You can then configure it in ÃÛ¶¹ÊÓƵ 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 note
    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 ÃÛ¶¹ÊÓƵ 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

Channel-specific application configuration in ÃÛ¶¹ÊÓƵ Campaign channel-specific-config

Your mobile application is now ready to be used in Campaign for push notification or In-App deliveries. You can now further configure it if needed to create events that will trigger your In-App messages and/or upload Push certificates.

  1. From the advanced menu, select Administration > Channels > Mobile app (AEP SDK).

  2. Select the mobile application you created and configured in the Data Collection UI.

  3. On the Mobile application properties tab, you can start adding events that are available in your mobile application for your In-App messages.

  4. To configure your events, click Create Element.

  5. Type a name and a description.

  6. Click Add.

    Your event is now available on the Triggers tab when you create an In-App message. For more information, see Preparing and sending an In-App message.

  7. In the Device-specific settings section of a mobile application dashboard, for each device, provide the application details.

    • accordion
      For iOS

      Enter the following application details:

      • App ID (iOS Bundle ID): Refer to for more information on Bundle ID.

      • iOS Certificate (P8) file: Drag and drop your .p8 auth key. For instructions on how to generate the .p8 authentication file, refer to your .

      • Key ID: Refer to for more information on Key ID.

      • iOS Team ID: Refer to for more information on iOS Team ID.
    • accordion
      For Android

      Enter the following application details:

      • App ID (Android Package Name): Refer to for more information on Package name.

      • Android Key (Json) file: Drag and drop your .json private key file. For instructions on how to generate the .json private key file, refer to the .

  8. After your certificate is uploaded, a message notifies you that the upload was successful and displays the expiration date of your certificate.

  9. Click the Mobile application subscribers tab to see a list of subscribers and other information about these subscribers, for example, whether they opted out of your notifications.

Deleting your application delete-app

CAUTION
Deleting your application cannot be reversed.

To delete your application, complete the steps in .

After your application is deleted, in ÃÛ¶¹ÊÓƵ Campaign, verify whether your application’s Property status has been correctly updated to Deleted in Launch.

By clicking on your application in ÃÛ¶¹ÊÓƵ Campaign, you can choose to completely remove this application from ÃÛ¶¹ÊÓƵ Campaign by clicking Delete from Campaign.

recommendation-more-help
3ef63344-7f3d-48f9-85ed-02bf569c4fff