Analytics Mode

Analytics (Observer) mode gives you best-in-class subscription analytics while you keep your existing in-app purchase flow. You can also use real-time subscriptions events in third-party integrations, webhooks, and collect Apple Ads attribution on iOS using this mode. After you install the SDK, follow the steps below.

1. Launch SDK

Initialize the SDK in Analytics mode:

import Qonversion

func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
    let config = Qonversion.Configuration(projectKey: "projectKey", launchMode: .analytics)
    Qonversion.initWithConfig(config)
  	return true
}

#import "Qonversion.h"

- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {
    QONConfiguration *configuration = [[QONConfiguration alloc] initWithProjectKey:@"projectKey" launchMode:QONLaunchModeAnalytics];
    [Qonversion initWithConfig:configuration];

    return YES;
}

import com.qonversion.android.sdk.Qonversion;
import com.qonversion.android.sdk.QonversionConfig;
import com.qonversion.android.sdk.dto.QLaunchMode;

public class App extends Application {
    @Override
    public void onCreate() {
        super.onCreate();
        final QonversionConfig qonversionConfig = new QonversionConfig.Builder(
                this,
                "projectKey",
                QLaunchMode.Analytics
        ).build();
        Qonversion.initialize(qonversionConfig);
    }
}

import com.qonversion.android.sdk.Qonversion
import com.qonversion.android.sdk.QonversionConfig
import com.qonversion.android.sdk.dto.QLaunchMode

class App : Application() {
    override fun onCreate() {
        super.onCreate()
        val qonversionConfig = QonversionConfig.Builder(
            this,
            "projectKey",
            QLaunchMode.Analytics
        ).build()
        Qonversion.initialize(qonversionConfig)
    }
}

import 'package:qonversion_flutter/qonversion_flutter.dart';

final config = new QonversionConfigBuilder(
  'projectKey',
  QLaunchMode.analytics
).build();
Qonversion.initialize(config);

import Qonversion, {
  QonversionConfigBuilder,
  LaunchMode,
} from '@qonversion/react-native-sdk';

const config = new QonversionConfigBuilder(
  'projectKey',
  LaunchMode.ANALYTICS
).build();
Qonversion.initialize(config);

using QonversionUnity;

private void Start()
{
    QonversionConfig config = new QonversionConfigBuilder(
            "projectKey",
            LaunchMode.Analytics
        ).Build();
    Qonversion.Initialize(config);
}

const config = new Qonversion.ConfigBuilder(
  'projectKey',
  Qonversion.LaunchMode.ANALYTICS,
).build();
Qonversion.initialize(config);

import Qonversion, {
  QonversionConfigBuilder,
  LaunchMode,
} from '@qonversion/capacitor-plugin';

const config = new QonversionConfigBuilder(
  'projectKey',
  LaunchMode.ANALYTICS
).build();
Qonversion.initialize(config);

→Get your Qonversion Project Key

2. Sync Purchases

iOS, StoreKit 2

Subscriptions only

In case you’re using StoreKit Version 1, we automatically handle all the needed data about transactions that occurred. However, in the case of StoreKit Version 2, it is necessary to leverage thesyncStoreKit2Purchases() SDK method. Call this function every time you receive a successful purchase result or auto-renewed transaction.

syncStoreKit2Purchases() is part of the Swift-only API and lives on QonversionSwift, not on Qonversion. With Swift Package Manager it is in the QonversionSwift module, so add import QonversionSwift; with CocoaPods everything is in the single Qonversion module. The method is not available from Objective-C — QonversionSwift is not exposed to the Objective-C runtime. StoreKit 2 itself requires iOS 15.0, macOS 12.0, tvOS 15.0 or watchOS 8.0; on earlier systems the call does nothing.

import QonversionSwift // Swift Package Manager only; with CocoaPods use import Qonversion

QonversionSwift.shared.syncStoreKit2Purchases()

Qonversion.getSharedInstance().syncStoreKit2Purchases();

Qonversion.getSharedInstance().syncStoreKit2Purchases();

Qonversion.GetSharedInstance().SyncStoreKit2Purchases();

Qonversion.getSharedInstance().syncStoreKit2Purchases();

