Back to blog

Views, Downloads, and QR Scans: How to Measure File Sharing

How file sharing analytics work: track views, downloads, and QR scans per file, compare channels, and measure print campaigns with the same numbers as digital.

Aug 18, 2026ShareKit TeamShareKit Team

Most people share files and then never think about them again. The file goes out, the conversation moves on, and nobody knows whether it was opened, downloaded, or ignored. For personal files that's fine. For client deliverables, marketing materials, and print campaigns, it's a blind spot — and blind spots cost money.

File sharing analytics close that gap. Every shared file can report three numbers: views, downloads, and QR scans. This guide explains what those numbers mean, how to read them, and how they turn file sharing from a chore into a measurement.

Why measure file sharing

The question analytics answers is simple: did the file actually reach people?

  • A client deliverable that was never downloaded tells you to follow up.
  • A digital menu with thousands of views tells you the channel works.
  • A printed QR code with zero scans tells you the placement fails.
  • A manual with ten times more views than downloads tells you people read it online.

Without numbers, every one of those signals is a guess. With them, file sharing becomes something you can improve.

The three numbers: views, downloads, and scans

ShareKit separates engagement into three metrics per file:

  • Views — how many times the file's public page was opened. Views show reach: who came to look.
  • Downloads — how many times the file was saved. Downloads show intent: who actually wanted the file.
  • QR scans — how many times a printed or offline code was used. Scans show physical reach.

The split matters because the three numbers answer different questions. A lot of views and few downloads suggests the preview is doing its job — people read the document online. A lot of downloads and few views suggests the link is being sent directly, bypassing the page. A spike in scans correlates a specific printed placement with activity.

What analytics tell you about your workflows

Applied to real workflows, the numbers become decisions:

  • Client deliverables — did the client open the proposal? If views stay at zero, the email was ignored and it's time to follow up.
  • Support and documentation — a tutorial with high views and low downloads is working as an online resource; high downloads suggest people want a copy to keep.
  • Marketing assets — a brochure shared to ten channels shows which channel drives actual opens.
  • Internal training — videos with high view counts are being watched; modules nobody opens need promotion or rework.

The same upload can be embedded in a doc, shared in chat, and printed as a QR code — and each surface reports to the same file, so you see the full picture in one place.

Measuring print with QR scans

Print is where file analytics earn their keep, because print has no other feedback loop. When you put a QR code on a menu, a package, or a poster, the scan count is the only signal you get.

The workflow is simple: generate the QR code with the file upload, print it, and watch the scans. A restaurant can compare this week's menu scans to last week's; an event team can compare signage placement A to placement B; a retailer can see which product boxes get scanned at the shelf. That turns print into a measurable channel instead of a leap of faith. The QR code guide covers placement best practices in detail.

Comparing channels honestly

Analytics only help if you compare like with like:

  • Compare the same file across channels — the PDF in email versus the PDF behind the QR code — rather than different files.
  • Give campaigns time. A printed code builds scans slowly; a chat link spikes immediately.
  • Watch the ratios, not just the raw numbers. Views-to-downloads and scans-to-views are more informative than any single count.

Over time, the ratios become a baseline: you learn what "normal" looks like for a menu, a proposal, or a handout, and deviations become early warnings.

Privacy of file analytics

Measuring file sharing doesn't mean tracking people. ShareKit's analytics are aggregate and file-level — how many views, downloads, and scans a file received — not who performed them. There's no personal data attached to the numbers, which keeps the measurement useful without making it creepy.

Where analytics live

Analytics are attached to the file, not the channel, which is the important architectural detail. Whether someone opened the share page, downloaded the original, or scanned the printed QR code, the activity lands in the same place. That means you never have to stitch together numbers from a link shortener, a file host, and a QR tool — the file sharing service is the single source of truth for every surface of the file.

From sharing to reporting

The endpoint of good file sharing isn't a sent message — it's a report you can act on. ShareKit turns every upload into a small measurement instrument: the public page counts views, the download endpoint counts downloads, and the QR route counts scans. Over a campaign or a quarter, those numbers aggregate into a channel performance picture: which placements drove scans, which emails drove opens, which documents earned downloads. Teams that treat file sharing as reporting get a measurable advantage — every menu, brochure, and deliverable contributes data instead of disappearing into a sent folder. That's the difference between sending files and managing them.

FAQ

What do views, downloads, and scans mean? Views are page opens, downloads are file saves, and scans are uses of the printed QR code. Together they show reach, intent, and physical engagement.

Can I track who downloaded my file? No. Analytics are aggregate and file-level — counts, not identities — which keeps the data private.

How do I measure a print campaign? Generate a QR code with the upload, print it, and compare scan counts across placements.

Do embedded files report views? Yes. Views are counted whenever the public page is opened, including through embeds and QR codes.

Can I compare two channels for the same file? Yes. Views, downloads, and scans are all attached to the same file, so channels report to one place.

Are analytics available on the free plan? Yes. View, download, and scan counts are tracked for every upload.

How long is analytics history kept? Analytics stay with the file for as long as the file exists.

Can I export analytics? View, download, and scan counts are available per file in the dashboard, with the history retained for as long as the file exists. Do QR scans count as views? No. Scans and views are tracked separately, so you can distinguish printed usage from online opens.

What is a good views-to-downloads ratio? It depends on the file: instructional documents often see high views and moderate downloads, while deliverables should approach a high ratio of downloads to shares.