Skip to content

FeaturesMeasure

From the tap to the purchase

Every tap is followed through: the install it led to, the opens after it, what the person did in the app and what a campaign cost to bring them there. All of it is first-party, counted without an advertising identifier.

Campaigns

The path from click to revenue for each campaign, source and link.

From click to purchase

  1. Clicks

    2,445

    Taps, clicks and QR scans

  2. Installs

    149

    6.1% of clicks

  3. Opened again

    119

    80% of installs

  4. In-app events

    152

    1.0 per install

  5. Purchases

    18

    12% of installs

Revenue

$3,830

From 18 purchases

Install matches

64 exact · 85 estimated

Spend and return

CampaignSpendClicksInstallsCost per installRevenueReturn
summer_saleMeta$1,2401,48096$12.92$2,5302.04×
creator_mayaEntered$40061241$9.76$1,0102.53×
winter_pushMeta$31035312$25.83$2900.94×
The real dashboard, with example data.

How it works

  1. 01

    Each request is classed

    As a person, a bot (preview fetchers and crawlers) or a scanner (security tools that open links in email). Dashboard totals count people.

  2. 02

    Installs are tied to taps

    With the method recorded on each one: exact, through the Play Install Referrer, or an estimate with a confidence score.

  3. 03

    The app reports what follows

    Opens and events you track from the SDK, including purchases with a value and currency.

  4. 04

    Spend goes next to revenue

    Type in what any channel cost, or import it from a Meta ad account. Cost per install and return follow.

What is included

  • Unique counts: a click is unique when it is the first from that visitor on that link in the hour, recognised by a hash that changes daily, not a cookie.
  • QR scans counted separately from taps.
  • Country, region and city, operating system, device kind, browser, in-app browser and referring website.
  • A live view of clicks as they arrive.
  • Click-by-click history for 30 days on Free and about 13 months on paid plans; daily totals are kept for the life of the project.
  • Past clicks can be reclassified when a bot is identified later.

Where it stops

  • This is not an ad-attribution suite. It can read what a Meta campaign spent, but it does not see who saw an ad.
  • No ad-network integrations and no multi-touch attribution, on purpose.
  • No full IP address is stored for a tap, so a single visitor cannot be looked up by address.

The detail

Start with one link

The free plan has no time limit and needs no card. Create a project, add your app, and send yourself the link.

Analytics and campaigns · DL2App