Qonversion.getSharedInstance().syncStoreKit2Purchases();

Subscriptions & Consumables

In case you’re using StoreKit Version 2 and selling Subscriptions and Consumables we recommend using one of these methods before finishing transactions: These three methods are also Swift-only (QonversionSwift) and are marked @available(iOS 15.0, macOS 12.0, tvOS 15.0, watchOS 8.0, visionOS 1.0, *).

import QonversionSwift // Swift Package Manager only; with CocoaPods use import Qonversion

if #available(iOS 15.0, macOS 12.0, tvOS 15.0, watchOS 8.0, visionOS 1.0, *) {
  await QonversionSwift.shared.syncStoreKit2Transactions()

  await QonversionSwift.shared.handleTransaction(transaction)

  await QonversionSwift.shared.handleTransactions(transactions)
}

Android

Check whether you have set your products up correctly. Make your GooglePlay subscriptions backwards compatible to have the best possible accuracy in Qonversion. Learn more here
While you are using Qonversion SDKs in Analytics Mode, in-app purchases implementation is entirely on your side, which means acknowledging every purchase is on your side too. If your app does not acknowledge or consume a purchase within 3 days, Google Play refunds it and revokes the entitlement. The 3 days count from the moment the purchase reaches the PURCHASED state. Consume consumable products and acknowledge everything else. See the Google Play Billing documentation on processing purchase details. Purchases made by license testers follow the same rule on a shortened schedule: an unacknowledged test purchase is refunded within minutes. Test subscriptions also renew on an accelerated schedule and renew at most six times. See Test Google Play Billing and Test Purchases — Google Play.
Sync data with Qonversion in your current purchase flow. Call syncPurchases() after every purchase.

Qonversion.getSharedInstance().syncPurchases();

Qonversion.shared.syncPurchases()

Qonversion.getSharedInstance().syncPurchases();

Qonversion.getSharedInstance().syncPurchases();

Qonversion.GetSharedInstance().SyncPurchases();

Qonversion.getSharedInstance().syncPurchases();

Qonversion.getSharedInstance().syncPurchases();

3. (Optional) Enable Server-to-Server notifications

Qonversion checks user receipts regularly and does not require server-to-server notifications from Apple or Google. Nevertheless, due to these notifications, your analytics charts, third-party integrations and webhooks will work much closer to real-time.

Guide on Apple Server-to-Server Notifications
Guide on Google Developer Notifications

4. Set additional user attributes

Optionally, to improve attribution in Adjust, AppsFlyer, Singular, or to match Qonversion revenue events to users in third-party tools, you can share with us such attributes as User Identifier, IDFA (Identifier for Advertisers, iOS 14.5+ only) or ASID (App set ID, Android 12+ only). Please, follow this guide to learn more.

Next steps

With Analytics Mode running, put your subscription data to work. For near real-time charts, also enable Apple Server-to-Server Notifications and Google Developer Notifications.

Set user properties

Attach custom user properties to segment subscribers and improve attribution.

Connect integrations

Forward real-time subscription events to Adjust, AppsFlyer, Amplitude, and more.

Explore analytics

Track subscription revenue, conversions, and cohorts in the Qonversion dashboard.

Enable server notifications

Add Apple and Google server notifications for near real-time analytics.

Start here

Install the SDK

Choose your mode

Connect your stores

Migrate to Qonversion

Test and go live

Your project

1. Launch SDK

2. Sync Purchases

iOS, StoreKit 2

Subscriptions only

Subscriptions & Consumables

Android

3. (Optional) Enable Server-to-Server notifications

4. Set additional user attributes

Next steps

Set user properties

Connect integrations

Explore analytics

Enable server notifications

​1. Launch SDK

​2. Sync Purchases

​iOS, StoreKit 2

​Subscriptions only

​Subscriptions & Consumables

​Android

​3. (Optional) Enable Server-to-Server notifications

​4. Set additional user attributes

​Next steps

Set user properties

Connect integrations

Explore analytics

Enable server notifications

1. Launch SDK

2. Sync Purchases

iOS, StoreKit 2

Subscriptions only

Subscriptions & Consumables

Android

3. (Optional) Enable Server-to-Server notifications

4. Set additional user attributes

Next steps