Offers V2 placements
A placement identifies one publisher app, website, or API network. An ad slot is a named surface inside that placement. Create a separate placement for each package name, bundle ID, domain, or network identity. Offer placements and legacy Survey Offerwall Applications are separate workflows with different credentials.
Offers V2 foundation and delivery are enabled by account and environment. A visible draft or verified placement is not proof that live offer delivery has been released. If the Offer Placement V2 page or offer operations are absent, confirm availability with RapidoReach before scheduling a launch.
Choose an identity
| Placement type | Identity to enter | Review URL | Offer slot types |
|---|---|---|---|
| Android app | Exact package name | Public HTTPS store listing required | Offerwall, Offer API, Static API |
| iOS app | Exact bundle ID | Public HTTPS store listing required | Offerwall, Offer API, Static API |
| Website | Exact hostname | Optional HTTPS review URL | Offerwall, Offer API, Static API |
| API network | Stable network identifier | Optional HTTPS review URL | Static API |
The console also supports other slot products on some placements. This offer guide covers only the offer slot types above. Choose a name your team can recognize, such as “Puzzle Quest — Android”; the name is internal. The platform identity is checked against the SDK session request and cannot be casually changed after setup.
Create and review
- Open Publisher → Offer Placement V2 → Placements and choose the integration type.
- Enter the placement name, exact platform identity, store or review URL, and minimum and recommended SDK versions. Keep the minimum compatible with the version installed in your app.
- Save the draft. Record the generated
placementId; it is an opaque identifier, not an API key. - Add at least one offer ad slot. Set its reward currency, offer policy, and placement callback.
- Use Request placement review. A publisher can request review from
DRAFTorREJECTED; a RapidoReach administrator verifies or rejects the identity. - Recheck each slot's readiness after verification. Slot readiness and placement release are separate from the review status.
| Placement status | Meaning |
|---|---|
DRAFT | Editable setup; not reviewed |
PENDING_REVIEW | Identity review requested |
REJECTED | Correct the stated issue and request review again |
VERIFIED | Identity accepted; slot readiness and release still matter |
DISABLED / ARCHIVED | Not available for new delivery |
You can update the placement name, review URL, SDK version requirements, and consent setting. The service blocks archival when live slots, historical sessions, callbacks, or a release create ongoing obligations. Treat IDs and prior financial records as permanent audit references.
Next: Configure offer ad slots.