Add Privacy Config feature to control ad attribution reporting #3506
+92
−13
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.
Task/Issue URL: https://app.asana.com/0/0/1208638248015576/f
Tech Design URL:
CC:
Description:
Adds the ability to use remote config to control
AdAttributionPixelReporter
and whether the token is added as parameter.Steps to test this PR:
⚠️ Device is required to fully test this change. Attribution is not available on simulator.
https://www.jsonblob.com/api/1301173210350215168
. Put app in the background and reactivate.includeToken
setting tofalse
in the linked configuration json file or remove setting object completely, verify attribution pixel is fired without token parameter.Definition of Done (Internal Only):
Copy Testing:
’
rather than'
Orientation Testing:
Device Testing:
OS Testing:
Theme Testing:
Internal references:
Software Engineering Expectations
Technical Design Template