Skip to content

Commit 0c46415

Browse files
committed
more links
1 parent c6fd844 commit 0c46415

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

src/unify/unify-event-filtering.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -17,13 +17,13 @@ Event Filtering is useful when you’re sending a lot of different event types i
1717

1818
Unify Event Filtering works differently from [Destination Filters](/docs/connections/destinations/destination-filters/) in a few important ways:
1919

20-
| | Unify Event Filtering | Destination Filters |
21-
| ---------------- | ---------------------------------------- | --------------------------------------- |
22-
| Where it applies | Unify space | Individual destinations |
23-
| Filter scope | All sources connected to the space | One source for each destination |
24-
| Filter action | Drops entire events | Can drop or modify events and fields |
25-
| Setup | Created through API, visible in Unify UI | Created in UI or API |
26-
| Timing | Before identity resolution | Before events get sent to a destination |
20+
| | Unify Event Filtering | Destination Filters |
21+
| ---------------- | ---------------------------------------------------------------- | --------------------------------------- |
22+
| Where it applies | Unify space | Individual destinations |
23+
| Filter scope | All [sources](/docs/connections/sources/) connected to the space | One source for each destination |
24+
| Filter action | Drops entire events | Can drop or modify events and fields |
25+
| Setup | Created through API, visible in Unify UI | Created in UI or API |
26+
| Timing | Before identity resolution | Before events get sent to a destination |
2727

2828
This helps simplify your setup and reduce noise in profile data without needing repeaters, webhooks, or custom logic.
2929

@@ -42,7 +42,7 @@ As a result, Unify Event Filtering helps you keep profile data clean from the st
4242

4343
## Creating and managing filters
4444

45-
During public beta, managing filters requires a mix of API and Segment UI actions. You'll define and create filters using the Space Filter API, then manage their status and visibility in the Segment app.
45+
During public beta, managing filters requires a mix of API and Segment UI actions. You'll define and create filters using the [Space Filter API](https://docs.segmentapis.com/tag/Space-Filters/){:target="_blank"}, then manage their status and visibility in the Segment app.
4646

4747
To create a filter, use the Space Filter API to write a filtering rule using FQL. The API lets you name the filter, enable or disable it, and delete it. You can create up to 10 filters per space, and any event that matches a filter gets dropped before it reaches Unify.
4848

@@ -73,7 +73,7 @@ Unify Event Filtering is most useful when you want to keep noisy, irrelevant, or
7373
| Drop obvious noise | Start with telemetry, test data, or internal events. |
7474
| Keep it simple | A few targeted filters are easier to manage than multiple, complex filters. |
7575
| Think at the space level | Filters apply to all sources. Write conditions accordingly. |
76-
| Test before enabling | Use the [preview endpoint](https://docs.segmentapis.com/tag/Destination-Filters#operation/previewDestinationFilter) to check filter behavior before turning it on. |
76+
| Test before enabling | Use the [preview endpoint](https://docs.segmentapis.com/tag/Destination-Filters#operation/previewDestinationFilter){:target="_blank"} to check filter behavior before turning it on. |
7777

7878

7979
Unify Event Filtering gives you an early control point for managing the quality of data entering your space. It helps reduce noise, control costs, and improve the accuracy of profile data before any identity resolution takes place.

0 commit comments

Comments
 (0)