Report transactions in Observer Mode in Flutter SDK

In Observer mode, the Adapty SDK can’t track purchases made through your existing purchase system on its own. You need to report transactions from your app store. It’s crucial to set this up before releasing your app to avoid errors in analytics.

Use reportTransaction to explicitly report each transaction for Adapty to recognize it.

Don’t skip transaction reporting! If you don’t call reportTransaction, Adapty won’t recognize the transaction, it won’t appear in analytics, and it won’t be sent to integrations.

If you use Adapty paywalls, include the variationId when reporting a transaction. This links the purchase to the paywall that triggered it, ensuring accurate paywall analytics.

try {
    // every time when calling transaction.finish()
    await Adapty().reportTransaction(
        "YOUR_TRANSACTION_ID", 
        variationId: "PAYWALL_VARIATION_ID", // optional
    );
} on AdaptyError catch (adaptyError) {
    // handle the error
} catch (e) {
    // handle the error
}

Parameters:

Parameter	Presence	Description
transactionId	required	For iOS: Identifier of the transaction. For Android: String identifier `purchase.getOrderId` of the purchase, where the purchase is an instance of the billing library Purchase class.
variationId	optional	The string identifier of the variation. You can get it using `variationId` property of the AdaptyPaywall object.

In Observer mode, the Adapty SDK can’t track purchases made through your existing purchase system on its own. You need to report transactions from your app store or restore them. It’s crucial to set this up before releasing your app to avoid errors in analytics.

Use reportTransaction on both platforms to explicitly report each transaction, and use restorePurchases on Android as an additional step to ensure Adapty recognizes it.

Don’t skip transaction reporting and purchase restoring! If you don’t call these methods, Adapty won’t recognize the transaction, it won’t appear in analytics, and it won’t be sent to integrations.

If you use Adapty paywalls, include the variationId when reporting a transaction. This links the purchase to the paywall that triggered it, ensuring accurate paywall analytics.

// every time when calling transaction.finish()
if (Platform.isAndroid) {
    try {
        await Adapty().restorePurchases();
    } on AdaptyError catch (adaptyError) {
        // handle the error
    } catch (e) {
    }
}

try {
    // every time when calling transaction.finish()
    await Adapty().reportTransaction(
        "YOUR_TRANSACTION_ID", 
        variationId: "PAYWALL_VARIATION_ID", // optional
    );
} on AdaptyError catch (adaptyError) {
    // handle the error
} catch (e) {
    // handle the error
}

Parameters:

Parameter	Presence	Description
transactionId	required	For iOS, StoreKit 1: an SKPaymentTransaction object. For iOS, StoreKit 2: Transaction object. For Android: String identifier (purchase.getOrderId of the purchase, where the purchase is an instance of the billing library Purchase class.
variationId	optional	The string identifier of the variation. You can get it using `variationId` property of the AdaptyPaywall object.

Reporting transactions

Use restorePurchases to report a transaction to Adapty in Observer Mode, as explained on the Restore Purchases in Mobile Code page.

Don’t skip transaction reporting! If you don’t call restorePurchases, Adapty won’t recognize the transaction, it won’t appear in analytics, and it won’t be sent to integrations.

Associating paywalls to transactions

Adapty SDK cannot determine the source of purchases, as you are the one processing them. Therefore, if you intend to use paywalls and/or A/B tests in Observer mode, you need to associate the transaction coming from your app store with the corresponding paywall in your mobile app code. This is important to get right before releasing your app, otherwise, it will lead to errors in analytics.

final transactionId = transaction.transactionIdentifier
final variationId = paywall.variationId

try {
  await Adapty().setVariationId('transactionId', variationId);
} on AdaptyError catch (adaptyError) {
  // handle the error
} catch (e) {
}