Unable to use IDSpecific consent fields in destination Activation

[Ikmo7]

Hi folks,

In my use case, the consent are storing at IdSpecific level which gets updated into profile and able to create segment as well on top of it but not able to use this fields for mapping while activating it for destination. Any other way this can be achieved or anything I am missing here?

Thanks in Advance!

[Rite18]

@Ikmo7 did you check The field must align with the data governance model for a destination?

- Check the destination schema and mapping configuration for the consent data.

- are you getting any error while activating it for destination?

[Parvesh_Parmar]

Hello @Ikmo7 ,

Just adding some extra information.

It’s possible that there might be an issue with the consent policy.

Consent Policy:
Filters the profiles that can be activated to destinations based on your customers’ consent or preferences.

Please check if any consent policy is enabled that might be preventing you from exporting the data.

Manage Data Usage Policies in the UI | Adobe Experience Platform

Kr,

Parvesh

[Ikmo7]

The consent I am storing is at IdSpecific. So when I try to utilize that fields while mapping that field is not be able to choose since that field is a map field.

The respective consent field in attribute looks like below,

[kautuk_sahni]

@Ikmo7 Did you find the suggestions helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!

[_Manoj_Kumar_]

Hello @Ikmo7  There are some guardrails while exporting data to destinations. https://experienceleague.adobe.com/en/docs/experience-platform/destinations/guardrails

Can you share more details on what destination you are exporting this data to?