Hi Team,
As per this KB Article currently streaming ingestion support up to 1MB of Experience Data Model (XDM) message. Can somebody help me understand what all things contribute to the size of the message? For example in a WebSDK ingestion, is it the entire XDM JSON object in the request payload including the XDM keys and values passed in it or is it calculated using just the values passed against XDM keys? Does anything additional to the XDM object like meta, query, events[].query, events[].data objects in below screen shot also contribute to this size?
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Thanks for the responses team. I believe it will be better understood with some end to end testing and monitoring the payload total and split sizes on every stage of ingestion. I'll spare some time in the coming weeks to test it in coming weeks and post the results here.
Cheers!
Views
Replies
Total Likes
I think this question would be better suited in the AEP forum since this corner here is more for tag management aspects.
@Harveer_SinghGi1 given link is for streaming ingestion on WebSDK, my understanding is that the question is for WebSDK , where data goes to EdgeNetwork / Kafta pipeline before going to the data lake - my experience it will hold only payload which is mapped to the data stream, not everything
@Harveer_SinghGi1 Did you find the suggestions helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!
Views
Replies
Total Likes
Thanks for the responses team. I believe it will be better understood with some end to end testing and monitoring the payload total and split sizes on every stage of ingestion. I'll spare some time in the coming weeks to test it in coming weeks and post the results here.
Cheers!
Views
Replies
Total Likes
Views
Likes
Replies