Existing Ad Unit IDs continue to work with the DARO 2.0.1 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. See legacy SDK (before 2.0.0) support for the support scope.
1. Update the dashboard
- In the DARO dashboard, select the app you are migrating and complete the update.
- Find its Integration Key and Ad Unit Keys.
2. Remove legacy key files and settings
-
Remove
ios-daro-key.txtfrom the project, its target membership, and Copy Bundle Resources. - Also remove any legacy build scripts that read or copy this file.
- Remove manually entered app key settings and previous key injection steps used for your legacy DARO integration.
- The new Integration Key tool applies the required settings again; do not overwrite them with old values.
3. Configure DARO integration tools
- Choose your installation method in Get Started.
-
CocoaPods: Update the Podfile dependency and add the Integration Key
post_installhook. If a hook already exists, add it to the same block. -
SPM: Update the package, then get the
Scripts/darotool from the SDK ZIP for that same version. - For CocoaPods, remove the pods you used before 2.0.0 from the Podfile, then add the DARO 2.0.1 SDK.
-
Swift apps use
DaroAdsand Objective-C apps useDaroObjCBridge. Apps that previously usedDaroMAdsorDaroMObjCBridgemove to these same two pods. - Use the version listed in Get Started.
4. Configure the Integration Key and app settings
- Add the key issued by the dashboard to the source
Info.plistused by your app target.
- For CocoaPods, run
pod install --repo-update. - For SPM, apply the settings to the source file with the downloaded tool.
- If Debug and Release use different Info.plist files, configure each file.
- Follow Get Started for the complete procedure.
Update SKAdNetworkItems
- The DARO 2.0.1 SDK supports a different set of ad demand sources than versions before 2.0.0.
-
Replace the existing
SKAdNetworkItemsarray in your app’sInfo.plistwith the list in Configure Your App. - Ad demand sources missing from the list cannot receive SKAdNetwork attribution.
-
Keep entries added by other SDKs, and if the same
SKAdNetworkIdentifierappears twice, keep only one.
5. Update app-ads.txt
- Follow the app-ads.txt guide and publish the latest content provided by the dashboard.
- Confirm that the file is accessible on the website registered in the dashboard.
6. Update SDK dependencies and code
Module and initialization
- Remove legacy SDK (before 2.0.0) dependencies and imports, and use the DARO 2.0.1 SDK.
- The Swift module is
Daroand the initialization entry point isDaroAds.shared.
- For Objective-C, install
DaroObjCBridgeand use this initialization API:
Ad Units and callbacks
- Create Swift Ad Units with
DaroAdUnit(unitId:). Remove the legacyplacementargument. - Remove rewarded video ad calls to
setPlacement(_:)and Objective-CsetPlacement:. - Register the
onPaidEventrevenue callback on each ad instance. - The legacy revenue plugin (
DaroPluginAdRevenueinDaroRevenuePlugin.xcframework) andregisterPlugin(_:)do not exist in the DARO 2.0.1 SDK. Remove that xcframework from the project and receive revenue data throughonPaidEvent. - Apply privacy settings using the APIs in Privacy Management.
- Banner and native ads load automatically, so SDK initialization must already be complete when you create those views.
- If you need to create a view earlier, set
autoLoad: falseand callloadAd()after initialization succeeds.
Check each ad format
- Use the guides below to verify loading, display, dismissal, and revenue callbacks for the formats used by your app.
- Also verify reward delivery for rewarded video ads.
- Banner and MREC
- Native
- Interstitial
- Rewarded
- App Open
- Light Popup
Verify before release
- Verify initialization and the loading, display, and cleanup of every ad format your app uses.
- Also verify reward callbacks and server callbacks if enabled.
- Confirm that the Integration Key and
SKAdNetworkItemsinInfo.plistuse the latest values. - Keep existing Ad Unit IDs for released app versions that still use the legacy SDK (before 2.0.0).

