Integrate an Offers V2 slot

Use a supported SDK or API integration for the slot type configured in your publisher placement. Your placement and slot must be approved and available before live traffic can be served.

For an Offerwall or Offer API feed, create a short-lived SDK session with the placement identity, platform, supported SDK version, external user ID, and consent state. The service checks that the identity and environment match and that the slot is available. Use the returned session for the user-bound feed; do not decide eligibility or calculate a reward in the client.

The Static API is for server-side inventory polling. It does not replace a user-bound session, personalized eligibility, reward crediting, or a callback. Store its slot-scoped key only on your server and rotate it before expiry.

Treat placement, slot, campaign, session, and click identifiers as opaque values. Verify server-to-server callback signatures and handle repeated deliveries idempotently. A successful click or a visible completion screen is not proof that a reward has been verified.

For SDK-specific setup, see the SDK documentation. For placement configuration, return to publisher placements and ad slots.