ÃÛ¶¹ÊÓƵ

DocumentationCampaignCampaign Standard Documentation

Experience Platform SDK integration FAQ aep-faq

Last update: Mon Sep 30 2024 00:00:00 GMT+0000 (Coordinated Universal Time)
  • Applies to:
  • Campaign Standard

CREATED FOR:

  • Experienced
  • Admin

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

The section below lists common questions about this synchronization.

For more information on Push or In-App, refer to the following FAQs:

Useful resources before starting resource-mobile-property

Check out the resources below for more information on the ÃÛ¶¹ÊÓƵ Experience Platform SDK and Campaign Standard integration:

  • Launch/Mobile
  • Launch/Mobile

Is ÃÛ¶¹ÊÓƵ Experience Platform SDK integration available for both ÃÛ¶¹ÊÓƵ Campaign Standard and ÃÛ¶¹ÊÓƵ Campaign Classic? aep-validity

Yes, ÃÛ¶¹ÊÓƵ Experience Platform SDK integration is available for both ÃÛ¶¹ÊÓƵ Campaign Standard and ÃÛ¶¹ÊÓƵ Campaign Classic. You must install the corresponding Extension via the Data Collection UI to enable the integration.

For more on this, refer to this .

What capabilities does ÃÛ¶¹ÊÓƵ Experience Platform SDK integration facilitate in ÃÛ¶¹ÊÓƵ Campaign? aep-capabilities

Refer to the table below to learn more about these capabilities.

NOTE
Places integration includes places events as triggers for In-App messages (N/A for Push notifications), enriching profiles with Places data and local notifications support. Refer to this page for more information.
Places limited integration includes enriching profiles with Places data.

What use case does ÃÛ¶¹ÊÓƵ Experience Platform SDK integration facilitate in ÃÛ¶¹ÊÓƵ Campaign Standard? aep-use-cases

The following use cases are supported:

  • Acquire a Mobile Profile in Campaign (identified by ECID in Administration > Channels > Mobile app (AEP SDK) > Mobile Application subscribers tab)
  • Enrich a Mobile Profile in ÃÛ¶¹ÊÓƵ Campaign (requires Custom resource Extension of appSubscriberRcp table)
  • Acquire a Push token for sending Push messages (requires user opt-in to receive Push messages)
  • Send Push and In-App Messages
  • Track user’s interaction with Push and In-App Messages and provide reports on that

What do I have to do in order to acquire a Mobile Profile in Campaign? mobile-profile-campaign

To do so, follow the steps below:

  1. Configure a Mobile property in Launch.

  2. Install ÃÛ¶¹ÊÓƵ Campaign Standard extension. Note that ÃÛ¶¹ÊÓƵ Campaign Standard extension also requires Mobile Core, Profile and Lifecycle extensions which are installed by default in Launch.

    • Users should configure Session timeout in Mobile Core extension which impacts the frequency of lifecycle events.
    • Once the extension is configured, users should add appropriate dependencies in the Mobile App using Cocoapods for iOS and Gradle for Android. Follow the directions .
    • Always take the latest versions of the libraries.
    • In Mobile App, register Campaign, UserProfile, Identity, Lifecycle and Signal extensions. Follow the directions .
    • Once extensions are registered, start ACPCore. For Android, be sure to setApplication onCreate(). Follow the exact instructions provided in Mobile Install Instructions for your Mobile Property in Launch.
    • Following SDK APIs will also be required. Implement Lifecycle Start and Pause APIs as described for Android and here for iOS.

  3. Configure a Mobile Property in ÃÛ¶¹ÊÓƵ Campaign Standard. Follow the procedure here.

What do I have to do in order to enrich a Mobile Profile in Campaign? enrich-mobile-profile

You must configure a CollectPII postback (refer to this page) and implement CollectPII API from SDK (refer to this ).

How frequently should a CollectPII call be fired? collect-pii

The objective of CollectPII call is to enrich the Mobile Profile in Campaign. It should be fired whenever there is new meaningful information that customers would like to add to the profile depending on their use cases and business needs.

Can CollectPII calls be fired in response to multiple trigger events? collect-pii-calls

Yes. Depending on your business need, you may fire CollectPII calls in response to user logging in the app, or purchasing something or lifecycle event or user entering a geofence etc. To sum up, an interaction of user with the app that generates information you would want to use for Profile enrichment.

Can I just fire CollectPII calls in response to all Mobile events? collect-pii-events

Frequency and design of CollectPII calls should be dictated by business needs and shouldn’t be fired blindly as it creates extra load on the DB.