Max complexity allowed in audience building

[NickMannion]

Hi Adobe Community,

I got an error while building an audience saying that "this column exceeds allowed complexity. Please simplify or remove" (see below). Has anyone else experienced this and if so, any ideas on how to fix this? The data that I am using is event data. Would I be able to get around this if I converted it into attribute data.

Thanks,

Nick

[Tof_Jossic]

@NickMannion Not necessarily, generally speaking (although not precisely documented) I think the system enforces "Audience Complexity" constraints to ensure audience definitions are optimal for efficient evaluation by the segmentation job. 

Is your definition maybe using nesting or grouping more extensively than other audiences?

Also, try and replicate this after opening the developer tools in Chrome, you 'may' be able to spot additional details about the error.

[_Andy_]

@Tof_Jossic Have audience complexity constraints in AEP changed over time?

We have an audience that was created with 10 rules in March 2024 with no errors, when trying to edit audience today we are now seeing this error.

[NickMannion]

Hi @Tof_Jossic , how do I open the developer tools in Chrome? 

[Tof_Jossic]

[Parvesh_Parmar]

Hi @NickMannion ,

We encountered a similar issue while building a condition, where an error appeared stating that the query string length exceeded the allowed limit. I don't recall the exact character limit, and unfortunately, we couldn’t find it documented anywhere.

As @Tof_Jossic mentioned, there seems to be a limitation that isn’t clearly documented—it might be the same case for you.

We were able to successfully build the audience using Data Distiller, where more complex conditions can be handled more easily. If possible, I’d recommend trying to build the audience there and defining your condition through Data Distiller.

You can find the documentation on how to build audiences using Data Distiller in Adobe Experience Platform.

Hope this helps!

Kind regards,
Parvesh

[NickMannion]

Thanks @Parvesh_Parmar I'll check this out

[kautuk_sahni]

@NickMannion Just checking in — were you able to resolve your issue?
We’d love to hear how things worked out. If the suggestions above helped, marking a response as correct can guide others with similar questions. And if you found another solution, feel free to share it — your insights could really benefit the community. Thanks again for being part of the conversation!