Per-Link Analytics: See Exactly How Recipients Engage with Your Shared Content

The Problem: Sending Proposals Into a Black Hole

You spend hours crafting a proposal, pricing sheet, or quarterly report. You send the link. Then you wait, refreshing your inbox, wondering: Did they open it? Did they scroll past the executive summary? Did they share it with their CFO or abandon it after three seconds?

Most file-sharing tools tell you nothing. Some offer a basic "opened" notification. Neither helps you understand actual engagement or time your follow-up intelligently.

HTMLVault's per-link analytics solve this by treating every shared link as a trackable touchpoint. You get the same engagement metrics that marketing teams expect from landing pages—but applied to individual proposals, reports, dashboards, and one-off deliverables.

Who This Is For

Sales reps who want to know when a prospect has reviewed a proposal before calling to follow up. Knowing that someone spent four minutes on the pricing page tells you something different than knowing they bounced after ten seconds.

Marketing teams sharing campaign reports, creative briefs, or landing page mockups with stakeholders. Scroll depth reveals whether your audience reached the bottom or stopped halfway.

RevOps leads measuring how internal playbooks, competitive battlecards, and training materials are actually consumed by the field. Analytics expose which content gets used and which gets ignored.

What You Can Track

Every HTMLVault link automatically collects engagement data. No extra setup required. All metrics are viewable in the per-link analytics dashboard.

• Total views: How many times the link was opened.
• Unique visitors: Distinct individuals based on browser fingerprinting (without storing PII).
• Repeat visits: How often someone returns to the same link—useful for complex proposals that require multiple reviews.
• Geography: Country and city derived from IP address. Helpful when you're waiting to hear from a specific office or region.
• Device and browser: Desktop vs. mobile, Chrome vs. Safari. If your content looks broken on mobile and 40% of views are mobile, you know where to fix.
• Referrer source: Where traffic came from—email client, Slack, LinkedIn, or direct. See whether your link is being forwarded or shared beyond your original recipient.
• Scroll depth: How far down the page recipients scrolled, expressed as a percentage. Did they reach your call-to-action or bail early?
• Time-on-page: How long the link stayed active in the browser. Distinguishes a quick glance from a thorough read.

How to Access Analytics

Analytics are available on all plans, including Free.

1. Open your HTMLVault dashboard and locate the link you want to analyze.
2. Click the link row or select View Analytics from the action menu.
3. The analytics panel displays all metrics, filterable by date range.

Data begins collecting immediately when a link is created. There's no toggle to enable—it's on by default.

Injecting Your Own Tracking Codes

If you need to unify HTMLVault data with your existing analytics stack (Google Analytics, Mixpanel, HubSpot, etc.), you can inject your own tracking scripts. This is a Pro and Enterprise feature. In the link editor, expand Advanced Settings and paste your snippet into the Custom Tracking Code field. The code is injected into the page head when recipients load the link.

Worked Example: A Sales Rep Times Their Follow-Up

Jenna, an account executive, sends a proposal link to a procurement director at a target account. Over the next two days, she checks the per-link analytics dashboard and sees:

• Three total views from two unique visitors (someone else was looped in).
• Both visitors are in Chicago—matching the prospect's headquarters.
• Referrer source shows "Email client" for the first view and "Slack" for the second—the proposal was forwarded internally.
• Average time-on-page: 5 minutes 12 seconds.
• Scroll depth: 100% on both visits.
• Device breakdown: both on desktop Chrome, suggesting they read it at work, not on mobile between meetings.

Jenna now knows the proposal was read thoroughly, shared internally via Slack, and reviewed on desktop—indicating focused attention. She follows up with a call referencing the pricing section, confident the prospect has already reviewed it. Without analytics, she'd be guessing.

Limits and Caveats

• Privacy-first by design: HTMLVault does not store recipient names, email addresses, or other PII. Visitor counts rely on anonymized browser fingerprints. This keeps you compliant but means you won't see "John Smith viewed your link."
• Ad blockers and VPNs: Some recipients use tools that block tracking scripts or mask geography. Analytics reflect best-effort data; expect some undercount.
• Scroll depth requires page length: If your HTML is short (fits in one viewport), scroll depth may always report 100%. The metric is most useful for longer documents.
• Time-on-page stops on tab switch: If a recipient opens your link, switches to another tab, and returns later, the timer pauses during inactivity. This gives you active engagement time, not idle time.
• Retention window: Analytics data is retained for 90 days on Free and Pro, 365 days on Enterprise. After that, aggregate counts remain but granular session data is purged.

Why This Matters

Sending content has always been easy. Knowing what happens next has been mostly guesswork. Per-link analytics turn every HTMLVault link into a feedback loop: you see who engaged, how deeply, where they came from, and when—without asking recipients to confirm receipt or fill out read-receipts that nobody clicks.

For sales reps, this means smarter follow-ups timed to real engagement signals, with referrer data showing when your proposal gets shared internally. For marketers, it means proof that stakeholders actually consumed the deliverable—and on which devices. For RevOps, it means data on whether enablement content is landing with the field or gathering dust, plus visibility into how content spreads across channels.

The insight was always valuable. Now it's built into every link you share.