Support matrix

Where attribution works today, browser by browser and system by system, and the one step that gets it where the default setup can’t.

Links an install to the visit on the same Mac or Linux computer in Chrome, Firefox, Edge, Brave and Vivaldi, and in Safari through the handoff command.1

Attribution (the same-machine match, the handoff command and reconstruction) runs on Standard and Enterprise. On Free, CLItrail counts visits and installs without matching them, and installs reported on Free are never matched later.

Last updated: 2026-09-24. The same data drives the support page.

#How to read it

#Browsers and systems

Supported Handoff command, unless a cell says otherwise: Browser-independent once prepared.

Probable Reconstruction, unless a cell says otherwise: Paid plans. When no receipt or token arrives, a match from the public network and other signals, labelled probable.

#macOS

The hook searches the browser profile folders under ~/Library/Application Support for the user who runs it.

Browser	Website tag	Same-machine match	Handoff command	Reconstruction	How to get attribution here
Chrome	Supported	SupportedThe hook searches Chrome’s profile folder for the user who runs it.	Supported	Probable	Works with the default tag and hook. Run the hook with --doctor as the visitor’s user to confirm it finds the profile. Hook diagnostics →
Firefox	Supported	SupportedThe hook searches Firefox’s profiles folder for the user who runs it.	Supported	Probable	Works with the default tag and hook. Confirm with --doctor on the installing Mac. Hook diagnostics →
Brave	Supported	SupportedThe hook searches Brave’s profile folder for the user who runs it.	Supported	Probable	Works with the default tag and hook. Desktop Brave sends a Chrome user agent, so auto mode treats it as Chrome and uses the receipt. Hook diagnostics →
Safari	SupportedFor Safari before 26, allow worker-src blob: in the page’s CSP.	Via handoffSafari’s protected storage is never read: the prepared command carries the visit instead.	SupportedAuto mode prepares it (reason safari_requires_handoff).	Probable	Show the command from prepareInstall({ mode: 'auto' }) on your install page. For Safari before 26, allow worker-src blob: in the page’s CSP. Handoff command →
Chrome Beta, Dev and Canary	Supported	SupportedThe same folder layout as Chrome.	Supported	Probable	Same as Chrome. --doctor names each channel it finds. Hook diagnostics →
Edge	Supported	SupportedThe Microsoft Edge profile folder is searched.	Supported	Probable	Default tag and hook. Edge names itself in its user agent, so auto mode uses the receipt. Where the hook looks →
Vivaldi and Chromium	Supported	SupportedBoth profile folders are searched.	Supported	Probable	Default tag and hook. Vivaldi sends a Chrome user agent, and its profiles are searched. Where the hook looks →
Arc	Supported	Via handoffArc publishes no profile folder, so the hook does not search it.	SupportedOnly when forced: Arc sends a plain Chrome user agent, so auto mode does not hand off.	Probable	Where Arc matters to your audience, use prepareInstall({ mode: 'handoff' }) so every visitor gets the prepared command. Handoff command →
Zen and other Firefox forks	Supported	Via handoffOn macOS only Firefox’s own profile folder is searched.	SupportedOnly when forced: these browsers send a Firefox user agent, so auto mode does not hand off.	Probable	If your audience uses Zen, LibreWolf, Floorp or Waterfox, use mode: 'handoff'. Handoff command →
Opera, Yandex, Whale and Coc Coc	Supported	Via handoffTheir profile folders are not searched.	SupportedAuto mode prepares it (reason unqualified_browser).	Probable	Nothing beyond prepareInstall({ mode: 'auto' }): these browsers name themselves, so they get the prepared command. Handoff command →
DuckDuckGo, Orion and other WebKit browsers	Supported	Via handoffWebKit storage is never read.	SupportedAuto mode hands off when the browser reports a Safari user agent.	Probable	Same as Safari: show the command from prepareInstall({ mode: 'auto' }). Handoff command →

#Linux

The hook searches ~/.config (or $XDG_CONFIG_HOME), ~/.mozilla, ~/.zen, and the Snap and Flatpak profile folders for the user who runs it.

