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
| auctionKeyMaxChars |integer| Specifies the maximum number of characters the system can add to ad server targeting. |
707
-
| alwaysIncludeDeals |boolean| If [enableSendAllBids](#setConfig-Send-All-Bids) is false, set this value to `true` to ensure that deals are sent along with the winning bid |
706
+
| auctionKeyMaxChars |Integer| Specifies the maximum number of characters the system can add to ad server targeting. |
707
+
| alwaysIncludeDeals |Boolean| If [enableSendAllBids](#setConfig-Send-All-Bids) is false, set this value to `true` to ensure that deals are sent along with the winning bid |
| allBidsCustomTargeting | boolean | Set to true to prevent custom targeting values from being set for non-winning bids |
711
+
| allBidsCustomTargeting | Boolean | Set to true to prevent custom targeting values from being set for non-winning bids |
712
+
| lock | Array of Strings | Targeting keys to lock |
713
+
| lockTimeout | Integer | Lock timeout in milliseconds |
712
714
713
715
{: .alert.alert-info :}
714
716
Note that this feature overlaps and can be used in conjunction with [sendBidsControl.bidLimit](#setConfig-Send-Bids-Control).
@@ -910,6 +912,27 @@ config.setConfig({
910
912
911
913
By default, non winning bids will have custom tageting values concatenated to the winning bid's custom targeting for the same key. The `allBidsCustomTargeting` setting is a boolean that, when set to `false`, prevents custom targeting values from being set for non-winning bids. This can be useful if you want to ensure that only the winning bid has custom targeting values set.
912
914
915
+
#### Details on the lock and lockTimeout settings
916
+
{: .no_toc }
917
+
918
+
When `lock` is set, targeting set through `setTargetingForGPTAsync` or `setTargetingForAst`
919
+
will prevent bids with the same targeting on any of the given keys from being used again until rendering is complete or
920
+
`lockTimeout` milliseconds have passed.
921
+
922
+
For example, with the following:
923
+
924
+
```javascript
925
+
pbjs.setConfig({
926
+
targetingControls: {
927
+
lock: ['hb_adid'],
928
+
lockTimeout:2000
929
+
}
930
+
});
931
+
```
932
+
933
+
calling `pbjs.setTargetingForGPTAsync()` will "lock" the targeted `hb_adid` until its slot renders or 2 seconds have passed, preventing subsequent calls to `setTargetingForGPTAsync` from using bids with the same `hb_adid` in the meanwhile.
934
+
If using standard targeting `hb_adid` is unique for each bid, so this would have the effect of preventing the same bid from being used for multiple slots at the same time.
0 commit comments