Installs and identity
Initialises on app open and attributes guests by device ID, then records signup once per install and customer.
Appbrew
Connect your Appbrew app to attribution
Use the Linkrunner Appbrew tracker for install attribution, app events, purchase revenue and deep links. Review the setup against the journeys your Shopify mobile app ships.
Join 400+ growth teams using Linkrunner.
What it does
What the tracker handles on its own
Purchases and refunds
Every Appbrew purchase becomes a payment with its transaction ID, so orders and revenue feed attribution for ecommerce apps. Refunds are forwarded once you turn them on.
Every other event
Sent under its Appbrew name, with Meta catalog fields added from the items in the event.
Deep links
Links that open the app are reported, and the deferred deep link routes into Appbrew's router once per install.
Uninstalls
The push token is registered for uninstall tracking, and the CleverTap ID is sent when CleverTap is installed.
In the dashboard
The Appbrew settings in Linkrunner
Setup
Set up Appbrew in 5 steps
01
Install the packages
Add @linkrunner/appbrew and rn-linkrunner, then run pod install. This needs a new binary build and a store release.
02
Register the tracker
Add LinkrunnerTrackerV2 to Appbrew's AnalyticsProvider in App.tsx. Keep the token out of code.
03
Configure in Appbrew
The Appbrew team enters your Linkrunner project token per store. Optional settings cover SDK signing, PII hashing, consent and screen views.
04
Finish native setup
On Android, exclude the SDK's preferences from auto-backup. For deep links, add your Linkrunner domain to Associated Domains and an autoVerify intent filter.
05
Test
Build with debug on, place an order and confirm one payment, then install from a campaign link and check the deferred deep link.
Notes and limits
Worth knowing before you launch
Needs @linkrunner/appbrew 0.2.0 or later, rn-linkrunner 3.1.0 or later, iOS 15 or later and Android minSdk 24.
Map events under Meta Ads, Event Mapping, for example add_to_cart to AddToCart. Without the mapping, events are stored but never sync to Meta.
Push taps bypass the tracker. Call handleDeeplink from your notification handler so push campaigns count as re-engagements.
Screen and page views are off by default because they are the highest-volume events.
Calling capturePayment from a Shopify webhook with a different payment ID duplicates payments. For the storefront, use the Shopify Web SDK setup.
Frequently asked questions
Do I need to write event code for Appbrew?
How does the Appbrew tracker relate to the React Native SDK?
Where does the Linkrunner project token go?
Can my app read the campaign behind an install?
How is Google Ads consent handled?
Verify your Appbrew app journey before launch
Configure the tracker and test an install, deep link and purchase. Use a consistent payment ID when checking revenue.