How to Send RevenueCat Purchase Events to Meta and TikTok
Connect RevenueCat to Airbridge, align device and user IDs, then map collected subscription events to Meta and TikTok postbacks for ad optimization.

Key Takeaway
- Connect your subscription billing tool to Airbridge using your subdomain and token, then align device and user identifiers across both SDKs.
- Route trials, initial payments, and renewals into the same campaign view and send conversions back to your ad networks.
- Select collected events in Airbridge postback settings, map them to channel event names, and for some channels, choose whether to include revenue data.
Running paid acquisition for a consumer subscription app gets expensive fast when your ad networks optimize for raw app installs instead of actual subscribers. With the Airbridge Core Plan, starting with a 30-day free trial and then $40+/mo, you can connect your subscription billing setup, tie subscription activity back to your campaigns, and configure postback settings so ad algorithms optimize for paying users.
Connect Your Account
The Core Plan includes up to two third-party integrations, and the Core Plan page lists RevenueCat among the tools those integrations cover. You can link the two dashboards in a few steps using the integration setup guide:
- Head over to your billing dashboard, open Integrations in the left sidebar, and select Airbridge under the Attribution section.
- Paste the Airbridge Subdomain and Airbridge Token, copied from Integrations > Third-party Integration > RevenueCat in the Airbridge dashboard, into the corresponding fields.
- Scroll to the Event names section and select Use default event names so the pre-mapped event names auto-fill.
- Click Add integration to finish the dashboard connection.
Pass Device and User IDs
Your app code needs to pass identifiers between the two SDKs.
First, configure your billing SDK to send the device IDs collected by Airbridge. Next, make sure User IDs are logged identically in both the Airbridge SDK and your subscription platform. The App User ID from your subscription tool should be sent to the Airbridge SDK alongside early lifecycle events like sign-up and sign-in, which usually happen before a user ever subscribes.
If Airbridge cannot find a matching User ID from your subscription events, it generates a random User ID instead. Because those unmatched events get assigned to newly generated IDs, your Airbridge reports may end up displaying a higher number of users for subscription-related events than you actually have.
Subscription Events Available
Once the integration and SDK identifiers are in place, trials, payments, and renewals land on the same campaigns inside Airbridge, and those conversions go back to your ad channels.
When you use the default event name setup, subscription lifecycle events map into Airbridge in two ways depending on whether they match standard events or custom events. The table below shows part of the mapping; the integration guide also lists custom events such as SUBSCRIPTION_EXTENDED, REFUND_REVERSED, and REFUND:
| Mapping Type | Incoming Subscription Event | Mapped Airbridge Event Name |
|---|---|---|
| Default standard-event mapping | TRIAL_STARTED | Start Trial |
| Default standard-event mapping | INITIAL_PURCHASE, TRIAL_CONVERTED, RENEWAL | Subscribe |
| Default standard-event mapping | CANCELLATION | Unsubscribe |
| Default custom-event mapping | TRIAL_CANCELLED | TRIAL_CANCELLED |
| Default custom-event mapping | TRIAL | TRIAL |
| Default custom-event mapping | UNCANCELLATION | UNCANCELLATION |
| Default custom-event mapping | NON_RENEWING_PURCHASE | NON_RENEWING_PURCHASE |
| Default custom-event mapping | SUBSCRIPTION_PAUSED | SUBSCRIPTION_PAUSED |
| Default custom-event mapping | EXPIRATION | EXPIRATION |
| Default custom-event mapping | BILLING_ISSUE | BILLING_ISSUE |
| Default custom-event mapping | PRODUCT_CHANGE | PRODUCT_CHANGE |
| Default custom-event mapping | TRANSFER | TRANSFER |
For the events that follow the default custom-event mapping, the Airbridge dashboard displays them using their original event names, and their event data is included inside custom attributes. Custom events are listed as a Growth Plan feature on the pricing page, so check which of these events your plan collects.
Configure Channel Postbacks
Keep in mind that only events that have already been collected by Airbridge will show up for selection in the postback configuration screen.
Follow these steps to configure your ad-channel postbacks:
- In the Airbridge dashboard, navigate to Integration, select the ad channel you want to configure, and switch on the Send postbacks toggle in its Postback tab.
- Click Postback event setup to open the event selection view.
- Select the collected events and data you want to send, and set a delivery rule for them.
- Edit the event details for your ad-channel postbacks to configure the channel event names.
- If you ever need to adjust an event setup that is already complete, return to this view to edit the event data or update the delivery rules.
FAQS
FAQ
How does the Core Plan price subscription event tracking and channel attribution?
The Core Plan starts with a 30-day free trial and then costs $40+/mo with no annual contract, allowing you to cancel anytime. It includes 500,000 data points per month, with additional data points billed at $0.0001 each.
What reports and ad channels are included alongside subscription revenue aggregation?
You get access to Revenue, Funnel, Retention, and Cohort reports, plus Predictive LTV, and ad network attribution covers Google, Meta, Apple Ads, and TikTok.
Why aren't my newly mapped subscription events showing up in the postback setup list?
Only events that Airbridge has already collected appear for selection in postback settings.
Route trials to your ads
Connect your billing setup to Airbridge and send conversions back.


