Destination Filters — filter by authorization

Destination filters can now be set on a single authorization, not just on a whole integration. Until now, every job of an integration got the same suppression list, whichever downstream account it delivered to.

What's new

• Keep an audience out of one downstream account without filtering the others — for example, a second email account for a region where open tracking is turned off, or an ad account managed by an agency.
• New jobs created on a filtered authorization are protected from their first run, with no per-job setup.
• Apply the filter to every integration using the authorization, so integrations added to it later are covered too, or to one integration only.
• Filters set on the integration and on an authorization combine. Adding one never weakens another.
• A job's filters show wherever you view the job, including ones it inherits from an authorization.

How it works

Open an integration's summary page with Manage Integration. Each authorization it delivers through now has its own filter below the integration-wide one. Changes take effect on each job's next run.

See Destination Filters for setup and permissions.