Offer ad slots
Create a named ad slot for each user-facing offer surface. For example, a main rewards tab and an in-app inbox can have different sorting, country rules, and currency. Slot type is chosen at creation and is immutable after activation. An API network placement supports only a Static API slot.
Choose the delivery type
| Type | Use it for | Delivery credential |
|---|---|---|
OFFERWALL | RapidoReach hosted offerwall or SDK surface | Short-lived, user-bound SDK session |
OFFER_API | A custom offer list for a signed-in user | Short-lived, user-bound SDK session |
STATIC_API | Server-side inventory polling by an approved network | Slot-scoped static key kept on the server |
A Static API response is not personalized for an individual user and cannot replace launch sessions or reward callbacks. Use an Offer API slot when the experience needs user-specific eligibility and progress.
Configure the slot
In Ad slots, choose the slot type and name. Then review these settings:
- Currency: name, decimal places, conversion numerator and denominator, minimum reward, and rounding mode. Preview a sample USD payout in the console before launch. A zero conversion numerator prevents readiness.
- Exposure: maximum items per session and per day, plus cooldown. Keep limits consistent with the frequency of the surface.
- Offer delivery: sort by payout, conversion rate, EPC, or eCPM, and set a minimum payout in USD micros where needed.
- Suitability policy: allowed or blocked two-letter country codes, blocked campaign IDs, excluded task types, and excluded categories. Empty allowed-country list means the slot does not add an allowlist restriction; blocked countries still apply.
- Design: the appearance for a hosted surface. Confirm the layout and virtual currency on a small screen.
Save and inspect the slot's readiness.ready and readiness.reasons. A verified placement, supported capability, and positive currency conversion rate are required. A slot may be DRAFT, READY, or ACTIVE; a ready slot still needs the placement and delivery capability released before production traffic.
Each save creates a new configuration version and immutable revision. Existing sessions retain the terms captured when they began. Use the generated integration snippet for the selected placementId and adSlotId; it contains no secret.
Next: Set up reward callbacks, then integrate an offer slot.