Airbridge supports integration with Adapty. With the integration, you can measure the in-app subscription attribution with Airbridge and send the attribution data to Adapty.
Integration with Adapty
With the integration, you can send subscription-related events from Adapty to Airbridge and send attribution data from Airbridge to Adapty.
To enable the integration, you have to send the subscription-related events from Adapty to Airbridge first. Once Airbridge receives the events from Adapty, the Adapty API token will show in your Adapty dashboard that is needed to send the attribution data from Airbridge to Adapty.
You must add codes to the Adapty SDK in order to be able to collect the Airbridge Device UUID so that the Airbridge SDK and Adapty SDK can uniquely identify each user. For more details, read the developer guide.
Send subscription data from Adapty to Airbridge
1. Navigate to [Integrations]>[Third-party Integrations] and select “Adapty”.
2. Find the Airbridge app name and API token. You can copy the values by clicking on them.
3. Sign in to your Adapty account.
4. Go to the [Integrations] menu and select “Airbridge”.
5. Switch on the toggle.
6. Paste the Airbridge app name and Airbridge API token into the respective fields.
You can check the checkboxes for “Report proceeds”, ”Report user’s currency”, “Exclude historical events,” and “Send trial price” to further specify conditions for sending subscription-related events to Airbridge.
The revenue generated from subscription-related events can be viewed in the Airbridge reports by selecting the Subscription Revenue (App) metric.
|Report proceeds||If checked, proceed amounts after App Store or Google Play Store fees are reported.|
|Report user’s currency||If checked, the revenue will be reported in the currency of the user’s choice. If not checked, the revenue is reported in USD.|
|Exclude historical events||If checked, events that occurred before the Adapty SDK install are excluded from the reporting. For example, if the subscription was renewed on the 5th, and the Adapty SDK was installed on the 1st, event data starting from the 5th is sent.|
|Send trial price||f checked, the revenue generated from trials will be sent. For free trials, set the trial price percentage to 0%.|
The events that occur before the Adapty SDK install will be sent to Airbridge in the last 24 hours instead of the real event time. There will be a discrepancy between the actual time the event occurred and the time displayed in the Airbridge dashboard. To avoid this discrepancy, please check the checkbox next to “Exclude historical events”.
In the “Events names” section, you can select which events to send to Airbridge. There are three event groups: Subscriptions, Trials, and Issues. You can change whether to send particular events at any time by clicking the toggle.
7. Click the “Save” button to save the settings.
Send attribution data from Airbridge to Adapty
When integrating Adapty with Airbridge for the first time, you have to copy the Airbridge app name and Airbridge API token from your Airbridge dashboard and paste them into your Adapty dashboard. If you have not completed these steps yet, please refer to the “Send subscription-related events from Adapty to Airbridge” section above.
1. Sign in to your Adapty dashboard.
2. Go to the [Integrations] menu and select “Airbridge”.
3. Copy the Adapty API token. If the toggle is switched off, click on it to switch it on.
4. In your Airbridge dashboard, navigate to [Integrations]>[Third-party Integrations] and select “Adapty.”
5. Paste the Adapty API token into the field and click the “Done” button to start sending the attribution data to Adapty. Airbridge sends only install events to Adapty. The Adapty API token consists of only alphabet letters, numbers, periods (”.”), and underscores (”_”).
You can see the connection status badge next to the channel name. Once the Adapty API token is entered and the data delivery is initiated, the “Active” status badge will show.
How to update the Adapty API token
If you have entered the wrong Adapty API token or if you have created a new account and have a new token, you have to update the token in Airbridge. Click the [Edit] icon to enter a new token. Click the “Done” button to save changes.
How to delete the Adapty API token
Click the “Delete” button to delete the Adapty API token. When you delete the token, Airbridge and Adapty will be disconnected. Even if you delete the token, any data sent to Adapty before the deletion will be saved. If you want to reconnect Airbridge with Adapty, enter the Adapty API token again.
How to view data
In the Airbridge dashboard, you can view your subscription-related events sent from Adapty along with the attribution data tracked with Airbridge. Key events are mapped with Airbridge standard events. You can’t change the names of the Adapty events that are mapped with Airbridge standard events. You can view the Adapty events by selecting the corresponding Airbridge events in your reports.
|Key Events||Adapty Event||Airbridge Event|
|Start of a trial||trial_started||startTrial|
|Conversion from a trial||trial_converted||subscribe|
|Purchase of subscription service||subscription_initial_purchase||subscribe|
Adapty Event Mapping
All Adapty events other than the key events listed above are mapped with Airbridge’s custom events. Custom event names are the same as the Adapty events. The properties of Adapty events mapped as custom events can be found as the custom attributes of the custom events in the raw data exports.
Meta Business data
User ID matching
You must add codes to the Adapty SDK in order to collect the Airbridge Device UUID. If the Adapty SDK fails to collect the Airbridge Device UUID, the number of unique users displayed in the Airbridge dashboard may be higher than the actual number. For more details, read the developer guide.
If a new subscription-related event is defined and tracked with the Airbridge SDK after being integrated with Adapty, you may see duplicate events in your reports. To avoid event duplication, your Airbridge SDK that is already integrated with Adapty shall not track subscription-related events.