Mobile attribution

Measure the path from web ad to app revenue

Connect the landing-page click to the install, paywall, trial, paid conversion, and renewal. Datalyr works with your web funnel, mobile app, Superwall, and RevenueCat.

Mobile growth is split across two environments. The campaign starts on the web, while the events that matter happen inside the app and your paywall provider.

Datalyr gives both sides one shared customer and campaign context.

Where tracking breaks

The app install should not erase the campaign

A customer can click an ad, visit your domain, open the app store, install later, and buy after a trial. Each handoff makes the original source harder to recover.

If the paywall webhook arrives without that context, you know a payment happened but not which campaign created it.

How it works

Use your domain as the start of the customer journey

Datalyr captures the click on your landing page. The mobile SDK reconnects the install to that web session, then passes the same attribution context into Superwall or RevenueCat. Their webhooks provide the confirmed revenue events.

Web ad click

We tag the click

minutes later, App Store hop

App install

App reconnects after install

Identity Bridge

days later, inside the app

Paywall purchase

Sent back to Meta

Enriched identity

{click,customer,location,subscription value}

One campaign context across the web visit, app, and paywall.

Setup

Connect the full path

Install the mobile SDK

Add Datalyr to iOS or React Native and initialize it when the app opens.

Connect the paywall

Pass Datalyr attributes to Superwall or RevenueCat and connect the provider webhook.

Add web tracking

Install the web SDK on the landing page where your campaigns start.

Run a complete test

Follow a test click through install and purchase, then confirm the joined events in Datalyr.

See the events that explain growth

Landing-page visits and campaign context
App installs, signups, and key in-app events
Paywall views, trial starts, and paid conversions
Renewals, cancellations, and refunds from provider webhooks
Revenue by channel, campaign, ad set, and creative

Common setup questions

Does purchase revenue come from the app?

Revenue should come from the Superwall or RevenueCat webhook, not a client-side purchase call. That keeps trials, refunds, and renewals accurate.

What happens after the ATT prompt?

On iOS, refresh the Datalyr attributes after the user answers the prompt so any newly available identifier reaches your paywall provider.

Where can my developer see the exact calls?

The mobile web-to-app guide covers SDK setup, paywall attributes, web tracking, and the verification flow.

Know which campaigns create paying app users

Connect the web click, app journey, and paywall revenue in one setup.

Read the mobile setup guide→

7-day trial · No credit card