In our Google setup we are getting huge blobs in the webpage context which causes the our page_view table to become extremely big (as we are unnesting the webpage context we get duplicates).
The picture below shows three events that happens in the same session. It looks like for each event a new id gets appended. Would it make sense to always return the latest value? I think I need some help in understanding what is happening here.
The effect of this is that our page_view model gets extremely big and throwing many duplicated page view events since it recognizes several UUIDs in the webpage context
Nothing immediately springs to mind unfortunately @brajjany
I think we’d need to see the initialisation code and an example of an event track which leads to this behaviour, I’ve certainly never seen anything like this before.
I’ll ask a couple of colleagues too in case they have any ideas!