Skip to content

iOS SDK: Install the SDK

AD80 sends you AD80-iOS-SDK-<version>.zip and its SHA-256 checksum. Use the release supplied to you by AD80; you do not download the SDK from GitHub or add a remote AD80 repository in Xcode.

Verify the ZIP against the checksum AD80 sent you, then unzip it. In the AD80-iOS-SDK folder, verify its contents:

Terminal window
shasum -a 256 -c SHA256SUMS

The folder contains:

Frameworks/Ad80Core.xcframework
Frameworks/Ad80.xcframework
Frameworks/Ad80GoogleMobileAds.xcframework
Package.swift
Sources/Ad80GoogleMobileAdsSupport/
README.md, INTEGRATION.md, CHANGELOG.md, SHA256SUMS

The SDK is compiled into the XCFrameworks. Package.swift and the small package support target let Xcode resolve the compiled frameworks and their dependencies; they do not contain the SDK implementation.

  1. Put the unzipped AD80-iOS-SDK folder somewhere stable next to your Xcode project. Keep its folder name.
  2. In Xcode, choose File → Add Package Dependencies → Add Local… and select that folder.
  3. Add the products Ad80 and Ad80GoogleMobileAds to your app target. Xcode resolves Google Mobile Ads 13.11.0 and embeds the required dynamic frameworks automatically.

If your app already uses Google Mobile Ads, keep it at exactly 13.11.0. A conflicting version in the same package graph prevents resolution. Google Mobile Ads is fetched from Google’s package; AD80’s SDK stays local.

For a package manifest of your own, the dependency is a local path:

// In your Package.swift:
dependencies: [.package(path: "../AD80-iOS-SDK")],
targets: [.target(name: "App", dependencies: [
.product(name: "Ad80", package: "AD80-iOS-SDK"),
.product(name: "Ad80GoogleMobileAds", package: "AD80-iOS-SDK"),
])]

Alternatively, add the three XCFrameworks to your app target. Set Embed & Sign for Ad80 and Ad80Core, and Do Not Embed for Ad80GoogleMobileAds (static). Add Google Mobile Ads 13.11.0 separately and add -ObjC to Other Linker Flags. The Ad80 framework contains the privacy manifest; keep it when embedding.

2. Register the app and configure Info.plist

Section titled “2. Register the app and configure Info.plist”

In the dashboard, open Apps and SDK, register the exact bundle identifier of your build, and create an upload key (ad80_ik_...). See Apps and SDK setup. Each build with a different bundle identifier needs its own app and key.

Add these entries inside your app’s Info.plist dictionary. Use the upload key and endpoint supplied by your AD80 setup:

Info.plist
<key>AD80PublisherKey</key>
<string>ad80_ik_YOUR_KEY</string>
<key>AD80Endpoint</key>
<string>https://api.ad80.dev</string>
<!-- Optional: false disables the SDK for this process. -->
<key>AD80Enabled</key>
<true/>

A missing key or invalid endpoint leaves the SDK inactive (configInvalid). AD80Enabled is a Boolean and defaults to true when absent. To keep your upload key out of source control, use a build setting such as $(AD80_PUBLISHER_KEY) and set it for every configuration you ship.

Call once on the main thread in your app delegate, before the first ad view appears:

import UIKit
import Ad80
import Ad80GoogleMobileAds
func application(_ application: UIApplication,
didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
Ad80.start(integrations: [Ad80GoogleMobileAds.integration])
return true
}

Keep your existing Google Mobile Ads initialization and consent flow. Nothing is captured or sent until you grant consent with Ad80.setConsent(...) on every app start, after your consent flow completes. For SwiftUI and Objective-C, and the full consent examples, see Consent and controls.

Banner and native ad discovery then runs automatically. Full-screen ads need a separate opt-in call immediately before each presentation; see Supported ads and networks. Finally, test the connection in the dashboard.