Accessing the Consent fields in the Condition Statement | Community
Skip to main content
Level 4
April 18, 2025
Solved

Accessing the Consent fields in the Condition Statement

  • April 18, 2025
  • 1 reply
  • 491 views

Hello all, 

So I'm creating a Journey that's using a Unitary event to start the Journey. Once the Journey starts, there's a 2 day wait and then I need to run a condition activity to confirm if the profile has consent to send an email. 

 

When trying to configure the condition - it only maps to the Prospect schema. Wondering if this is something that OOTB, or can it be changed so I can access the Core profile table?

 

 

 

Best answer by SatheeskannaK

@montezh2001 You've got a custom consents object set up in the Prospect profile. That's why you're seeing the Prospect schema consents object included via the datasource. You can configure to choose OOTB fields. If you'd prefer to use the out-of-the-box consent object, just choose it from the ExperiencePlatform datasource (administration -> configurations -> datasources -> ExperiencePlatform -> ProfileFieldGroup) to display it in the journey condition activities. No matter which consent object you go with, just ensure it's been utilized to obtain customer consent.

1 reply

SatheeskannaK
Community Advisor
SatheeskannaKCommunity AdvisorAccepted solution
Community Advisor
April 19, 2025

@montezh2001 You've got a custom consents object set up in the Prospect profile. That's why you're seeing the Prospect schema consents object included via the datasource. You can configure to choose OOTB fields. If you'd prefer to use the out-of-the-box consent object, just choose it from the ExperiencePlatform datasource (administration -> configurations -> datasources -> ExperiencePlatform -> ProfileFieldGroup) to display it in the journey condition activities. No matter which consent object you go with, just ensure it's been utilized to obtain customer consent.

Thanks, Sathees
Level 2
April 22, 2025

@satheeskannak  - Thank you. This works.