If you are someone who comes from a background of data collection for adobe analytics, adobe target and AAM. the term “AEP data collection” may overwhelm you.
We users of adobe marketing/analytics cloud of products have historically been implementing/using “product specific” data collection library and clearly made this work at an enterprise level.
The all new “AEP Data collection” hopes to be faster, more flexible and distribute events on edge networks where it can be enriched, transformed, and distributed to Adobe or non-Adobe destinations
This post will help you visualise the AEP Web SDK data collection and in the future posts will cover details of each of the capabilities within AEP Data Collection
The Concept of Data Collection
The concept of data collection for adobe marketing and analytics suite of products has also been tied to a certain library/method from the time of inception.
While this is all good and worked great for us so far, the client (browser) bears the brunt of loading all of these without affecting the page load and user experience.
The all new Data collection service offers us an agnostic way of data collection, independent of who will end up using the data. This concept helps us design “Single Data Model” which will form the foundation for all the data consumers within Adobe and Non Adobe destinations.
Some of the features of the new data collection include
- Ability to consolidate Data Collection for all adobe experience cloud products (Fewer network requests)
- 70% lighter Code – Web SDK
- Forward data to Non Adobe applications (Event Forwarding)
- Server to server API for use cases where data from internal apps or secure apps are not collected on client side.
Data Collection – Using AEP Data collection services
Here’s a short visualisation of data collection features available with Adobe Experience Platform.
AEP Data Collection Technologies
Reference and further reading
Some help/documentation articles to get started