Artikel ini belum diterjemahkan ke dalam bahasa anda lagi — teks asal dalam bahasa Inggeris dipaparkan.

ExitApi in App campaigns — what PlayableRun generates

Why App campaign HTML5 creatives must call ExitApi.exit() instead of a custom landing URL.

Oleh pasukan PlayableRun··1 min bacaan

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 clickTag and no window.open on 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

Sumber

Tukarkan senarai kedai anda menjadi playable

Tampal pautan App Store atau Google Play dan dapatkan playable HTML5 yang boleh diuji dalam beberapa minit. Yang pertama adalah percuma.

Teruskan membaca