Build a working reward flow

Android offerwall SDK

Integrate the Maven Central Android SDK into an Activity and open a rewarded survey wall from your app’s rewards screen.

Create a publisher account See integration code

com.rapidoreach:cbofferwallsdk:1.1.0 · Guide reviewed October 15, 2026

RapidoReach public web playground showing sample survey cards

Public web playground · Sample inventory · Native presentation varies

01 / Integrate

From install to the first open.

Initialize with the signed-in app user and a foreground Activity. Enable the entry point only after readiness; retain a useful retry path when the network is unavailable.

1. Install the released package

Add mavenCentral() to dependency repositories and implementation "com.rapidoreach:cbofferwallsdk:1.1.0" to the app module. Confirm INTERNET permission in the merged manifest.

Package and source reference

2. Configure your app

Use a foreground Activity and Android minSdk 23 or higher for this artifact. Initialize after you have a stable signed-in user identifier.

Create a publisher app in the dashboard and use its SDK token with a stable, non-personal app user ID. The web UID signing App Key stays on your backend.

Android integration reference

3. Connect your opt-in entry point

Replace the placeholders in your own app. Catch SDK errors in the calling screen, handle unavailable inventory and refresh balances from your server.

Java / Gradle / integration example

// app/build.gradle
// implementation 'com.rapidoreach:cbofferwallsdk:1.1.0'

import com.rapidoreach.rapidoreachsdk.RapidoReach;

// In your Activity, after login:
void initializeRewards() {
    RapidoReach.initWithApiKeyAndUserIdAndActivityContext(
        "YOUR_API_TOKEN", "YOUR_USER_ID", this);
}

// Connect to your opt-in rewards button after initialization.
void openRewards() {
    if (RapidoReach.getInstance().isSurveyAvailable()) {
        RapidoReach.getInstance().showRewardCenter();
    } else {
        // Render “No surveys available”; allow a later retry.
    }
}

02 / See the experience

Inspect the wall. Try the return flow.

These are screenshots of the public web playground, captured October 15, 2026. They show sample survey cards shared as a visual reference, not screenshots of a Android native build or a guarantee of inventory.

Mobile layout of the public web demo with four sample survey cards — Mobile web demo. Open image to inspect the full capture.

Android reward journeySimulation

This local interaction illustrates presentation states. It does not call the SDK, load live surveys or issue rewards.

Ready to explore

A survey is available in this simulated placement.

Open the public widget playground ↗

The playground previews layout and themes. To validate Android SDK behavior, use the package example and your own development app on a supported device.

Get the Android package / example

03 / Test before live traffic

Make the first reward traceable.

Set up a test user

Use a development publisher app. In the app’s Test users section, add the raw app user ID exactly as your SDK sends it and enable Test mode for that test user. For web, generate the signed UID from that same raw user ID.

The test survey helps verify the journey. Keep test activity separate from live earnings.

Open the integration testing guide

Verify your server ledger

Configure the app’s server callback and send a Test Callback from the dashboard. Verify the documented hash, attribute the transaction to the correct user and store it once. Repeat the same transaction to check duplicate handling.

Client reward notifications should refresh UI. They should not create a second credit.

Callback verification reference

Android acceptance checklist

Inspect the merged manifest and resolve the pinned Maven artifact in a clean build.
Background and resume the Activity while the wall is open.
Test an internal release build as well as a debug build.
Test loading, no inventory, offline, invalid credentials and retry. Reopen for the same user and verify attribution stays consistent.
Confirm your backend handles duplicate and invalid callback hashes, then review reversal handling before enabling live traffic.

04 / Troubleshoot

Find the failing boundary.

Dependency cannot be resolved

Use Maven Central and the cbofferwallsdk artifact name. Avoid old android-sdk coordinates or mixing the Maven artifact with a second bundled AAR.

Offerwall will not present

Use the foreground Activity context and wait for SDK readiness and survey availability. A background service cannot present the reward center.

Works in debug but fails in release

Validate the selected artifact’s release and shrinking requirements, merged manifest and network access in a signed internal build.

The user completed a survey but the balance is unchanged

Trace the same app user ID and transaction through your callback receiver and reward ledger. Check hash verification, duplicate detection and currency conversion. Use redacted diagnostics when contacting support.

Build your android offerwall sdk pilot.

Create a publisher account, register your app and connect the first test user. Review the reward flow before opening the placement to live users.

Platform documentation SDK release matrix Testing reference