Bu makale henüz dilinize çevrilmedi — İngilizce orijinali gösteriliyor.
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
Kaynaklar
Mağaza sayfanızı bir playable'a dönüştürün
Bir App Store veya Google Play bağlantısı yapıştırın, dakikalar içinde test edebileceğiniz bir HTML5 playable alın. İlki ücretsiz.
Okumaya devam edin
- Google Ads HTML5
HTML5 Display Ads vs App Campaigns: Different Code
7 dk okuma
- Google Ads HTML5
Google Ads HTML5 Eligibility: Get Your Account Ready
7 dk okuma
- Google Ads HTML5
Self Contained HTML5 Ad: No CDNs, No Web Fonts
8 dk okuma