add context about spaces in trait/property names

Author: spencerattick

src/connections/destinations/destination-filters.md

@@ -218,6 +218,11 @@ You must have write access to save and edit filters. Read permission access only
 
 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.
 
+#### Can I filter on properties/traits that have spaces in the name (ex. `properties.test event field`)? 
+
+Unfortunately, properties or traits with spaces in the field name cannot be targeted by Destination Filters at this time. Another option would be to use an [Insert Function]([url](https://segment.com/docs/connections/functions/insert-functions/)) where you can write code that could take care of such filtering.
+
+
 #### Can I use destination filters to drop events unsupported by a destination?
 
 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).