Resolving audience loading issues with domain filters

If your audience is hanging or failing to load when using domain-based filters, the issue is likely caused by using certain filter combinations that create performance problems.

Common problematic configuration

The most common cause of audience loading issues is combining these two filter types:

• Domain contains one of - combined with

• Domain contains none of

This combination can cause audiences to hang indefinitely during the loading process due to the complexity of the underlying database queries.

Recommended solutions

Option 1: Modify your domain filters

Replace your current filter setup with a more efficient approach:

1. Change Domain contains one of to Domain is one of

2. Remove the Domain contains none of filter entirely

This modification should provide equivalent results while significantly improving loading performance.

Option 2: Use CRM fields instead

For better performance, consider restructuring your audience criteria to use CRM fields that separate:

• Included companies (positive criteria)

• Excluded companies (handled separately, not as exclusion filters)

This approach loads much faster than domain-based exclusion filters.

Performance best practice

When building audiences, structure your filters using positive inclusion criteria rather than combining inclusion and exclusion filters. This reduces query complexity and improves loading performance across all audience functionality in plays and triggers.