Adzerk has added support for "multiple winners" for each placement on an ad request. There are a LOT of use cases for this, and there is a LOT that goes on under the covers to make it work, but suffice it to say that each placement has an optional count parameter that indicates the maximum number of winners it wants. Each decision returned then has zero or more selections. The Android and iOS SDKs, however, were built before multi-winner and so only expects each decision to ever have only zero or one selections. (There isn't even a concept of "selection" in these SDKs as a result.)
Note that in the Swagger-generated SDKs we've moved to always returning an array of selections inside a decision, even for non-multi-winner requests. We expect the same will be necessary in the mobile SDKs, and that this will be a breaking change. (However, as breaking changes go, this one isn't a lot of work for integrating developers to respond to.)
Acceptance Criteria
Support an optional count value on each placement of the ad request.
When specified it is a non-zero integer.
Note there is a maximum, but it will be handled by the server and NOT the SDK.
Support each decision potentially returning an array of selections rather than only one single selection.
Update code examples to show both multi-winner and traditional single-winner requests.
Background
Adzerk has added support for "multiple winners" for each placement on an ad request. There are a LOT of use cases for this, and there is a LOT that goes on under the covers to make it work, but suffice it to say that each placement has an optional
countparameter that indicates the maximum number of winners it wants. Each decision returned then has zero or more selections. The Android and iOS SDKs, however, were built before multi-winner and so only expects each decision to ever have only zero or one selections. (There isn't even a concept of "selection" in these SDKs as a result.)Note that in the Swagger-generated SDKs we've moved to always returning an array of selections inside a decision, even for non-multi-winner requests. We expect the same will be necessary in the mobile SDKs, and that this will be a breaking change. (However, as breaking changes go, this one isn't a lot of work for integrating developers to respond to.)
Acceptance Criteria
countvalue on each placement of the ad request.