Add FAQ about destination filters #6634
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ashton-huxtable
requested review from
forstisabella
and removed request for
a team
src/connections/test-connections.md
Outdated
Comment on lines
67
to
69
| #### Why are my destination filters being ignored? | ||
|
|
||
| Events passed into the Event Tester bypass destination filters. Destination filters are applied to events as they are sent to specific destinations based on your configuration. However, the Event Tester is designed to help you troubleshoot your Sources, their configuration, and their downstream destinations by showing a sample of the data available. It allows you to check that data is being sent, and that it's in the correct format without the filters being applied. This means that when you use the Event Tester, you're seeing the data before any destination filters or other processing rules are applied, providing a clear view of the raw event data as it comes from the source. |
There was a problem hiding this comment.
"based on your configuration" - is this referring only to the destination filters, or does this refer to all tools that someone could enable to impact delivery (integrations object, consent management, etc.?)
There was a problem hiding this comment.
Destination filters would only apply to events that are passed to the destination, so this would be regardless of other tools that impact how data is sent downstream. Reviewing it, I can see that this line is a little confusing so we could remove the 'based on your configuration' rather than explaining further to keep it simple.
forstisabella
approved these changes
Jun 13, 2024
|
Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
We occasionally get questions about why the event tester is not accounting for destination filters. The event tester bypasses these filters and is not designed to test for them. I added an FAQ to the docs to cover this topic.
Merge timing
Related issues (optional)
n/a