Skip to content
T1KTheOneKit

t1k:marketing:monetization:ironsource

FieldValue
Modulemonetization
Version1.16.9
Efforthigh
Tools—

How to invoke

Section titled “How to invoke”
/t1k:marketing:monetization:ironsource

ironSource / LevelPlay

Section titled “ironSource / LevelPlay”

ironSource (now Unity LevelPlay) mediation setup, optimization, and revenue reporting integration.

When to Use

Section titled “When to Use”
  • Integrating the LevelPlay/ironSource SDK and network adapters
  • Setting up in-app bidding + waterfall A/B testing and segmentation
  • ARM (Ad Revenue Measurement) integration with MMPs
  • Pulling mediation revenue via the Monetization Reporting API (per-network/ad-source dashboards)

Reporting API — endpoint & auth

Section titled “Reporting API — endpoint & auth”
  • Monetization Reporting API: GET https://platform.ironsrc.com/partners/publisher/mediation/applications/v5/stats
  • Auth: Basic HTTP auth over HTTPS — Authorization: Basic base64(<login-email>:<secret-key>). The secret key is per-account (Account > API). A bearer-token flow also exists via https://platform.ironsrc.com/partners/publisher/auth.
  • Rate limit: 20 requests / 10 minutes — budget calls and cache.

Per-network breakdown

Section titled “Per-network breakdown”
  • Break down by adSource (the mediated network/source) — this is the per-network dimension. Also breakdownable by date, application (appKey), adUnit, country, platform.
  • Common metrics: revenue, impressions, eCPM, activeUsers, engagedUsers, revenuePerActiveUser. Per-adSource revenue decomposes the app’s mediated total.
  • Filters: date range, appKey, adSource, adUnits, country.

Revenue semantics & quirks

Section titled “Revenue semantics & quirks”
  • Reported revenue is estimated; recent days adjust as data finalizes.
  • The Impression-Level Revenue (server-side) API is a separate stream for ILRD/ARM (per-impression revenue), distinct from the aggregate Monetization Reporting API above.
  • Post-Unity-merger, “LevelPlay” is the mediation brand; ironSource endpoints (platform.ironsrc.com) remain in service. Confirm the current API version (v5 / general v4) against the live docs before coding.

References

Section titled “References”

Gotchas

Section titled “Gotchas”
  • LevelPlay (ironSource) is the rebrand — old IronSource SDK code paths still exist in some samples; do not mix the two namespaces in a single integration.
  • ARM with MMPs requires server-to-server callbacks — client-side ARM events are sampled and underreport revenue.
  • Bidding-only waterfalls fall apart in low-fill geos — keep at least one classic-waterfall network for India/SEA fallback.