Hi @m_alcantara  what types of data element are you using? A Web SDK variable or XDM object?

to my knowledge the ECID is implicitly becoming the primary identity if no other identity is set in the identityMap. Hence, as soon as you flag your email as primary identity, it should automatically become a non-primary identity.

In general, the Web and Mobile SDKs can only send data to Experience Event-based datasets, hence you won't see a Individual Profile schema in your Launch XDM data elements UI.   What you can play around with is using Launch server-side and do a POST to an HTTP API source you must set up in AEP. If y...

Hi @KalaivaniL4  by any chance, can you add screenshots? Having a hard time following your setup.

Hi @dymt  I have a client that is reporting data in their workspace that looks like stemming from a news outlet.

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.