Installs

The Installs screen, at https://app.adto.app/dashboard/installs, lists every install the SDK recorded, newest first, with how it was matched. Its header reads “Every install and why it was credited.” The Overview’s Recent installs card links here with View all, and the installs sheet on the Links screen with Open in Installs, which opens the screen searched for that link.

The list

Each row shows when the app was installed, the verdict (referrer, clipboard or fingerprint with the confidence, organic, or credit withheld when a fraud rule the app blocks withheld it), the link it was credited to (or, for a withheld one, the link that was tapped), the OS with its version and the device model, the app version, and chips for a reinstall, an app update and each fraud flag, labelled by rule (for example Emulator for a simulator build). A flag chip is amber when the rule only flags and red when a blocked rule acted on it; hovering it explains the rule. See Fraud rules. 25 rows load at a time; Load more adds the next 25.

reinstall means one of two things: the app reported that it was installed on this device before, or the server already has an install with the same device id in this account. On an iPhone the SDK knows from a first-install date it keeps in the Keychain, which survives deleting the app; Android cannot tell on the phone, so there only the server’s check applies. A reinstall is credited like any install and counted under the Overview’s Reinstalls and each link’s +{n} reinstalls, not under Installs.

app update means an existing user updated into your first build with AdTo: the app was on the device before the SDK was, so the SDK reports the install as an update. It is never matched to a tap and counts as neither an install nor a reinstall; the Overview’s Installs card counts app updates on a line of their own. Its first identify records no signup lead and no referral.

Above the list:

• Search finds one install id, one device id or one link. A viewer searches install ids and links only, because viewers never see device ids.
• iOS and Android narrows to one platform.
• Every verdict narrows to credited or organic installs, to one signal (Store referrer, Pasted link or Fingerprint), or to Blocked by a fraud rule: installs a blocked rule acted on.
• With or without fraud flags narrows to Any fraud flag or to one rule. The Overview’s fraud chips open the screen with this filter set (?flag=<rule>).

Clicking a row opens the install detail, described below.

Watch

Watch is for testing on a phone. While it is on, and the browser tab is in view, the screen fetches the newest installs and the latest taps again every 5 seconds. A pulsing dot reads “Watching · updated 3 s ago”. Stop watching turns it off.

A Latest taps card appears above the list with the 10 newest taps of the account: the link, the OS, browser and device model, the screen size the page reported (402×874 @3), the country, and the time. A chip says whether the page’s beacon arrived (page beacon): it carries the screen size and device settings the fingerprint compares, so a tap without it can only be matched on fewer signals. A tap that brought an install shows Installed →, which opens that install; otherwise it reads “no install yet”.

New installs appear at the top of the list, tinted until you change a filter or reload. The filters apply to the refreshed list too.

To test a link:

1. Use the test environment’s SDK key in debug builds, so test installs stay out of your live numbers.
2. Turn on Watch.
3. Tap the link on the phone and check the tap appears, with page beacon if the link shows a page.
4. Install and open the app. The install appears within a few seconds; open it to read the verdict.

To run the same test again on the same phone, open the install, choose Erase this device, then tap the link again before you reinstall. Erasing removes the device’s installs and strips the taps they were credited to of everything personal, so the fingerprint can no longer match an old tap. Erasing is for owners; see A request from one person.

Erasing clears the server’s data, not the phone’s. On Android that is enough for the next install to count as new. An iPhone keeps the SDK’s first-install date and saved device id in the Keychain, which survives deleting the app, so its next install still arrives as a reinstall. For a fresh install:

• iOS simulator: delete the app, then run this in Terminal on your Mac. It clears the Keychain of every app on the running simulator.

  xcrun simctl keychain booted reset

  Then tap the link in the simulator’s Safari and build and run the app again.

• iPhone: one app’s Keychain cannot be cleared, so use a phone that never had the app.

The install detail

The detail opens from this screen, from the Overview’s Recent installs and from a link’s installs. Under its title are the install’s time, OS and device model, and the country the install request came from. It shows:

• Verdict: credited link, organic, or credit to /{slug} withheld, match source, confidence, reinstall, fraud flags. When a blocked rule acted, a line says what it did.
• Fraud checks: every install rule with its label, what it means and Flagged, Flagged · acted, Clear or Not checked with the reason (for example no Google Play install-begin time on iOS), and the values it compared: physical device, model and CPU; the tap time and the gap to the first launch or to the download’s start; the installer; the signing certificate and how many fingerprints the app lists; other installs from the network in 24 hours and the line; taps from the network in the hour before; the tap’s age. Installs recorded before these checks existed show none.
• Why: the signal that named the click (store referrer, pasted link, Meta referrer, a late claim), or the fingerprint’s best and runner-up candidates with each signal marked agree, mismatch or missing, their scores, the gap between them, the window that applied and how many repeat taps were merged. The full list of signals is under Recent installs.
• Show values: a checkbox above the signals. With it on, each signal also shows what the app and the tap reported, as app 1206×2622 · tap 402×874 @3 = 1206×2622. The screen compares the app’s physical pixels with the tap’s screen times its pixel ratio; the time zone reads UTC+3; the network reads AS36935; the IP version reads IPv4 or IPv6. A dash means that side reported nothing, which is why the signal reads missing. No IP address is ever shown. A viewer sees no network values.
• Tap, App opens, Events and Screens, as on the Overview.
• This device’s data: Download everything stored (JSON) and Erase this device, and on this screen Every install from this device →, which searches the list for the device id. Viewers do not see this part.