Getting Started

An Ad Unit defines an ad placement and format in your app. For the DARO 2.0 SDK, copy the Ad Unit Key from the updated dashboard. This is different from the app’s Integration Key. API parameters such as adUnitId, unitId, and key, and example placeholders such as YOUR_AD_UNIT_ID, keep their names but take that Ad Unit’s Ad Unit Key. Existing integrations using Ad Unit IDs remain supported. Do not confuse reporting or callback identifiers with the key for a new integration.

Before You Begin

Prepare these items before installing DARO Unity SDK:

A per-platform Integration Key issued from the DARO dashboard
Ad Unit Keys for each ad format
Unity 2021.3 LTS or newer
A build environment with Android Build Support or iOS Build Support installed

Complete the app-ads.txt setup as well.

Configure the SDK with an Integration Key for each platform. You do not need to enter separate app keys or key files.

Install SDK

Use DaroPackageInstaller.unitypackage for the recommended installation path.

Download Installer Package

Download DaroPackageInstaller.unitypackage from the GitHub Release.

Import into Unity Project

In Unity Editor, select Assets > Import Package > Custom Package, then import DaroPackageInstaller.unitypackage.

Confirm Package Installation

The installer adds the OpenUPM scoped registry, EDM4U, and so.daro.unity dependency to Packages/manifest.json.The latest so.daro.unity package version is 1.0.0 and uses EDM4U [email protected].Unity shows an Importing a scoped registry notice during installation. It is Unity’s own note that the OpenUPM registry was added — click Close.

Run Integration Manager

In the Unity Editor menu bar, open Daro > Integration Manager and validate your project setup. Daro is a top-level menu, not an entry under Assets.

The installer adds the OpenUPM registry to Packages/manifest.json and starts installing [email protected].

Configure Project

In Unity Editor, open Daro > Integration Manager and enter platform settings.

A dropdown at the top of the window switches the display language between English and Korean. English is the default, and the choice is stored in Editor preferences rather than the project, so it carries across every project on the same machine.

Create Settings Asset

In Integration Manager, select Create Settings Asset. This creates Assets/Daro/DaroSettings.asset.

Enter iOS Settings

For iOS builds, enter the iOS key in INTEGRATION KEY under Settings > iOS. Put the App Tracking Transparency prompt text in ATT Description.Select Validate Key to check the key format. Also verify an app build and SDK initialization after completing setup.

Enter Android Settings

For Android builds, enter the Android key in INTEGRATION KEY under Android, then press Validate Key to check its shape.

Check Android Build Templates

When you switch the build target to Android, EDM4U asks Enable Android Auto-resolution?. Choose Enable.With auto-resolution on, EDM4U resolves the ad demand dependencies and creates these three files itself, turning on the matching Player Settings options. You do not need to enable them by hand.

Assets/Plugins/Android/mainTemplate.gradle
Assets/Plugins/Android/gradleTemplate.properties
Assets/Plugins/Android/settingsTemplate.gradle

If you chose Disable, those three files are not created. You then have to enable Custom Main Gradle Template, Custom Gradle Properties Template, and Custom Gradle Settings Template yourself under Edit > Project Settings > Player > Android > Publishing Settings > Build, and run Assets > External Dependency Manager > Android Resolver > Resolve by hand whenever dependencies change. Without resolution the app does not work.Auto-resolution can be turned back on from Assets > External Dependency Manager > Android Resolver > Settings.

During the Android build, DARO Unity SDK applies the required Gradle plugins, minimum SDK setting, and ProGuard rules to the exported project.

Validate Settings

Press Run Checks under Build Validation in Integration Manager.

The checks only look at the active build target. While the target is Standalone (Windows, Mac, Linux), the iOS and Android checks never run, so validation passes even with both INTEGRATION KEYs empty. Switch to Android or iOS under File > Build Settings before running it.

When building for Android with Unity 6000.3.17f1 or newer, add the following setting to Assets/Plugins/Android/gradleTemplate.properties.

android.uniquePackageNames=false

This setting is required for compatibility with some dependencies.

Turning on AI Integration Helper in Integration Manager lets AI coding agents — Claude Code, Codex, Cursor, Cline — pull the SDK’s integration knowledge base automatically when a session starts. Enable it only if you hand the integration to an agent.

The Integration Key is not passed to InitializeAsync(). Unity injects it into iOS Info.plist and Android gradle.properties at build time.

