本文尚未翻譯成您的語言,目前顯示的是英文原文。
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 可試玩廣告。第一個免費。
繼續閱讀
- 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 分鐘