Commitc0886d3

authored

Update destination-filters.md

1 parent7b0d7bd commitc0886d3Copy full SHA for c0886d3

File tree

-2

lines changed

-2

lines changed

Lines changed: 2 additions & 2 deletions

Original file line number	Diff line number	Diff line change
`@@ -218,9 +218,9 @@ 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 (ex.`properties.test event field`)?
	`221`	+####Can I filter on properties/traits that have spaces in the name (for example,`properties.test event field`)?
`222`	`222`
`223`		`-Unfortunately,properties or traits with spaces in the field name cannot be targeted by Destination Filters at this time. Another option would be tousean[InsertFunction]([url](https://segment.com/docs/connections/functions/insert-functions/)) whereyoucanwrite codethat could take care of such filtering.`
	`223`	`+Destination Filters can't targetproperties or traits with spaces in the field name. As an alternative,use[InsertFunctions](/docs/connections/functions/insert-functions/), which letyou write codeto take care of such filtering.`
`224`	`224`
`225`	`225`
`226`	`226`	`####Can I use destination filters to drop events unsupported by a destination?`

Comments

(0)