The CloudX SDK handles ad caching automatically — there is nothing custom you need to build. When an impression opportunity arises, an auction runs, bids come back from the demand sources, and the SDK caches the winning ad and expires it automatically. There is no publisher-facing cache TTL to configure.
Rule of thumb: Retain ads that were loaded successfully — this avoids wasting loaded fill and ensures fill is utilized effectively. Load as close to show time as possible for the best price; avoid preloading far ahead of the impression.
Consistent across setups
The caching fundamentals do not change with your mediation setup. They are the same whether CloudX runs in First Look, Parallel, or CloudX-only mode, and the same for MAX and AdMob. Only the integration path differs — see Trusted Arbiter for parallel arbitration and the First Look integration guides under each platform tab.
The differences between formats are about how you drive freshness at show time, not the caching mechanism itself.
- Trusted Arbiter — parallel arbitration and retaining non-winning fills.
- First Look — CloudX loads first with no held cache; see the First Look integration guide under your platform tab.
- Per-format integration code lives under the Android, iOS, Unity, and React Native tabs.
