Skip to content

Commit f132bbe

Browse files
authored
Apply suggestions from code review
1 parent e122a2b commit f132bbe

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/connections/destinations/destination-filters.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -68,7 +68,7 @@ The following examples illustrate common destinations filters use cases:
6868
* [Remove internal and test events from production tools](#remove-internal-and-test-events-from-production-tools)
6969
* [Sample a percentage of events](#sample-a-percentage-of-events)
7070
* [Drop events](#drop-events)
71-
* [Only send event with userId](#only-send-events-with-userid)
71+
* [Only send events with userId](#only-send-events-with-userid)
7272

7373
### PII management
7474

@@ -111,7 +111,7 @@ Using the [destination filters API](https://docs.segmentapis.com/tag/Destination
111111

112112
### Only send events with userId
113113

114-
You may only want to send some events downstream to your destinations if they contain a `userId`. You won't be able to configure a filter like that in the Destination Filter UI, but you can use the [Public API](https://docs.segmentapis.com/tag/Destination-Filters/){:target="_blank"} to achieve this. Here is an example of how you might format such a request:
114+
Use the [Public API](https://docs.segmentapis.com/tag/Destination-Filters/){:target="_blank"} to only send events to your destination if they contain a `userId`. Here's an example of how you might format this request:
115115

116116
```json
117117
{

0 commit comments

Comments
 (0)