How to Send Start Trial and Subscribe Events to Ad Channels With Airbridge Postbacks
Send Airbridge Start Trial and Subscribe postbacks to ad channels, with filters for attribution, first event per device ID, and event value.

Key Takeaway
- You can send Start Trial and Subscribe from Airbridge's 25 preconfigured standard events to your ad channels by turning on Send postbacks in your channel integration settings.
- Delivery rules let you filter postbacks by attribution status, first occurrence per device ID, or a specific event value threshold.
- Only events already collected by Airbridge are available for selection in the postback settings after you submit any required postback keys.
Running paid acquisition for a consumer subscription app gets expensive fast when your ad networks only see app installs. You might spend your Monday ad budget testing creatives, see installs roll in, and realize by Friday that not a single user started a free trial or converted to a paid plan. When your ad channels do not know which clicks turned into trial starts or subscriptions, their algorithms keep bidding on people who download and immediately churn. Forwarding your in-app subscription events back to those ad networks gives them the conversion signals they need to evaluate campaign performance beyond the initial download.
How Postbacks Feed Ad Channels
Postback data gives ad channels visibility into what users do after clicking an ad, such as installing the app or making a purchase. Airbridge transmits this event and attribution data to an ad channel through a postback URL, which requires selecting a data transmission method and configuring the matching postback URL for that method.
If you are running campaigns on a small team without a dedicated data engineer, you need this pipeline to work across your core acquisition channels. The Airbridge Core Plan includes ad network attribution for Google, Meta, Apple Ads, and TikTok. On Core, mobile app postbacks are also available for those four channels.
Once postbacks are active, your ad networks receive the downstream signals required to see which ads drive actual trial and subscription activity rather than just raw install volume.
Configuring Postback Delivery Rules
For Mobile app postback, you can turn on the Send postbacks toggle inside an ad channel's Postback tab in the Airbridge dashboard. To set up postbacks for an ad channel from scratch, navigate to Integration, select the channel you are working with, switch on Send postbacks in the Postback tab, and click Postback event setup. Some ad channels require postback keys; depending on the channel's requirements, you can submit or edit these using Postback Keys located beside the Send postbacks toggle after checking the individual channel integration guide. Once your event setup is complete, you can adjust your configuration through Edit event data or Edit delivery rules.
Sending every single event blindly to an ad network is not always the right move for your campaign structure. You might want an ad channel to see only the conversions it directly caused, or you might want to feed it all conversions so its algorithm learns faster from your broader user base. You also might want to prevent renewal events from being counted as brand-new customer acquisitions. Airbridge gives you three specific delivery rules to control exactly how and when postbacks fire:
- Attribution delivery rule: When set to Attributed events, Airbridge sends only the events attributed to that specific ad channel; when set to All events, it sends both attributed and non-attributed events.
- First or All Events rule: You can choose to send only the first event per device ID or all occurring events, though Ad Impression events are always sent as all events because this setting is unavailable for them.
- Event Value filter: You can filter postbacks using a numeric event property like revenue so that a threshold limits delivery to events meeting your criterion, with values calculated in the app's standard currency regardless of the raw-data currency.
Mapping Start Trial and Subscribe Events
Airbridge provides three standard subscription events: Start Trial, Subscribe, and Unsubscribe. When you are forwarding events to ad channels or third-party platforms, the event category used for Start Trial is airbridge.startTrial. Knowing how these events behave in your lifecycle is critical before you map them to an ad network's optimization goals. Depending on how your app or billing integration logs it, Subscribe can be recorded for the first paid purchase and again for renewals. Because of that, pairing it with the First or All Events delivery rule helps you control whether an ad channel receives only the initial conversion per device ID or every subsequent renewal as well.
If you are configuring in-app event postbacks for TikTok For Business, map the Airbridge events you want to use for AEO to the corresponding TikTok For Business events in Airbridge's TikTok For Business integration settings.
Verifying Events and Tracking Outcomes
When you open your postback settings to select the events you want to forward, any required postback keys must be submitted first, and only events that have already been collected by Airbridge will be available for selection.
Airbridge provides 25 preconfigured standard events in total, three of which are subscription events: Start Trial, Subscribe, and Unsubscribe.
You can view your subscription outcomes broken down by channel and campaign.
FAQS
FAQ
How much does the Airbridge Core Plan cost after the free trial?
The Airbridge Core Plan starts with a 30-day free trial and then costs $40+/mo, which includes 500,000 data points per month, charges $0.0001 for each additional data point, and can be canceled at any time.
Which ad channels are supported for attribution on the Core Plan?
The Airbridge Core Plan supports ad network attribution for Meta Ads, Google Ads, Apple Ads, and TikTok for Business.
Why does the Subscribe event fire more than once for the same user?
Subscribe can be recorded for the first paid purchase and again for renewals, depending on how your app or billing integration logs it. If you only want an ad channel to receive the first occurrence per device ID, you can adjust the First or All Events delivery rule in your postback settings.
Related reading
Feed your ad networks
Install the self-serve SDK and configure postback rules for your app.


