is there a way to stop evaluating an audience, but still have it available for destination and to use it in other audiences

[itsMeTechy]

Can you please let me know if there is an option to create an audience as batch evaluation and publish it, wait for the audience evaluation job to run, once it is evaluated one time, is there a way to stop further evaluation but still have the audience available for activation to destination, and use it in other audiences.

[Karuppiah_Sakthivel]

In AEP:

• If an audience is published, it is automatically evaluated on every batch run.
• There is no “freeze audience” or “evaluate once” mode.
• AEP must continually recalculate audiences to keep Profile Store and destinations accurate.
• Adobe does not allow disabling evaluation while keeping the audience “active,” because it could generate inconsistent or stale profile results.

So you cannot stop evaluation and still use the audience for activation or building other segments.

You can do

• Snapshot the audience into a dataset, then build a new static audience
• Activate the audience once.
• Export the audience qualified profiles into a dataset.
• Create a new dataset-based audience (static list).

This "freezes" the result — but it requires manual or workflow processing.

[Sukrity_Wadhwa]

Hi @itsMeTechy,

Was the given solution helpful to resolve your query or do you still need more help here? Do let us know. In case the given solution was helpful, then kindly choose it as the 'Correct Reply'.

Thanks!

[itsMeTechy]

Thanks for the details. 

As in our use case we want to run campaign to set of profiles repeatedly in certain time intervals and for this purpose only I was looking for static audience. So we achieved it by creating another audience using campaignid after the campaign was run once in AJO. So this second audience though gets evaluated daily but it wont qualify or disqualify any profiles, similar to static audience but active.

[itsMeTechy]

We did evaluated the import audience feature, but as we use dataset precedence merge policy the new schema/dataset created for import audience is not part of merge policy which requires change in merge policy configuration as well. so we avoided this option. but this option does work as expected for this use case.