Breadcrumbs

Data Filters

Data Filters

Data Filters let you restrict a sync to only import records that match specific field values in the source data. Each filter defines a path into the record and an expected value — only records where all configured filters match are imported. Records that fail any filter are skipped.

Without any filters configured, all incoming records are imported. This is the default.

Which integrations use this

Data Filters are currently available on:

  • Genesis — filter exhibitors by source-system fields (for example, status equals active)

  • A2Z Exhibitors — filter booths by source-system fields (for example, statusDescription equals Occupied to skip reserved or cancelled booths)

  • HubSpot — filter contacts and companies by property values (for example, properties.lifecyclestage equals customer)

How to configure

The setting appears under Data Filters in the entity's settings section of the relevant integration's configuration page. You can add as many filter rows as needed using the Add Filter button.

Each filter row has two fields:

Field

Description

Example

Filter Path

A dot-separated path to the field inside the source record.

status, category.id, statusDescription

Filter Value

The value the field must equal for the record to pass. Text and number fields require an exact match; for true/false fields, see the note below.

active, 123, Occupied, true

All filters are evaluated together — a record must match every filter to be imported. To remove a filter, click Remove on that row.

Filtering on a true/false field

When the source field holds a true/false value, enter true or false as the Filter Value — the natural word. Alternative representations are also accepted (case-insensitive):

  • True: true, 1, yes, on

  • False: false, 0, no, off

Any other value matches neither. Text and number fields are unaffected and continue to match by exact string comparison.

Behaviour summary

Filters configured

Record matches all filters

Result

None

(any)

Record proceeds through the pipeline

One or more

Yes

Record proceeds through the pipeline

One or more

No

Record skipped with reason settings

Data Filters vs Category Mapping

Both settings can skip records, but they're used for different things:

  • Category Mapping decides whether an incoming category is recognised, and what ExpoPlatform category it becomes. Use it when you want to translate categories or exclude records with unmapped categories.

  • Data Filters decides whether the record should be imported at all, based on any field(s) in the source data. Use it to filter by status, booth type, lifecycle stage, or any other source-system attribute that isn't a category.

The two work together — a record has to pass Data Filters and have a resolvable category to be processed.

HubSpot: filters vs event scope

For HubSpot integrations, note that filtered-out records are skipped, not unlinked. Data Filters determine which records get imported, but they don't determine which records belong to the event — that's the job of the HubSpot Event Scope setting. See the HubSpot integration page for details.