identityLink Id System : fix 3p call to always use tcf consent type 4 #10778
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
|
Hi! @smenzer can you please take a look? Tnx |
ChrisHuie
changed the title
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.
Type of change
Description of change
identityLinkIdSystem - Liveramp - bug fix. Fix 3p call to always use tcf consent type 4.
We have removed logic where we were checking tcfPolicyVersion since back in a days we needed to know which version to send to our api because of backward compatibility. Since our back-end now only allows ct=4 parameter we need to change this, since tcfPolicyVersion been increased (now is 4) so now because of this logic, we always set ct parameter to 1, which is incorrect and causes error on http request.