Documentation

​
​

Development

User Acquisition

Monetization

Industry

Unity Offerwall

Offerwall Android SDK

Offerwall iOS SDK

Offerwall Unity SDK

Unity Offerwall

Tapjoy Offerwall
​
​
Introduction
  • Quickstart
  • Manual integration
  • Changelog
  • Update guide
  • SDK reference
  • Offerwall migration checklist
Placements
  • Virtual currency
  • SDK
  • Offerwall migration guide
Testing
  • Test devices
  • Examples
Advanced
  • User privacy
  • User properties
Cocos2dx
  • C++ library
  • C++ API reference
  1. Grow your game
  2. Unity Offerwall
  3. iOS SDK

Offerwall migration checklist

Use the checklist to ensure a successful migration to Tapjoy Offerwall.
Read time 2 minutes
Last updated 6 months ago

If you are currently using the ironSource Offerwall and want to transition to the Tapjoy Offerwall we have a step-by-step guide available to make the transition as seamless as possible. You can find a detailed guide, including instructions on code changed, here. Below you will find a high level checklist you can use to ensure you have made all necessary changes.

Checklist

Dashboard changes

  1. Apply for a Tapjoy account.
  2. Create an app on the dashboard.
  3. Create a virtual currency. For more information on the two available currency types, refer to Virtual currency overview.
  4. Create a placement and add an Offerwall content card to your placement. For more information on placement setup, refer to SDK.

Code changes

  1. Replace your ironSource Offerwall code with the equivalent Tapjoy Offerwall code, as outlined here.
  2. Launch your app and confirm you can show the Tapjoy Offerwall.

In-progress offers

When migrating to Tapjoy Offerwall it is important to remember that users might have already started offers on the ironSource Offerwall and are yet to complete these. The next steps are crucial to ensuring your users continue to receive currency for in-progress offers they complete.

If using server-to-server callbacks with ironSource Offerwall

ironSource will continue firing callbacks whenever we are notified of a completion from the MMP/Advertiser. Continue listening to callbacks fired from the ironSource servers and rewarding their users accordingly, for 90 days after the date you stop showing new offers by using the ironSource offerwall
In this flow, it doesn't matter if ironSource's SDK is still integrated in your application or not.

If using client-side callbacks with ironSource Offerwall

Keep the LevelPlay SDK integrated in your application. While you will stop showing the ironSource Offerwall, you are still required to call the
[IronSource offerwallCredits];
function to check for new rewards for the user. At a minimum, we recommend checking for credits each time the user opens the app, and preferably more often. This implementation should continue for at least 90 days after the date you stop showing new offers by using the ironSource Offerwall, and then it can be removed.

Privacy

If you're using Unity LevelPlay, you can use LevelPlay APIs to share with Tapjoy the following privacy flags:
  1. GDPR consent.
  2. Opt-out of sale or share of personal information under US state privacy laws.
  3. Flagging specific end users as children. Note that if your app is primarily directed to children under COPPA you must flag all end users as children.
If you're not using Unity LevelPlay or if you want to configure the Offerwall SDK separately, follow these guidelines to share with Tapjoy the relevant privacy flags.

Copyright © 2026 Unity Technologies
LegalPrivacy PolicyCookiesDocumentation Terms of UseDo Not Sell or Share My Personal InformationYour Privacy Choices (Cookie Settings)

"Unity", Unity logos, and other Unity trademarks are trademarks or registered trademarks of Unity Technologies or its affiliates in the U.S and elsewhere (more info here). Other names or brands are trademarks of their respective owners.

Some pages are machine-translated for convenience, and may contain inaccuracies. In the event of conflicting information, the English version is authoritative.

  • On this page
    • Checklist

      • Dashboard changes

      • Code changes

      • In-progress offers

        • If using server-to-server callbacks with ironSource Offerwall

        • If using client-side callbacks with ironSource Offerwall

    • Privacy


Report a problem with this page