To send push notifications and In-App messages with Experience Platform SDK application, a mobile application has to be set up in Adobe Experience Platform SDK and configured in Adobe Campaign.
The section below lists common questions about this synchronization.
For more information on Push or In-App, refer to the following FAQs:
Check out the resources below for more information on the Adobe Experience Platform SDK and Campaign Standard integration:
Yes, Adobe Experience Platform SDK integration is available for both Adobe Campaign Standard and Adobe Campaign Classic. You must install the corresponding Extension via the Data Collection UI to enable the integration.
For more on this, refer to this [page]https://developer.adobe.com/client-sdks/documentation/adobe-campaign-standard).
Refer to the table below to learn more about these capabilities.
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.
The following use cases are supported:
To do so, follow the steps below:
You must configure a CollectPII postback (refer to this page) and implement CollectPII API from SDK (refer to this page).
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.
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.
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.
This is a known issue and happens due to token expiration. You should try login out and in.
Check out the resources below:
You should check the following:
The mobile app should be mapped to the organization unit of the user that needs to create and send push deliveries. User of a child organizational unit can not create a push delivery using an app mapped to the parent organizational unit.
Campaign or program within which the push delivery is created should be mapped to the organizational unit of the user that needs to create and send push deliveries. User of the child organizational unit can not create a push delivery in a campaign or program mapped to the parent organization unit.