Getting Started
Teads delivers in-content video, display, and native recommendations inside publisher content, with banner and interstitial for moments outside the article. This SDK loads those formats in your iOS app. You can integrate Teads SDK directly, through a mediation adapter, or with Prebid.
Compatibility and Requirements
| Teads SDK | Requirements |
|---|---|
| iOS | iOS 14.0+ (deployment target) |
| Xcode | 26.2+ (required — the framework is built with the Swift 6.2.3 toolchain, and older toolchains cannot link against it) |
| Swift compiler | The framework is compiled with 6.2.3, which is the toolchain shipped in Xcode 26.2 |
| Swift language mode | Swift 5 (SDK compiled with SWIFT_VERSION = 5.0). Library evolution is enabled, so your app can use either the Swift 5 or Swift 6 language mode — migrating to Swift 6 is not required |
| Swift runtime | Ships with the OS. Swift has been ABI-stable since Swift 5, so no Swift runtime is embedded in your app |
| Objective-C | Supported — the SDK exposes an Objective-C compatible interface |
| UI Frameworks | UIKit and SwiftUI |
| Dependency managers | CocoaPods, Swift Package Manager, or a manually embedded XCFramework |
Formats by integration type
These are three different ways to ship Teads. Pick the one that matches how you load ads.
Direct is Teads SDK in your app. Your app requests ads from Teads SDK. No mediator and no Prebid auction sit in front. You get the full format set.
Mediation is Teads as one ad network inside another mediation SDK. Your app requests ads from that mediator. The mediator calls Teads through an adapter, in a waterfall or as a bidding source. You follow that mediator's adapter. The format set depends on the adapter.
Header bidding (Prebid) is Teads as a bidder behind Prebid SDK. Your app requests ads through Prebid SDK and Prebid Server. When the Teads bidder adapter wins, Teads SDK renders the ad.
Direct integration
| Format | What it is | Guide |
|---|---|---|
| Media | In-content slot in the article. Renders video and display ads. | Media |
| Media Native | Same as Media, but you own the layout and surrounding UI. | Media Native |
| Feed | Ready-made content recommendation widget you add to the page. | Feed |
| Recommendations | Same recommendations as Feed, with no Teads UI — you build the list yourself. | Recommendations |
| Banner | Anchored adaptive banner in a fixed slot. Height follows the creative. | Banner |
| Interstitial | Fullscreen ad. Preload it, then show it at a natural transition. | Interstitial |
Mediation
Install the Teads adapter for the mediation SDK you already use. Format meanings are in Direct above; adapters do not all expose the same set.
| Mediation | What it is | Formats | Guide |
|---|---|---|---|
| Google Ad Manager and AdMob | Teads as a custom event in Google’s mediation. | Media, Native, Interstitial, Banner | AdMob |
| AppLovin MAX | Teads as a custom network in MAX. | Media, Native | AppLovin |
| Smart AdServer | Teads as a custom event in Smart. | Media, Native | Smart |
Header bidding (Prebid)
| Kind | What it is | Formats | Guide |
|---|---|---|---|
| Standard | Use Prebid Mobile SDK alongside Teads SDK to add Teads demand to your header bidding auction. | Media (inRead) | Standard Prebid |
| Standalone | Use Teads SDK with your own Prebid Server, without the official Prebid Mobile SDK. | Media (inRead) | Standalone Prebid |
What the ads look like
The tables above are how you request ads. To see the creatives Teads can render, especially in Media, browse the video specifications and display specifications.
Get Teads demand
To serve Teads ads in your app, you need a placement set up by a Teads publisher manager. Reach your publisher manager to start that setup, or contact Teads if you do not have one yet.