Configure a Third-Party Integration

Botsi allows you to integrate with various third-party platforms, such as the Apple App Store and Google Play Store, to manage in-app purchases and subscriptions, analyze purchase data, and gain insights into your app's revenue. Below are the steps to configure these integrations.

Connect to Your Apple App Store Account

To integrate Botsi with your Apple App Store account for managing in-app purchases, follow these steps to configure settings in your Apple Developer and App Store Connect accounts:

1

Obtain your App's Bundle ID

This unique identifier for your app can be found in App Store Connect under the App Information section.

2

Enable the In-App Purchase API (StoreKit 2)

Generate an In-App Purchase Key in App Store Connect. Download the .p8 key file and save the Key ID and Issuer ID.

3

Retrieve your Shared Secret

This can be found in App Store Connect under the App Information section. (For StoreKit 1 or legacy receipt validation.)

Once you have gathered this information, you can enter it into the Botsi dashboard to connect your Apple App Store account.

For more detailed information, refer to the Connect to Your App Store Account page.

Connect to Your Google Play Store Account

Connecting Botsi to your Google Play Store account is essential for managing in-app purchases and subscriptions for your Android applications. This integration enables Botsi to analyze purchase data, manage subscriptions, and provide insights into app revenue.

To connect Botsi, you need to:

1

Get the Package Name

This is the unique identifier of your app, located in the Google Play Developer Console.

2

Enable the In-App Purchase API

Ensure the Google Play Developer API is enabled in your Google Cloud project to programmatically manage purchases.

3

Obtain the Service Account Key File:

This file, obtained from the Google Play Developer Console, authenticates Botsi's access to Google Play services.

After collecting this information, enter it into the Botsi dashboard to complete the integration process.

For more detailed information, refer to the Connect to Your Google Play Store Account page.

Events Feed in Integrations

Botsi's Event Feed feature is designed to help you track and display customer interactions with your products or services in real-time. This feed is crucial for monitoring customer behavior and gaining insights into how users engage with your offerings.

The connection to third-party integrations lies in the data flow:

1

Data Ingestion via Integrations

The initial integrations with platforms like the Apple App Store and Google Play Store are essential for Botsi to ingest raw purchase and subscription data. These integrations act as the primary source of information regarding your users' transactions.

2

Event Processing by Botsi

Once this data is pulled into Botsi through these third-party connections, Botsi processes it into meaningful events. These events represent key customer actions and lifecycle stages related to your products.

3

Real-time Visibility in Event Feed

The Event Feed then provides a centralized, real-time display of these processed customer interactions. It shows crucial details such as trial activations, purchases, renewals, customer IDs, product purchased, revenue generated, and timing.

In essence, the third-party integrations (e.g., App Store, Google Play) provide the raw material (transaction data), and Botsi's Event Feed transforms this into actionable insights, making it visible and understandable. While the direct integrations mentioned here are for data acquisition into Botsi, the enriched event data visible in the Event Feed often forms the basis for potential future integrations with other types of third-party tools (e.g., CRM systems, marketing automation platforms, or business intelligence dashboards) where you might want to export or leverage this detailed event information for further analysis, segmentation, or automated customer engagement.

For more information on the Event Feed, please visit the Botsi Event Feed documentation.