Maybe open a support ticket in that case

Depends on whether you consider Email to be an identity namespace unique to one specific profile. If so, flag it as primary.   If not, ECID will/should implicitly be used as a primary identity in your request.

Hi @AmarapuramMahesh,   when you disable an HTTP API dataflow in Adobe Experience Platform (AEP), the change should be effectively immediate and the dataflow will stop ingesting new data. While the dataflow itself is disabled quickly, any data that was in transit or buffered before you disabled it m...

Hi @Michael_Soprano    you can specify a different merge policy on audience level. That is why you are seeing a different schema in the third column.      

Hi @Mel  there is no limitation to a single select as far as I know. Users will always have to either manually remove or clear the filters by clicking the clear all link.   Could be a great product idea though if you want to open one.

Hi @tyrese  Since the Version numbers indicate major version changes, it depends on your current integration. If you a starting a new implementation, I would definitely choose the 2.x one. Lower version numbers are typically indicating deprecated functionality that may be outdated and phased out in ...

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?