Skip to main content
GitHub release

​
Install via Git URL

Available starting from Unity 2018.3. Just add this line to the Packages/manifest.json file of your Unity Project:

​
Install via OpenUPM

Qonversion SDK package is available on the openupm registry. You can install it via openupm-cli.

​
Install Native Dependencies

The SDK declares its native iOS and Android dependencies in Editor/QonversionDependencies.xml and relies on the External Dependency Manager for Unity (EDM4U) to resolve them. Make sure your project contains EDM4U, otherwise the native modules are not installed and the build fails. Install it in one of two ways:
  • OpenUPM — openupm add com.google.external-dependency-manager.
  • Unity package — download external-dependency-manager-<version>.unitypackage from the root of the EDM4U repository at the release tag (the GitHub releases carry no assets), then in the Unity Editor click Assets → Import Package → Custom Package… and import it.
If your project pulled EDM4U from Google’s former Unity package registry (unityregistry-pa.googleapis.com), it no longer resolves — switch to OpenUPM or the .unitypackage.

​
iOS: Swift Package Manager (default) or CocoaPods

Starting from Unity SDK 9.10.0 the iOS dependency (QonversionSandwich, which brings the Qonversion iOS SDK) is declared both as a Swift package and as a CocoaPod. EDM4U picks the Swift package when all of the following are true, and falls back to the CocoaPod otherwise:
  • EDM4U 1.2.189 or newer;
  • Unity 2021.3 or newer;
  • Swift Package Manager Integration is enabled in Assets → External Dependency Manager → iOS Resolver → Settings (it is enabled by default).
On the Swift Package Manager path EDM4U links the package into the UnityFramework target of the exported Xcode project and the QonversionSandwich pod is left out of the generated Podfile; the Install Cocoapods step is not needed for Qonversion once you turn off Allow empty Podfile generation (see the notes below). The build machine needs Xcode 15 or newer and access to github.com to resolve the package; the iOS deployment target must be 13.0 or higher.
Do not use EDM4U 1.2.187 or 1.2.188 with Unity older than 2021.3: those versions drop the pod when a Swift package is declared without adding the package (fixed in EDM4U 1.2.189). Update EDM4U or turn Swift Package Manager Integration off.
Notes for the Swift Package Manager path:
  • With default EDM4U settings an empty Podfile is still generated and pod install still runs, so the CocoaPods tool must still be installed and the build produces Unity-iPhone.xcworkspace as before. If Qonversion is your only pod, turn off Allow empty Podfile generation in the iOS Resolver settings — then no Podfile is generated and you open and build Unity-iPhone.xcodeproj instead of the workspace.
  • If your project adds the native iOS SDK itself — a Qonversion pod in your own *Dependencies.xml or Podfile, or a qonversion-ios-sdk Swift package — remove it: the sandwich package depends on the exact matching Qonversion iOS SDK version, a second copy produces duplicate symbols or a package resolution conflict.
  • To stay on CocoaPods, turn off Swift Package Manager Integration in the iOS Resolver settings.
CocoaPods trunk becomes read-only on December 2, 2026: new versions of the native Qonversion SDK will no longer be published to CocoaPods trunk — the Swift Package Manager path is the supported way to receive them; existing CocoaPods builds keep working. Move to the Swift Package Manager path before then — see the migration guide.

​
Resolve the dependencies

After installing EDM4U:
  1. For iOS on the CocoaPods path — Assets → External Dependency Manager → iOS Resolver → Install Cocoapods (once per machine). On the Swift Package Manager path nothing is required: the package is added when you build the iOS player.
  2. For Android — Assets → External Dependency Manager → Android Resolver → Resolve.
Now you are ready to build and run your project!

​
Kids Mode for Qonversion Unity SDK

In case you are building an App for Kids, please follow this guide to learn more about Kids Mode for Qonversion SDKs.

​
Next steps

The SDK is installed. Choose the mode to implement — this determines how much code you write next.