Destination filters

With filters, you have the possibility to define some conditions. As a result, some events will be sent and some don't, according to your conditions.

Simple filter

For Events Destinations

Use the drop down to select the property on which you want to filter, then select the operator and the value to filter on.

Available operators:

• is

• isn't

• match regex (see also 'About regex' section)

• doesn't match the regex (see also 'About regex' section)

• contains

• doesn't contain

• starts with

• doesn't start with

• ends with

• doesn't end with

• exists

• doesn't exist

• is empty

Advanced filter

For Events Destinations

An "Advanced" filter can be used when a simple one is not sufficient.

The simple filter will be automatically transcribed into the advanced one, but the opposite is not possible, as advanced functions are not supported by the simple filter.

From simple filter...

...to advanced filter

With Advanced filter, you can use formula and advanced functions, simply click on the button on the right of the field to see all available functions.

Supported operators:

• = (equals to)

• > (smaller than)

• < (greater than)

• != (different from)

Supported conditions:

• AND

• OR

Supported functions:

Supported transformation functions - Data cleansing

Always use " " to enter a value in advanced mode. All values entered without " " will be treated as a number.

About Regex

Both simple and advanced filter can manage regex:

To know how to build a regex, please refer to regular expression documentation.

Consent filter

For Events Destinations

For clients using our CMP module: simply select the appropriate category in the drop down.

For clients using an external CMP: Simply enter the value as it is collected in the "user.consent_categories" of your server side events.

Example:

For Audience Destinations

The Consent filter is also available on Audience destinations, under the Filters tab. Select the consent category in the drop down to send only the users who granted it.

On Audience destinations, the Consent filter relies on the CDP variable user_privacy_categories. If this variable is not used, you won't be able to filter on consent directly in the Audience Destination.

If you use the Data Activation Legacy destination, you must map the server side variable user.consent_categories to the Data variable user_privacy_categories for the filter to work.