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
There is a behavior difference between Android and iOS TargetingInfo handling.
The difference is in case of Android, the targetingInfo is passed in the Ad object regardless of whether the bid is winning or not. But in case of iOS it's only passed when the bid is a winning bid. In our use case, we want to pass any targeting info that we get from our Prebid Server to Ad Server, regardless of whether Prebid won or not.
In case of iOS, I see it happening in this function
There is a behavior difference between Android and iOS TargetingInfo handling.
The difference is in case of Android, the targetingInfo is passed in the Ad object regardless of whether the bid is winning or not. But in case of iOS it's only passed when the bid is a winning bid. In our use case, we want to pass any targeting info that we get from our Prebid Server to Ad Server, regardless of whether Prebid won or not.
In case of iOS, I see it happening in this function
prebid-mobile-ios/PrebidMobile/AdUnits/AdUnit.swift
Line 189 in 5012008
Here it returns prebidDemandNoBids in case of no winning bid
Due to this it doesn't perform
Utils.shared.validateAndAttachKeywords(adObject: adObject, bidResponse: bidResponse)
prebid-mobile-ios/PrebidMobile/AdUnits/AdUnit.swift
Line 198 in 5012008
The above func performs the following
adObject.setValue( existingDict, forKey: "customTargeting")
which attaches the targetingInfo to the ad object.
To Reproduce
Steps to reproduce the behavior:
cust_params
in gam request for a non-winning auction.Expected behavior
The text was updated successfully, but these errors were encountered: