Targeting: Add configurable targeting prefix #4355
Open
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 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 changes
✨ What's the context?
#3094
🧠 Rationale behind the change
According to 3094 some publishers would like to have a different set of ad targeting prefixes rather than
hb_.In scope of the current change we add a possibility to configure prefix in:
ext.prebid.targeting.prefixaccount.targeting_prefixIf both
ext.prebid.targeting.prefixandaccount.targeting_prefixconfiguration value are present, prefer the one from the request. The length of prefix is controlled bysettings.targeting.truncate-attr-chars.🧪 Test plan
New functionality is covered by
TestFindTargetingByKey,TestGetTargetDataPrefixandTestTargetingCacheRequestPrefix