Per 18.5 May 2018 release, we can now create and manage dynamic reports based on custom profile data created during the profile resource extension. But these data are not getting passed to Adobe Analytics for campaign reporting. From OOOB integration procedure, all the dimensions are passed to Adobe Analytics except these custom profile attributes. I understand this can be achieved by modifying the ACS & AA integration for Technical workflows.. Is there any documentation to refer on how to do it?
18.5 - May 2018 release
GDPR: Core Service Integration
Privacy Core Service Integration allows you to automate your GDPR requests in a multi-solution context through a single JSON API call. GDPR requests pushed from the Privacy Core Service to all Experience Cloud solutions are now automatically handled by Campaign. For more information, refer to the detailed documentation.
Push improvements – detailed delivery feedback
Adobe Campaign now provides the ability to receive detailed feedback (sending logs et exclusion logs) on push messages from the providers (APNS/GCM) via MCPNS. For more information, refer to the detailed documentation.
Delivery logs extension
Delivery logs extension allows you to extend sending logs with profile data and segment code coming from workflows. This information can then be used in Dynamic Reports, and lets you keep a snapshot of some information at the sending time of a delivery. There are 2 more use cases :
Export extended broadlogs with "frozen" data: As a marketer, I would like to export all the profiles where segment code equals "A" (coming from the workflow engine).
Segmentation on "frozen" data: As a marketer, I would like to retarget all profiles who have won 1000 loyalty points since the last sending or where segment code was equal to “A”.
This feature allows you to create and manage reports based on custom profile data created during the profile resource extension. You can breakdown reports by profile attribute such as loyalty program, preferred channel, etc. For more information, refer to the detailed documentation.