この記事はまだお使いの言語に翻訳されていません。英語の原文を表示しています。
ExitApi in App campaigns — what PlayableRun generates
Why App campaign HTML5 creatives must call ExitApi.exit() instead of a custom landing URL.
When you pick App Campaign (ExitApi) in the PlayableRun workspace, we inject Google’s Exit API script and bind the install CTA to ExitApi.exit(). That is the supported click path for HTML5 in App campaigns.
Why this exists
App campaigns optimize toward installs. The ad should not invent its own destination URL in the ZIP. ExitApi hands control back to Google Ads so the platform can attach the correct store listing and measurement.
What you will see in index.html
- A script tag pointing at
https://tpc.googlesyndication.com/pagead/gadgets/html5/api/exitapi.js - A visible, high-contrast CTA (minimum 44px height in our generator)
- No
clickTagand nowindow.openon that CTA
If you need a Display destination instead, generate a second ZIP with campaign type Display. Do not edit ExitApi ads by hand to add a URL.
Sources
参考資料
ストアページをプレイアブルに変換
App StoreまたはGoogle Playのリンクを貼り付けるだけで、数分でテストできるHTML5プレイアブルを作成できます。最初の1本は無料です。
関連記事
- Google Ads HTML5
HTML5 Display Ads vs App Campaigns: Different Code
読了目安:7分
- Google Ads HTML5
Google Ads HTML5 Eligibility: Get Your Account Ready
読了目安:7分
- Google Ads HTML5
Self Contained HTML5 Ad: No CDNs, No Web Fonts
読了目安:8分