Other Ad Networks

Elo is a single demand source. The SDKs do not mediate other networks: there is no client-side auction and no network adapter to register. Elo’s own server already runs a real-time auction across programmatic exchanges and Elo’s advertiser inventory for every request, so what reaches your app is the winning ad and its price.

If you also run another ad network, keep the fallback in your own code. Request Elo first, render the ad when it fills, and hand the same slot to your other network when it does not. Both noFill and error mean Elo has nothing to show for this request, so treat them the same way.

The per-platform guides show the pattern in code:

• iOS: Falling back to another network
• Android: Falling back to another network

Requesting twice in a chat UI

A chat slot can be requested twice: once when the user’s message arrives, and again with the assistant’s answer appended if the first request did not fill. The second request carries more context, so it can fill where the first did not. Fall back to your other network only after the second request.

Comparing prices

Every Elo fill carries eCpm, the price the Elo server quoted for that ad, so you can decide by price rather than by order:

• If your other network quotes a price at load time, request both and render the higher one. Call releaseResources() on the Elo ad you discard.
• If it does not (AdMob’s native ads, for example, expose no price on the device), pick a floor from that network’s dashboard eCPM and use Elo whenever its eCpm clears it.