Browser	Website tag	Same-machine match	Handoff command	Reconstruction	How to get attribution here
Chromium	Supported	SupportedThe hook finds ~/.config/chromium itself, as the user who runs it.	Supported	Probable	Works with the default tag and hook. Hook diagnostics →
Firefox	Supported	SupportedThe hook finds ~/.mozilla/firefox itself, as the user who runs it.	Supported	Probable	Works with the default tag and hook. Hook diagnostics →
Snap, Flatpak and XDG profiles	Supported	SupportedUbuntu’s Firefox snap, the Chromium snap, the Flathub Firefox and Chromium builds, and Firefox 147+ profiles under ~/.config/mozilla.	Supported	Probable	Default tag and hook. --doctor lists them as Firefox (Snap), Chromium (Flatpak) and so on. Hook diagnostics →
Chrome, Edge, Brave and Vivaldi	Supported	SupportedTheir ~/.config folders are searched, including Chrome Beta and Dev.	Supported	Probable	Default tag and hook. Where the hook looks →
Zen	Supported	Supported~/.zen and the Flathub build are searched.	Supported	Probable	Default tag and hook. Where the hook looks →
Opera, Yandex and other browsers	Supported	Via handoffTheir profile folders are not searched.	SupportedAuto mode prepares it (reason unqualified_browser).	Probable	Nothing beyond prepareInstall({ mode: 'auto' }) for browsers that name themselves; force mode: 'handoff' for any other. Handoff command →
WebKit browsers	Supported	Via handoffWebKit storage is never read.	SupportedAuto mode hands off when the browser reports a Safari user agent.	Probable	Show the command from prepareInstall({ mode: 'auto' }). Handoff command →

#Windows

There is no native Windows hook. Run the handoff command from WSL (a POSIX shell); PowerShell and cmd are not supported.

Browser	Website tag	Same-machine match	Handoff command	Reconstruction	How to get attribution here
Edge, Chrome, Firefox and other browsers	Supported	Via handoffNo native Windows hook, and a Windows browser and a CLI inside WSL do not share profile folders: the prepared command carries the visit instead.	SupportedAuto mode prepares it (reason platform_requires_handoff). Run it from WSL (a POSIX shell); PowerShell and cmd are not supported.	ProbablePaid plans, when an install is reported, for example by a hook inside WSL.	Show the command from prepareInstall({ mode: 'auto' }) and run it from WSL. For packages that also run on Windows, call a platform-aware entry point, and rely on reconstruction for installs a hook reports from WSL. Handoff command →

#ChromeOS

The SDK routes ChromeOS to the handoff command. Run it in ChromeOS’s Linux environment.

Browser	Website tag	Same-machine match	Handoff command	Reconstruction	How to get attribution here
Chrome	Supported	Via handoffThe SDK routes ChromeOS to the handoff command.	SupportedRun it in ChromeOS’s Linux environment (a POSIX shell).	ProbablePaid plans, when an install is reported.	Show the command from prepareInstall({ mode: 'auto' }) and run it in the Linux environment. Handoff command →

#iOS and iPadOS

Installs happen on a computer, so a phone visit needs the handoff command or reconstruction.

Browser	Website tag	Same-machine match	Handoff command	Reconstruction	How to get attribution here
Safari, Chrome and others	Supported	Not supportedThe install happens on another device.	SupportedAuto mode prepares it (reason platform_requires_handoff); the command still has to reach the computer.	ProbablePaid plans. A phone visit and a computer install on the same network can match.	Rely on reconstruction for phone-to-computer journeys on the same network. iPads that request desktop sites are routed to the handoff command too. Reconstruction →

#Android

Installs happen on a computer, so a phone visit needs the handoff command or reconstruction.

Browser	Website tag	Same-machine match	Handoff command	Reconstruction	How to get attribution here
Chrome, Samsung Internet, Firefox and others	Supported	Not supportedThe install happens on another device.	SupportedAuto mode prepares it (reason platform_requires_handoff); the command still has to reach the computer.	ProbablePaid plans. A phone visit and a computer install on the same network can match.	Rely on reconstruction for phone-to-computer journeys on the same network. Reconstruction →

#Install contexts

