The landing page and the app, in one project.

An app and its website share a project, a write key and a privacy mode. Platform is a dimension: Sessions, Screens, Retention, Crashes and Data each switch between the app and the site, so both sides are read the same way.

Start for freeRead the docs

The problem. Sound familiar?

  • Site analytics in one tool and app analytics in another, with different definitions of a “visit” and a “session”.
  • Downloads that rise after a launch with no way to see where the traffic came from.

Where Tapll answers it.

  • 01

    Add the website to the project

    Settings → General → Platforms → Add website. Same key, and 28 days of history are rolled up for the switcher.

  • 02

    Read both sides

    Site traffic, channels and campaigns on one side; app sessions, retention, crashes, releases and App Store referrers on the other.

  • 03

    Compare, do not stitch

    Tapll puts the two next to each other. It does not follow a single person from a page view to an install, and says so.

In the docs: Add the website script

Questions.

Can Tapll tell which visit became an install?

No. The site and the app are measured side by side in one project, not joined per person. The App Store’s own referrer report names the websites that sent downloads.

Are website and in-app revenue added together?

Never. Website money (Stripe, Paddle) and in-app money (RevenueCat, Apple) are separate blocks.

Other questions.

See who is on your app and site right now. No analyst, no query building.

Start for free