As @jonathanschwarz also stated, there seem to be a couple of bugs since Adobe's latest release that they are currently working on.As annoying as that may seem, rest assured that they are on it.   What you can do is open a support ticket and get an update and as ETA as soon as it is fixed.

I mean technically you can do whatever you want with the adobeDataLayer, but I think you won't need to. I have seen AEM pages that push all sorts of component show events, ending up with 100+ items in the data layer and never experienced problems with that.  Obviously, you can argue whether all of t...

It's the actual limit of javascript arrays    as I said, I don't see an issue. Tracking of state changes with WebSDK is standard.

Hi @Dmitriy1  which exact opt out cookie are you referring to? The one that gets set through your cookie banner or a global Adobe opt out cookie that is set through the Adobe website?

Hi @dlynch80  please refer to the documentation here (> Attribution).  

Yes

Hi @YutaNa2  can you make sure in a separate freeform table that the utm source (v231) and utm medium (v21) are actually still capturing data as before?

Hi @YutaNa2  can you give more details like which breakdowns are missing? For the UTM sources, are you certain you are actually still capturing them?

Hi @tyrese  only if you are mapping the data layer pushes to any kind of analytics tracking call.   In general, any push to the data layer without triggering a tag (marketing or analytics side) won't do anything to the performance of the website. In theory, you can - had to look it up - push 4,294,9...

Hi @tyrese  I would not care about the number of items in the data layer. That's an array that will likely never reach its maximum length. I would rather be concerned of potentially sending a LOT of billable server calls. Since these calls will likely not happen at the same time, the overall used ba...