Original vs Rendering API 40 Tech Dives Tech Dives Prebid Mobile SDK Prebid Server Demand Partners GMA SDK + PUC Prebid WebView Prebid Cache 1 request 2 OpenRTB 3 bids 4 bid + adm 5 Original API 6 Render API 7 cache fetch 8 from memory P_
Original vs Rendering API Tech Dives Tech Dives 40 Bid path matches 15 : SDK → Prebid Server → bids. Original API: GMA SDK fetches from Prebid Cache on win. Rendering API intercepts PrebidAppEvent, writes ad into its WebView — MRAID 3.0, SKAdNetwork. FIELD NOTES → Cache fetch adds 70–400 ms on 4G; Rendering API = 0 ms extra latency → Two InterstitialAdUnit classes; wrong import = silent fail → OM SDK bundled, not IAB-certified; MOAT may reject impressions P_ atd.postindustria.com/40

How It Works

Bid path matches {15}: SDK → `Prebid Server` → bids. Original API: `GMA SDK` fetches from `Prebid Cache` on win. Rendering API intercepts `PrebidAppEvent`, writes ad into its `WebView` — `MRAID 3.0`, `SKAdNetwork`.

Field Notes

  • Cache fetch adds 70–400 ms on 4G; Rendering API = 0 ms extra latency
  • Two `InterstitialAdUnit` classes; wrong import = silent fail
  • `OM SDK` bundled, not IAB-certified; `MOAT` may reject impressions

Questions about Original vs Rendering API?

Get expert guidance from our team. We'll help you implement it.