Skip to main content

Key concepts

Summarizes behavior for AdScope Unity SDK v1.0.0 (beta).

What you integrate​

  1. Configuration — Supplied by AdScope for your inventory. You load it using the APIs described in Integration and Configuration.

  2. Reporting — You notify the SDK when ads fill (with revenue) and when they do not fill, using the public API and the AdFormat that matches your placement.

  3. Targeting — You read a key-value string from the SDK when building ad requests, and attach it according to your ad stack (e.g. Ad Manager line items). The exact string format must respect Google Ad Manager key-value rules.

Ad formats​

Use the AdFormat enum (Banner, MREC, Interstitial, Rewarded, AppOpen) consistently with how you map mediation placements. Your AdScope materials may name formats differently—map them to these values as agreed with AdScope.

Context fields​

The SDK may expose APIs for country, consent, and advertising ID opt-in. Whether and how those affect targeting is defined by AdScope product behavior and your contract—not by this documentation site.

Where to learn more​

  • Behavior, tiers, and policy — AdScope account / integration documentation.
  • Public API surface — API reference.