[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["缺少我需要的資訊","missingTheInformationINeed","thumb-down"],["過於複雜/步驟過多","tooComplicatedTooManySteps","thumb-down"],["過時","outOfDate","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["示例/程式碼問題","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-04 (世界標準時間)。"],[[["\u003cp\u003eApple's SKAdNetwork API measures app install ad campaign success while prioritizing user privacy, with versions 2.2 and later supporting view-through ad attribution in addition to click-based attribution.\u003c/p\u003e\n"],["\u003cp\u003eTo ensure correct SKAdNetwork attribution, ad click actions must directly link to the Apple App Store or use server-side redirects (HTTP 301, 302) that ultimately lead to the App Store.\u003c/p\u003e\n"],["\u003cp\u003eFor view-through attribution in SKAdNetwork v2.2 and later, ads must be displayed for a minimum of 3 seconds to initiate the impression timer, with iOS 15.4 and later versions supporting multiple concurrent impressions.\u003c/p\u003e\n"],["\u003cp\u003eThe bid request fields indicate supported SKAdNetwork features, including attribution fidelity types and supported versions, ensuring compatibility and preventing bid filtering.\u003c/p\u003e\n"],["\u003cp\u003eSKAdNetwork ad requests are backward compatible, allowing ad networks to respond with earlier versions listed in the bid request, providing flexibility in adopting new SKAdNetwork versions.\u003c/p\u003e\n"]]],[],null,["Apple's [SKAdNetwork\nAPI](//developer.apple.com/documentation/storekit/skadnetwork) aims to\nmeasure the success of app install ad campaigns while maintaining user privacy.\nFor SKAdNetwork v2.0 and v2.1, install attribution for StoreKit-rendered ads is\ndriven by clicks on the ad that would lead to the user installing the app.\n[SKAdNetwork v2.2](//developer.apple.com/documentation/storekit/skadnetwork/skadnetwork_release_notes/skadnetwork_version_2_2_release_notes)\nand later versions additionally supports view-through ads where attribution is\ndriven by just viewing the ad.\n\nThe following guidelines are provided to ensure that the Google Mobile Ads SDK\ncan initiate SKAdNetwork attribution correctly.\n\nOn-click attribution for mobile ads\n\nSKAdNetwork attribution is initiated by the Google Mobile Ads SDK ad click event\nonly if the click action specifically lands in the Apple App Store. The reason\nfor this requirement is to prevent the app store from being launched by clicks\nthat are *not* meant to open the app store. These types of click actions could\ninclude, for example, navigating to an Ad Choices page.\n\nGuidelines\n\nTo guarantee that click actions on ads and subsequent app installs would result\nin a SKAdNetwork attribution, when building the creatives, make sure that the\ncreative's click-through URL is either\n\n- a direct link to the advertised app in the app store, or,\n- uses redirect methods, such as HTTP 301, 302, or other types of server-side HTTP redirect chains that would have a final destination of the app store.\n\nLinks to the app store either directly or through a redirect chain are confirmed\nif the URL begins with any of the following patterns:\n\n- `https://apps.apple.com`\n- `https://itunes.apple.com`\n- `itms-apps://`\n- `itms://`\n\nAny other landing pages or using any other client-side redirect methods are\ndetermined to *not* land in the app store and might not initiate the SKAdNetwork\nattribution process. Examples:\n\n- HTML page that requires user action to redirect to the app store\n- HTML page that has an automated JavaScript-based redirect script to the app store\n- Meta refresh tags\n\nBest practices for different creative types\n\nThe click action to initiate SKAdNetwork attribution can be set up for the\ndifferent creative types as follows:\n\nHTML creatives\n: This can be set up as the destination URL on the anchor tags surrounding the\n clickable element, or as the target URL of `window.location` operations from\n JavaScript-based on-click events.\n\nMRAID\n: The click action needs to call `Mraid.open()` to initiate the SKAdNetwork\n attribution.\n\nVAST video\n: The app store URL should be set in the `ClickThrough` element in the VAST\n XML.\n\nNative\n: The app store URL should be set on the `native.link.url` field for OpenRTB\n (or the `native_ad.click_link_url` field for the deprecated Google RTB\n protocol).\n\nView-through attribution for mobile ads\n\nWhen SKAdNetwork v2.2 view-through attribution is supported, the SKAdNetwork API\nstarts an impression timer once the ad is rendered and is viewed by the user.\nAttribution is only allowed for ads that have been displayed for a [minimum of 3\nseconds](//developer.apple.com/documentation/storekit/skadnetwork/generating_the_signature_to_validate_view-through_ads).\n\nNote that iOS versions 15.3 and earlier only supports 1 active impression timer\nat a time, in which case it could be possible for an impression to fail\nview-through attribution initiation if there are multiple view-through\nattribution ads within the same screen. This restriction has been [lifted on iOS\nversion 15.4 and above](//developer.apple.com/documentation/storekit/skadnetwork/3727304-startimpression#discussion),\nso SKAdNetwork now allows for multiple concurrent impressions enabled for\nview-through attribution.\n\nGuidelines\n\nThe bid request field `BidRequest.imp.ext.skadn.fidelities` specifies which\nattribution fidelity types are supported. This field includes the\n`VIEW_THROUGH_ADS` fidelity type in SKAdNetwork versions v2.2 or higher.\n\nEnsure the bid response doesn't include `VIEW_THROUGH_ADS` fidelities if\nview-through attribution is not supported. Responding with `VIEW_THROUGH_ADS`\nfidelities when not supported causes the bid to be filtered before the auction.\n\nBackwards compatibility\n\nAs of SKAdNetwork v4.0, ad requests enabled for SKAdNetwork attribution are\nbackward compatible. This allows ad networks to respond with earlier SKAdNetwork\nversions even when the ad request supports newer versions.\n\nGuidelines\n\nThe user's device OS version and the publisher app's Google Mobile Ads SDK\nversion both dictate which SKAdNetwork features are supported by the ad request.\nThis can be determined on the bid request using\n`BidRequest.imp.ext.skadn.versions`. This lists all SKAdNetwork versions\nsupported by the ad request.\n\nTo prevent bid filtering, ensure that the SKAdNetwork version used to build the\nresponse is one of the listed versions on the bid request. In addition, when\nnewer SKAdNetwork versions are introduced, note that responding with earlier\nversions are allowed as long as the version is in this list. This allows ad\nnetworks to continue responding with earlier versions and adapt newer versions\nat their own pace."]]
