RevenueCat

Integrate Botsi AI Pricing with RevenueCat so each user sees the optimal Offering based on Botsi's prediction. RevenueCat handles Offerings and paywall display. Botsi decides which Offering that user should get.

Complete the AI Pricing Model Setup first. This page assumes the Botsi side already works end to end.

Integration flow#

1. Create a Botsi Profile at launch and keep the profileId.
2. Send events, attributes, and attribution during onboarding so the model has signal.
3. Call Fetch Paywall with the profile and placement → receive the predicted externalId (and paywallSessionId).
4. Set a RevenueCat custom attribute to that externalId.
5. Call syncAttributesAndOfferingsIfNeeded(), then fetch Offerings → RevenueCat Targeting Rules return the matching Offering.
6. Send paywall_shown via the Send Paywall Shown Event API when the paywall is presented.
7. Validate the purchase with Botsi after a successful RevenueCat transaction.

See the full API sequence in the AI Pricing Model API.

Matching Offerings and Paywalls#

Decide which prices you want to show, then configure Offerings in RevenueCat and matching Paywalls in Botsi with the same products.

If you use RevenueCat Offerings to control which products appear on a paywall, set up those Offerings with the products attached in the RevenueCat dashboard:

For several annual price points:

• Offering default — annual → com.app.pro.annual_standard
• Offering discounted — annual → com.app.pro.annual_discounted

Then create corresponding Paywalls in Botsi and attach the same Products. That is what tells the model which prices are available to choose between.

External ID and Fetch Paywall#

Set the external ID on each Botsi Paywall when you configure it. Any unique value works; a readable convention pays off when you see the same string in RevenueCat Targeting Rules and Botsi analytics (for example onboardingPaywall_29.99Annual_v2).

Fetch Paywall returns that value as data.externalId. You could use data.id instead, but it is a number you cannot set or recognize at a glance. Use externalId.

Targeting with a custom attribute#

Write the externalId into a RevenueCat custom attribute, then configure Targeting Rules to match on it. The attribute name is yours; something like botsi_paywall_id or botsi_paywall_prediction is legible to teammates. Use the externalId as the value.

// Set the custom attribute with Botsi's predicted paywall ID
Purchases.shared.attribution.setAttributes([
    "botsi_paywall_id": botsiExternalPaywallId
])

// Sync attributes and refresh offerings so targeting sees the new value
_ = try await Purchases.shared.syncAttributesAndOfferingsIfNeeded()

// Then fetch offerings / present your paywall as usual

// Set the custom attribute with Botsi's predicted paywall ID
Purchases.sharedInstance.setAttributes(
    mapOf("botsi_paywall_id" to botsiExternalPaywallId)
)

// Sync attributes and refresh offerings so targeting sees the new value
Purchases.sharedInstance.syncAttributesAndOfferingsIfNeeded { offerings ->
    // Present the current offering from the refreshed result
}

import Purchases from 'react-native-purchases';

// Set the custom attribute with Botsi's predicted paywall ID
Purchases.setAttributes({
  botsi_paywall_id: botsiExternalPaywallId,
});

// Sync attributes and refresh offerings for targeting
await Purchases.syncAttributesAndOfferingsIfNeeded();

// Then fetch offerings / present your paywall as usual

using RevenueCat;

var purchases = GetComponent<Purchases>();

// Set the custom attribute with Botsi's predicted paywall ID
purchases.SetAttributes(new Dictionary<string, string> {
    { "botsi_paywall_id", botsiExternalPaywallId }
});

// Sync attributes and refresh offerings for targeting
purchases.SyncAttributesAndOfferingsIfNeeded();

// Then fetch offerings / present your paywall as usual

Sending the impression#

When the paywall is shown, send paywall_shown with the paywallSessionId from the Fetch Paywall response. Details: Send Paywall Shown Event.

Sending the purchase#

After a successful purchase through RevenueCat, extract the iOS transaction ID and original transaction ID, or the Android purchase token, and post them to the matching validate endpoint. See RevenueCat's making purchases docs for how each SDK surfaces transaction data.

