Description -
1. AWS Web Analytics product team uploads AWS blog meta data via classification importer feature in Adobe Analytics (AA). Also we use Classification rule builder feature to automatically classify AWS product pages meta data in AA reporting. Unfortunately these classification data can't be sent to downstream AWS s3 location via Adobe Analytics data feed feature. We have a downstream bigger data lake system where we send hourly data feed from Adobe Analytics. Every time my team works on the classification addition or modification needs to be manually worked by AWS downstream data engineering team to add the same details in their database to bring parity to AA and other system reporting. This is time consuming and repetitive task.
2. There are limited eVars (250) available for Adobe Analytics. Classification is a great feature to separate out concatenated data being passed to an eVar and store individual values in different coulmns associated with that eVar. This feature saves number of eVars to be used for this kind of implementation. Unfortunately AWS Web Analytics team can't utilize this feature because we send hourly data feed to downstream data lake where classification data can't be sent.
How would you like the feature to work - Classification columns (eVars columns) needs to be included in data feed eVar list.
Why is this feature important to you - This feature is important because this will save significant time for AWS data engineering team and also reporting will be in sync automatically.