Skip to content

Apps and SDK setup

Apps and SDK setup: “Register an app, create its upload key, and add the SDK.” SDK integration is part of the Starter and Enterprise plans. On Free, the page shows a preview of the setup with the key step locked (Not in your plan).

Enter the app id in the field labelled Android application id: the package name (applicationId, for example com.example.news) of an Android app, or the bundle identifier of an iOS app. Add an optional Display name, then press Create app.

The id must be at least two dot-separated segments that each start with a letter (letters, digits and underscores), up to 150 characters, and unique in your organization. Hyphens are not accepted: an iOS bundle identifier with a hyphen cannot be registered today.

Under Upload keys press Create upload key. Give it a Label (the default is Release build). The dialog Your new key shows the key once: “This key is shown once. Copy it now and store it safely. We cannot show it again.” Copy it, then press I have saved it.

Upload keys start with ad80_ik_. They can only upload ads for this one app; they cannot read anything. You put the key in the app (the manifest on Android, Info.plist on iOS; see Install the SDK).

The list shows each key’s prefix, Label, Created, Last used and status (Active or Revoked).

  • Rotate creates a new key for the same app. The old key keeps working until you revoke it, so you can ship the new key in an app update first.
  • Revoke (then Revoke now) stops the key immediately. Apps that still use it can no longer upload.

The Integration box shows the Android snippets for this app: “Add the dependency and the manifest entries. The SDK finds ad views by itself; no other code is needed.” It also notes “The Maven coordinates are a placeholder until the SDK is published.” Do not use that coordinate: AD80 sends you the compiled SDK. For an iOS app, follow the iOS tab of Install the SDK; the box does not show iOS snippets.

For full-screen ads the box adds a line with the note “For full-screen ads, add this line right before each show call.” That line is Ad80.trackFullScreenAd(ad); the iOS call is the same name.

The full, current instructions, including the required endpoint entry and the consent call, are in Install the SDK.

The switch Full-screen ad capture (“Capture full-screen ads in this app”) controls whether interstitial, rewarded and app open ads can be captured for this app. It is on by default for every app. Two more things decide:

  • The app has to opt in: the SDK captures a full-screen ad only after your app calls Ad80.trackFullScreenAd right before showing it. See Full-screen ads (opt-in).
  • Capture must also be on for the app. If AD80 has paused the SDK or capture for the app, full-screen ads are not captured either.

The SDK itself starts with full-screen capture off, until it has fetched its settings and found the switch on. So a change here reaches an app the next time it checks its settings (“The app picks up the change the next time it checks its settings.”).

Only an owner or an admin can change the switch. Everyone else sees it with “Only an owner or admin can change this.”

Connection check tells you whether the app’s uploads arrive:

StateMeaning
No upload keyCreate an upload key, then add it to the app.
Waiting for first upload“Build the app with the SDK and open a screen with an ad. This page checks every few seconds.”
Receiving adsUploads arrive; the page shows Last upload {when}.

See Test your integration if it stays on Waiting for first upload.

API keys are “for scripts and exports that read your data. Never put these in an app.” Press Create API key, choose a label and the Scopes, and copy the key from the dialog; it is shown once. API keys start with ad80_ck_. See REST API: authentication for the scopes.

Only owners and admins can create apps and keys.