Support SKAdN in Bidding Only scenario #1086
Open
Conversation
This file contains 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
OlenaPostindustria
force-pushed
the
1085/support-skadn-in-bidding-only-scenario
branch
4 times, most recently
from
37294ec to
1dfd418
Compare
OlenaPostindustria
force-pushed
the
1085/support-skadn-in-bidding-only-scenario
branch
from
45a0eaa to
9785de1
Compare
OlenaPostindustria
force-pushed
the
1085/support-skadn-in-bidding-only-scenario
branch
from
9785de1 to
f7f7a92
Compare
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.
Closes #1085
Overview
The primary objective of this pull request is to facilitate the adoption of SKAdNetwork in a bidding-only scenario. This feature has been implemented to support banner, video, and native ad formats.
SKAdNetwork support is automatically enabled for all native ads. No additional steps are required.
seatbid[].bid[].ext.skadnparameters and fidelity type is 1, the SDK will display aSKStoreProductViewControllerwith the appropriate product parameters when the user clicks on the ad.seatbid[].bid[].ext.skadnparameters and fidelity type is 0, SKAdNetwork impression tracking begins when the SDK registers the corresponding event.Note: This PR does not include support for view-through ads because the SDK currently lacks the ability to track impression events for
bannerand video formats. Support for view-through ads will be implemented in a future update once the necessary changes are made (see issue #790 for details).The support for view-through ads was implemented for banner format.
To enable SKAdNetwork StoreKit ads support for banner ads, the publisher needs to call the method
activatePrebidSKAdNetworkStoreKitAdsFlow(adView:)oractivatePrebidSKAdNetworkStoreKitAdsFlow()of the respective ad unit within theGADBannerViewDelegatemethodbannerViewDidReceiveAd(_ bannerView: GADBannerView).The
PrebidSKAdNetworkHelperwill attempt to locate thehb_cache_id_localkey within the creative contained in the banner view. If the key is found, the SDK will retrieve the corresponding bid from the cache using this key, verify the presence ofseatbid[].bid[].ext.skadnparameters, and create a transparent, click-through overlay view to track user interactions. When the SDK detects a user click, it will trigger the presentation of anSKStoreProductViewControllerusing the retrievedskadnparameters.If the SDK is unable to find the
hb_cache_id_localkey in the creative (e.g., in the case of a video format), it will then attempt to locate thehb_uuidkey. The SDK will compare this key against the keys of bids stored in the cache to retrieve the corresponding bid information.Note: StoreKit ads are not supported for video ad format.