When updating from 0.4.0 or earlier, replace the old integration settings in your Settings asset with Integration Keys. Enter the keys issued through the DARO dashboard in the iOS and Android INTEGRATION KEY fields.

Check iOS build settings

Enable Podfile generation in EDM4U’s iOS Resolver. Complete CocoaPods installation in the generated project to apply the integration settings. If you maintain an existing post_install block, check that it includes the DARO configuration and do not declare the block twice.

Initialize SDK

Call DaroSdk.InitializeAsync() when your app starts.

using Daro;
using UnityEngine;

public sealed class GameBootstrap : MonoBehaviour
{
    private async void Start()
    {
        DaroSdk.HasGdprConsent = true;
        DaroSdk.SetUserId("user-12345");

        await DaroSdk.InitializeAsync();
        Debug.Log("Daro SDK ready");
    }
}

You can set privacy options and user ID before SDK initialization.

Mute and logging settings

With 0.5.0-rc.4, you can configure mute before initialization on both Android and iOS. Call these APIs on the Unity main thread.

DaroSdk.LogLevel = DaroLogLevel.Info;
DaroSdk.SetAppMuted(true);
await DaroSdk.InitializeAsync();
// Load ads after initialization and the saved mute setting have been applied.

If you change mute several times before or during initialization, the last value is applied. The SDK applies mute before raising OnSdkInitialized and completing the initialization Task. After initialization, use SetAppMuted(false) to unmute. On iOS, the default Info setting enables only error logs from the native SDK. Repeated DaroRewardedAd.IsReady() queries do not produce native debug logs. Use DaroSdk.LogLevel = DaroLogLevel.Verbose when detailed diagnostics are needed, then switch back to Info. Unity and bridge log levels are preserved; this setting does not suppress every log emitted directly by individual ad demand sources.

Use Ad Instances

Use fullscreen ad instances in this order:

Complete await DaroSdk.InitializeAsync().
Create the ad instance.
Register event handlers.
Call Load().
After load completes, check IsReady() and call Show().
Call Dispose() when the screen closes.

Banner ads are displayed automatically when Load() succeeds. Use Show() only to display a banner again after calling Hide().

using Daro;
using UnityEngine;

public sealed class InterstitialAdHost : MonoBehaviour
{
    private const string AdUnitId = "your-ad-unit-id";
    private DaroInterstitialAd ad;

    private void OnEnable()
    {
        ad = new DaroInterstitialAd(AdUnitId);
        ad.OnAdLoaded += info => Debug.Log($"Loaded: {info.AdUnitId}");
        ad.OnAdFailedToLoad += error => Debug.LogWarning(error.Message);
        ad.Load();
    }

    public void Show()
    {
        if (ad != null && ad.IsReady())
        {
            ad.Show();
        }
    }

    private void OnDisable()
    {
        ad?.Dispose();
        ad = null;
    }
}

Best Practices

Working With Ad Instances

Create ad instances after initialization completes
- Call the constructor and Load() only after await DaroSdk.InitializeAsync() returns
Call public methods on Unity’s main thread
- This covers constructors, Load(), Show(), Hide(), and Dispose(). SDK callbacks are delivered on Unity’s main thread as well
Dispose instances you no longer need
- The SDK provides finalizer-based cleanup as a fallback, but cleanup timing is not guaranteed
Check IsReady() before Show()
- Banner ads are the exception: they display automatically once Load() succeeds. Use Show() only to display a banner again after Hide()

Next Steps

With the integration and initialization done, move on to the format you plan to use.

To read revenue per impression, see Use ILRD.

DARO 2.0 SDK Migration

SDK Integration

How to Use DARO

FAQ

Legacy SDK

Getting Started

Before You Begin

Install SDK

Configure Project

Check iOS build settings

Initialize SDK

Mute and logging settings

Use Ad Instances

Best Practices

Working With Ad Instances

Next Steps

​Before You Begin

​Install SDK

​Configure Project

​Check iOS build settings

​Initialize SDK

​Mute and logging settings

​Use Ad Instances

​Best Practices

​Working With Ad Instances

​Next Steps

Before You Begin

Install SDK

Configure Project

Check iOS build settings

Initialize SDK

Mute and logging settings

Use Ad Instances

Best Practices

Working With Ad Instances

Next Steps