Skip to content

Commit eaa8136

Browse files
authored
Merge pull request #4447 from segmentio/volneyvj-patch-1
Update faq.md
2 parents 8bf9e81 + bb4b18a commit eaa8136

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

src/protocols/faq.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -145,6 +145,10 @@ All users with Protocols admin or read-only permissions can view transformations
145145

146146
Transformations introduce advanced logic that at scale may impact performance of client-side libraries. If you are interested in testing new functionality which supports device-mode destination transformations in analytics.js, contact your account rep.
147147

148+
### Are Destination Filters applied before or after my Protocols Transformations?
149+
150+
That depends. If you are working with source-level Transformations, the Protocols conversion will come first. If you are dealing with a destination scoped transformation (which is set to only impact data going to a specific destination), Destination Filters will be applied prior to Protocols Transformations.
151+
148152
### Why do I need Protocols to use transformations?
149153

150154
Transformations are but one tool among many to help you improve data quality. Segment highly recommends that all customers interested in improving data quality start with a well defined Tracking Plan. The Tracking Plan serves as a roadmap for how you want to collect data. Without a clear roadmap, it's nearly impossible to build alignment around how transformations should be used to improve data quality, leading to more data quality issues than it solves.

0 commit comments

Comments
 (0)