이 문서는 아직 회원님의 언어로 번역되지 않아 영어 원문이 표시됩니다.
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분