This repository was archived by the owner on Apr 1, 2025. It is now read-only.
DWEB-43 Add support for nested property blacklisting for fb pixel#34
Open
vjnathe-webonise wants to merge 2 commits intomasterfrom
Open
DWEB-43 Add support for nested property blacklisting for fb pixel#34vjnathe-webonise wants to merge 2 commits intomasterfrom
vjnathe-webonise wants to merge 2 commits intomasterfrom
Conversation
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What does this PR do?
Add support for nested property blacklisting for fb pixel
Are there breaking changes in this PR?
No.
Any background context you want to provide?
NA
Is there parity with the server-side/android/iOS integration components (if applicable)?
The problem is that Facebook will also detect PII violations for properties in objects nested within the Properties object but the Blacklist PII Properties setting does not allow for blacklisting at this level.
Does this require a new integration setting? If so, please explain how the new setting works
No.
Links to helpful docs and other external resources
NA