Skip to main content
Move your app to the DARO 2.0 SDK. After support ends, ad requests from the legacy SDK (before 2.0.0) may fail or ads may no longer display.

​
Support schedule

  • The legacy SDK will be supported for approximately one year after the release of DARO 2.0.0 SDK.
  • The exact support end date will be announced later.
Complete the SDK update and app release before the support period ends. See the migration guide for the transition steps.

​
Frequently asked questions

​
Will ads stop immediately if I do not update now?

You can continue using the legacy SDK (before 2.0.0) with existing Ad Units during the support period. Newly issued Ad Units require DARO 2.0 SDK.

​
Is updating the dashboard enough?

Updating the dashboard and updating the SDK in your app are separate tasks. Get your Integration Key from the dashboard, apply it to your app, and release an app containing the DARO 2.0 SDK.

​
Do I need to create my existing Ad Units again?

Existing Ad Unit IDs continue to work with the DARO 2.0 SDK and do not need to be reissued or replaced. For new integrations or when copying a value, use the Ad Unit Key from the updated dashboard. Keep existing Ad Unit IDs in app versions that use the legacy SDK (before 2.0.0); newly created Ad Unit keys do not work with that SDK.

​
What if I cannot migrate within the support period?

Contact DARO support before support ends. Include your platform, SDK version, and expected update schedule to help us guide your transition.

​
Refer to your previous integration

  • Legacy SDK integration guides remain available during the legacy SDK support period. See Support schedule above for the dates.
  • Check your integration settings for the legacy SDK before 2.0.0 in the platform guides: Android · iOS · React Native · Flutter.