In-app channel prerequisites

Last update: 2024-01-26
  • Topics:
  • In App
    View more on this topic
  • Created for:
  • Intermediate
    Admin

Delivery prerequisites

For the In-app messages to be delivered correctly, the following settings must be defined:

  • In the Adobe Experience Platform Data Collection, make sure you have a datastream defined such as under the Adobe Experience Platform service you have the Adobe Experience Platform Edge and Adobe Journey Optimizer option enabled.

    This ensures that the Journey Optimizer inbound events are correctly handled by the Adobe Experience Platform Edge. Learn more

  • In Adobe Experience Platform, make sure you have the default merge policy with the Active-On-Edge Merge Policy option enabled. To do this, select a policy under the Customer > Profiles > Merge Policies Experience Platform menu. Learn more

    This merge policy is used by Journey Optimizer inbound channels to correctly activate and publish inbound campaigns on the edge. Learn more

    NOTE

    When using a custom Dataset preference merge policy, make sure to add the Journey Inbound dataset within the specified merge policy.

Channel configuration prerequisites

  1. Access the App surfaces menu and click Create App surface.

  2. Add a name to your App surface.

  3. From the Apple iOS drop-down, configure your mobile application for Apple iOS.

     Learn more
    1. Type-in your iOS Bundle ID. Refer to Apple documentation for more information on Bundle ID.

    2. (optional) Choose the Sandbox where you want to send push notifications from. Note that choosing a specific Sandbox requires the necessary access permissions.

      For more information on sandbox management, refer to this page.

    3. Enable the Push credentials option to drag and drop your .p8 auth key file if needed.

      You can also enable the Manually enter push credentials option to copy and paste your APNs auth key directly.

    4. Enter your Key ID and Team ID.

  4. From the Android drop-down, configure your mobile application for Android.

     Learn more
    1. Type-in your Android package name. Refer to Android documentation for more information on Package name.

    2. (optional) Choose the Sandbox where you want to send push notifications from. Note that choosing a specific Sandbox requires the necessary access permissions.

      For more information on sandbox management, refer to this page.

    3. Enable the Push credentials option to drag and drop your .json private key file if needed.

      You can also enable the Manually enter push credentials option to copy and paste your FCM private key directly.

  5. Click Save when you finished the configuration of your App surface.

    Your App surface will now be available when creating a new campaign with an In-app message. Learn more

  6. After creating your app surface, you now need to create a mobile property.

    Refer to this page for the detailed procedure.

  7. From the Extensions menu of your newly created property, install the following extensions:

    • Adobe Experience Platform Edge Network
    • Adobe Journey Optimizer
    • AEP Assurance
    • Consent
    • Identity
    • Mobile Core
    • Profile

    Refer to this page for the detailed procedure.

The In-app channel is now configured. You can start sending In-app messages to your users.

Content experiment prerequisites

To enable content experiments for In-app channel, you need to make sure the dataset used in your In-app implementation datastream is also included in your reporting configuration.

In other words, when configuring experiment reporting, if you add a dataset that is not present in your web datastream, web data will not display in the content experiment reports.

Learn how to add datasets for content experiment reporting in this section.

NOTE

The dataset is used read-only by the Journey Optimizer reporting system and doesn’t affect data collection or data ingestion.

If you are not using the following pre-defined field groups for your dataset schema: AEP Web SDK ExperienceEvent and Consumer Experience Event (as defined in this page), make sure to add the following field groups: Experience Event - Proposition Interactions, Application Details, Commerce Details, and Web Details. These are needed by the Journey Optimizer content experiment reporting as they are tracking which experiments and treatments each profile is participating in.

NOTE

Adding these field groups doesn’t impact the normal data collection. It is additive only for the pages where an experiment is running, leaving all the other tracking untouched.

How-to videos

  • The video below shows how to assign the Manage app configuration permission to access the App surfaces menu.

     See video

Related topics:

On this page