Destination Filters

Destination filters are a powerful feature that allows you to exclude specific audiences from workflows, effectively creating suppression lists for your data exports.

Overview

When configuring export workflows, you may need to exclude certain users from being sent to destinations. Common use cases include:

Suppression Lists: Exclude users who have opted out of marketing communications
Compliance: Exclude users from specific regions due to data privacy regulations
Segmentation: Exclude internal employees or test users from customer campaigns
Campaign Management: Exclude users who have already converted or are in other active campaigns

Destination filters provide a flexible way to handle these scenarios without modifying your primary audience segments.

How Destination Filters Work

Destination filters operate as exclusion lists that are applied during the export process. When a workflow runs:

The primary audience is selected based on your segment configuration
Destination filters are applied to exclude users who match the filter criteria
Only users who pass through all filters are sent to the destination

The filtering happens at export time, ensuring that your base segments remain unchanged while giving you granular control over which users reach each destination.

Configuration

Basic Setup

Destination filters are configured within individual workflow setup. The filter configuration appears as an extra feature when managing a workflow.

To add a destination filter follow the following steps.

Navigate to Data Pipeline > Jobs, then click on + Create New Job.
Find the workflow you'd like to add the destination filter to, click the ... and then click on Manage Integration.

Under Exclude specific audiences from this integration?, turn on All jobs of this integration.

Choose the audience to use as a destination filter.

Finally, click Save Changes to save the destation filter audience.

Filtering by Authorization

A filter set for All jobs of this integration applies to every job of that integration, whichever downstream account it delivers to. When only one account should hold an audience back — for example, a second email account for a region where open tracking is disabled, or an ad account managed by an agency — set the filter on that account's authorization instead.

Each authorization the integration can deliver through is listed below the integration-wide filter, with its status.

Turn on the switch next to the authorization and choose the audience to exclude.
Choose where the filter applies:
- All integrations using this authorization (the default) — every job delivering through this authorization, including jobs of integrations added to it later.
- This integration only — only jobs of the integration you are viewing.
Click Save Changes.

Switching between the two options moves the filter rather than copying it.

A new export job created on a filtered authorization is filtered from its first run, with no per-job setup.

Filter Logic

Destination filters use exclusion logic:

If a user exists in ANY of the selected filter audiences, they will be excluded from the export
Multiple filters are combined with OR logic (user excluded if they match any filter)
Filters are applied after the primary audience selection
Integration-wide and authorization filters combine: a user in any filter that applies to the job is excluded. Adding a filter never replaces or weakens another
Changes take effect on each job's next run

Where Applied Filters Show

A job's filters are shown wherever the job is viewed, whether they were set on the integration or inherited from an authorization: a badge in the jobs list, a notice in the job wizard, and, on the job's configuration tab, the name of every audience held back from it.

Permissions

Managing destination filters requires the Workflow Rule Manage role. Setting a filter on an authorization also requires a role that can see authorizations, such as Authorizations View or Jobs View. See Granular Permissions.

Example Configuration

For a Facebook Audience Export with destination filters:

Primary Audience: "High-Value Customers" (1,000 users)
Destination Filters:
- "Opted Out Users" (50 users)
- "Internal Employees" (25 users)
- "Recent Converters" (100 users)

Result: The export would send approximately 825-875 users (depending on overlap between filter segments) to Facebook, excluding anyone who appears in any of the filter audiences.

Supported Workflows

Destination filters are available in workflows that export a Lytics audience.

Common workflows that support destination filters include:

Facebook Audience Export
Google Ads Customer Match
Braze Export
HubSpot Export
Salesforce Export
And many other audience export integrations

Best Practices

1. Naming Convention

Use clear, descriptive names for your filter audiences:

✅ "Email Unsubscribed Users"
✅ "GDPR Opt-Out - EU"
✅ "Employees and Test Accounts"
❌ "Filter 1"
❌ "Exclusions"

2. Segment Maintenance

Regularly review and update your filter segments
Ensure filter segments are actively maintained and current
Document the purpose and criteria for each filter segment

3. Filter Overlap

Consider overlap between multiple filters to avoid over-exclusion
Use segment analysis tools to understand the combined impact of multiple filters
Test filters with smaller audiences before applying to large campaigns

4. Compliance Filters

For compliance-related filters:

Create dedicated segments for regulatory opt-outs (GDPR, CCPA, etc.)
Implement automated processes to keep compliance filters up-to-date
Document the legal basis for each compliance filter

5. Performance Considerations

Keep filter segments optimized for performance
Avoid using overly complex filter segments that might slow export processing
Monitor export job performance when using multiple filters

Troubleshooting

Common Issues

1. Unexpected Export Sizes

Symptom: Export contains fewer users than expected
Cause: Destination filters may be excluding more users than anticipated
Solution:

Review filter segment definitions and sizes
Check for unintended overlap between primary audience and filters
Verify filter segment criteria are correct

2. Users Still Receiving Communications

Symptom: Users who should be excluded are still receiving messages
Cause: Filter segments may not be up-to-date or properly configured
Solution:

Verify filter segments are actively maintained
Check that the export workflow is properly configured with filters
If the destination account is reached through more than one authorization, check that the filter is set on the authorization the job actually uses, or on the integration as a whole
Ensure filter segments include the problematic users

3. Export Job Failures

Symptom: Export jobs fail when filters are applied
Cause: Filter segments may be invalid or too large
Solution:

Verify all filter segments exist and are accessible
Check filter segment sizes and complexity
Review export job logs for specific error messages

Validation

Before deploying destination filters in production:

Test with Small Audiences: Validate filter behavior with small test segments
Verify Exclusions: Manually verify that known test users are properly excluded
Monitor Initial Runs: Closely monitor the first few production exports
Validate Metrics: Ensure export metrics align with expectations