Device fingerprinting is a broader concept than browser fingerprinting specifically — it spans mobile apps, hardware-level identifiers, and telemetry that exists entirely outside the browser context, worth understanding as its own category.
Browser fingerprints: one piece of the picture
As covered in Browser Fingerprinting, a browser's characteristics can identify it across sessions. Device fingerprinting includes this, but extends further.
Mobile advertising identifiers
Mobile operating systems provide advertising identifiers specifically designed to let apps and ad networks track engagement — a more direct, explicit tracking mechanism than browser fingerprinting, though modern mobile platforms increasingly give users controls to reset or limit these identifiers.
App telemetry
Native apps can collect a range of device and usage information beyond what a browser typically exposes — hardware model, installed app lists (on some platforms), and detailed usage analytics, depending on what permissions the app has been granted and what the app developer chooses to collect.
Hardware-level traits
Certain hardware characteristics — sensor calibration data, battery status APIs (largely restricted now due to fingerprinting concerns), and similar low-level signals — have historically been explored as fingerprinting vectors, leading platform vendors to restrict access to several of these over time specifically because of the privacy implications.
Account correlation
Perhaps the most powerful device-fingerprinting-adjacent signal: if you're signed into the same account (a social media platform, an app ecosystem) across multiple devices, that account link directly correlates your devices together, far more reliably than any technical fingerprint.
FAQ
Can I fully prevent device fingerprinting?
Not completely, though resetting advertising identifiers periodically, reviewing app permissions, and being deliberate about account linkage across devices all meaningfully reduce exposure.