Hi Team,
We have a Streaming Data source connection of Adobe Analytics into CDP. Data has been ingesting in CDP every hour since last year (no WebSDK). But today the data has stopped ingesting. There seems to be no error message in UI, in workflows > Target Dataset is also correctly mapped, in Adobe Analytics, the required report suite is also showing the data for the day.
I checked in CDP > Monitoring, selected streaming header > there I could see the Batch IDs and Record count of Batch of every hour for today, but the same is not populating in Dataset. Please suggest. Thanks.
Solved! Go to Solution.
Views
Replies
Total Likes
Hi @mansibedi - Seems you have set up a bacth ingestion for adobe analytics (since you leveraged AA native connector set up in platform) and it is not streaming ingestion, for your information. Also, since it is batch and event data, request you to check the same in "Batch end-To-end" tab and see if you have any batch ingestion error.
Also, your second screenshot indicates that data are ingested as streaming for profile related datasets but adobe analytics comes as event related data. So request you to check the exact batch error from adobe analytics source and sorted out the issue.
Hi @mansibedi - Seems you have set up a bacth ingestion for adobe analytics (since you leveraged AA native connector set up in platform) and it is not streaming ingestion, for your information. Also, since it is batch and event data, request you to check the same in "Batch end-To-end" tab and see if you have any batch ingestion error.
Also, your second screenshot indicates that data are ingested as streaming for profile related datasets but adobe analytics comes as event related data. So request you to check the exact batch error from adobe analytics source and sorted out the issue.
@jayakrishnaaparthasarathy - thank you for the response. The ingestion we have set up for Adobe Analytics is a Streaming ingestion itself. due to unavailability of Adobe Edge currently, it is ingesting every 1 hour as batch data as you suggested.
Seems like there was a technical issue from the Adobe side, and was restored when we raised a ticket on Adobe support regarding this.
Thanks.
Views
Replies
Total Likes