Where the install command runs matters as much as the browser. The hook needs the visitor’s own computer and OS account to find a receipt.

#Methodology

The coverage figures answer one question: what share of desktop install-page visits happen in a browser where CLItrail can re-link a same-machine install through the receipt? A visit counts as covered when its user agent names a browser family whose storage the hook searches on that system: Chrome, Edge, Firefox or Brave on macOS, and Chrome, Chromium, Edge, Firefox or Brave on Linux. Vivaldi and Chromium sit inside “Chrome” in user-agent data. Windows, ChromeOS, iOS and Android count as zero.

These are shares of visits (requests, respondents or unique visitors), never of installs, and they are upper bounds:

• user-agent “Chrome” includes Arc and other Chromium forks the hook does not search, and “Firefox” includes Zen and other forks;
• a covered browser is only the first condition: the install must also run on the same computer, as the same OS user, while the receipt is still there (see below).

#Developer audiences

Nine Devographics surveys, measured from each respondent’s user agent (desktop OS mix × that edition’s browser split). Buckets under about 10 responses are suppressed by the API and treated as not covered. “With handoff” adds Safari on macOS through the handoff command.

Worked example, State of Devs 2026: on macOS, Chrome 752 + Firefox 242 + Edge 24 = 1,018 of 1,168 respondents (87.16%) × 53.43 = 46.57 points; on Linux, Firefox 209 + Chrome 160 = 369 of 375 (98.40%) × 17.17 = 16.90 points; together 63.46%.

Public Plausible dashboards of four developer sites, desktop unique visitors, September 2025 to August 2026:

These sites’ Plausible scripts are on a common blocklist, so visitors who block trackers, who lean towards Firefox and Brave (both covered), are missing.

#General web traffic

For transparency, not for marketing: on general web traffic the same browsers account for 17.3% of desktop requests worldwide and 24.0% in the US (Cloudflare Radar, August 2026, likely-human). Windows, which has no native hook, is 74.6% and 64.2% respectively. Adding Safari through the handoff command gives 23.90% and 33.21%. Worldwide, the monthly figure ranged from 15.26% to 17.79% between August 2025 and August 2026.

#Worst case

A stress test treats self-reported use of browsers the hook does not read as if it were visit share, which overstates the loss. From State of Devs 2026: 63.46 − Arc 5.73 − Zen 6.02 − Ubuntu-token Linux Firefox 2.70 = 49.01%; for the median edition, 47.96%; for direnv.net, 53.84%. So under worst-case assumptions about half of developers’ desktop visits remain in covered browsers, and the measured user-agent figures put the upper bound at about 6 in 10.

#Windows

Windows counts as zero because there is no native hook. People on Windows can still be attributed: run the handoff command from WSL (a POSIX shell). PowerShell and cmd are not supported.

#Why there is no recovery percentage

A claim such as “recover X% of your lost install attribution” would multiply the share of visits in covered browsers by factors nobody measures: how often the install runs on the same computer and OS account as the visit, whether the receipt is still there (not private browsing, not cleared, under 30 days), whether the hook runs (not CI, no opt-out, the right user), and whether the visit carried the platform’s click ID with consent. It would then divide by a number nobody defines: installs whose attribution is lost today, which include README copies, registry pages and word of mouth.

Only the first factor is measured, and only as a share of visits. Reconstruction is probabilistic and has no measured accuracy. What you can measure is your own ratio of matched, reconstructed and unattributed installs, which the dashboard’s Overview shows for your traffic.

#Sources

Refreshed monthly for Cloudflare Radar and Plausible, and when new Devographics editions publish.

#Notes

1. On macOS and Linux the hook searches the profile folders of Chrome, Chrome Beta, Chrome Dev, Chromium, Edge, Brave, Vivaldi and Firefox; on macOS also Chrome Canary, and on Linux also Zen and the Snap and Flatpak builds. Safari, WebKit browsers and forks that name themselves, such as Opera, get the handoff command from prepareInstall in auto mode. For browsers that present themselves as Chrome or Firefox but keep their own profiles, such as Arc or LibreWolf, use handoff mode. See where the hook looks.