Skip to main content
Mobile attribution spans more than the app. A useful setup connects the campaign link, store or deep-link handoff, mobile SDK, known user, revenue provider, and conversion destination.

​
Build the path

  1. Install the iOS or React Native SDK and verify an app-open event.
  2. Configure the platform attribution and deep-link requirements described in that SDK guide.
  3. Create a tracking link and choose App install.
  4. Add the App Store and Play Store destinations you support.
  5. Preserve the campaign macros required by the ad platform.
  6. Call identify when the app knows the customer.
  7. Connect RevenueCat, Superwall, Stripe, or another supported revenue source.
For Snapchat app delivery, a conversion rule can optionally use the connected Snap App ID. Other destinations expose their own supported app assets.

​
Test correctly

Use a real device and a controlled link. Test both a fresh install and an open of an existing app where relevant. Confirm:
  • the link click or landing event;
  • the app event and supported attribution context;
  • the known user after signup or login;
  • the trial, purchase, or subscription event;
  • the conversion delivery result.
Simulator tests do not reproduce every store, privacy, deep-link, or attribution framework behavior. Complete the final verification on a physical device.
Missing app attribution is commonly caused by stripped campaign parameters, an unhandled deep link, identity established after the revenue event, an offline queue that has not flushed, or platform privacy limitations.