Adobe Journey Optimizer

DiegoGa8 · 7/2/25

I’m trying to implement suppression logic inside a Journey in AJO for cases where a user enters the journey before being flagged as suppressed.

I have a custom field group with a boolean field called isSuppressed, which I added to a profile-enabled schema. The ingestion works fine. I can see the field correctly populated in the Unified Profile.

The problem is: I need to use a Condition node to check isSuppressed == false before an email is sent. But when I try to configure the condition, the field does not appear in the list of available profile fields. I also tried using expression mode with profile.isSuppressed == false, but it returns a “field not found” error.

Using an audience is not a viable workaround because the profile might enter the journey before it’s suppressed, and audience reevaluation won’t remove them from the journey once they’re in.

Is there any way to expose this custom field so it can be used in journey conditions? Or does it need to be part of a specific schema or field group to be accessible?

Thanks in advance!

Mayank_Gandhi · 7/2/25

@DiegoGa8 A field that lives in Unified Profile only becomes selectable in the journey after the schema (or a field-group built from that schema) is declared in the AJO data source. Until the field-group is added, the picker and the expression engine do not know the attribute, so you get the field not found error you saw. Edit the built-in Adobe Experience Platform data source (or create a new one). Click + Field group and pick the profile-enabled schema that contains isSuppressed.
Once the field-group is in place your isSuppressed flag can be evaluated in real time for every profile that reaches the node.

View solution in original post

Mayank_Gandhi · 7/2/25

@DiegoGa8 A field that lives in Unified Profile only becomes selectable in the journey after the schema (or a field-group built from that schema) is declared in the AJO data source. Until the field-group is added, the picker and the expression engine do not know the attribute, so you get the field not found error you saw. Edit the built-in Adobe Experience Platform data source (or create a new one). Click + Field group and pick the profile-enabled schema that contains isSuppressed.
Once the field-group is in place your isSuppressed flag can be evaluated in real time for every profile that reaches the node.

DiegoGa8 · 7/3/25

Thank you! This was it.

ap95 · 8/14/25

@Mayank_Gandhi , @ReenaJohn Would this work for Read Audience based Journey? as I only see few attributes to select in conditions. Is there a way to see all profile attributes and use them for conditions instead of relying on "InAudience" based condition in journey activity?