let result = try await Purchases.shared.purchase(package: package)
if let tx = result.transaction {
    let appleTransactionId = tx.transactionIdentifier   // e.g. "2000001234567890"
    let originalTxId = tx.sk2Transaction?.originalID
    // POST /v2/purchases/apple-store/validate
}

val result = purchases.purchase(activity, packageToBuy)
result?.let { tx ->
    val purchaseToken = tx.purchaseToken    // e.g. "abcdefhijklmnop..."
    val orderId = tx.orderId                // if you also need the Google orderId
    // POST /v2/purchases/play-store/validate
}

import Purchases from 'react-native-purchases';

const { customerInfo } = await Purchases.purchasePackage(pkg);

// For subscriptions, check customerInfo.entitlements
// For non-subscriptions, check customerInfo.nonSubscriptionTransactions
const transactions = customerInfo.nonSubscriptionTransactions;
if (transactions.length > 0) {
  const transactionId = transactions[0].transactionIdentifier;
  // iOS:     POST /v2/purchases/apple-store/validate
  // Android: POST /v2/purchases/play-store/validate
}

using RevenueCat;

purchases.PurchasePackage(package, (productIdentifier, customerInfo, userCancelled, error) => {
    if (!userCancelled && error == null) {
        var transactions = customerInfo.NonSubscriptionTransactions;
        if (transactions.Count > 0) {
            var transactionId = transactions[0].TransactionIdentifier;
            // iOS:     POST /v2/purchases/apple-store/validate
            // Android: POST /v2/purchases/play-store/validate
        }
    }
});

See Validate Apple Store Purchase and Validate Google Play Store Purchase.

Forwarding subscription events to Botsi#

Use this if RevenueCat is your revenue infrastructure and you use Botsi for AI personalization rather than for revenue infrastructure. RevenueCat receives App Store Server Notifications directly, so forwarding them keeps Botsi's analytics and model data complete.

1. In Botsi, copy the URL for App Store server notifications from App Settings → Apple App Store → App Store server notifications. It looks like https://api.botsi.com/v2/notifications/apple/<notification-key>. See Notification URLs.
2. In RevenueCat, go to Apps → your iOS app → Apple Server to Server notification settings.
3. Paste the Botsi URL into Apple Server Notification Forwarding URL and save.

RevenueCat forwards Apple's notifications to Botsi as they arrive. See App Store Server Notifications.

Reporting revenue through the RevenueCat webhook#

Botsi can also receive RevenueCat's own webhook and record App Store and Google Play revenue from it for revenue reporting. The webhook records revenue only: it doesn't change subscriber status or Access Levels. See Notification URLs.

Connecting the webhook#

1. In Botsi, go to App Settings → RevenueCat → Connect your webhook and copy the Webhook URL.
2. In RevenueCat, add a webhook integration pointed at that URL, and turn on HMAC webhook signing for it.
3. Copy RevenueCat's signing secret into Botsi. RevenueCat shows it only when you create or rotate it.
4. Map each RevenueCat app ID to its store, App Store or Play Store. Use RevenueCat's app ID, not your bundle ID.
5. Enable the integration. Botsi needs the signing secret and at least one app mapping before it can be enabled.

The header has the form t=<unix timestamp>,v1=<hex signature>. The signature must be the HMAC-SHA256 of <t>. followed by the raw request body, keyed with the signing secret, and t must be within 5 minutes of Botsi's clock.

Only one of RevenueCat, Superwall, and Adapty can report an app's revenue at a time. See Using one revenue platform at a time.

What the webhook records#

• App Store and Google Play revenue, for revenue reporting. Events from other stores are stored but ignored.
• Status events, at $0.
• RevenueCat's TEST event confirms the connection and records no revenue.

Webhook responses#

Notes#

• Configure server-side notifications on both RevenueCat and Botsi for accurate analytics.
• The custom attribute you set must match the Targeting Rules in the RevenueCat dashboard, or targeting silently fails to match.
• Handle errors from both APIs. A failed Fetch Paywall should fall back to a known Offering rather than showing nothing.
• Test in sandbox before production.
• Call syncAttributesAndOfferingsIfNeeded() after setting the attribute and before displaying the paywall. The method is rate-limited (typically five calls per minute); prefer calling it once per prediction, not on every UI refresh.