Firebase Campaign Attribution for Mobile Apps: Connecting Campaigns to App Events
When you are running a consumer subscription app with a lean team, watching trials and purchases fire in your analytics dashboard without knowing which paid…
Key Takeaway
- Product analytics tools track in-app funnels and retention, yet they cannot reliably pinpoint which paid campaign, ad set, or creative brought each user in because they do not connect with ad networks as attribution authorities.
- Airbridge links installs and downstream events to the exact source, campaign, and creative, letting you see whether users went on to start a trial, subscribe, or pay.
- You can forward attribution data from Airbridge to your analytics setup through a server-to-server integration by passing the analytics App Instance ID as an Airbridge device alias in your app code.
When you are running a consumer subscription app with a lean team, watching trials and purchases fire in your analytics dashboard without knowing which paid campaign drove them makes budget decisions guesswork. You might be wondering if you need to replace your current analytics setup or simply add a dedicated attribution layer alongside it. Understanding where your existing analytics stops and how a campaign attribution layer connects to your app events helps you decide what your stack actually needs before you scale your ad spend.
Adding a Mobile Measurement Partner to Your Analytics Stack
If your team already uses a product analytics tool to monitor in-app behavior, you have visibility into how users move through onboarding funnels, how often they return, and which features they tap. The blind spot appears the moment you start spending on user acquisition. Because product analytics platforms are not integrated with ad networks as attribution authorities, they cannot reliably tell you which paid campaign, ad set, or creative acquired a given user.
This limitation becomes even clearer when you put meaningful spend behind more than one ad network. Suppose you are testing campaigns across multiple paid advertising channels at the same time. When a user converts, multiple paid channels might claim credit for the same user, and a product analytics tool cannot deduplicate those overlapping claims. An MMP steps in to reconcile those competing claims into a single attribution view. By collecting, attributing, and organizing mobile app data, an MMP gives you a unified picture of campaign performance across your marketing channels. Because the MMP operates independently of the ad networks it measures, it applies consistent attribution logic across every channel you run.
Adding an MMP does not mean abandoning your current product analytics setup. Many teams run both tools side by side: you use the MMP to handle acquisition attribution, and you keep using your product analytics tool to analyze in-app behavior. As an MMP providing cross-platform attribution, analytics, and deep linking across mobile and web in a single dashboard, Airbridge fits right into this workflow.
App Outcomes Connected to Campaigns Through Attribution
When you are evaluating whether an attribution layer is worth the engineering time, the real question is what downstream actions it can tie back to your ad spend. For a subscription app, attributed installs are only the starting line; you need to know which campaigns bring users who actually start trials and convert to paid plans.
Here is how the attribution flow works and which app outcomes get connected to your campaigns:
- SDK Data Collection: The process starts by integrating an MMP SDK into your mobile app. Once in place, the SDK collects interaction data across devices and channels, capturing campaign clicks and impressions, installs, and in-app events like registrations or purchases.
- Source, Campaign, and Creative Mapping: Airbridge attributes both installs and post-install events back to the specific source, campaign, and creative that brought the user into your app. With campaign tracking, you can see which campaign acquired each user and whether they went on to install, start a trial, subscribe, or pay.
- Target Events and Default Windows: Under the Airbridge Attribution Model, attribution centers on three target events: app install, deeplink open, and deeplink pageview. In standard Attribution Scenarios, the default attribution window is 30 days for app installs and 3 days for deeplink opens.
- Crediting Subsequent In-App Events: Any subsequent events that happen within a target event's attribution window are credited to the same touchpoint that drove the target event. Within an app-install attribution window, tracked events include login, deeplink open, add to cart, and purchase. An add to cart event is also listed within a deeplink-open attribution window; when a user adds an item to their cart within that window, the event is credited to the touchpoint behind the deeplink open.
- Granular Subscription Reporting: The Actuals report groups install, trial start, first app subscription, and subscription revenue events across three levels: campaign, ad group, and ad creative.
- Conversion Funnel Visibility: When you want to spot where users drop off after clicking an ad, the Funnel report maps out the conversion journey from install to trial start and subscription for each campaign.
How to Connect Attribution Data to Your Analytics Setup
If your team relies on your existing analytics workspace to explore how users interact with your product, you can send attribution data from Airbridge directly into that environment. Once the integration is complete, Airbridge-collected Target Events and their properties can be sent over so you can analyze user interactions alongside acquisition context.
Keep in mind that completing the configuration in the Airbridge dashboard alone will not properly establish this connection; you must also add the integration code to the Airbridge SDK in your app.
Follow these steps to set up the server-to-server integration:
- Map the App Instance ID as a Device Alias: For the server-to-server connection to work, you must set the analytics SDK's App Instance ID as the Airbridge SDK's device alias.
- Configure Android Apps: In an Android environment, retrieve the App Instance ID asynchronously from
Firebase.analytics.appInstanceIdusing anaddOnCompleteListenercallback. Check that the returned value is not null, and then set it as the Airbridge device alias using the keyga4_app_instance_id. - Configure React Native Apps: If your app is built with React Native, first set
autoStartTrackingEnabledtofalseinside yourairbridge.jsonfile. Next, fetch the App Instance ID by callinganalytics().getAppInstanceId(), assign it as the Airbridge device alias under the keyga4_app_instance_id, and then invokeAirbridge.startTracking(). - Verify Dashboard and Code Setup: Make sure both your in-app SDK code changes and the necessary Airbridge dashboard setup are finished so Target Events and their properties begin flowing into your analytics property.
FAQS
FAQ
How do I know when my team is ready to add an attribution layer to our stack?
Look at how you currently allocate your acquisition budget and whether you are running ads on more than one channel. If you are spending across multiple ad networks and cannot tell which specific creatives or campaigns are driving paying subscribers versus free users, it is time to bring in an attribution tool alongside your product analytics.
Which view should I check first when evaluating subscription campaign performance?
Start with your high-level outcome groupings when you need to compare how different ad groups or creatives generate trials and revenue, and switch to a stage-by-stage conversion view when you want to diagnose where users drop off between installing the app and starting a paid plan. Reviewing both angles helps you separate ads that merely drive volume from those that bring in long-term subscribers.
What should I coordinate with my developer before turning on the analytics connection?
Since dashboard toggles alone will not sync your data, plan the integration around an upcoming app release cycle so your developer can include the required SDK identifier mapping in the build. Having engineering verify that the device identifier is properly passed during initialization before you enable the dashboard settings prevents gaps in your event stream.
See which ads pay off
Connect paid campaigns to installs, trials, and subscriptions.
