Hi @krp328603 there are limits to what certain downstream destinations will accept. I don’t know the limits off top of my head but we’ve ran into this issue with sending to Acv8

@GigiCotruta  ok, one more thing I want to check. Within your datastream, do you have personalization destinations enabled? (see below) Reason I ask this, is within the documentation I see the following:Enables Custom Personalization for this datastream. When the Web SDK or Edge Network API sends d...

@GigiCotruta those profile attributes that you exported to custom pz destination, are they available on the edge in the profile, if you look in the UI?

Hi @ShivaniMa4  is your dataset that these are going to, enabled for profile?

Hi @GigiCotruta  I think maybe you are needing this documentation? Look up edge profile attributes in real-time | Adobe Experience Platformor potentially this curl: curl --location 'https://platform.adobe.io/data/core/ups/models/Profile/edge/entities?schema.name=_xdm.context.profile&entityId={{infoh...

hi @SantoshRa5  We have just done it in the past by updating the display name to have the prefix of "Do Not Use-"

Hi @god_prophet If you are just trying to activate down to AC Classic, the native connection should be enough. If you require more of a custom solution, you may want to go the s3 path. 

@SantoshRa5 As of now, this is still not possible at the schema level. We can disable the datasets that feed the schemas, but the schema itself can only be marked as un-usable

Hi @GigiCotruta  I can't find the exact documentation, but I believe you'll have to add the permissions to write to the dataset via the Admin Console. There should be an option to manage datasets within the product profile if i'm remembering correctly.

Hi @Michael_Soprano I believe the answer to this is yes, but it may not be recommended. If the merge policies are different - the population of Audience A may not align with that of Audience B from my understanding. Causing potential stitching issues.