You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's not optimal that stored requests have to contain ext.prebid.targeting values for AMP and SDK scenarios. This creates a need to update many DB entries if there's a change (e.g. in how they want deals prioritized). It would be more convenient to have the account-level config store the target settings.
Suggested config:
auction:
truncate-target-attr: 20 // we should move this under targeting with a future major release
targeting:
includewinners: true/false
includebidderkeys: true/false
includeformat: true/false
preferdeals: true/false
alwaysincludedeals: true/false
And, as usual, if the value is seen in both the request/stored-request AND config, request takes precedence.
The text was updated successfully, but these errors were encountered:
It's not optimal that stored requests have to contain ext.prebid.targeting values for AMP and SDK scenarios. This creates a need to update many DB entries if there's a change (e.g. in how they want deals prioritized). It would be more convenient to have the account-level config store the target settings.
Suggested config:
And, as usual, if the value is seen in both the request/stored-request AND config, request takes precedence.
The text was updated successfully, but these errors were encountered: