You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/connections/destinations/destination-filters.md
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -218,6 +218,11 @@ You must have write access to save and edit filters. Read permission access only
218
218
219
219
Use the destination filter tester during setup to verify that you're filtering out the right events. Filtered events show up on the schema page but aren't counted in event deliverability graphs.
220
220
221
+
####Can I filter on properties/traits that have spaces in the name (for example,`properties.test event field`)?
222
+
223
+
Destination Filters can't target properties or traits with spaces in the field name. As an alternative, use[Insert Functions](/docs/connections/functions/insert-functions/), which let you write code to take care of such filtering.
224
+
225
+
221
226
####Can I use destination filters to drop events unsupported by a destination?
222
227
223
228
The check for unsupported events types happens before any destination filter checks. As a result, Destination Filters can't prevent unsupported event type errors. To filter these events, use the[Integrations Object](/docs/guides/filtering-data/#filtering-with-the-integrations-object).