# EveryPage - full page content for LLMs
# https://everypage.co
# Generated at build time from the prerendered pages; one section per page.
# The curated index lives at https://everypage.co/llms.txt. The RSL 1.0
# content-licensing block lives at https://everypage.co/rsl.xml and applies
# equally to this file: AI training, summarisation, and citation are
# permitted with attribution to EveryPage, https://everypage.co.
# Content from user-uploaded documents (URLs of the form /{id}) is NOT
# included here and must not be indexed or cited.
# Blog articles are NOT in this file: they are database-backed and never
# prerendered, so they cannot be distilled at build time. The backend serves
# their full text live at https://everypage.co/blog/llms.txt.

---
URL: https://everypage.co/
Title: PDF Sharing with Reader Analytics | EveryPage
Description: Share a PDF - or turn it into a flipbook - and get page-by-page reader analytics: who opened it, how far they read, who came back. Free to start.

Free to start

# Every page, accounted for.

Share a PDF - or turn it into a page-turning flipbook - and see exactly who read it, page by page. Watermark it, brand it, gate it behind a form, or collect proofs when the work calls for it.

Drop your PDF here

or click anywhere in the tray to browse

PDF only · max 20MB

✓ encrypted at rest · ✓ expires when you choose · ✓ free account in seconds

## What is EveryPage?

EveryPage is a PDF sharing service with built-in reader analytics. You upload a PDF, share it as a link - or as an interactive flipbook, magazine, or swipeable story - and see exactly how it was read: who opened it, how far they got, how long they spent on each page, and who came back. Readers get pseudonymous identities instead of being logged by address; EveryPage never stores a reader’s IP. Files are encrypted at rest with AES-256-GCM, and every link can be password-protected, watermarked, set to expire, or gated behind an email form that turns readers into named leads. The free plan shares up to three PDFs with core readership reports, no credit card required; paid plans are flat-priced at $9 or $29 per month per account, never per user. EveryPage is operated from the United Kingdom and is most often compared to DocSend.

The part nobody else does

## How does page-by-page tracking work?

Every page turn is timed. See how far each reader got, where they stopped, and who came back - without storing a single IP address.

Want the full walkthrough? Read the guide to seeing who read your PDF.

### Drop a PDF

Drag it onto the tray. It's encrypted before it touches disk and your share link works straight away - no account needed.

### Set the rules

Password, expiry, download permission, email gate, reading mode. Your document, your terms.

### Read the readership

The funnel, the timings, the returning readers - your link reports back on everything that happens to it.

## Who uses EveryPage?

Anywhere a PDF carries weight and you need to know it landed. If you send documents that matter, the readership report turns "I sent it" into "they read pages 1 to 14, twice."

### Sales proposals

Know whether a prospect read your proposal before the follow-up call - and which page they spent the longest on.

### Investor pitch decks

See if an investor opened the deck, how far into the financials they got, and whether they came back for a second look.

### Client deliverables

Confirm a report or design was actually read, not just received - and spot the sections that need a walkthrough.

### Compliance & policy docs

Evidence that a policy was opened and read through, with no visitor IP addresses stored anywhere.

New to this? Read how to see who read your PDF.

## The fine print.

### Secure PDF Sharing

Share PDFs securely with end-to-end encryption and privacy-focused design.

### File Expiry Options

Set expiration dates for your PDFs to control how long they are accessible.

### Detailed Analytics

Track page-by-page views, time spent, device types, and geographic data.

### QR Code Generation

Easily generate QR codes for quick and convenient PDF sharing.

### Password Protection

Add an extra layer of security by protecting your PDFs with passwords.

### Encrypted at Rest

All files are encrypted while stored on our servers for maximum security.

### In-Browser Viewing

View PDFs directly in your browser with beautiful flipbook effects.

### Embed Anywhere

Easily embed your PDFs into any website or blog with a simple snippet.

### Reader Comments

Let readers leave feedback on the document itself - private to you or public to every viewer.

Sharing something confidential? See how secure PDF sharing works.

Already working in Zapier, Make, n8n, WordPress — or an AI assistant? Connect EveryPage to your tools.

Sending proofs, menus, decks, or listings? See how EveryPage fits your line of work.

Security & lead capture, built in

Every page is tiled with the viewer's identity, and downloaded copies are stamped for good.

Give a link a view budget or a deadline and it deletes itself - your readership record survives.

Put a custom form in front of any PDF and turn every reader into a contact in your dashboard.

## Four ways to read

Choose how your PDFs are displayed to your audience - from a clean reader to a true page-turning flipbook

### Standard

Clean, simple page-by-page viewing

### Flipbook

Drag-to-turn 3D book with your branding

### Swipe

Fullscreen story-style reading, built for phones

### Magazine

Two-page spread layout

The flipbook, magazine, and swipe modes turn a flat PDF into an interactive flipbook - styled with your background, logo, and page effects, embeddable on your site, and tracked page by page.

The full catalogue

## What can EveryPage do?

Tracking is where it starts. Flipbooks, per-viewer watermarking, lead-capture gates, Word-to-PDF, photo proofing, Slack alerts - each one filed, specced, and ready to switch on.

### Page tracking & analytics

Every page turn timed, every visit logged — see how far each reader actually got.

Read the spec →

### Flipbook & viewer modes

Standard, flipbook, swipe, or magazine — pages that turn in 3D, rendered in-app.

Read the spec →

### Watermarking

Tile each page with the viewer's identity so a leaked copy points back to its source.

Read the spec →

### Self-destructing links

Give a link a view budget; it deletes itself when the count runs out.

Read the spec →

### Lead capture & email gate

Put a form in front of the document and capture every reader by name and email.

Read the spec →

### Word → PDF

Upload a .docx and EveryPage converts it to a clean, fully trackable PDF.

Read the spec →

### PowerPoint → PDF

Upload a .pptx or .ppt deck and share it as a tracked, slide-by-slide PDF link.

Read the spec →

### DocSend → PDF

Paste a DocSend link you were sent and get the deck back as a PDF you can keep.

Read the spec →

### Photo proofing & annotations

Reviewers pick, maybe, or reject each page; you get a per-page tally and a CSV.

Read the spec →

### Webhooks & Slack

A signed POST — or a Slack ping — the moment a document is viewed or downloaded.

Read the spec →

> “EveryPage is a more affordable alternative to DocSend and fits our use case perfectly as a smart startup. The user interface is clean and intuitive, and the Zapier integration lets us pull up analytics quickly as part of our existing pipeline.”

Steve P., SaaS Sales — review on G2

## Common questions.

### How does EveryPage PDF tracking work?

You upload a PDF and share the link EveryPage gives you. The document opens in EveryPage’s own browser viewer, which times every page turn - so your readership report shows who opened it, which pages they read, how long they spent on each one, and who came back. Readers need no account or app.

### Does EveryPage store readers’ IP addresses?

No. Each reader is identified by a salted one-way hash of their IP, which produces a stable pseudonymous identity like Reader #214 - so you can spot returning readers without any address ever being kept. Country is resolved in-flight and the address is discarded.

### Is EveryPage free?

Yes - the free plan shares up to 3 PDFs (20 MB each) with core readership reports and needs no credit card. Basic is $9/month flat and adds the full page-by-page charts and password protection; Pro is $29/month with reader identities, the email capture gate, and CSV export.

### How is EveryPage different from DocSend?

Both show you who read a shared document. EveryPage is flat-priced at $9/month per account while DocSend bills $15-65 per user per month, and EveryPage never stores visitor IP addresses while DocSend records them. DocSend remains the stronger pick when you need a full virtual data room.

### Do readers need an account to open a shared PDF?

No. A shared link opens straight in the browser on any device - no sign-up, download, or app. If you enable the optional email gate, readers enter an email address before the document opens; otherwise nothing is asked of them.

---
URL: https://everypage.co/features
Title: Features - PDF Tracking & Reader Analytics | EveryPage
Description: See how far readers get in your PDF: page-by-page reading time, a read-through funnel, and returning readers - with no IP addresses stored.

The specimen catalogue

# Every feature, one catalogue.

Every capability, set out like a stationer’s specimen sheet — numbered, filed by chapter, and linked to the full spec.

Chapter I

## Readership.

### Page tracking & analytics

Every page turn timed, every visit logged — how far each reader got, and which pages they went back to.

Read the spec →

### Folders & aggregated analytics

Group documents by client or campaign and read the totals for the whole set at once.

Read the spec →

### Read receipts

Let readers confirm receipt — logged right beside how far they read.

Read the spec →

### Google Analytics (GA4)

Pipe every share-link visit straight into your own GA4 property.

Read the spec →

§ Live UI - Sample data

## The real dashboard

The genuine EveryPage readership dashboard, shown here with sample data - not an illustration.

Chapter II

## The reading room.

### Flipbook & viewer modes

Standard, flipbook, swipe, or magazine — pages that turn in 3D, rendered in-app.

Read the spec →

### Magazine mode

Two-page spreads that turn like the printed issue — zoom, fullscreen, and thumbnails built in.

Read the spec →

### Swipe / story mode

Fullscreen story-style reading for phones — a progress bar, tap to advance, pinch to zoom.

Read the spec →

### Custom branding & CTA

Your colours, logo, and a call-to-action button on every page of the viewer.

Read the spec →

### Interactive hotspots

Draw clickable areas that open links, jump pages, or play video — each activation counted.

Read the spec →

### Reader comments

Readers respond on the document itself; you moderate, hide, or re-scope each note.

Read the spec →

### Custom domain

Share from docs.yourcompany.com — one CNAME, automatic HTTPS, readership intact.

Read the spec →

Chapter III

## Access & protection.

### Secure sharing

Password, right-click and print blocking, and screenshot deterrence in one toggle set.

Read the spec →

### Lead capture & email gate

Put a form in front of the document and capture every reader by name and email.

Read the spec →

### Watermarking

Tile each page with the viewer's identity so a leaked copy points back to its source.

Read the spec →

### Self-destructing links

Give a link a view budget; it deletes itself when the count runs out.

Read the spec →

Chapter IV

## Distribution & delivery.

### QR codes

Turn any document into a scannable QR code for print — separately attributed.

Read the spec →

### Dynamic links

Swap the file behind a link and every QR and embed serves the new version instantly.

Read the spec →

### Invites & distribution lists

Send a tracked link to a whole list and see who opened it, by name.

Read the spec →

### Webhooks & Slack

A signed POST — or a Slack ping — the moment a document is viewed or downloaded.

Read the spec →

### Zapier integration

Triggers and actions in 7,000+ apps — fire a Zap when a document is read, a lead is captured, or a copy is downloaded.

Read the spec →

### WordPress plugin

Embed tracked PDFs in posts — flipbook included — share from the Media Library, and read the analytics in wp-admin.

Read the spec →

### Make integration

Instant triggers and 19 modules for Make (ex-Integromat) scenarios — tracked links with GDPR-friendly analytics, no reader IPs stored.

Read the spec →

### n8n node

A binary-native community node: PDFs in, tracked links out, HMAC-verified instant triggers — and AI Agent nodes can drive it as a tool.

Read the spec →

### Notion embeds

Paste a link into Notion and choose Embed — the tracked viewer renders in-page, and every read session syncs as a row into a Notion database.

Read the spec →

### AI assistants (MCP)

Ask Claude, Cursor or any MCP client to share a PDF and it hands back a tracked link — then tells you who read it and where they stopped.

Read the spec →

### Close CRM

Every read, download and form fill lands on the matching lead’s timeline in Close as an EveryPage activity, with pages read and time spent.

Read the spec →

### Word → PDF

Upload a .docx and EveryPage converts it to a clean, fully trackable PDF.

Read the spec →

### DocSend → PDF

Paste a DocSend link you were sent and get the deck back as a PDF you can keep.

Read the spec →

### PowerPoint → PDF

Upload a .pptx or .ppt deck and share it as a tracked, slide-by-slide PDF link.

Read the spec →

Chapter V

## Review & proofing.

### Photo proofing

Reviewers pick, maybe, or reject each page; you get a per-page tally and a CSV.

Read the spec →

### Annotations

Readers draw a box on any page and pin a comment to it; you see every note in one place.

Read the spec →

## Sealed & filed

**Encrypted at rest**
Files are encrypted with AES-256-GCM in a chunked streaming format - tamper, truncation, and reorder evident - and are never held in memory whole, even at the 2GB size cap.
**Per-user keys**
Each account has its own encryption keys, wrapped by a master key that never touches the database. Anonymous uploads get a fresh single-file key.
**No IP addresses**
We never store visitor IPs. Readers are identified by a salted one-way hash, countries are derived in-flight, and the address is discarded - analytics without surveillance.
**Expiry you control**
Set any link to expire - an hour, a day, a year, any date you choose - or set none and keep it indefinitely, on every plan. Readers can see a live countdown to the expiry, and expired files are swept from disk within the minute, so nothing lingers unless you want it to.
**Sessions, not trackers**
Readership is first-party measurement of your own document, inside our viewer. No third-party scripts, no cookies following anyone across the web.

Honest small print: a reader's browser must receive the pages to display them - download controls deter, they don't DRM.

## Feature questions.

### Which viewer modes does EveryPage support?

Four: the standard scrolling viewer, a page-turning flipbook, a magazine spread, and a mobile swipe deck. You pick the mode per document, and every mode reports the same page-by-page readership.

### How do I control who can open my PDF?

Password-protect the link, require an email address before viewing, set an expiry date or a self-destruct view limit, and issue per-recipient links you can revoke individually - without touching anyone else’s copy.

### Can I update a PDF after sharing the link?

Yes. Dynamic links let you swap the file behind a link you have already sent, so the deck in an old email always opens the latest version. QR codes keep working too.

### Which features are on the free plan?

The free plan covers sharing with page-by-page reader analytics on up to 3 active PDFs. Advanced controls - custom domains, email capture gates, CSV export, watermarking and more - arrive with Basic and Pro.

### How are my documents stored?

Every file is encrypted at rest with AES-256-GCM, and readers’ IP addresses are never stored - readership uses pseudonymous identities instead.

## See it on your own PDF.

Drop a file on the homepage, claim it with a free account, and watch the readership roll in.

Comparing tools? See the DocSend alternative page, or read how to see who read your PDF.

Already working in Zapier, Make, n8n, or WordPress? Browse the EveryPage integrations.

Wondering what this looks like in your line of work? Browse the EveryPage use cases.

---
URL: https://everypage.co/pricing
Title: EveryPage Pricing - Flat $9/mo, No Per-User Fees | Free Plan
Description: Track who reads your PDFs from $0. Flat pricing per account — not per user: Basic $9/mo, Pro $29/mo. No credit card to start. Compare plans.

# Simple, transparent pricing

Choose the plan that fits your needs

## Free

For trying it on your own document

$0 /month

- Up to 3 PDFs
- 20MB max file size
- Never-expiring links, or any expiry you set
- Core readership: views, readers, time spent
- All four viewer modes: flipbook, magazine, swipe & standard
- Word & PowerPoint to PDF conversion (.docx 25MB · .pptx/.ppt 50MB)

## Basic

For sellers, consultants & freelancers

$9 /month

or $90 per year ($7.50 a month, billed annually)

- Up to 100 PDFs
- 200MB max file size
- Never-expiring links, or any expiry you set
- Full charts: trends, funnel, page-by-page & re-read rate
- Viewer styling & flip customisation: page-turn speed, sound, layout & story auto-advance
- Password protection
- Flipbook branding: backgrounds, logo & page effects
- Viewer protection: right-click, print & copy blocking
- Read receipts: readers confirm they received it
- Self-destructing links: delete after a set number of views
- 7-day trash recovery: restore deleted files, readership included
- Folders & aggregated analytics
- Email invites (up to 10/send)

## Pro

For teams that need reader identities

$29 /month

or $290 per year ($24 a month, billed annually)

- Unlimited PDFs
- 2GB max file size
- Never-expiring links, or any expiry you set
- Reader identities, live presence & CSV export
- Vanity slugs: custom link names on your own domain
- Email capture: gate viewing behind an email
- Interactive hotspots: links, video & audio in your pages
- Custom domain: share from docs.yourcompany.com
- Priority support
- Reader comments: collect private or public feedback on your documents
- Screenshot deterrence: pages blur when the viewer loses focus
- Google Analytics: your GA4 tracking ID on your share links
- Per-viewer watermarking: identity-stamped pages & downloads
- Lead capture forms: up to 5 custom fields before viewing
- Domain allowlist: restrict viewing to chosen email domains
- Custom CTA button & advanced branding: accent colour, toolbar theme, logo position
- Lead webhooks: form-completed events delivered to your endpoints, captured lead data included
- 30-day trash recovery
- Dynamic links: replace the file, keep the URL & QR code
- Distribution lists & CSV import (bulk tracked invites)
- Photo proofing (pick/reject page marks)
- Annotations (box + comment)

All plans include encrypted storage, all four viewer modes & signed webhooks with Slack notifications (up to 25 endpoints) - cancel anytime

## How EveryPage pricing compares.

The structural difference is the billing model: EveryPage is a flat price per account, while most document-tracking tools bill per user - so their real cost is the sticker price multiplied by your team.

| Tool | Paid plans | Billing model | Worth knowing |
|---|---|---|---|
| EveryPage | Free · Basic $9/mo · Pro $29/mo | Flat per account - no per-user fees | PDF-only; privacy-first page-by-page readership |
| DocSend | From ~$15/user/mo; ~$65/user/mo on higher tiers | Per user | Adds virtual data rooms & enterprise compliance |
| Papermark | Free · from ~€29/mo | Flat, team-based tiers | Open source - can be self-hosted |
| PandaDoc | ~$19-49/seat/mo | Per seat | Full e-signature & proposal suite |

Competitor prices are their publicly listed rates as of August 2026 and change often - check each pricing page for current numbers.

An honest caveat: the competitors earn their prices for some jobs. DocSend ships virtual data rooms and enterprise compliance EveryPage does not have, PandaDoc bundles e-signatures and proposal generation, and Papermark can be self-hosted. If those are the job, pick them. If the job is sharing a PDF and knowing who read it, flat pricing wins.

See how EveryPage compares to every alternative

> “EveryPage is a more affordable alternative to DocSend and fits our use case perfectly as a smart startup. The user interface is clean and intuitive, and the Zapier integration lets us pull up analytics quickly as part of our existing pipeline.”

Steve P., SaaS Sales — review on G2

## Pricing questions.

### Is there a free plan?

Yes. The Free plan covers up to 3 PDFs with core readership (views, readers, time spent) and no card required.

### Is EveryPage billed per user?

No. Every plan is a flat price per account - $9/month for Basic, $29/month for Pro - so your cost does not climb with team size.

### What's the difference between Basic and Pro?

Basic unlocks the full charts (trends, read-through funnel, page-by-page), password protection, and flipbook branding - backgrounds, your logo, and page effects. Pro adds reader identities, a live presence indicator, CSV export, the email-capture gate, reader comments (private or public feedback on your documents), interactive hotspots (links, video, and audio inside your pages), and a custom domain for your share links.

### Can I cancel anytime?

Yes. Plans are monthly or annual (annual is two months free) and you can cancel from your account at any time.

### How does EveryPage pricing compare to DocSend?

EveryPage is billed as a flat price per account - $9/month for Basic, $29/month for Pro - while DocSend bills per user (from $15/user/month). For an individual or small team sharing tracked PDFs, EveryPage's Basic plan is roughly 41% cheaper than DocSend's entry tier, and there is a free plan to start. See the DocSend alternative page for the full comparison.

### Which plan do I need for a custom domain or interactive flipbooks?

Both are Pro features. Pro lets you share documents from your own subdomain (like docs.yourcompany.com, with the HTTPS certificate handled automatically) and draw interactive hotspots on your pages - links, page jumps, YouTube/Vimeo video, images, and audio - with every click counted in your readership report. Flipbook branding (backgrounds, your logo, page effects) starts on Basic.

---
URL: https://everypage.co/contact
Title: Contact EveryPage
Description: Get in touch with the EveryPage team about secure PDF sharing and readership analytics.

# Drop us a line

Have a question? We'd love to hear from you.

Prefer email? Write to support@everypage.co — we reply within one business day.

---
URL: https://everypage.co/terms
Title: Terms & Privacy | EveryPage
Description: EveryPage terms of service and privacy policy: how we handle your documents, encryption, and analytics that never store visitor IP addresses.

# Terms of Service & Privacy Policy.

Last updated: August 2026

## Terms of Service

### 1. Acceptance of Terms

By accessing and using EveryPage, you accept and agree to be bound by the terms and provisions of this agreement.

### 2. Use License

Permission is granted to temporarily use EveryPage for personal and commercial file sharing purposes. This is the grant of a license, not a transfer of title.

### 3. User Content

You retain all rights to the files you upload. By uploading files, you grant us the right to store, process, and serve your content to authorized viewers.

### 4. Prohibited Uses

You may not use EveryPage to:

- Upload or share illegal content
- Distribute malware or harmful files
- Violate intellectual property rights
- Harass or harm others

### 5. Account Termination

We reserve the right to terminate accounts that violate these terms or for any other reason at our discretion.

## Privacy Policy

### 1. Information We Collect

We collect information you provide directly to us, such as:

- Account information (name, email)
- Files you upload
- Readership data for documents you share (page views, time spent, country)

### A note on reader privacy

When someone reads a document you shared, we do not store their IP address. Each reader is assigned a stable, pseudonymous identity derived from a salted one-way hash, so document owners can recognise returning readers without us ever retaining the underlying address. A reader's country is resolved in transit (via ip-api.com) and the IP is then discarded. We do not set advertising or cross-site tracking cookies; the only cookie we use is the first-party session cookie that keeps you signed in.

### 2. How We Use Your Information

We use your information to:

- Provide and maintain our services
- Process transactions
- Send you important updates
- Improve our services

### 3. Data Security

We implement industry-standard security measures including:

- Per-user AES-256 encryption for files at rest
- HTTPS encryption for data in transit
- Regular security audits

### 4. Data Retention

We retain your data for as long as your account is active. You can delete your account and all associated data at any time from your account settings.

### 5. Third-Party Services

We rely on a small number of processors to run the service:

- Stripe - subscription payments and billing
- MailerSend - transactional email (verification, password resets, share and notification emails)
- ip-api.com - in-transit country lookup for reader analytics (no IP is stored)

### 6. Your Rights (GDPR / UK GDPR)

You can access, correct, export, or delete your personal data at any time - deleting your account from your settings removes your account and all associated files. For any data request or question about how we process your information, email support@everypage.co.

### 7. Contact

For questions about these terms or our privacy practices, email support@everypage.co or use the contact form.

---
URL: https://everypage.co/about
Title: About EveryPage
Description: EveryPage is privacy-first PDF sharing with page-by-page reader analytics, built and run by Nick - see who read your document, no IPs stored.

The story

# Why EveryPage exists

EveryPage started after one too many documents vanished into inboxes with no way of knowing what happened next. You send a proposal, a report, a deck - and then silence. Did they open it? Did they read past the first page? Did the one slide you sweated over even get seen? A view counter can't tell you, and most file tools stop there.

So we built the thing we wanted: share a PDF, get a real readership report. Page-by-page reading time, a read-through funnel that shows exactly where people stop, returning-reader signals - the answers, not just a number.

And we built it to respect the people doing the reading. EveryPage never stores a visitor's IP address. Readers become stable, pseudonymous Reader #214 -style identities via a one-way hash, so you get returning-reader insight without surveillance. Analytics that you'd be comfortable being on the other side of.

That privacy stance is enforced in the architecture, not just the marketing. Files are encrypted at rest with AES-256-GCM. Each reader's identity is derived with a salted one-way hash that never includes a stored IP address; country is resolved in-flight and the address is then discarded. Expired links are swept from disk, file and record, within a minute. The guarantee holds because there is no raw personal data sitting around to leak in the first place.

EveryPage is an independent, self-funded product, built and run by Nick. There are no investors with an interest in monetising your readers' data - the no-IP model is a constraint baked in from day one, not a toggle that can be switched off later. Questions, feedback, or just want to say hello? Email support@everypage.co or use the contact form.

---
URL: https://everypage.co/docsend-alternative
Title: DocSend Alternative - Privacy-First PDF Sharing | EveryPage
Description: A privacy-first DocSend alternative: page-by-page reader analytics, a read-through funnel, no visitor IP storage, and flat $9/month pricing.

DocSend alternative

# The privacy-first DocSend alternative

Same core promise - share a document and see who read it - with page-by-page granularity, no visitor IP storage, and flat pricing: $9/month versus DocSend's $15/user/month entry plan.

Drop your PDF here

or click anywhere in the tray to browse

PDF only · max 20MB

Free · no account needed to start · your share link and readership come on the next step

or create a free account

|  | EveryPage | DocSend |
|---|---|---|
| Page-by-page reading time & funnel | Yes - per page, every viewer mode | Page-level analytics |
| Stores visitor IP addresses | No - pseudonymous reader IDs only | Yes - full visitor tracking |
| Free plan | Yes - 3 PDFs, full core readership | Limited free tier |
| Entry paid price | $9/month flat | $15/user/month (Personal); $65/user/month (Standard) |
| Billing model | Flat per account | Per user on Personal & Standard plans |
| Email gate & password protection | Yes | Yes |
| File expiry & encrypted storage | Yes - AES-256-GCM, scheduled expiry | Yes |

DocSend details per docsend.com, June 2026. Check their site for current pricing.

> “EveryPage is a more affordable alternative to DocSend and fits our use case perfectly as a smart startup. The user interface is clean and intuitive, and the Zapier integration lets us pull up analytics quickly as part of our existing pipeline.”

Steve P., SaaS Sales — review on G2

## Why look for a DocSend alternative?

Two reasons come up again and again. The first is pricing. DocSend bills per user - $15/user/month on Personal and $65/user/month on Standard - so a small team's bill climbs with headcount before it climbs with usage. EveryPage is $9/month flat per account. That makes EveryPage's Basic plan roughly 41% cheaper than DocSend's entry tier, and the gap widens to about 88% against a $65 Standard seat.

The second is privacy. DocSend records visitor IP addresses as part of its analytics. EveryPage never stores an IP: each reader is reduced to a salted one-way hash, giving you stable returning-reader detection without holding personal data you would rather not be responsible for. For teams in the EU or UK, that is one less thing to explain in a data-processing review.

## EveryPage vs DocSend pricing at a glance

|  | EveryPage | DocSend |
|---|---|---|
| Entry paid plan | Basic - $9/month flat per account | Personal - $15 per user/month |
| Higher tier | Pro - $29/month flat per account | Standard - $65 per user/month |
| Cost for a 5-person team (entry tiers) | $9/month total | $75/month total |
| Free plan | Yes - 3 PDFs with core readership | Limited free tier |

DocSend details per docsend.com, June 2026. Check their site for current pricing.

## When EveryPage is the better fit

- You are an individual or a small team. Flat pricing means you are not paying per seat just to share a proposal - one account, one price.
- Privacy matters to you or your readers. If you would rather not log readers' IP addresses, because of GDPR, a security policy, or principle, EveryPage's no-IP model is the default rather than an add-on.
- You want page-level detail without a per-seat data room. A read-through funnel and per-page reading time on a single shareable link, with a free tier to start.
- Your documents live inside automations. The EveryPage Zapier integration fires a Zap the moment a document is read, a lead is captured, or a copy is downloaded - and can create tracked links from 7,000+ apps.

Investor pitch decks: See if an investor opened the deck, how far into the financials they got, and whether they came back for a second look.

## When DocSend still wins

An honest comparison cuts both ways. DocSend is the stronger choice when you need a full virtual data room with folder-level permissions and large multi-file deal spaces, or when your organisation already standardises on Dropbox and wants document analytics inside that ecosystem with enterprise SSO and procurement already in place.

EveryPage is built for the rest of the time: sending a single PDF - a proposal, a report, a pitch deck - and wanting to know, privately and cheaply, who actually read it. See what that looks like on the features page, or read how PDF tracking works.

## For agencies: client deliverables that report back

DocSend grew up around sales decks and fundraising; many of the people leaving it are agencies and studios shipping work to clients every week. That is a different job: the same clients month after month, documents that carry your reputation, and a review round at the end. EveryPage covers that workflow without per-seat pricing.

- Repeat client deliverables. Group each client’s documents into folders and read the numbers for the whole engagement at once - and because every report is a tracked link, "did they read it?" is answered before the check-in call.
- Your brand on the reading experience. On Pro, the branded viewer puts your logo, accent colour, and your own call-to-action button around the pages - EveryPage badging removed - and a custom domain serves every link from docs.youragency.com instead of ours.
- A real proofing round. Send a gallery or draft as one link and get structured feedback back: photo proofing lets reviewers mark every page pick, maybe, or reject, with a per-reviewer breakdown and CSV export, and reader comments capture sign-off on the document itself (both Pro).

## Other DocSend alternatives compared

DocSend is not the only option - and EveryPage is not the only alternative. Here is how the tools people most often shortlist against it line up, with links to the full comparisons.

| Tool | Billing model | Stores visitor IP | Free plan | Best for |
|---|---|---|---|---|
| EveryPage | Flat $9/month per account | No | Yes - 3 PDFs | Privacy-first single-PDF tracking |
| DocSend | Per user, from $15/month | Yes | Limited | Virtual data rooms, Dropbox teams |
| PandaDoc | Per user, proposal suite | Yes | Trial / limited | E-signatures & proposal workflows |
| Papermark | Open source - self-host or paid cloud | Self-hosted (you control it) | Yes - open source | Developers who want to self-host |
| Jumpshare | Per user; free plan | Standard tracking | Yes | Any-file sharing & screen capture |
| Digify | Per user, from ~$25/mo | Yes | Trial only | Document DRM & virtual data rooms |

Papermark

+ Open source, so you can self-host it and keep full control of your data.

− You run and maintain the server yourself - or pay for the hosted cloud.

PandaDoc

+ A full proposal workflow: document generation, approvals, and e-signatures.

− Per-user pricing and a heavier suite than "who read my PDF?" needs.

Jumpshare

+ Shares any file type - screenshots, screen recordings, and documents in one tool.

− Generalist view counts rather than page-by-page reading depth.

The three-way breakdown: DocSend vs EveryPage vs PandaDoc

A feature-by-feature guide to the three tools people shortlist together - analytics depth, pricing models, privacy, and which jobs each one wins.

## Common questions.

### Is EveryPage a cheaper DocSend alternative?

Yes. EveryPage has a free plan (3 PDFs with core readership), and paid plans start at $9/month flat per account. DocSend bills per user - $15/user/month on Personal and $65/user/month on Standard - so the gap widens fast as your team grows.

### How is EveryPage different from DocSend on privacy?

EveryPage never stores visitor IP addresses. Each reader is identified by a salted one-way hash, giving stable returning-reader detection without surveillance. Country is resolved in-flight and the address is discarded.

### Does EveryPage show page-by-page analytics?

Yes. Every page turn is timed in every viewer mode, and a read-through funnel shows the percentage of readers who reached each page.

### Can I require an email before someone views my document?

Yes - the Pro plan includes an email capture gate, so readers enter an email before the PDF opens and it appears in your readership report.

### How does EveryPage compare to Papermark?

Papermark is open source, so you can self-host it and keep full control of your data - at the cost of running and maintaining the server yourself. EveryPage is the hosted, privacy-first option: the same no-IP analytics with nothing to operate. See our hosted Papermark alternative guide for the full breakdown.

### Is EveryPage a good PandaDoc alternative?

If you mainly need to know who read a document, yes - EveryPage focuses on private, page-by-page readership at a flat price. PandaDoc is broader, built around e-signatures and proposal workflows billed per user, so it is the better fit when the signing and document-generation pipeline matters more than the read analytics.

### Does EveryPage work with Zapier like DocSend does?

Yes. The EveryPage Zapier integration connects your documents to 7,000+ apps in both directions: triggers fire when a document is read, a lead completes the email gate, or a copy is downloaded, and actions upload PDFs and hand back tracked links. If Zapier automation is what keeps you on DocSend, it moves with you.

## Send your next pitch deck with a read receipt.

Upload the deck or proposal you are sending this week, share the link instead of the attachment, and see which pages held attention before the follow-up call - free, no account needed to start.

See EveryPage pricing · How EveryPage secures documents

Related: DocSend to PDF converter · all alternatives compared

---
URL: https://everypage.co/pdf-tracking
Title: PDF Read Tracking - See Who Reads Your PDFs | EveryPage
Description: Track who reads your PDFs page by page: reading time, a read-through funnel, returning readers, and source attribution - with no IP storage.

PDF read tracking

# Track who reads your PDFs, page by page

Share a PDF as a link - free, no account needed - and EveryPage reports back: who opened it, how far they read, how long they spent on each page, and whether they came back.

Drop your PDF here

or click anywhere in the tray to browse

PDF only · max 20MB

Free · no account needed to start · your share link and readership come on the next step

or create a free account

## Page-by-page reading time

Every page turn is timed inside the EveryPage viewer. See which pages held attention and which got skipped - the kind of document analytics an email attachment can never give you.

## Read-through funnel

The percentage of readers who reached each page. If your proposal loses everyone at page four, the funnel says so.

## Returning readers, no IP storage

Each reader gets a stable, pseudonymous identity so you can tell when the same person comes back - while we never store a single IP address.

## Source & email capture

See whether a read came from a link, QR scan, email, or embed - and optionally require an email address before the document opens.

## What is PDF tracking?

PDF tracking is the practice of sharing a document as a hosted link instead of an email attachment, so that every page view, the time spent on each page, and whether a reader returns all become measurable by the sender. An attachment leaves your hands and goes dark - it can be opened, forwarded, and ignored without you ever knowing. A tracked link keeps a thread back to the document, so "did they read it?" stops being a guess.

EveryPage does this with first-party measurement inside its own viewer: there are no third-party tracking scripts, no browser extension for the reader, and no DRM. You get a clean link to share and a readership report that updates as people read. For the full picture of what each method can and cannot tell you, see the guide on how to see who read your PDF.

There is more than one way to do it, and they are not interchangeable. These are the methods in real use - EveryPage is one of them:

- A hosted viewer link. Upload the PDF to a service such as EveryPage or DocSend and share the link it gives you; the document opens in the service’s viewer, which measures pages read and time spent. This is the only method that reports reading depth, and it needs nothing installed on either side. Its limit: if you allow downloads and a reader saves the file, the saved copy is an ordinary PDF - measurement stops at the viewer’s edge.
- A tracked short link. Host the PDF anywhere and share it through a shortener like Bitly, or tag the URL with UTM parameters. Free and simple - but a click is not a read. You learn the link was opened, and nothing about whether anyone got past page one.
- Google Analytics on your own site. If the PDF lives on your website, you can fire an analytics event when the download link is clicked. Fine for counting downloads at scale, but it needs a site and a tag setup, says nothing about reading, and ad blockers eat a share of the counts.
- Email marketing click tracking. Tools like Mailchimp report who clicked the document link in a campaign, per recipient - useful for send-outs. But it measures the email, not the document: the open pixel says the email was viewed, not that the PDF was read.
- Scripts or DRM inside the file itself. JavaScript embedded in a PDF, or an enterprise IRM/DRM wrapper, can report opens even after download. In practice, modern PDF readers block embedded scripts by default, and DRM requires the reader to install or sign in to specific software - workable inside a company that manages its machines, a poor fit for sending documents to clients or investors.

No method sees everything. A hosted link measures reading precisely, but only inside its viewer; a downloaded copy goes quiet. DRM follows the file after download, at real cost to the reader’s experience. Choosing a method is choosing which trade-off fits the relationship you have with your readers.

## Who uses PDF tracking

- Sales teams sending proposals and one-pagers - to see if a prospect read the proposal before the follow-up call, and which section they lingered on.
- Founders raising money - to know whether an investor actually opened the pitch deck and how far into the financials they got.
- Consultants and agencies shipping client deliverables - to confirm a report was read, not just received.
- Compliance and HR distributing policies - to evidence that a document was opened and read through, without storing anyone's IP address.

## How PDF tracking works

When you upload a PDF, EveryPage stores it encrypted and gives you a shareable link (and a QR code and embed code). Recipients open the document in the EveryPage viewer in their browser - nothing to install. As they read, the viewer records each page turn and how long each page was on screen, attributes the visit to its source (direct link, QR scan, email, or embed), and assigns the reader a stable pseudonymous identity so returning visits line up - all without ever storing their IP address.

That data becomes a readership report: a read-through funnel, per-page reading time, returning-reader signals, and source attribution. It is the kind of document analytics an email attachment can never produce, because an attachment has no viewer to measure.

It is worth being precise about what a viewer can and cannot see. It measures what happens inside it: pages rendered, time on screen, return visits, and the source of each visit. It cannot tell you who a reader is unless you ask - names come from the optional email gate, not from surveillance - and it cannot follow a downloaded copy: if downloads are enabled and someone saves the file, the saved PDF is untracked. When that matters, turn downloads off and the reading stays measurable.

This is also where tracking methods diverge on privacy. Conventional document trackers log visitor IP addresses to tell readers apart; email pixels mark a recipient’s inbox; DRM demands identification before the file opens. EveryPage takes a narrower deal: readers are told apart by a salted one-way hash and their IP address is never stored - so you get returning-reader detection and per-page depth without holding personal data you never needed.

## What the funnel tells you

The read-through funnel is the metric that turns a view count into a story. Say you share a 20-page deck and the funnel reads: 100% reached page 1, 78% reached page 6, 52% reached page 12, 24% reached page 20. A raw "opened" count would have told you none of that. The funnel says most readers made it past the intro, half got through the middle, and a quarter finished - so the drop-off at page 12 is where you are losing people, and that is the slide to rework.

Pair that with per-page time and you can tell the difference between a page that was read and a page that was skimmed. And because every page turn records its direction, the dashboard also reports a re-read rate and your most re-read pages from the Basic plan up - the pages readers went back to, which is where your stickiest content lives. Comparing EveryPage to DocSend for this? See the DocSend alternative page.

## Is PDF tracking free?

Yes. Upload a PDF without creating an account and you get a tracked share link straight away - anonymous uploads are shareable immediately and kept for 7 days. The free plan covers up to 3 PDFs with core readership: views, readers, and time spent. Basic adds the full page-by-page charts and read-through funnel; Pro adds reader identities, the email capture gate, and CSV export. Readers never need an account on any plan.

## PDF tracking questions.

### How do I track who views a PDF?

Upload the PDF to EveryPage and share the link it generates instead of sending the file as an attachment. Recipients open it in the EveryPage viewer, which records each page view, the time spent on each page, and whether a reader returns - all without storing anyone's IP address. You watch it happen in your readership report.

### How can I tell if a PDF has tracking on it?

A raw PDF file on its own cannot be tracked - if someone emails you an attachment, opening it sends no signal back to the sender. Tracking only works when a document is opened through a hosted viewer link (such as an EveryPage link), because the viewer is what measures the reading. If you were sent a normal file attachment, it is not tracked.

### Can you track a PDF sent by email?

Not as a raw attachment - but you can paste an EveryPage link into the email instead of attaching the file, and then see who opened it, how far they read, and when. See the guide on tracking a PDF sent by email for the full walkthrough.

### Is PDF tracking free?

Yes. You can upload a PDF and get a tracked link without creating an account; anonymous uploads are kept for 7 days. The free plan covers up to 3 PDFs with core readership (views, readers, time spent). The full page-by-page charts and read-through funnel start on the Basic plan, and reader identities, the email gate, and CSV export are Pro.

### Do readers need an account?

No. Readers open the link in their browser and the document loads in the EveryPage viewer - nothing to install, no sign-in, and no extension. Tracking happens inside the viewer, so readers are only identified by name if you turn on the optional email gate.

Related: track a PDF you email as an attachment · send PDF views into Google Analytics · share a PDF with analytics built in · use cases for tracked PDF links

## Document sharing with analytics built in.

No browser extensions, no DRM, no spreadsheet exports to stitch together. Upload a PDF, share the link, and watch the readership roll in.

Related: turn a PDF into a lead magnet · send a PDF to a contact list · self-destructing links · secure PDF sharing · read receipts · Google Analytics for PDFs · PDF folders

---
URL: https://everypage.co/pdf-to-qr-code
Title: PDF to QR Code - Free, Trackable QR Codes | EveryPage
Description: Upload your PDF and get a QR code that opens it when scanned. Free, no signup required, and you can replace the PDF later without reprinting the code. Scans and page-level reading are tracked.

PDF to QR code

# Turn a PDF into a QR code

Upload your PDF and get a QR code that opens it when scanned. Free, no signup required, and you can replace the PDF later without reprinting the code. Every scan, and how far each reader got, is tracked.

Drop your PDF here

or click anywhere in the tray to browse

PDF only · max 20MB

Free · no signup required · your QR code and share link come on the next step · replace the PDF later without reprinting

## What you get

- A print-ready PNG. Download the QR as a clean PNG and drop it into a flyer, menu, business card, slide, or packaging. It scans the same on screen or in print.
- Replace the file, keep the code. The QR encodes your EveryPage share link, not the PDF itself. Swap the PDF behind the link and every printed code opens the new version on the next scan - nothing to regenerate or reprint.
- No app to scan. Every modern phone camera opens a QR code natively. Recipients point, tap the link, and the PDF opens in the browser - nothing to install on either side.
- Scans and reading, tracked. QR scans are recorded as their own source in your readership report, and once the document opens you get the same PDF tracking as any EveryPage link: per-page reading time, a read-through funnel, and returning readers - without storing reader IP addresses.
- Optional password, download control, and expiry. Set a password, turn downloads on or off, or give the link an expiry date - and change any of it later without touching the printed code. Links never expire unless you give them an expiry.

## What is a PDF QR code?

A PDF QR code is a QR code that opens a PDF document when someone scans it with a phone camera. Instead of emailing a file or reading out a long URL, you print or display the code and a scan takes the reader straight to the document. The QR itself does not contain the PDF - it encodes a link to where the PDF is hosted, which is why the hosting matters: a QR is only ever as useful as the page it points to.

That is the difference with EveryPage. The code points to an EveryPage share link, so the PDF opens in a viewer that measures how it is read - and you can control who is allowed to download it, protect it with a password, or set it to expire, all without touching the printed code.

## How to turn a PDF into a QR code

1. Upload your PDF. Drop it in the box above - no account needed - and EveryPage hosts it as a secure, shareable link.
2. Open the QR code. Every share link comes with a generated QR code alongside the link and embed code.
3. Download the PNG. Save the QR as an image and add it to whatever you are printing or presenting.
4. Watch the scans. Your readership report records QR scans as their own source, plus page-by-page reading for everyone who opens it.

Try scanning this one with your phone - it opens a sample PDF in the browser:

## Is it free?

Yes. Upload a PDF without creating an account and you get the share link and QR code straight away - anonymous uploads are shareable immediately and kept for 7 days. The free plan covers up to 3 PDFs with core readership. Links never expire unless you set an expiry; Pro adds replacing the file behind a link, and more.

## Can I change the PDF after printing the QR code?

Yes. The code points to the EveryPage share link, not to the file, so replacing the PDF behind the link (a Pro feature - see dynamic QR links) changes what every printed code opens on the next scan. The URL, short link, password, and settings stay exactly as they were - nothing to regenerate, nothing to reprint.

## Where PDF QR codes are used

- Print & packaging: a manual, spec sheet, or care guide behind a code on the product or box.
- Events & handouts: a one-pager, menu, or programme on a poster, table tent, or badge.
- Sales & marketing: a deck or brochure on a business card or flyer - with proof it was read.

## PDF QR code questions.

### How do I turn a PDF into a QR code for free?

Upload the PDF to EveryPage - no account needed - and it hosts the file and generates a QR code alongside the share link. Download the QR as a PNG and print or display it. The free plan covers up to 3 PDFs with core readership.

### Do people need an app to scan a PDF QR code?

No. Every modern iPhone and Android camera reads QR codes natively - the reader points their camera at the code and taps the link that appears, and the PDF opens in their browser. Nothing to install.

### Can I see how many people scanned the QR code?

Yes. Scans are recorded as their own source in your readership report, and once the document opens you also see page-by-page reading time and a read-through funnel, all without storing reader IP addresses.

### Can I change the PDF after printing the QR code?

Yes. The QR code encodes the EveryPage share link, not the file, so on Pro you can replace the PDF behind the link and every printed code serves the new version on the next scan - the short link, password, gates, and settings all persist. On every plan you can also set a password, turn downloads on or off, or schedule the link to expire without changing the printed code.

### Is it free?

Yes. You can upload a PDF and get its QR code without creating an account; anonymous uploads are shareable immediately and kept for 7 days. The free plan covers up to 3 PDFs, and links never expire unless you set an expiry. Replacing the file behind a link is a Pro feature.

## Make a trackable PDF QR code.

Upload a PDF, download its QR code, and see every scan and read roll in - no browser extensions, no reader IP storage.

Related: dynamic QR links - replace the PDF, keep the code · PDF read tracking · restaurant QR menus

---
URL: https://everypage.co/pdf-flipbook
Title: Convert PDF to Flipbook Free - Flipbook Maker | EveryPage
Description: Turn a PDF into a page-turning flipbook free, no account needed: add your logo and background, put links and video inside the pages, and embed it anywhere. Page-by-page readership is included on every link.

PDF flipbook

# Convert your PDF into a flipbook

Turn a PDF into a page-turning flipbook free, no account needed - styled with your logo and background, embeddable on your site, with page-by-page readership on the same link.

Drop your PDF here

or click anywhere in the tray to browse

PDF only · max 20MB

Free · no account needed to start · pick the flipbook viewer on the next step

View the live example

Drag a page corner, tap the edges, or use the arrow keys — this is the real viewer, not a video.

Same page-turn, other documents — tap a cover to swap

## A real page-turn, on any device

Drag pages with a finger or mouse and they curl around the spine in 3D. Zoom, fullscreen, and page thumbnails are built in - in any browser, nothing to install.

## Your brand, not ours

Set a background colour, gradient, or image; add your logo with a link back to your site; tune the page shadow, corners, and turn speed - with a live preview as you edit.

## Embed it on your website

Every flipbook comes with a copy-paste iframe embed. The embedded viewer is the full flipbook - page turns, your branding and hotspots included - and reads on your site are counted in your report like any other.

## Links & video inside the pages

Draw hotspots on any page that open a link, jump to another page, or play YouTube, Vimeo, image, and audio content - an interactive flipbook, not just a pretty one.

## What is a PDF flipbook?

A PDF flipbook presents a PDF as a digital book or magazine: instead of scrolling a flat document, the reader turns pages that curl and flip like paper. Converting a PDF into a flipbook suits anything laid out as pages meant to be leafed through - a catalogue, a lookbook, a brochure, a zine, an annual report. The format signals "made to be read," which is why brands reach for it over a raw PDF download.

EveryPage renders the flipbook in its own in-browser viewer, so there is nothing for the reader to install and no third-party player. And because every page turn happens inside that viewer, the reading is measurable in a way a downloaded PDF never is.

## How to convert a PDF into a flipbook

1. Upload your PDF. Drop it in the uploader above - no account needed to try it - and EveryPage hosts it as a shareable link.
2. Choose the flipbook view. Set the viewer mode to Flipbook (a 3D book) or Magazine (two-page spreads with the same page-turn). On phones both adapt to full-width single pages automatically.
3. Make it yours. Pick a background, add your logo, tune the page effects and turn speed, and draw link or video hotspots onto the pages - all with a live preview that saves as you go.
4. Share or embed it. Send the link, drop in the QR code, or copy the embed snippet to put the flipbook on your own website. You can even link readers straight to a specific page.
5. See who read it. Your readership report shows page-by-page reading, a read-through funnel, and which hotspots readers clicked.

## Is it free?

Yes. Upload a PDF without an account, pick the Flipbook viewer on the next step, and share the link - anonymous uploads are shareable immediately and kept for 7 days. The free plan covers up to 3 PDFs with core readership. Branding (background, logo, page effects) starts on Basic; link and video hotspots are Pro.

## Can I add my logo and change the background?

Yes, from the Basic plan. A converted PDF should look like your publication, not ours. The flipbook editor gives you a background of any colour, gradient, or uploaded image (with blur and darkening controls so the pages stay legible), your logo in any corner - linked back to your site - and page cosmetics from shadow depth to rounded corners and stacked paper edges.

Behaviour is yours to tune too: page-turn speed, an optional page-turn sound, right-to-left reading for Arabic, Hebrew, and Japanese documents, and whether the cover opens alone or paired like a calendar. Everything edits against a live preview and saves automatically - what you see is exactly what readers get.

## Can I put links, video and audio inside the flipbook?

Yes, on Pro. Hotspots turn a static catalogue into something readers can act on. Draw a rectangle over any part of a page and give it a job: open your order page, jump to the spec sheet on page 12, play a YouTube or Vimeo demo, open a full-size photo, or play an audio note.

Every hotspot tap is counted in your readership report, so you learn not just who read the flipbook but which call-to-action actually got clicked.

## Can I see who reads the flipbook?

Yes. Most flipbook makers stop at making the flipbook: you publish it, share it, and then you are back to guessing whether anyone opened the catalogue or got past the first spread. An EveryPage flipbook is a tracked link, so that question is answered.

EveryPage treats the flipbook as a tracked document. You see how far each reader got, which pages held attention and which were skimmed, whether the same reader came back, and where the read came from - link, QR scan, or embed. You get the same PDF tracking as any EveryPage link - a read-through funnel for your catalogue - without storing a single reader IP address.

## When a flipbook is the right format

- Catalogues & lookbooks: product ranges and collections meant to be browsed page by page.
- Brochures & magazines: marketing pieces, zines, and issues laid out as facing pages.
- Reports & portfolios: annual reports, case studies, and folios where presentation matters.

## Turn the catalogue into a lead form

A lookbook or price list is exactly the document people will trade contact details for. On Pro, put a lead capture form in front of the flipbook - up to five fields, with the email validated server-side - and every reader lands in your dashboard as a contact, with their page-by-page reading attached: who browsed the whole collection, and who stopped at the cover.

## PDF flipbook questions.

### How do I convert a PDF into a flipbook?

Upload the PDF to EveryPage - no account needed to try it - and set the viewer mode to Flipbook or Magazine. Share the link and readers get a page-turning book that opens in any browser, with nothing to install and no software to convert with.

### Do readers need an app or plugin to view the flipbook?

No. The flipbook renders in the EveryPage viewer in the browser, on desktop and mobile - there is no app, no download, and no Flash. Readers just open the link, and on phones the flipbook adapts to a full-width single-page layout.

### Can I see who reads my flipbook?

Yes. Because the flipbook is an EveryPage link, you get page-by-page reading time, a read-through funnel, returning-reader detection, and hotspot click counts - all without storing reader IP addresses. That is the difference from a plain flipbook maker.

### Is it free to convert a PDF to a flipbook?

Yes - the free plan lets you convert up to 3 PDFs into shareable flipbooks with core readership. Paid plans add branding, interactive hotspots, the full charts, more storage, and reader identities.

### Can I add my logo and change the flipbook background?

Yes. On the Basic plan you can set a background colour, gradient, or image, add your logo in any corner with a link to your site, adjust page shadow and corners, and remove the EveryPage badge - all edited against a live preview.

### Can I embed the flipbook on my website?

Yes. Every flipbook comes with a copy-paste iframe embed code, and the embedded viewer is the full flipbook - page turns, your branding, and hotspots included - with reads still counted in your report.

### Can I put links or videos inside the flipbook?

Yes. On the Pro plan you can draw hotspots on any page that open a link, jump to another page, or play YouTube or Vimeo video, images, and audio - and every hotspot tap is counted in your readership report.

## Convert your PDF into a flipbook.

Upload a PDF, pick the flipbook viewer, style it like your brand, and share a page-turning link that tells you who actually read it.

Related: PDF magazine viewer · PDF story mode · make your PDF interactive · share it from your own domain · PDF read tracking

---
URL: https://everypage.co/pdf-magazine
Title: Turn a PDF Into a Digital Magazine - Free | EveryPage
Description: Turn a PDF into a digital magazine with page-turning spreads - free, no account needed to start. Zoom, fullscreen, right-to-left reading, embeds; readership on every issue.

PDF magazine

# Turn your PDF into a magazine

Turn a PDF into a digital magazine with page-turning spreads - free, no account needed to start. Flat-lay spreads around a centre spine, pages that turn like the printed issue, readable in any browser.

Drop your PDF here

or click anywhere in the tray to browse

PDF only · max 20MB

Free · no account needed to start · pick the magazine viewer on the next step

## A page-turn worthy of print

Spreads lie flat around a centre spine shadow, artwork edge to edge - and the leaf turns in real 3D. Drag it across, flick to commit, or tap the page edge: the same physics engine as our flipbook, dressed as an open issue.

## Zoom, fullscreen, thumbnails

Read close with the zoom buttons, Ctrl/Cmd+scroll, or a pinch - up to 3x, with panning. Go fullscreen (yes, on iPhone too), and jump anywhere from page thumbnails or a table of contents built from your PDF outline.

## Reads the way you published it

Right-to-left reading for Arabic, Hebrew, and Japanese titles, a cover that opens alone or paired like a calendar, your page-turn speed, and an optional page-flip sound - you set the house rules.

## See who read the issue

A magazine link is an EveryPage link: page-by-page reading time, a read-through funnel, and returning readers - without storing a single reader IP address.

## What is a PDF magazine viewer?

A PDF magazine viewer presents a PDF as facing-page spreads - the way magazines, lookbooks, catalogues, zines, and annual reports are actually designed. Instead of scrolling a flat file, the reader sees the open issue: left and right pages side by side around a centre spine, artwork running edge to edge, and a leaf that turns when they drag it.

EveryPage works as an online magazine maker for a PDF you already have: no re-layout, no export plugin, no reader app. Upload the print file, pick the magazine viewer, and the link opens in any browser. And an issue is a lasting thing - the link lives as long as you choose, indefinitely unless you set an expiry.

## How to make a digital magazine from a PDF

1. Upload your PDF. Drop it in the uploader above - no account needed to try it - and EveryPage hosts it as a shareable link.
2. Choose the magazine view. Set the viewer mode to Magazine and the file renders as two-page spreads with a real page-turn. All four viewer modes are free on every plan.
3. Set the reading rules (Basic and up). Page-turn speed, an optional page-flip sound, right-to-left reading, and whether the cover opens alone or paired - tuned against a live preview.
4. Share or embed it. Send the link, drop in the QR code, or copy the embed snippet to put the magazine on your own website.
5. Read the readership. Your report shows page-by-page reading time, a read-through funnel, and returning readers - which spreads held attention, and where the issue was put down.

## Is it free?

Yes. Upload a PDF without creating an account, set the viewer mode to Magazine, and share the link - anonymous uploads are shareable immediately and kept for 7 days. All four viewer modes, magazine included, are on every plan; the free plan covers up to 3 PDFs with core readership. Reading rules (turn speed, sound, direction, cover pairing) start on Basic; interactive hotspots and advanced branding are Pro.

## Magazine or flipbook - which one?

Both modes share the same 3D page-turn - drag, flick, or tap - so the choice is about dress. Magazine mode is the flat-lay: spreads sit flush around a centre spine shadow and the artwork runs edge to edge, the presentation for anything designed as facing pages. The flipbook viewer is the book: it adds backgrounds, your logo, and page cosmetics - shadow depth, rounded corners, stacked paper edges - plus a one-page/two-page layout toggle.

A fair rule of thumb: if the design is the hero, choose magazine; if the object should feel like a bound book in your brand, choose flipbook. Either way it is the same tracked link, and you can switch modes at any time without re-uploading.

## Does the magazine work on phones?

A two-page spread crushed onto a phone screen helps nobody. Below phone width the magazine switches to single-page reading automatically - one page at a time, full width, with the same drag, flick, and tap page turns. No settings, no second file, no "best viewed on desktop" apology.

The link is the same everywhere: a reader who opens your issue on the train gets a phone-shaped magazine, and the readership report records their pages just the same.

## Can I brand the magazine?

On Basic, the viewer takes your branding: a background colour, gradient, or image behind the spreads, your logo linked back to your site, and the reading behaviour - turn speed, sound, reading direction - set the way you want it.

On Pro, the pages themselves become interactive: draw hotspots that open a link, jump to another page, or play video and audio inside the issue - every tap counted in your readership report - and serve the whole thing from your own domain.

## PDF magazine questions.

### How do I turn a PDF into a digital magazine?

Upload the PDF to EveryPage - no account needed to try it - and set the viewer mode to Magazine. Share the link and readers get an online magazine with two-page spreads and a real page-turn, in any browser, nothing to install.

### Do the pages actually turn?

Yes. Drag a page and the leaf curls over the spread in 3D, flick to commit the turn, or tap the page edges - the same page-turn physics as the EveryPage flipbook, presented as a flat-lay magazine.

### Does the magazine work on phones?

Yes. On screens narrower than about 700px the magazine switches to single-page reading automatically, keeping the same drag, flick, and tap page turns - so phone readers get full-width pages instead of a shrunken spread.

### Can readers zoom in and read fullscreen?

Yes. Zoom runs from 1x to 3x with panning - via the toolbar buttons, Ctrl/Cmd+scroll, or a pinch - and fullscreen works across devices, including iPhone. Page thumbnails and a table of contents from the PDF outline handle navigation.

### Can I set right-to-left reading or keep the cover on its own?

Yes. Magazine mode honours your document settings: right-to-left reading for Arabic, Hebrew, and Japanese titles, a cover that opens alone or paired, page-turn speed, and an optional page-flip sound. These controls start on the Basic plan.

### Is the magazine viewer free?

Yes - all four viewer modes, magazine included, are available on every plan, including Free. Customisation (turn speed, sound, reading direction, cover pairing) starts on Basic; interactive hotspots and advanced branding are Pro.

### What's the difference between magazine mode and the flipbook?

They share the same page-turn. Magazine is the flat-lay presentation - spreads flush around a centre spine shadow, artwork edge to edge - while the flipbook adds book styling: backgrounds, page shadow and rounded corners, stacked paper edges, and a one-page/two-page layout toggle.

## Publish your PDF as a magazine.

Upload the issue, pick the magazine viewer, and share a link that turns like print - and tells you which spreads were read.

Related: PDF flipbook maker · PDF story mode · portfolios & lookbooks · PDF read tracking

---
URL: https://everypage.co/pdf-story
Title: Share a PDF That Reads Like a Story on a Phone | EveryPage
Description: Share a PDF that reads like a story on a phone - free, no account needed: fullscreen pages, tap or swipe to advance, pinch-to-zoom, one link. Page-by-page readership included.

PDF story mode

# Share a PDF that reads like a story on a phone

Share a PDF that opens fullscreen on a phone and swipes like a story - free, no account needed. Pick the swipe viewer and send one link: a segmented progress bar up top, a tap to advance, the reading grammar your audience already uses all day.

Drop your PDF here

or click anywhere in the tray to browse

PDF only · max 20MB

Free · no account needed to start · pick the swipe viewer on the next step

## Tap, swipe, progress bar

A segmented progress bar across the top - one segment per page. Tap the right side to go forward, the left to go back, or drag and flick between pages with a soft rubber-band at the ends. Nobody needs instructions; their thumbs already know.

## Fullscreen, with a real zoom

Pages fill the screen edge to edge, and fine print is never lost: pinch to zoom from 1x to 3x with panning, and pinch back out to return to the page. On a desktop, double-click jumps in and back out.

## Desktop keeps the feel

On a big screen the story becomes a centred portrait card with side arrows and a dimmed backdrop - the phone-story feel, without stretching your pages across a monitor.

## Switch modes any time

The same link can be shown as a story, a flipbook or a magazine - change the viewer mode without re-uploading. Readership carries across: page-by-page reading time, a read-through funnel, returning readers, and from Basic a re-read rate.

## What is PDF story mode?

Story mode - the EveryPage swipe viewer - presents each page of a PDF as a fullscreen card, advanced with a tap or a flick under a segmented progress bar. It borrows the presentation grammar of social stories because that is simply how people read on their phones now - but what you are sharing is still your document: the proposal, the one-pager, the lookbook, delivered as a link that opens perfectly from a tap in a chat, an email, or a QR scan.

That is the whole idea: meet readers where their thumbs are. A prospect who opens your one-pager on the train gets something built for the hand it is in - not a pinch-and-squint rendition of an A4 page - and the document itself remains a lasting artifact: the link lives as long as you choose, indefinitely unless you set an expiry.

## How do I share a PDF on a phone so it swipes like a story?

Upload the PDF, set the viewer mode to Swipe, and share the link. It opens fullscreen in the phone browser - one page per story card under a segmented progress bar; tap the right side for the next page and the left to go back, or drag and flick between pages. Nothing for the reader to install and no account to create, and the swipe viewer is free on every plan.

## How to share a PDF that reads like a story

1. Upload your PDF. Drop it in the uploader above - no account needed to try it - and EveryPage hosts it as a shareable link.
2. Choose the swipe viewer. Set the viewer mode to Swipe and every page becomes a fullscreen story card. All four viewer modes are free on every plan.
3. Add auto-advance if you want it (Basic and up). Pages can turn themselves at an interval you choose, from 3 to 30 seconds - readers press and hold to pause. It is off by default, so nothing moves unless you say so.
4. Share or embed it. Send the link, put the QR code on print, or copy the embed snippet to put the story on your own site.
5. Read the readership. Page-by-page reading time, a read-through funnel, returning readers - and from Basic, the re-read rate and your most re-read pages.

## Story, magazine, or flipbook?

Every viewer mode shares the same tracked link - the choice is presentation. Story mode is the phone-first one: single fullscreen pages, tap to advance, built for a document that will mostly be opened from a link tap on a phone. The magazine viewer is the flat-lay for artwork designed as facing-page spreads, and the flipbook is the bound book in your brand - both at their best on larger screens, and both adapt to single pages on phones.

A fair rule of thumb: if the design is the hero, choose magazine; if the object should feel like a book, choose flipbook; if most of your audience reads from their hand - a one-pager, a menu, a lookbook sent by chat - choose story. Either way you can switch modes at any time without re-uploading.

## What does it look like on a phone and on a desktop?

On a phone the story is fullscreen: the page fills the display, the progress bar sits along the top, and the tap zones are exactly where story-trained thumbs expect them. Drag and flick work too, with a rubber-band snap at the first and last page - and pinch-to-zoom for the detail.

On a desktop, EveryPage does not stretch a portrait page across a landscape monitor. The story renders as a centred portrait card with side arrows and a dimmed backdrop - the same reading rhythm, at the proportions it was designed around.

## Do watermarks, passwords and gates still work in story mode?

Yes. Story mode is a presentation, not a compromise: per-viewer watermarks, passwords and email gates, your branding, and readership analytics all carry through unchanged. Auto-advance (from Basic) behaves politely too - it waits while a reader holds the page or has a sheet open, and it stops at the last page rather than looping.

On Pro, your custom call-to-action appears as a story-style swipe-up sheet at the bottom of the screen, and interactive hotspots - video, audio, and images drawn onto your pages - open the same way: as bottom sheets that slide over the story and hand it back when closed.

## PDF story questions.

### How do I share a PDF on a phone?

Upload the PDF to EveryPage and set the viewer mode to Swipe. Share the link and it opens fullscreen in the phone browser, one page per story card, with a progress bar and tap-to-advance - nothing for the reader to install and no account to create.

### How do readers navigate a PDF story?

The way they navigate stories everywhere: tap the right side of the screen for the next page, the left to go back, or drag and flick between pages - with a soft rubber-band at the first and last page. A segmented bar across the top shows one segment per page, so readers always know where they are.

### Can readers zoom in?

Yes. Pinch to zoom from 1x to 3x with panning, and pinch back out to return to the page - on a desktop, double-click zooms in and back out. Fine print and detailed artwork stay readable without leaving the story.

### What is auto-advance and which plan has it?

Auto-advance turns the pages automatically at an interval you choose, from 3 to 30 seconds. It starts on the Basic plan and is off by default. Readers press and hold to pause, it waits while a call-to-action sheet or media is open, and it stops at the last page instead of looping.

### What does swipe mode look like on a desktop?

A centred portrait card with side arrows on a dimmed backdrop - the story presentation at phone proportions, rather than a portrait page stretched across a landscape screen. The tap zones, dragging, and progress bar all work the same.

### Is the swipe story viewer free?

Yes - all four viewer modes, swipe included, are available on every plan, including Free. Auto-advance starts on Basic; the swipe-up call-to-action sheet and media hotspots are Pro features.

### Does readership analytics work in story mode?

Fully - every page is timed and every visit recorded, exactly as in the other modes. Every page turn also records its direction, so from the Basic plan your dashboard shows a re-read rate and your most re-read pages: the ones readers went back to, which is where your stickiest content lives.

## Ship the story, keep the document.

Upload the PDF, pick the swipe viewer, and share a link that reads like a story on the phone - and reports back like an EveryPage link.

Related: PDF magazine viewer · PDF flipbook maker · restaurant menu QR codes · portfolios & lookbooks · PDF read tracking

---
URL: https://everypage.co/custom-domain
Title: Custom Domain PDF Sharing - White-Label Links | EveryPage
Description: Share PDFs from docs.yourcompany.com instead of everypage.co - a Pro feature, set up with a CNAME and a TXT record, HTTPS certificate issued automatically. Read tracking works the same on your domain.

Custom domain

# Share PDFs on your own domain

Share PDFs from your own domain (docs.yourcompany.com) instead of everypage.co - a Pro feature, set up with a CNAME and a TXT record. Connect your subdomain once and every share link, QR code, embed, and share email uses it.

Drop your PDF here

or click anywhere in the tray to browse

PDF only · max 20MB

Free to start · custom domains are a Pro feature · connect yours from Account settings

## Your brand, end to end

The link in the email, the address bar while reading, the QR code on print - all your domain. Pair it with your logo and background so nothing about the experience says third-party tool.

## Connected in minutes

Add your subdomain in Account settings and create two DNS records. The HTTPS certificate is issued and renewed automatically - there is nothing to install and no server to run.

## Tracking comes along

Links on your domain report the same page-by-page readership as any EveryPage link: reading time, the read-through funnel, returning readers, and hotspot clicks.

## Safe by design

Your domain serves your documents only - never another customer's - and it exposes just the viewer. Sign-in, billing, and account pages never appear on it.

## Why share documents from your own domain?

Trust, mostly. Recipients see where a link points before they click it, and spam filters, IT policies, and plain human caution all treat a familiar domain more kindly than a generic file-sharing URL. When the proposal, catalogue, or report is doing the selling, the domain it lives on is part of the pitch.

The other half is continuity. Your document opens under your name, styled with your background and logo, at an address you own. If you ever leave, the domain is still yours - a custom domain keeps your sharing history portable in a way a third-party URL never is.

## How do I set up a custom domain?

1. Pick a subdomain. Something like docs.yourcompany.com, share.yourcompany.com, or files.yourcompany.com - any subdomain of a domain you control.
2. Add it in Account settings. EveryPage shows you exactly two DNS records to create: a CNAME that routes the subdomain to us, and a TXT record that proves you own it.
3. Verify. One click checks the records. The HTTPS certificate is issued automatically within a couple of minutes - no certificate files, no renewals to remember.
4. Share as usual. From then on your share links, embed snippets, QR codes, and share emails are built on your domain. Existing everypage.co links keep working too.

## Does it need a certificate?

No - not one you manage. Once the CNAME and TXT records verify, the HTTPS certificate for your subdomain is issued automatically within a couple of minutes and renewed automatically after that. There are no certificate files to upload, no server or plugin to run, and no renewal dates to remember; every link on your domain is served over HTTPS from the start.

## What changes on a custom domain - and what stays the same?

Everything a reader touches moves to your domain: the link itself, the in-browser viewer with your flipbook styling, the embed on your website, the QR code on your print run. Everything you rely on stays put: readership analytics, password protection, the email gate, expiry - the link is fully yours on the surface and fully tracked underneath.

If you remove the domain (or your plan lapses), links fall back to everypage.co behaviour and your documents stay safe - the domain simply stops serving until it is reconnected.

## Custom domain questions.

### How do I share a PDF from my own domain?

On the EveryPage Pro plan: add a subdomain like docs.yourcompany.com in Account settings, create the CNAME and TXT records it shows you, and click Verify. Every share link, QR code, embed, and share email then uses your domain automatically.

### Do I need to host anything or manage an SSL certificate?

No. Your DNS points the subdomain at EveryPage and the HTTPS certificate is issued and renewed automatically. There is no server, plugin, or certificate file on your side.

### Can I use my root domain, like yourcompany.com?

Subdomains only - docs.yourcompany.com works, yourcompany.com does not. Root domains cannot point at a service by CNAME, and you almost certainly want your main site to stay where it is.

### Does read tracking still work on a custom domain?

Yes, identically. Page-by-page reading time, the read-through funnel, returning readers, source attribution, and hotspot clicks are all recorded exactly as they are on everypage.co links.

### Which plan includes custom domains?

Pro ($29/month, or $290/year). One domain per account, and you can change or remove it at any time.

### Can visitors tell EveryPage is behind it?

The viewer runs on your domain with your background and logo, and paid plans can remove the "Made with EveryPage" badge - so the reading experience is fully yours.

## Put your documents on your domain.

Upgrade to Pro, connect docs.yourcompany.com in a few minutes, and send links that look like they came from you - because they did.

Related: convert your PDF into a flipbook · make your PDF interactive · PDF read tracking · branded PDF viewer

---
URL: https://everypage.co/interactive-pdf
Title: Make a PDF Interactive - Links, Video & Audio | EveryPage
Description: Add clickable links, video and hotspots to a PDF online without Acrobat: upload free with no account, draw hotspots in the browser, and share one link. Hotspots are a Pro feature; every click is counted.

Interactive PDF

# Make your PDF interactive

Add clickable links, video and hotspots to a PDF online - upload free with no account, draw the hotspots in the browser, and share one link that works on every device. Hotspots are a Pro feature, and every click is counted in your readership report.

Drop your PDF here

or click anywhere in the tray to browse

PDF only · max 20MB

Free · no account needed to start · draw hotspots in the editor after upload

## Draw it on, no Acrobat

Drag a rectangle over any part of a page and give it a job. No desktop software, no re-exporting the PDF - the original file stays untouched and the hotspots live on top.

## Video inside the pages

A hotspot can play a YouTube or Vimeo video in a lightbox without the reader ever leaving the document - a product demo inside the catalogue page it belongs to.

## Jumps, images & audio

Send readers from the contents page straight to page 12, open a full-size photo, or play a narration clip. Five hotspot types cover most jobs a static PDF wishes it could do.

## Edit after sharing

Hotspots live in the viewer, not the file, so you can change a link after sending without re-sending anything. Every hotspot activation is counted in your readership report alongside page-by-page reading time.

## What is an interactive PDF?

A static PDF can only be read. An interactive one can be acted on: tap the product photo and a demo video plays, tap "order now" and the order page opens, tap an entry in the contents and the document jumps there. That difference matters most in documents built to drive an action - catalogues, brochures, media kits, proposals.

The traditional way to get there is desktop software and exported link annotations, with no way of knowing whether anyone ever clicked. EveryPage takes a different route: upload the PDF as-is, draw hotspots in the browser, and share a link. The interactivity lives in the viewer, works on every device, and reports back.

## How to add links and video to a PDF online

1. Upload your PDF. Drop it in the uploader above - the file itself is never modified, so there is nothing to re-export when you change a link later.
2. Draw a hotspot. Open the hotspot editor, drag a rectangle over the area readers should click - a button, a photo, a line in the table of contents.
3. Give it a job. Open a link, go to a page, play a YouTube/Vimeo video, show an image, or play audio. Everything saves as you go, against a live preview.
4. Share and watch the clicks. Share the link (or embed it, or use your own domain). Your readership report counts every hotspot activation alongside the page-by-page reading.

## How do I add a link to a PDF without Acrobat?

Upload the PDF to EveryPage, open the hotspot editor and drag a rectangle over the area readers should click - a button, a photo, a line in the contents. Give it a URL and it saves against a live preview. No desktop software, and the original file is never modified: the link lives in the shared viewer, works on any device, and can be changed later without re-exporting or re-sending. Uploading and sharing are free with no account; drawing hotspots is a Pro feature.

## Where are interactive PDFs used?

- Catalogues & price lists: every product links to its order page, and the click counts tell you which products pulled.
- Portfolios & media kits: case studies link to live sites, showreels play inline, and the contents page actually navigates.
- Proposals & reports: cite sources readers can open, link the appendix from the summary, and see whether the pricing page got the clicks.

## Interactive PDF questions.

### How do I add a link to a PDF without Acrobat?

Upload the PDF to EveryPage and draw a hotspot over the area readers should click - no desktop software, and the original file is never modified. The link works in the shared viewer on any device.

### Can I embed a YouTube or Vimeo video in a PDF?

Yes. Draw a hotspot, paste the YouTube or Vimeo URL, and readers get the video in a lightbox without leaving the document. Uploaded audio clips and full-size images work the same way.

### Do readers need an app or plugin?

No. Hotspots work in the EveryPage viewer in any browser, on desktop and mobile, in every viewer mode - including the flipbook and embeds on your own website.

### Are hotspot clicks tracked?

Yes. Every activation is counted per hotspot in your readership report, next to page-by-page reading time - so you can see which call-to-action actually got clicked, without any reader IP addresses being stored.

### Which plan includes interactive hotspots?

Hotspots are a Pro feature ($29/month). Flipbook branding - backgrounds, logo, page effects - starts on Basic ($9/month), and the viewer itself is free.

### Does the interactivity survive downloading the PDF?

Hotspots live in the shared viewer, not in the file, so the downloaded PDF is your untouched original. If clicks matter, share the link - which also means you can edit hotspots after sending without re-sending anything.

### Is it free to make a PDF interactive?

Uploading and sharing the PDF is free and needs no account - anonymous uploads are kept for 7 days. Drawing hotspots is a Pro feature ($29/month), so the free plan gives you the shared viewer and the link; Pro adds the link, video, image and audio hotspots on top.

## Give your PDF something to click.

Upload a document, draw your first hotspot, and share a link that turns readers into clicks you can count.

Related: convert your PDF into a flipbook · share it from your own domain · PDF read tracking

---
URL: https://everypage.co/share-pdf-with-analytics
Title: Share a PDF With Analytics - See Who Reads It | EveryPage
Description: Share a PDF with analytics built in: page-by-page reads, a read-through funnel, returning readers. No Google Analytics setup - upload, share, done.

Share PDF with analytics

# Share a PDF with analytics built in

Send one link instead of an attachment - free, no account needed - and the analytics come with it: who opened your PDF, how far they read, which pages held attention, and who came back.

Drop your PDF here

or click anywhere in the tray to browse

PDF only · max 20MB

Free · no account needed to start · your share link and analytics come on the next step

## Page-by-page reads

The EveryPage viewer times every page. See which sections held attention and which got skimmed - detail an email attachment can never send back.

## The read-through funnel

The percentage of readers who reached each page. If everyone stops at the pricing table, the funnel points at exactly that page.

## Returning readers

Each reader gets a stable pseudonymous identity, so a prospect who comes back to your proposal three times shows up as one interested reader - not three anonymous views. From Basic, a re-read rate shows the pages they went back to.

## Zero setup

No Google Analytics, no tag manager, no pixel. Upload the PDF, share the link, and the report starts filling in on its own.

## The report you get for every share.

## What sharing a PDF with analytics gets you

When you email a PDF as an attachment, it goes dark the moment you press send: you cannot tell whether it was opened, skimmed, read to the end, or forwarded around a team. Sharing the same document as an EveryPage link keeps a thread back to it. The viewer times every page, so instead of a delivery receipt you get answers: twelve people opened the proposal, most spent two minutes on the case study, and half stopped at the pricing page.

That last part - where readers stop - is the read-through funnel, and it is the difference between analytics and a view counter. Add returning-reader signals (the same prospect coming back to page six twice is worth a phone call) and source attribution for links, QR scans, emails, and embeds, and a shared document starts telling you what to do next. The full detail of what gets measured is on the PDF tracking page.

## Embed the PDF on your website - and keep the analytics

Sharing does not have to mean sending. Every document comes with an embeddable viewer: copy the snippet, paste it into your site - a WordPress page, a landing page, a documentation hub - and the PDF renders right there on your page. A catalogue, a whitepaper, a case study, or a menu can live on your website for as long as you want it there.

The embedded viewer is the same viewer that does the measuring, so an embed is never a dead iframe: page-by-page time, the funnel, and returning readers all keep working, and embedded reads are attributed as their own source next to direct links, emails, and QR scans. For the step-by-step walkthrough, see the guide to embedding a tracked PDF on your website.

## Reader analytics without setting up Google Analytics

1. Upload your PDF. Drop it in the uploader above - no account needed to try it. EveryPage stores it encrypted and gives you a share link, a QR code, and an embed snippet.
2. Share it your way. Paste the link into an email or a DM, embed the viewer on your website, or print the QR code.
3. Watch the analytics appear. The readership report fills in as people read - no tracking code to install, no events to define, no dashboard to build.

If you have ever put off measuring a document because it meant wiring up Google Analytics, a tag manager, or a tracking pixel, this is the whole appeal: the analytics are a property of the link itself. Drag, drop, share - done. Start free and upgrade when you want deeper reporting; plans are on the pricing page.

## Is it free?

Yes. The free plan is $0: upload up to three PDFs (20MB each), share them, and get core readership summaries for every document. You do not even need an account to start - an upload made without one is shareable straight away and kept for 7 days. Basic ($9/month) adds the read-through funnel, per-page stats, and source breakdowns; Pro adds reader-level sessions, the email gate, and CSV export.

## Analytics without surveillance

Measurement this useful usually comes at readers' expense; EveryPage's deliberately does not. Reader IP addresses are never stored - each visitor becomes a stable pseudonymous identity via a one-way hash, the country is derived in flight, and the address is discarded. There are no third-party scripts in the viewer and no cross-site tracking, and your documents are encrypted at rest. You learn how your document was read; your readers are not followed around the internet for opening it.

## Sharing a PDF with analytics - questions.

### How much does it cost to share a PDF with analytics?

The free tier is $0: upload up to three PDFs (20MB each), share them, and get core readership summaries for every document. Basic is $9/month and adds the read-through funnel, trends, per-page stats, source breakdowns, larger files (200MB), password protection, and view notifications. Pro adds reader-level sessions, the email gate, CSV export, and live presence. Every plan records reading in full detail from the first visit, so upgrading later reveals the history you already collected.

### How do I share a PDF with analytics?

Upload the PDF to EveryPage and send the share link it gives you instead of attaching the file. Anyone who opens the link reads the document in EveryPage's in-browser viewer, and the viewer does the measuring: every page turn is timed, visits are attributed to their source, and returning readers are recognised. Your readership report updates as people read. There is nothing to configure - no tracking code and no analytics account - and your readers do not need to install or sign up for anything.

### Can I embed a PDF on my website and still get analytics?

Yes. Every link comes with an embed snippet - paste it into any page, WordPress post, or landing page and the document renders in the viewer right on your site. Because the embedded viewer is the same one that measures reading, you still get page-by-page time, the read-through funnel, and returning readers, and embedded reads are attributed as their own source so you can compare the embed against the direct link or the QR code.

### Do I need Google Analytics or a tracking pixel?

No. The measurement happens inside EveryPage's document viewer, not on your website, so there is no snippet to install, no tag manager to configure, and no events to define. That also means nothing new for your own site's cookie banner: EveryPage's readership measurement is first-party to the document, uses no third-party trackers, and never stores a reader's IP address.

### Is it fair to my readers to measure a PDF like this?

EveryPage is built so the answer is yes. Readers are identified by a stable pseudonymous label like "Reader #214", never by IP address - visitor IPs are never stored, and the country is derived in flight before the address is discarded. There are no third-party scripts and nothing follows a reader across the web; measurement happens only inside the document they chose to open. If you need names, the optional email gate asks readers to sign in openly before the document opens, so identification is explicit rather than covert.

### Do I need an account to share a PDF with analytics?

No. An upload made without an account is shareable immediately and kept for 7 days. A free account is what puts the document in your library and the analytics in front of you.

### Do readers need an account?

No. A reader clicks your link (or scans your QR code, or opens the embed on your site) and the PDF opens in their browser - phone, tablet, or desktop. There is nothing to install and no account to create on their side.

## Share a PDF and see what happens to it.

Upload a document, send one link, and get page-by-page analytics from the first read - free to start, nothing for your readers to install.

---
URL: https://everypage.co/pdf-comments
Title: PDF Comments - Collect Feedback on Shared PDFs | EveryPage
Description: Collect feedback on any PDF you share: readers comment without an account - privately to you or publicly - and you moderate everything.

Reader comments

# Collect comments and feedback, right on the PDF

Turn on reader comments and everyone you share with can respond on the document itself - privately to you or publicly to every viewer, with no reader account required. A Pro feature: only the document owner needs a plan.

## Private or public - per comment

Every commenter chooses: send feedback only you can see, or post it publicly for every viewer. Sign-off notes stay between you; testimonials go on the record.

## No accounts for readers

Anyone with the link can comment - anonymously, or signed with an optional name. There is no sign-up wall between you and the feedback you asked for.

## You moderate everything

Hide or delete any comment, flip one between public and private, or force private-only for the whole document so nothing is ever shown to other readers.

## Know the moment feedback lands

EveryPage emails you when new feedback arrives, so a client's sign-off or a reader's question never sits unnoticed on a link you shared last week.

## What are reader comments on a PDF?

Reader comments let the people you share a PDF with respond on the document itself, instead of scattering feedback across email threads, chat messages, and annotated copies. You share one link; readers open it in the EveryPage viewer and leave their feedback right there - anonymously or with a name, and with no account to create. Every response stays attached to the document it is about, where you will actually find it again.

Comments complete the picture that PDF read tracking starts. Readership tells you a client reached page 9 and stopped; a comment tells you why. Together they turn "did they read it?" into "what did they think?"

## Private to you, or public to every reader

Every comment carries a visibility the commenter chooses: private, seen only by you as the document owner, or public, shown to everyone who opens the link. A client can flag a pricing concern without broadcasting it; a happy reader can leave a testimonial where the next reader will see it. The same document supports both at once.

You set the rules per document. Turn feedback on only where you want it, or force private-only so the comment box becomes a direct line to you and nothing is ever shown to other viewers - the right setting for confidential proposals and early drafts.

## Sign-off, reactions, and testimonials

The obvious use is client sign-off: send a proposal, and the approval or the objection arrives attached to the proposal itself instead of as a "looks good" buried three replies deep in an email thread. The same mechanism covers reader reactions on a pitch deck, private feedback on a draft before it goes wide, and public Q&A or testimonials on a published document.

Comments also pair well with interactive PDFs - a lookbook with clickable hotspots and a public comment thread reads less like a file you sent and more like a page you published.

## How reader comments work

Feedback is enabled per document, so nothing changes on the links you have already shared until you say so. Once it is on, readers see a comment box in the viewer: they write their note, optionally sign it with a name, and choose private or public - unless you have forced private-only. You get an email as new feedback arrives, and the moderation controls stay with you: hide, unhide, delete, or switch any comment between public and private.

Reader comments are part of the Pro plan, alongside reader identities, email capture, interactive hotspots, and a custom domain. Your readers never need a plan - or an account - at all.

## Is it free?

Uploading and sharing a PDF on EveryPage is free. Reader comments are a Pro feature: the document owner needs a Pro plan ($29/month, or $24/month billed annually) to turn them on. Readers never pay anything - they open the link and comment.

## Do readers need an account to comment?

No. Readers comment straight from the shared link with no sign-up and no sign-in. Comments are anonymous by default, and a reader can optionally sign one with a name. The only account involved is yours, as the document owner.

## PDF comment questions.

### How do I collect feedback on a PDF?

Upload the PDF to EveryPage, enable reader comments in the document settings, and share the link. Anyone who opens it can leave feedback in the viewer - no account needed - and you get an email when new comments arrive. Reader comments are a Pro feature.

### Do readers need an account to comment?

No. Commenters are anonymous by default and can optionally sign a comment with their name. There is no sign-up step, so a client or reader can respond the moment they finish reading.

### Who can see the comments on my document?

The commenter chooses per comment: a private comment is visible only to you as the document owner, and a public comment is shown to every viewer of the document. As the owner you see everything, and you can force a document to private-only so no comment is ever shown to other readers.

### Can I moderate or remove comments?

Yes. You can hide or unhide any comment, delete it outright, or switch it between public and private at any time. Feedback is enabled per document, so you can also turn it off entirely for any link.

### Which plan includes reader comments?

Reader comments are part of the Pro plan ($29/month, or $24/month billed annually). Only the document owner needs Pro - readers never need a plan or an account to comment.

### Is it free to collect comments on a PDF?

Uploading and sharing a PDF is free, but turning on reader comments requires a Pro plan ($29/month, or $24/month billed annually) on the document owner's account. Readers never pay - they open the link and comment.

### Do commenters have to sign in or create an account?

No. There is no sign-up and no sign-in for readers. Comments are anonymous by default, with an optional name field, so anyone with the link can respond immediately.

## Feedback that stays with the document.

Stop excavating email threads for "any thoughts?". Turn on reader comments and collect sign-off, questions, and testimonials right where the reading happened.

---
URL: https://everypage.co/secure-pdf-sharing
Title: Secure PDF Sharing - Passwords & Read Receipts | EveryPage
Description: Share a PDF securely: password protection, an email gate, print blocking, screenshot deterrence, and read receipts - on one encrypted link.

Secure PDF sharing

# Share PDFs securely, on your terms

Free to start, no account needed. Password-protect a document, gate it behind an email, block right-click and printing, blur it against screenshots, and get a receipt when it lands - all on one link you stay in control of.

Drop your PDF here

or click anywhere in the tray to browse

PDF only · max 20MB

Free · no account needed to start · protection settings come on the next step

## Password protection

Put the document under seal. Readers enter the password once; verification happens server-side and the password never appears in any URL. Available from the Basic plan.

## The email gate

Require readers to sign the register before the document opens - enforced on the server, so a made-up address does not pass, and every session is attributed by name. A Pro feature.

## Right-click, print & copy blocking

One toggle disables right-click saving, printing, and text copying in the viewer, so a confidential proposal is read on the page - not quietly copied off it. From Basic.

## Read receipts

Readers can mark a document as received, and the confirmation lands in your readership report next to their session - proof of delivery, attached to proof of reading. From Basic.

## What makes a shared PDF secure?

An email attachment has no security at all: the moment you press send, the file can be opened by anyone, forwarded anywhere, and kept forever - and you will never know. Sharing the same document as a controlled link changes who holds the keys. The file stays on the server, encrypted at rest, and every protection is applied at the moment of reading: you decide who gets in (a password, an email gate), what they can do there (download, print, copy), and how long the link stays live.

Because the protections live on the link rather than inside the file, you can change your mind after sending. Tighten a document that travelled further than you expected, add a password to a link that is already out in the world, or expire it early - without recalling anything.

## The protection toolkit

- Password protection (Basic). Readers enter a password before the document opens. Verified server-side, never carried in a URL.
- Email gate (Pro). The document refuses to open until the reader signs in with a working email address - so your readership report shows names, not just numbers.
- Right-click, print & copy blocking (Basic). Disable the context menu, printing, and text selection in the viewer with one per-document toggle. Pairs with download control, which hides the download button entirely.
- Screenshot deterrence (Pro). The pages blur the moment the viewer window loses focus or a capture shortcut is pressed. It deters casual screenshots - no tool can make a screen truly unrecordable, and we will not pretend otherwise.
- Read receipts (Basic). Readers mark the document as received, and the confirmation is recorded with their reading session - delivery and readership on one report.
- Per-viewer watermarking (Pro). A tiled overlay carries each viewer's identity and a timestamp across every page, and downloaded copies are permanently stamped - so a leaked copy points back to its source. Full detail on the PDF watermarking page.
- Self-destructing links (Basic). The link deletes itself after a set number of views - or on a schedule - while your readership record of every read survives the burn. See self-destructing links.
- Domain allowlist (Pro). Tighten the email gate to specific domains, so only readers with an @yourclient.com address get past it - the right scope for partner decks and client-only material.

## Honest security: deterrence, not DRM

A reader's screen has to display the pages for them to be read, which means no viewer - ours included - can make a document impossible to capture. What the protections do is raise the cost of casual copying: the file cannot be saved with a right click, printed to PDF, or copy-pasted, and on Pro the pages blur whenever the window loses focus. A determined attacker can always photograph a screen; honest readers are kept honest, and your readership report tells you exactly who was on the page.

The rest of the security is the quiet kind: files encrypted at rest with AES-256-GCM in a tamper-evident format, per-account encryption keys, expiry you control - from an hour to never - and no reader IP address ever stored. Protection on the surface, encryption underneath.

## Is it free?

Yes. Upload a PDF without creating an account and share the link straight away - anonymous uploads are kept for 7 days, and the free plan covers up to 3 PDFs with core readership. Every plan stores files encrypted, lets you turn downloads off per document, and lets you set any timed expiry - or none at all. Password protection, right-click/print/copy blocking, read receipts, and self-destructing links start on Basic ($9/month); the email gate, screenshot deterrence, and per-viewer watermarking are Pro ($29/month).

Prefer a walkthrough?

Our guide compares every way to send a PDF securely - file passwords, email encryption, cloud links, and tracked links - with honest tradeoffs and steps for each.

## Secure PDF sharing questions.

### How do I share a PDF securely?

Upload it to EveryPage and share the link instead of attaching the file. Then set your protections per document: a password, an email gate, right-click and print blocking, screenshot deterrence, download control, and an expiry date. The file is stored encrypted, and you can tighten or revoke access at any time - even after the link has been sent.

### Can I stop people from downloading or printing my PDF?

Yes. Download control hides the download button and refuses direct download requests, and viewer protection additionally blocks right-click saving, printing, and text copying. Both are per-document toggles, and viewing in the browser keeps working normally.

### Can EveryPage prevent screenshots of my PDF?

No tool can truly prevent screenshots - a screen that displays a page can always be photographed. What EveryPage offers is screenshot deterrence, a Pro feature: the pages blur the moment the viewer window loses focus, which stops casual capture without pretending to be DRM.

### How do read receipts work?

With read receipts enabled, readers can mark the document as received right in the viewer. The confirmation is recorded alongside their reading session in your readership report, so you get proof of delivery next to proof of reading. Available from the Basic plan.

### Is the file itself stored securely?

Yes. Files are encrypted at rest with AES-256-GCM in a tamper-evident chunked format, each account has its own encryption keys, and expired files are swept from disk within a minute. Reader IP addresses are never stored.

### Which plans include the security features?

Password protection, right-click/print/copy blocking, read receipts, and self-destructing links start on the Basic plan ($9/month). The email gate, its domain allowlist, screenshot deterrence, and per-viewer watermarking are Pro ($29/month). Every plan stores files encrypted and lets you expire links on your schedule.

### Is secure PDF sharing free?

Yes. You can upload a PDF and share it as an encrypted link without creating an account; anonymous uploads are kept for 7 days, and the free plan covers up to 3 PDFs. Download control and timed expiry are on every plan. Password protection, right-click/print/copy blocking, and read receipts start on Basic ($9/month); the email gate, screenshot deterrence, and per-viewer watermarking are Pro ($29/month).

### Do recipients need an account to open a protected PDF?

No. Recipients open the link in any browser, on any device, with nothing to install and no account to create. If you set a password they enter it once; if you enable the email gate they type their email address - and that is all. Every protection is enforced on the server as they read.

## Send it sealed.

Upload a PDF, set the rules - password, gate, blocking, expiry - and share one link you stay in control of, with a readership report to prove it landed.

Related: per-viewer watermarking · self-destructing links · PDF read tracking · share from your own domain · convert your PDF into a flipbook

---
URL: https://everypage.co/photo-proofing
Title: Photo Proofing: Send a Gallery, Get Picks Back | EveryPage
Description: Send clients a proofing gallery from a PDF contact sheet - they tap the photos they want, no account needed on their side. Pick/maybe/reject per page, annotations, CSV export; a Pro feature. Readership included.

Photo proofing & page marks

# Send a proofing gallery, get picks back

Send clients a proofing gallery from a PDF contact sheet - they tap the photos they want and you get the selection back, no account needed on their side. Each reviewer marks every page pick, maybe, or reject and can pin a comment to the exact spot; you get a per-page tally, a breakdown by reviewer, and a CSV of the selections. Proofing is a Pro feature.

Drop your PDF here

or click anywhere in the tray to browse

PDF only · max 20MB

Free to try · photo proofing & annotations are Pro features · reviewer and protection settings come on the next step

## Pick · maybe · reject

Every reviewer marks each page or photo with one tap - pick, maybe, or reject. No account, no download, no spreadsheet: the whole selection happens inside the gallery link.

## A tally you can act on

You see a running tally on every page - how many picks, maybes, and rejects it collected - and a breakdown of exactly which reviewer chose what, so a split decision is never a mystery.

## Box-and-comment annotations

A reviewer drags a box around the detail they mean and attaches a comment to it - "crop tighter here", "retouch this" - and you read every annotation grouped by page, tagged with who left it.

## Selections that persist

Each reviewer's picks are saved and waiting when they come back, so a client can proof across several sittings - and when you invited them by name, every selection carries that name.

## How does online photo proofing work?

You upload a PDF contact sheet - one image per page works best - and share a single link. Each reviewer opens it in the browser on any device and marks every page pick, maybe, or reject with one tap; no account, no download, no spreadsheet. Where they want a change, they drag a box around the detail and attach a comment to it. Your side is one report: a per-page tally, the reviewers behind each mark, every annotation grouped by page, and a CSV export of the whole round.

Because the marks are structured rather than typed, what comes back is an answer page by page - not "the third one from the top" in an email thread. Invite reviewers by email and every selection carries their name; a returning client finds their shortlist exactly where they left it.

## What you get on a proofing link

- Pick, maybe, reject - per page. One image per page works best: each page becomes a unit a reviewer can mark. Every mark updates a live per-page tally so you can watch the shortlist form.
- A breakdown by reviewer. You get more than a total - you see which reviewer chose pick, maybe, or reject on each page, so you can tell the art director from the client and act on the split.
- Named reviewers via invites. Send the gallery to a list and every set of picks arrives with a name attached rather than as anonymous marks - the same email-invite distribution that names your readers.
- Box-and-comment annotations. A reviewer drags a box around the detail and attaches a comment to it; you read them all grouped by page, tagged with who left each one - no account required of the reviewer.
- Selections that persist across visits. A reviewer's marks are saved to them, so proofing can span several sittings and pick up where they left off - and a returning client sees their own shortlist intact.
- Export the selections to CSV. Pull the whole round out as a CSV - every page, every reviewer, every pick/maybe/reject - to hand to the retoucher, the printer, or your own records.
- Watermark and self-destruct the preview. Client previews are proofs, not deliverables: per-viewer watermarking names every page per reviewer, and a self-destructing link lets the whole gallery expire on a view budget or a date once the selection is made.

## What do I see as the owner?

Your side of a proofing gallery is a single report. Each page shows its pick/maybe/reject tally and, expanded, the individual reviewers behind those marks; each annotation sits under the page it belongs to with the box preserved and the commenter named. The shortlist is whatever you filter to - every page a majority picked, everything one specific client rejected - and the CSV export hands the same data to whoever does the next step.

And because an EveryPage link is tracked underneath all of it, the selection sits on top of full readership: you know the gallery was opened, which frames held attention longest, and whether a reviewer came back for a second pass before committing - usually the sign a decision is close. None of it stores a reviewer's IP address.

## Do clients need an account to pick their photos?

No. A reviewer opens the gallery link and marks pages straight away - there is nothing to sign up for, nothing to install, and nothing to download. Their picks, maybes, rejects, and annotations are saved to them so they can come back later, and if you invited them by email their name is already attached to every mark.

## Is it free?

No - photo proofing is a Pro feature, though trying EveryPage is free. You can upload a PDF and share it without creating an account (anonymous uploads are kept for 7 days, and the free plan covers up to 3 PDFs with core readership). The pick/maybe/reject marks, the per-reviewer breakdown, CSV export, and box-and-comment annotations are on Pro ($29/month).

## Photo proofing questions.

### How do reviewers mark their picks?

Open the gallery link and each page carries pick, maybe, and reject controls - one tap marks the page, and the mark is saved to that reviewer. There is no account to create and nothing to download; the whole selection happens inside the shared link, on any device.

### Can I see who picked what, not just a total?

Yes. Every page shows a tally of picks, maybes, and rejects, and you can expand it to a per-reviewer breakdown - which named reviewer chose what. When you invited reviewers by email, each set of marks carries their name instead of being anonymous.

### How do annotations work?

A reviewer drags a box around the exact area they mean and attaches a comment to it. In your report the annotations are grouped by page, each showing the box and the name of whoever left it - so feedback lands on the precise spot rather than in a paragraph of description.

### Do a reviewer’s selections survive if they come back later?

Yes. Each reviewer’s picks, maybes, rejects, and annotations are saved to them and restored on their next visit, so a client can proof a large gallery across several sittings without losing their place or starting over.

### Can I export the selections?

Yes. Export the whole round to CSV - every page against every reviewer with their pick/maybe/reject mark - to pass to a retoucher or printer, or to keep as a record of what was chosen and by whom.

### Which plan includes photo proofing and annotations?

Photo proofing (pick/maybe/reject page marks with the per-reviewer breakdown and CSV export) and box-and-comment annotations are both Pro features ($29/month). Watermarking and self-destructing previews that pair naturally with a client proofing round are also on Pro; every plan stores files encrypted and lets you expire links on your schedule.

### Do clients need an account to pick their photos?

No. Reviewers open the gallery link and mark pages pick, maybe, or reject straight away - no sign-up, nothing to install or download. Their selections are saved to them for later visits, and reviewers you invited by email are named automatically.

### Is photo proofing free?

Proofing itself is a Pro feature ($29/month); uploading and sharing a PDF is free and needs no account. The free plan covers up to 3 PDFs with core readership; Pro adds the pick/maybe/reject marks, the per-reviewer breakdown, CSV export, and annotations.

## Send the next round as a link.

Upload a PDF of your selects, invite your reviewers by name, and get the picks - and the annotations - back in one report.

Related: photography proofing use case · portfolios & lookbooks · send to a list of reviewers · per-viewer watermarking · self-destructing links · reader comments

---
URL: https://everypage.co/self-destructing-links
Title: Self-Destructing PDF Links - Set a View Budget | EveryPage
Description: Share a PDF on a link that deletes itself after a set number of views - or on a schedule you pick - with your readership record kept.

Self-destructing links

# Share a PDF that disappears after reading

Upload free, no account needed, and give the link a view budget or a deadline so it deletes itself on cue. Timed expiry is on every plan; expire-by-views starts on Basic. The document disappears; your record of who read it survives.

Drop your PDF here

or click anywhere in the tray to browse

PDF only · max 20MB

Free to try · self-destructing links start on the Basic plan · expiry settings come on the next step

## Expire by views

Set a view budget - one view, five, fifty. When it is spent, the link stops resolving and the encrypted file is deleted from disk. Available from the Basic plan.

## Expire by time

Prefer a deadline? Every plan can set a lifetime - an hour, a day, a year, any date - or keep a link forever. The link dies on schedule whether or not anyone opened it.

## The record survives the burn

Most burn-after-reading tools take the evidence with them. When an EveryPage link self-destructs, your readership record - who read it, how far, for how long - stays in your dashboard.

## Change your mind after sending

Tighten the view budget, shorten the timer, or expire the link on the spot - even after it is out in the world. Nothing to recall, nothing to apologise for.

## What is a self-destructing link?

A self-destructing link is a document link that removes itself once it has done its job - after a set number of views, or at a set time. Instead of a file that lives on indefinitely in inboxes and download folders, you share a link with a built-in ending: the recipient opens the document, reads it in the browser, and when the budget is spent or the clock runs out, the link returns "Gone" and the encrypted file is swept from disk within the minute.

That matters for anything you want read but not kept in circulation: a quote that should not resurface after the deal closes, a board paper that was for one meeting, a salary letter meant for exactly one pair of eyes. An email attachment can never be un-sent; a self-destructing link can.

## Two ways to expire - views and time

- Expire by views (Basic). Choose how many views the link is good for. One view makes it a true one-time link for one-time delivery; a larger budget suits a small, known audience. When the count is reached, the document deletes itself.
- Expire by time (every plan). Set a lifetime - an hour, a day, a year - and the link dies on schedule. Set none and the link stays up indefinitely on every plan, because documents are not inherently short-lived: expiry is a control, not a default.
- Combine both. Set a view budget and a deadline together and the link expires at whichever comes first - five views or five days, whichever the document hits.
- Expire on demand. Any link can be expired manually at any moment, so "please disregard that document" becomes a button rather than a request.

## The link burns - the ledger doesn't

Here is the part most self-destructing tools get wrong: they destroy your proof along with the document. EveryPage deliberately separates the two. When a link burns, the file is gone for good - but your readership record survives: every session, the page-by-page reading time, the read-through funnel, and any captured emails stay in your dashboard.

So you can send a confidential quote on a one-view link and still answer the questions that matter afterwards - did they open it, did they reach the number, did they come back before it burned? It is the same PDF read tracking as any EveryPage link; the only thing that disappears is the document.

## Is it free?

Uploading and sharing is free: upload a PDF without creating an account, set a lifetime on the next step and share the link - anonymous uploads are shareable immediately and kept for 7 days, and the free plan covers up to 3 PDFs with core readership. Timed expiry - or no expiry at all - is on every plan, including Free. Self-destruct by views (delete after 1, 5 or 50 reads) starts on the Basic plan ($9/month).

## When to use a self-destructing link

- Quotes & pricing - a quote that should not float around - or be forwarded to a competitor - after the decision is made.
- Confidential one-offs - board papers, legal drafts, HR and salary letters - read by the people they were meant for, then gone.
- One-time delivery - a deliverable handed over exactly once, with the readership record as your receipt.

## Self-destructing link questions.

### How do I make a PDF link that expires after one view?

Upload the PDF to EveryPage and set "delete after views" to 1 in the document settings. The first completed view spends the budget: the link stops resolving, the encrypted file is deleted from disk, and your readership record of that one read is kept. Self-destructing links are available from the Basic plan.

### What happens when the view limit is reached?

The link immediately returns "Gone" and the encrypted file is swept from disk within the minute. Nobody - including you - can retrieve the document afterwards, which is the point. Your readership record of every view before the burn stays in your dashboard.

### Do I lose my analytics when the document self-destructs?

No - this is the difference from most burn-after-reading tools. The document is destroyed; the readership record is not. Who opened it, how far they read, how long they spent per page, and any captured emails all remain in your report after the link is gone.

### Can I expire a link by time instead of views?

Yes - timed expiry is built into every plan - an hour, a day, a year, any date you choose - and a link with no expiry stays up indefinitely. You can set a view budget and a deadline on the same link, and it expires at whichever arrives first.

### Can I change or remove the self-destruct after sharing the link?

Yes, right up until it triggers. Raise or lower the view budget, change the expiry date, or expire the link immediately - the settings live on the link, not in the file, so nothing needs to be re-sent.

### Which plans include self-destructing links?

Expire-by-views starts on the Basic plan ($9/month). Timed expiry - or no expiry at all - is on every plan, including Free.

### Is it free?

Uploading and sharing is free and needs no account - anonymous uploads are kept for 7 days, and the free plan covers up to 3 PDFs with core readership. Timed expiry is included on every plan. Self-destruct by views starts on the Basic plan ($9/month).

### Does the recipient need an account?

No. The recipient opens the link and reads the document in the browser - no sign-up, no download, no app. Each completed view counts against the budget you set, and their read is recorded in your dashboard.

## Send it, then let it vanish.

Upload a PDF, give the link a view budget or a deadline, and share a document with a built-in ending - and a readership record that outlives it.

Related: secure PDF sharing · per-viewer watermarking · PDF read tracking

---
URL: https://everypage.co/pdf-watermarking
Title: PDF Watermarking - Per-Viewer Watermarks | EveryPage
Description: Watermark a PDF with each viewer’s email or reader ID and a timestamp - tiled on screen and stamped into every downloaded copy. Per-viewer watermarking is a Pro feature; a leaked page points back to its source.

Per-viewer watermarking

# A watermark that names the reader

Watermark a PDF with each viewer’s email or reader ID and a timestamp - tiled across every page on screen, and stamped permanently into any copy they download. Per-viewer watermarking is a Pro feature; uploading and sharing the PDF is free. A leaked page points straight back to its source.

Drop your PDF here

or click anywhere in the tray to browse

PDF only · max 20MB

Free to start · per-viewer watermarking is a Pro feature · protection settings come on the next step

## Tiled with the viewer's identity

The overlay repeats diagonally across every page: the viewer's email address - from the email gate or lead form - or their reader ID, plus the date and time. Awkward to crop, obvious in any photo of the screen.

## Downloads stamped for good

This is not a CSS overlay trick. If you allow downloading, the copy is watermarked by real PDF stamping - written into the file itself, so it survives re-saving, printing, and forwarding.

## Per viewer, not per document

Everyone sees the same document, but each copy carries its own name. Ten recipients means ten distinguishable copies - which is exactly what makes forwarding one of them a bad idea.

## What it can and cannot do

A watermark cannot make a leak impossible - nothing can. What it does is make every leak attributable, and documents that name their reader have a way of not leaking in the first place.

## How do I watermark a PDF with each viewer’s name or email?

Upload the PDF to EveryPage and turn on per-viewer watermarking in the document settings (Pro). You never prepare separate copies: one link serves everyone, and every page a viewer sees is tiled with their identity and the moment they viewed it. Documents leak when copies are anonymous - a PDF that looks the same on every screen costs nothing to forward. Per-viewer watermarking removes that anonymity, so passing a copy along means passing along your own name.

The identity comes from how the reader arrived. Behind the email gate or a lead capture form, the watermark carries their verified email address; otherwise it carries their stable pseudonymous reader ID, so even an anonymous session produces a traceable copy. Either way the timestamp pins down exactly which visit a stray page came from - and your readership report tells you who was on the page at that moment.

## What gets watermarked, and when?

- Pages on screen. A tiled overlay with the viewer's identity and viewing time renders across every page, in every viewer mode - standard, flipbook, swipe, and magazine. The reader cannot switch it off.
- Downloaded copies. If downloading is allowed, the file the viewer receives is stamped by real PDF stamping: the watermark becomes part of the page content itself, not a removable layer, and it travels with every subsequent copy.
- Printed pages. Because downloads are stamped into the file, anything printed from a stamped copy carries the watermark too.

## Does watermarking stop screenshots and copying?

Not by itself - no tool can. Watermarking covers the gap the other protections cannot: what happens after the pixels reach the screen. Right-click, print, and copy blocking stop casual saving; screenshot deterrence blurs the pages the moment the viewer window loses focus; watermarking makes whatever still gets captured attributable. Together they cover the document before, during, and after the read - the full toolkit is on the secure PDF sharing page.

The honest small print, as always: a screen that displays a page can be photographed, and no vendor can change that. The difference with a watermarked page is that the photograph names its photographer.

## Where is per-viewer watermarking used?

- Proposals & price lists - pricing that should not end up in front of a competitor - and identifies its route if it does.
- Manuscripts & pre-release content - drafts, embargoed reports, and launch material shared before the world is meant to see them.
- Investor & board material - decks and papers for a small, named audience, where each copy should answer for itself.

## PDF watermarking questions.

### How do I watermark a PDF for each viewer?

Upload the PDF to EveryPage and turn on per-viewer watermarking in the document settings - a Pro feature. From then on, every viewer sees the pages tiled with their own identity and a timestamp, and any copy they download is permanently stamped with the same mark. You never prepare separate copies; one link serves everyone.

### What identity does the watermark show?

The viewer's verified email address when the document sits behind the email gate or a lead capture form, or their stable pseudonymous reader ID otherwise - plus the date and time of the visit. Either way a stray copy can be matched to a specific reading session in your report.

### Can the watermark be removed?

The on-screen overlay is rendered by the viewer and cannot be disabled by the reader. Downloaded copies are stamped by real PDF stamping - the watermark is written into the page content, not layered on top, so it survives re-saving and printing. No watermark on earth is literally irremovable to a determined expert, but removing this one is real work, and the leak it came from is already attributable.

### Does watermarking stop screenshots?

No - and no tool can. What it does is make screenshots self-incriminating, since the capture includes the viewer's identity and timestamp. For capture itself, pair it with screenshot deterrence (also Pro), which blurs the pages whenever the viewer window loses focus.

### Does watermarking change the document I uploaded?

Never. Your original file is stored encrypted and untouched; the overlay is rendered at viewing time and download stamping is applied to the copy being served. Turn watermarking off and the document serves clean again.

### Which plan includes per-viewer watermarking?

Pro ($29/month, or $24/month billed annually) - alongside the email gate, screenshot deterrence, lead capture forms, and reader identities that make the watermark name a real person.

### Can I watermark a PDF for free?

Uploading and sharing a PDF is free and needs no account, but per-viewer watermarking itself is a Pro feature ($29/month). On the free plan the document serves clean; upgrade to Pro and turn watermarking on in the settings of the same link - no re-upload needed.

## Put a name on every copy.

Upload a PDF, switch on per-viewer watermarking, and share a link where every page - on screen or downloaded - answers for where it came from.

Related: secure PDF sharing · self-destructing links · PDF read tracking

---
URL: https://everypage.co/lead-capture-pdf
Title: PDF Lead Capture - Make Any PDF a Lead Magnet | EveryPage
Description: Put a custom form in front of any PDF - up to five fields - and collect every contact in your dashboard, with CSV export and a domain allowlist.

Lead capture

# Turn a shared PDF into a lead magnet

Upload a PDF free, no account needed, and share it as one link. Lead capture - a custom form of up to five fields in front of the document - is a Pro feature: every reader becomes a contact in your dashboard, with their page-by-page reading attached.

Drop your PDF here

or click anywhere in the tray to browse

PDF only · max 20MB

Free to start · lead capture forms are a Pro feature · gate settings come on the next step

## A gate form you design

Choose up to five fields - name, email, phone, company, or your own labels - and mark each required or optional. The email is validated server-side, so a made-up address does not pass.

## Leads with reading attached

Every captured contact lands in your readership dashboard next to their session - so you know not just who took the whitepaper, but who read it to the pricing page and who came back.

## B2B domain allowlist

Restrict viewing to specific email domains and the gate becomes a door: a partner deck only @yourclient.com can open, an internal doc only your own domain gets past.

## CSV export for your CRM

Export captured contacts together with their reading behaviour to CSV and feed your pipeline - the follow-up list writes itself, sorted by who actually read.

## How do I add a lead capture form to a PDF?

Upload the PDF to EveryPage and enable the lead capture form in the document settings - a Pro feature. Pick up to five fields (name, email, phone, company, or your own labels) and mark each required or optional. Anyone opening your link fills in the form before the document renders, and the contact lands in your readership dashboard with their reading session attached.

## Is it free?

Uploading and sharing a PDF is free and needs no account. Gating it - the lead capture form, the email-only gate, and the domain allowlist - is a Pro feature ($29/month, or $24/month billed annually). Your readers never pay and never need an account.

## What is a PDF lead magnet?

A lead magnet is a document worth trading contact details for - a whitepaper, a guide, a case study, a price list. The classic setup needs a landing page, a form builder, an email tool, and a file host stitched together. EveryPage collapses that: upload the PDF, switch on the gate form, and the link itself is the lead magnet - the form, the delivery, and the analytics in one URL you can share anywhere.

And because the document opens in the EveryPage viewer, the exchange keeps paying after the form: you see how far each lead actually read, which pages held them, and whether they returned - signals a download-and-goodbye funnel never captures.

## A form you shape to the ask

The gate form is yours to design, up to five fields. Ask for just a name and email when the document is light; add phone and company when the offer justifies it; use your own field labels when you need something specific. Each field can be required or optional, so you decide how much friction the document is worth.

The form appears before the first page renders, and the email address is validated on the server - the same enforcement as the email gate, so your contact list is made of addresses that work, not keyboard mashing.

## Qualify at the door: the domain allowlist

For B2B sharing you often do not want more leads - you want the right ones. The domain allowlist restricts viewing to email domains you choose: share a proposal that only @yourclient.com addresses can open, or a partner enablement pack limited to the three companies in the deal. Everyone else is politely refused at the gate.

Allowlisting works with the plain email gate too, not only the full form - so even a single-field "sign the register" gate can be scoped to the companies that matter.

## From reader to pipeline

Captured contacts appear in your readership dashboard attached to their reading sessions: name, email, company - and then pages read, time spent, return visits. That combination is the qualification step done for you. The lead who read all fourteen pages twice is not the same call as the one who bounced off page two.

Export the lot to CSV whenever you like and feed your CRM or mail tool. The reading detail comes from the same PDF read tracking every EveryPage link gets - the gate form just puts a name on it from page one.

## PDF lead capture questions.

### How do I add a lead capture form to a PDF?

Upload the PDF to EveryPage and enable the lead capture form in the document settings - a Pro feature. Pick up to five fields and mark them required or optional. Anyone opening your link fills in the form before the document renders, and the contact lands in your readership dashboard with their reading session attached.

### What fields can I ask for?

Up to five per document - name, email, phone, and company are the usual set, and you can label fields yourself for anything else. Email addresses are validated server-side, so invented addresses do not get through.

### Where do captured leads go?

Into your readership dashboard, attached to each contact's reading sessions - pages read, time spent, and return visits included. You can export everything to CSV for your CRM at any time.

### Can I restrict viewing to specific companies?

Yes - the domain allowlist limits viewing to email domains you choose, so a deck can be openable only by @yourclient.com addresses. It works with the full lead form or with the simple email gate.

### Do readers need an account to get the document?

No. They open your link, fill in the form in the browser, and read - nothing to install, no account to create. Only you need a plan.

### Which plan includes lead capture?

Lead capture forms and the domain allowlist are Pro features ($29/month, or $24/month billed annually). The simpler email-only gate is also Pro; core readership starts free.

### Is it free?

Uploading and sharing a PDF is free, with no account needed. Putting a lead capture form, email gate, or domain allowlist in front of it is a Pro feature ($29/month, or $24/month billed annually).

### Do readers need an EveryPage account to get through the gate?

No. Readers fill in the form in their browser and the document opens - no account, no sign-in, nothing to install. Only the person sharing the document needs a Pro plan.

## Make the document earn its keep.

Upload a PDF, put your form in front of it, and share one link that delivers the document, captures the contact, and reports the reading.

Related: PDF read tracking · send a PDF to a contact list · self-destructing links · per-viewer watermarking

---
URL: https://everypage.co/send-pdf-to-contacts
Title: Send a PDF to Your List - See Who Opened It | EveryPage
Description: Send a PDF to a list of contacts and see who opened it, by name: paste recipients or import a CSV and each person gets their own tracked link. Up to 10 per send on Basic; lists and CSV import on Pro.

Send to a list

# Send a PDF to your whole list - and see who opened it

Send a PDF to a list of contacts and see who opened it, by name - paste recipients or import a CSV, and each person gets their own tracked link. Basic covers direct sends of up to 10 recipients; saved distribution lists and CSV import are Pro. The report shows who opened it, how far they read, and who has not touched it yet.

Drop your PDF here

or click anywhere in the tray to browse

PDF only · max 20MB

Free to try · distribution lists are a Pro feature · add recipients on the next step

## One send, a named list

Paste or import your recipients and EveryPage emails each of them a link to the document. Your readership report shows the reads by name, not as a pile of anonymous views.

## A link per recipient

Every person on the list gets their own tracked link, so opens are attributed to a specific name from the first page turn - no email gate form for them to fill in first.

## Invited, not yet opened

The list shows the gap that matters for follow-up: who read it, and who was invited but has not opened it yet - so the nudge goes to exactly the right people.

## Import from a CSV

Bring a contact list straight in from a CSV - name and email, plus any columns you already keep - and send to the whole distribution list at once. A Pro feature.

## How do I send a PDF to a list and track who opens it?

Upload the PDF, add your recipients - paste them in, or import a CSV on Pro - and EveryPage emails each person their own tracked link. As they open it, your readership report fills in by name: who read it, how far they got, and who was invited but has not opened it yet. Compare that with an attachment, which goes dark the instant you press send - you cannot tell who opened it, who ignored it, or who forwarded it, and a delivery receipt is not a read.

This is per-recipient PDF read tracking: the same page-by-page readership every EveryPage link gets - reading time, a read-through funnel, returning readers - but attached to a name from the first visit, because you already know who each link went to. No reader has to sign anything before you learn who they are.

## How list distribution works

- Build the list. Paste recipients in, or import a contact list from a CSV on Pro. Basic covers small direct sends of up to 10 recipients at a time; Pro adds saved distribution lists and bulk CSV import.
- Each recipient gets their own link. EveryPage mints a separate tracked link per person and emails it out, so every open is tied to a specific name rather than a shared anonymous URL.
- Watch the list fill in. Your readership report lists recipients by name with their reading attached - opened or not, how far they read, how long they spent, and whether they came back.
- Skip the gate for invited readers. Because an invited recipient is already identified, the email gate lets them straight through - no form to fill in - while unknown visitors to the same document still sign the register.
- Or capture the ones you did not invite. Share the same document publicly as well and a lead capture form names the readers who were not on your list - the two channels land in one readership report.
- Name every copy. Turn on per-viewer watermarking and each recipient's identity is tiled across their pages and stamped into any download - so a leaked copy points straight back to the person on the list it was sent to.

## How are readers named without storing an IP?

Knowing who opened a document usually means either trusting a plain "delivered" receipt or wiring the reader up to trackers. EveryPage does neither. Recipients are named because you named them - the identity comes from the invitation, not from surveillance - and everyone else is still measured by a stable pseudonymous reader ID. No visitor IP address is ever stored, the country is derived in flight and discarded, and the measurement is first-party to your own document.

It is the same apparatus a sales team uses to send a deck to a prospect list, or a course to a cohort, or a brochure to a partner channel: one document, a list of people, and a report that answers "who read it?" with names - not a number, and not a guess.

## Which plan do I need?

Basic ($9/month) covers small direct sends of up to 10 recipients at a time, pasted in. Saved distribution lists and bulk CSV import are Pro ($29/month, or $24/month billed annually). Per-recipient reading - opened or not, how far, how long - is included on both.

## Sending a PDF to a list - questions.

### How do I send a PDF to a list of contacts and track who opens it?

Upload the PDF to EveryPage, add your recipients (paste them in, or import a CSV on Pro), and EveryPage emails each person their own tracked link. As they open the document, your readership report fills in by name: who read it, how far they got, and how long they spent - all without storing anyone's IP address.

### Can I import my contact list from a CSV?

Yes, on Pro. Import a distribution list from a CSV - name and email, plus any extra columns you keep - and send to everyone at once. On Basic you can still do small direct sends of up to 10 recipients at a time by pasting them in.

### Can I see who was invited but has not opened the PDF yet?

Yes - that is the point of sending to a named list. The report shows each recipient as opened or not opened, so you can see exactly who still needs a nudge alongside the readers who have already been through it.

### Does each recipient get their own link?

Yes. EveryPage mints a separate tracked link per recipient, so every open is attributed to a specific person from the first page turn rather than to a shared, anonymous URL that anyone could have opened.

### Do invited recipients still have to fill in the email gate form?

No. Because an invited recipient is already identified by their personal link, the email gate lets them through without a form. Anyone who reaches the document another way still signs the register, so you never lose an identity - and if watermarking is on, each recipient's identity is stamped onto their copy.

### Which plan do I need to send to a distribution list?

Saved distribution lists and bulk CSV import are Pro ($29/month, or $24/month billed annually). Basic ($9/month) covers small direct sends of up to 10 recipients per send. Core readership and per-recipient reading are included on both.

## Send it to the list, see who read it.

Upload a PDF, add your recipients or import a CSV, and turn a mailshot into a named readership report - opened, half-read, or still waiting for a nudge.

Related: PDF read tracking · turn a PDF into a lead magnet · per-viewer watermarking · send a sales deck · distribute course materials

---
URL: https://everypage.co/pdf-webhooks
Title: PDF Webhooks - Signed Real-Time Events | EveryPage
Description: Get an HTTPS POST the moment someone views, downloads, or fills a form on your PDF: HMAC-signed webhooks with retries, plus Slack notifications.

Outbound webhooks

# Real-time webhooks for PDF activity

The moment someone opens your proposal, downloads the report, or completes the lead form, EveryPage sends a signed HTTPS POST to any endpoint you choose - your CRM, your own service, or a Slack channel.

Drop your PDF here

or click anywhere in the tray to browse

PDF only · max 20MB

Free to start · webhooks on every plan, up to 25 endpoints · add them from Account settings

## Every event, pushed

Views, downloads, completed gate forms, reader comments, receipt confirmations, and self-destruct burns - each one lands at your endpoint seconds after it happens. No polling, no refresh loop.

## Signed like it matters

Every delivery carries an HMAC-SHA256 signature computed with your endpoint secret, Stripe-style. Your receiver can prove each POST really came from EveryPage and is not a replay.

## Retries until it lands

A failed delivery is retried automatically on an increasing backoff schedule. An endpoint that keeps failing is disabled - and you are told - rather than silently swallowing events forever.

## Slack pings, no app install

Point a webhook at a Slack Incoming Webhook URL and pick the Slack format: events arrive as formatted Block Kit messages in your channel. Nothing from the Slack directory to install or approve.

## What events can a webhook send?

A shared PDF generates moments you want to act on while they are still happening - a prospect opening the proposal, a lead completing the gate form, a one-time link burning itself. Each endpoint subscribes to exactly the events it cares about:

- Viewed. A reader opened the document. Fired per visit, carrying the file, the visit source, and the reader identity your plan reports - enough for a CRM to log who came back.
- Downloaded. A copy left the building. The event says which document, and which reader took it.
- Form completed. A reader passed the email gate or lead capture form. The payload carries the captured fields, ready to post straight into your CRM while the lead is still reading. The one Pro-only delivery - it carries lead data, so it is sent while the account is on Pro.
- Comment added. A reader left feedback on the document - private or public - so the right person can respond while the reader is still on the page.
- Receipt confirmed. A reader marked the document as received. Proof of delivery, pushed to wherever your audit trail lives.
- Link burned. A self-destructing link spent its view budget and deleted itself - the last event a link ever sends. Your readership record survives; the webhook tells you the moment the document went.

## Verifying the signature

Every delivery includes a signature header in the same t/v1 style Stripe uses: a Unix timestamp and a hex digest, comma-separated. The digest is an HMAC-SHA256 of the timestamp, a dot, and the raw request body, keyed with the signing secret of the endpoint that received it.

To verify: read the timestamp and signature from the header, recompute HMAC-SHA256 over timestamp-dot-body with your secret, and compare your digest to v1 with a constant-time comparison. Reject anything whose timestamp is older than your tolerance - five minutes is typical - and forged or replayed deliveries never make it past the front door.

The signing secret is generated per endpoint and shown exactly once, at creation. Store it like a password; if it leaks or goes missing, rotate the endpoint and a new secret is minted.

## Delivery, retries & housekeeping

A delivery is a POST to your HTTPS endpoint with a JSON body; any 2xx response counts as received. Anything else - a timeout, a 500, a dropped connection - is retried automatically with increasing backoff, so a deploy or a blip on your side costs you nothing. The event arrives when you are back.

An endpoint that fails every retry over a sustained run is disabled automatically, so it does not sit there absorbing events into the void - its status shows in Account settings and you can re-enable it once your side is fixed. Each account can register up to 25 endpoints, each with its own secret, its own event selection, and its own payload format.

## Slack notifications in three steps

Slack support ships as a webhook format, not a Slack app - there is nothing from the app directory to install and nothing for a workspace admin to approve.

1. Create a Slack incoming webhook. In Slack, add an Incoming Webhook to the channel where you want notifications. Slack hands you a unique URL for that channel.
2. Paste the URL into EveryPage. Add it as a webhook endpoint in Account settings, exactly as you would any other endpoint URL.
3. Pick the Slack format. Choose Slack as the payload format and select your events. From then on, a view on your proposal becomes a formatted Block Kit message in the channel, seconds later.

## Prefer no code? Use Zapier

If you would rather not run a receiving endpoint at all, the Zapier integration connects EveryPage to 7,000+ apps with no code. It polls on a schedule rather than pushing in real time, which is fine for most notification and logging flows.

Webhooks are the real-time, developer-grade end of the same spectrum: push delivery, signed payloads, and your own code deciding what happens next. Browse all EveryPage integrations for everything in between.

## Webhook questions.

### What are PDF webhooks?

A webhook is an HTTPS POST that EveryPage sends to a URL you control the moment something happens to a document you shared - a view, a download, a completed gate form, a comment, a confirmed receipt, or a self-destruct burn. Instead of checking your readership dashboard, your systems are told in real time.

### How do I get Slack notifications when someone reads my PDF?

Create an Incoming Webhook in Slack for the channel you want, paste its URL into EveryPage as a webhook endpoint, and choose the Slack payload format. Events then arrive as formatted Block Kit messages in that channel. No Slack app install or workspace admin approval is needed.

### How do I verify a webhook really came from EveryPage?

Every delivery is signed with HMAC-SHA256 using your endpoint secret, in the same timestamp-plus-signature header style Stripe uses. Recompute the digest over the timestamp and raw request body, compare it to the v1 value in constant time, and reject stale timestamps - forged or replayed requests fail the check.

### What happens if my endpoint is down?

Failed deliveries are retried automatically on an increasing backoff schedule, so an outage on your side just delays the event. An endpoint that keeps failing across the whole schedule for a sustained period is disabled automatically; its status shows in Account settings and you can re-enable it once fixed.

### Which plan includes webhooks, and how many endpoints can I add?

Every plan includes outbound webhooks - Free, Basic, and Pro - and the Slack format with them. Each account can register up to 25 endpoints, each with its own signing secret, event selection, and payload format. One exception: form-completed (gate.completed) deliveries carry captured lead data, so they are only sent while the account is on Pro. If you want automation without code, the Zapier integration is available as an alternative.

## Wire your documents into everything else.

Add an endpoint or a Slack channel - it works on every plan - and the next time someone opens your proposal your tools will know before you do.

Related: the developer API · PDF read tracking · lead capture forms · all integrations

---
URL: https://everypage.co/integrations
Title: Integrations - Zapier, Make, n8n & WordPress | EveryPage
Description: Share tracked PDF links from the tools you already use: Zapier, Make, n8n, a WordPress plugin, signed webhooks, and Slack notifications.

Integrations

# Tracked links from the tools you already use

Every integration uploads to your own EveryPage account and hands back a secure, trackable link - so you see who read it, how far they got, and for how long, without leaving your workflow.

Most integrations connect with an EveryPage API key (create one under Account -> API keys) and then work in both directions: your tools create tracked documents, and EveryPage reports back on what readers do with them. Webhooks run the other way on their own - EveryPage pushes signed events to your tools, including Slack, the moment a document is read.

Availability is marked on every card below, because it matters: some of these are live today, some are in review with their marketplaces, and the roadmap is listed honestly further down rather than dressed up as shipped.

## Connect EveryPage today.

AI assistants (MCP)

Available now · MCP server

Connect Claude, Cursor or any MCP client: ask it to share a PDF and it returns a tracked link - then tells you who read it and where they stopped.

Zapier

Early access · Automation

Triggers and actions across 7,000+ apps: fire a Zap when a document is read, a lead is captured, or a copy is downloaded - and upload PDFs to get tracked links back.

Make (ex-Integromat)

Early access · Automation

Instant triggers push reads, downloads, and form fills into your scenarios in seconds, and 19 modules turn PDFs from 2,000+ apps into tracked links - GDPR-friendly, no reader IPs stored.

n8n

Available now · Community node

A binary-native node for self-hosted and cloud n8n: PDFs in, tracked links out, instant HMAC-verified triggers - and AI Agent nodes can drive it as a typed tool.

Notion

Available now · Embeds + database sync

Paste a link into any Notion page and choose Embed - the tracked, branded viewer renders in-page - and every read session syncs as a row into an EveryPage Reads database in your workspace.

Close

Available now · CRM activity sync

Reads, downloads and form fills posted as an EveryPage activity on the matching lead in Close - pages read, time spent and read-through on the timeline your reps already work from.

WordPress

Available now · Plugin

Embed tracked PDFs in posts with a Gutenberg block - flipbook included - share from the Media Library, and read page-by-page analytics in wp-admin.

Webhooks

Available now · Real-time, all plans

HMAC-signed HTTPS POSTs the moment a document is viewed, downloaded, gated, commented on, receipted, or burned - with automatic retries.

Slack via webhooks

Available now · Notifications

Point an EveryPage webhook at a Slack Incoming Webhook URL and pick the Slack format - readership pings arrive as formatted messages, no Slack app install.

## On the roadmap.

These are not available yet. They are listed so you know where the work is going, not to suggest you can connect them today:

Canva · Google Workspace · Browser extension · Slack app · HubSpot · Microsoft 365 · Figma · Shopify

The Canva app, the Google Workspace add-on, and the Chrome and Edge browser extension all shipped in an earlier form and are being rebuilt for EveryPage before they go back on the list above. Everything else is new work.

Need one of these sooner, or a tool that is not listed at all? Tell us which one.

## Or build your own.

The same platform API every integration above is built on is open to you: upload a PDF and get a tracked link, a QR code, and an embed code back in one call.

the developer API · the documentation · webhooks · PDF read tracking · lead capture forms · dynamic QR links

## Put a tracked link at the end of every workflow.

Connect the tool you already work in, and the next document it produces will tell you whether anyone read it - page by page.

---
URL: https://everypage.co/integrations/zapier
Title: Zapier PDF Tracking - Reads, Leads & Downloads | EveryPage
Description: Fire a Zap the moment your PDF is read, a lead completes the email gate, or a copy is downloaded - and create tracked links from 7,000+ apps.

Zapier integration

# Know when your PDF gets read - in any of 7,000+ apps

The EveryPage Zapier app works in both directions: triggers that fire the moment a document is read, a lead is captured, or a copy is downloaded - and actions that turn any PDF into a tracked share link, QR code, and embed.

## How the integration works.

The app connects with a personal API key - no OAuth dance, no admin approval - and then works in both directions: EveryPage pushes reader activity into your Zaps, and your Zaps create and manage tracked documents in EveryPage.

### Connect in two minutes

Add EveryPage as a step in any Zap, then paste an API key from your account page (Account -> API keys -> create one named "Zapier"). The key works on every plan, and the connection is labelled with your account email so multiple accounts stay distinguishable.

### Start from a trigger or an action

Triggers start Zaps from what readers do: opens, downloads, form fills, comments, receipt confirmations, link expiry. Actions go the other way - upload a PDF from Drive or Gmail and get a tracked link back, expire a proposal when the deal closes, mint a per-recipient link for every row in a sheet.

### Turn it on - the plumbing manages itself

Switching on a Zap with an instant trigger registers a webhook subscription on your account automatically; switching it off removes it. You can see every live subscription under Account settings. Nothing to configure on a server, nothing to clean up.

### Under the hood

#### Instant, signed delivery

Instant triggers arrive within seconds of the event - EveryPage pushes them over HMAC-signed webhooks, and the app verifies every signature before your Zap runs, so a forged payload never reaches your workflow. Accounts hold up to 25 webhook subscriptions, and each Zap uses one.

#### Three share channels from every upload

Every document that the integration creates comes back with a share link, a QR code image URL, and an embed code. All three are keyed to the document itself - replace the file behind the link and the printed QR poster, the embedded viewer, and the emailed URL all keep working.

#### Plan-aware, not cryptic

Fields that need a higher plan say so in their help text, and if a Zap sends a setting your plan does not include, the error names the feature and the plan that unlocks it - never a bare status code. Captured leads are never discarded: if a subscription lapses, capture continues and delivery resumes when the plan is restored.

#### Private by design

Your API key is only ever sent to everypage.co - the app refuses to attach it to any other host, including the URLs your Zaps fetch files from. Reader identity stays pseudonymous (EveryPage never stores visitor IP addresses), and your own visits to your own documents never fire your triggers, so there is no self-notification noise.

## Triggers: when this happens in EveryPage.

Start a Zap from what your readers do. Triggers deliver instantly - EveryPage pushes the event to Zapier the moment it happens, no polling delay.

### New Document Read

A reader opened your document - with country, pages viewed, and reading time. Choose scheduled polling or instant delivery.

### New Form Fill / Email Gate Capture

A reader completed your email gate or lead-capture form. Every captured field arrives ready to map into your CRM - while the lead is still reading.

### New Download

A reader saved a copy. Log it, score it, or follow up on it.

### Link Expired / Self-Destructed

A link reached the expiry date or view budget you gave it. Run the wrap-up: archive the record, pull the final analytics summary.

### New Reader Comment

A reader left feedback on the document. Route it to Slack or your ticket queue while they are still on the page.

### Receipt Confirmed

A reader confirmed receipt of the document - proof of delivery, pushed wherever your audit trail lives.

## Actions: make EveryPage do this.

Create and manage tracked documents from any of the 7,000+ apps on Zapier.

### Upload PDF & Get Tracking Link

Send a PDF in, get the share URL, QR code, and embed code back - plus the file ID for any later step.

### Update File Settings

Change the passcode, expiry, download permission, or gating on an existing document - the link never changes.

### Find File

Look a document up by name and feed it into the rest of the Zap.

### Create Link Variant

Mint a per-recipient tracked link off one document - one link per contact, attribution built in.

### Replace File Content

Swap a new version in behind the same link - every QR code and embed serves the update instantly.

### Get Analytics Summary

Pull a document readership summary - views, readers, completion - into your Zap.

### Delete File

Permanently remove a document when your workflow decides it is done.

### Get Page Marks

The pick, reject and maybe verdicts readers left on each page - document totals, comma-joined page lists ready to drop into an email or a Notion row, and a per-viewer breakdown as line items.

### Get Annotations

The annotations readers drew on the document, flattened into one loopable list with the page, the reader, and their note.

## Zaps our users start with.

Six patterns that cover most of what people wire up first.

New Form Fill → HubSpot

### Gate capture → CRM contact

A lead completes the email gate on your whitepaper and lands in HubSpot with every field they entered - seconds after they start reading.

New Document Read → Slack

### New read → Slack DM

The moment a prospect opens the proposal, the deal owner gets a Slack message naming the document and how far they read.

Google Drive → Upload PDF → Gmail

### Drive file → tracked link → Gmail

A new PDF lands in a Google Drive folder, becomes a tracked EveryPage link, and goes out by Gmail - hands-free.

Google Sheets → Create Link Variant

### Sheets row → personal link per recipient

For every row in a spreadsheet, mint a link variant labelled with that recipient - one document, per-person readership.

CRM stage → Update File Settings

### CRM Closed-Lost → expire the link

Expiry is your rule, not a default: when a deal closes lost, have the CRM set the proposal link to expire automatically.

New Download → Google Sheets

### New download → spreadsheet row

Every download appends a row to a sheet - a running log of which documents leave the building, and when.

## What each plan unlocks.

The Zapier app is free to connect on every EveryPage plan. Pro-gated fields and triggers show a friendly upgrade note in the Zap editor instead of failing.

| In the Zapier app | Free | Basic | Pro |
|---|---|---|---|
| Read, download, comment, receipt & link-expired triggers | ✓ | ✓ | ✓ |
| Upload PDF, Update Settings, Find File, Analytics Summary & Delete actions | ✓ | ✓ | ✓ |
| Protection toggles on upload (block right-click, print, copy) | — | ✓ | ✓ |
| Form Fill / Email Gate Capture trigger | — | — | ✓ |
| Create Link Variant & Replace File Content actions | — | — | ✓ |
| Get Page Marks & Get Annotations searches | — | — | ✓ |

## Zapier questions.

### What can I automate with the EveryPage Zapier integration?

Both directions of a document workflow. Triggers start Zaps from reader activity - a document read, a lead captured through the email gate, a download, a comment, a confirmed receipt, or a link reaching the expiry rule you set. Actions let 7,000+ apps create tracked links, update settings, mint per-recipient link variants, replace the content behind a live link, pull analytics summaries, and delete files.

### Is EveryPage a DocSend Zapier alternative?

Yes. If Zapier automation is part of why you use DocSend, EveryPage covers the same job: triggers when documents are read or leads are captured, plus actions to create and manage tracked PDF links - with flat $9/month pricing instead of per-user billing, and no reader IP addresses stored.

### Are the triggers instant or polled?

Both are available. New Document Read can run as a scheduled polling trigger or as an instant trigger; form fills, downloads, comments, receipts, and link-expiry events are delivered instantly - EveryPage pushes them to Zapier the moment they happen.

### How does EveryPage authenticate with Zapier?

You connect with an EveryPage API key, created under Account and starting with ep_live_. The integration attaches the key only to HTTPS requests bound for everypage.co - when a Zap step fetches a PDF from somewhere else, that download carries no credentials - and you can revoke a key at any time.

### Which Zapier and EveryPage plans do I need?

The EveryPage side works on every plan, free included. The Form Fill trigger and the Create Link Variant and Replace File Content actions are Pro, because the product features they drive are Pro. On the Zapier side, single-step Zaps work on the Zapier free tier; multi-step Zaps need a paid Zapier plan.

### Do tracked links have to expire?

No - expiry is a control you set per document, never a default. Give a link an expiry date, a view budget, or neither - with neither, the link never expires. The Link Expired / Self-Destructed trigger exists so a rule you chose can kick off the follow-up, like archiving the record or pulling a final analytics summary.

## Put your documents on autopilot.

Connect EveryPage to Zapier with an API key, pick a trigger, and the next time someone reads your PDF the rest of your stack will know.

Related: all integrations · the Zapier setup guide · automation recipes · raw webhooks · lead capture forms · the DocSend alternative

---
URL: https://everypage.co/integrations/wordpress
Title: WordPress PDF Tracking Plugin & Flipbooks | EveryPage
Description: See who reads the PDFs on your WordPress site: tracked embeds with flipbook modes, gated lead magnets, and page-by-page readership in wp-admin.

WordPress plugin

# See who actually reads the PDFs on your WordPress site

The EveryPage plugin embeds tracked PDFs in your posts - flipbook included - shares them from the Media Library, and reports readership page by page inside wp-admin. No cookies, no consent banner, and reader IP addresses are never stored.

## How the plugin works.

The plugin is free and connects to your EveryPage account with an API key - no OAuth dance, no per-site configuration. From then on, everything happens inside wp-admin: your PDFs get tracked links, your posts get an embedded viewer, and your dashboard gets the readership.

### Install the plugin

Add the EveryPage plugin from your WordPress dashboard (Plugins -> Add New) and activate it. The plugin itself is free on every EveryPage plan - what the readership report shows and which link controls you get follow your plan, not the plugin.

### Connect your account

Paste an API key from your account page (Account -> API keys -> create one named "WordPress") under EveryPage -> Settings. The plugin runs a connection test so you know it is linked, stores the key in your site's options table, and only ever sends it to everypage.co over HTTPS.

### Insert the block - or share from the Media Library

Drop the EveryPage Document block into any post to embed a tracked PDF inline, or use the "Share via EveryPage" action on any Media Library PDF to get a tracked link, QR code, and embed snippet. Every document's settings live in a drawer right there in wp-admin - no round trip to everypage.co.

### Under the hood

#### Analytics without a consent banner

Readership is measured first-party inside the EveryPage viewer: no cookies, no third-party tracking scripts, and no reader IP addresses stored - readers get a salted, pseudonymous identity instead. Page-level PDF analytics your cookie banner never has to mention.

#### Embedders display; EveryPage measures

A raw Media Library PDF is a dead end: plugins like PDF Embedder and EmbedPress render the pages, and GA4 can only count clicks on the link. The EveryPage viewer renders the same pages and reports read-through per page - how far each reader got, and how long they stayed.

#### Plan-aware, not cryptic

The per-file settings drawer shows everything your plan includes, and fields that need a higher plan are labelled with the plan that unlocks them - a Basic or Pro tag in the drawer, never a bare error after you hit save.

#### Light on your site

Your PDFs are stored encrypted on your EveryPage account, not in your media library or on your host, and nothing runs on your public pages except the viewers you place. Your API key is only ever sent to everypage.co, and you can revoke it from your account at any time.

## In the editor: the EveryPage Document block.

Embed a tracked PDF the way you embed anything else in Gutenberg - and style the viewer without touching a line of CSS.

### EveryPage Document block

Insert a tracked PDF inline in any post or page. Pick a document you have already shared, or upload one right from the block.

### Four viewer modes

Standard scroll, page-turning Flipbook, phone-friendly Swipe, or two-page Magazine spreads - a WordPress flipbook embed with readership built in.

### Match your theme

Full viewer appearance customisation in the block sidebar, including picking up your theme's colours - the embed looks like part of your site, not an iframe from somewhere else.

### Button or link mode

Render a tracked button or text link instead of the inline viewer when you want the document one click away.

### The [everypage] shortcode

Using the classic editor, widgets, or a page builder? The shortcode places the same tracked viewer anywhere shortcodes go.

### QR codes

Every document comes with a QR code for print - scans are attributed as their own source, separate from your site traffic.

## In wp-admin: share, migrate, and measure.

The Media Library stops being where PDFs go to disappear: share what is already there, migrate old links, and read the results without leaving WordPress.

### Share via EveryPage

A row action - and a bulk action - on every Media Library PDF. One click opens a share modal with the tracked link, QR code, and embed snippet.

### Replace links in content

Scan your posts and pages for raw media-library PDF links and swap them for tracked EveryPage links - with a dry run that shows every change before anything is touched.

### Per-file settings drawer

Viewer customisation, expiry rules, the download toggle, and protection toggles for every document - everything your plan includes, right in wp-admin.

### Passwords & view notifications

Put a password on a document and get notified when it is read - set from the same drawer.

### Email gate & vanity slugs

Gate a document behind an email form or give it a readable vanity slug - Pro controls, managed from wp-admin.

### Readership in wp-admin

Per-file analytics inside WordPress: views, readers, page-by-page read-through, and reading time - the report lives where the content does.

### Recent reads dashboard widget

The latest reader activity - which document, how far they read, and when - on the wp-admin dashboard you already open every day.

## Built for the way WordPress sites use PDFs.

Six jobs the plugin walks into on day one.

Bloggers · lead magnets

### A lead magnet that names its leads

Put the email gate in front of your download and every reader arrives in your list by name - and you see how far each one actually read, not just that the form was filled.

Agencies · client deliverables

### Deliverables that report back

Share reports and proposals as tracked links straight from the Media Library. Before the check-in call, you already know who opened it and which pages held them.

Courses & memberships

### Materials students actually read

Embed workbooks and handouts with the block and the read-through funnel shows exactly where students stop - so you fix the page that loses them, not the whole course.

WooCommerce · digital documents

### Product documents that measure themselves

Manuals, spec sheets, and catalogues embedded on product pages report reading, not downloads - and QR codes carry the same documents onto packaging and print.

Publishers & magazines

### Flipbook issues on your own site

Publish an issue as a page-turning flipbook or two-page magazine spread inside your own pages - with per-page readership instead of a view counter.

Switching from a PDF embedder

### Keep the embed, gain the analytics

PDF Embedder and EmbedPress display your PDF; EveryPage displays it and measures it. The replace-links tool migrates your existing posts, dry run first.

## What each plan unlocks.

The plugin is free and connects on every EveryPage plan. Controls your plan does not include appear in the settings drawer labelled with the plan that unlocks them - nothing fails silently.

| In the WordPress plugin | Free | Basic | Pro |
|---|---|---|---|
| Document block, shortcode, Media Library sharing & QR codes | ✓ | ✓ | ✓ |
| Viewer modes, appearance customisation & readership in wp-admin | ✓ | ✓ | ✓ |
| Password protection & view notifications | — | ✓ | ✓ |
| Email gate on embedded & shared documents | — | — | ✓ |
| Vanity slugs | — | — | ✓ |

## WordPress plugin questions.

### What does the EveryPage WordPress plugin do?

It connects your WordPress site to your EveryPage account so every PDF you publish becomes trackable. You get a Gutenberg block that embeds a tracked PDF inline (with Flipbook, Swipe, and Magazine viewer modes), a "Share via EveryPage" action on Media Library PDFs, a shortcode, QR codes, per-file settings, and page-by-page readership analytics - all inside wp-admin.

### Does PDF analytics on my site need a cookie consent banner?

EveryPage's readership analytics does not: it is measured first-party inside the viewer with no cookies and no third-party tracking scripts, and reader IP addresses are never stored - each reader gets a salted, pseudonymous identity instead. Whatever else your site runs still follows its own rules, but EveryPage adds nothing for a banner to disclose.

### How is this different from PDF Embedder or EmbedPress?

Those plugins display a PDF; EveryPage displays it and measures it. An embedded media-library PDF tells you nothing about reading, and Google Analytics can only count clicks on the link. The EveryPage viewer reports read-through per page, reading time, and returning readers - and adds controls like passwords, email gates, and expiry rules that a plain embed cannot have.

### Can I track PDFs that are already in my Media Library?

Yes. The "Share via EveryPage" row action (or bulk action) uploads the file to your EveryPage account and hands back a tracked link, QR code, and embed snippet. The replace-links tool then finds raw media-library PDF links across your posts and swaps them for the tracked versions - with a dry run that previews every change first.

### Is the plugin free, and what do I need to use it?

The plugin is free. You need a WordPress site where you can install plugins and an EveryPage account with an API key - the free plan covers core readership on up to 3 PDFs, no card required. Basic adds passwords, view notifications, and deeper analytics; Pro adds the email gate and vanity slugs.

### Do embedded or shared links expire?

Only if you tell them to - expiry is a per-document control, never a default. Give a document an expiry date, a view budget, or neither, from the settings drawer in wp-admin - with neither, the link never expires, so a PDF embedded in a post keeps working for as long as the post does.

## Give your site's PDFs a memory.

Install the plugin, paste an API key, and the next PDF you publish reports back - page by page, reader by reader.

Related: all integrations · the WordPress setup guide · PDF flipbook embeds · lead capture forms · Google Analytics for PDFs

---
URL: https://everypage.co/integrations/make
Title: Make (Integromat) PDF Tracking Integration | EveryPage
Description: Turn any document in a Make scenario into a tracked PDF link: instant triggers for reads, downloads, and form fills - no reader IPs stored.

Make integration

# Turn any document in your scenario into a tracked link

The EveryPage app for Make (ex-Integromat) works in both directions: instant triggers push reads, downloads, and form fills into your scenario within seconds, and 19 modules turn PDFs from 2,000+ apps into tracked links - with GDPR-friendly analytics: no cookies, no reader IP addresses stored.

## How the integration works.

The app connects with a personal API key - no OAuth dance, no admin approval - and then works in both directions: EveryPage pushes reader activity into your scenarios, and your scenarios create and manage tracked documents in EveryPage.

### Connect with an API key

Add EveryPage to a scenario and paste an API key from your account page (Account -> API keys -> create one named "Make"). The key works on every plan, is only ever sent to everypage.co, and the connection is labelled with your account email and plan so multiple accounts stay distinguishable.

### Pick a module

Nineteen modules cover both directions: instant watch modules that start scenarios from reader activity, actions that upload PDFs and manage live links, searches to find documents by name, and a universal "Make an API Call" module for anything else the EveryPage API can do.

### Turn the scenario on - the plumbing manages itself

Activating a scenario with an instant watch module registers a dedicated webhook on your account automatically; deactivating removes it, and an already-deleted webhook never errors your teardown. Every live subscription stays visible under Account settings.

### Under the hood

#### Instant where it matters, frugal where it counts

Reads, downloads, and form fills arrive over dedicated webhooks within seconds of the event - no operations spent polling for them. A Watch Events polling fallback exists for scenarios that prefer scheduled pulls, and because Make prices by operations, its recommended schedule is 15 minutes.

#### GDPR-friendly by architecture

EveryPage readership is measured without cookies and reader IP addresses are never stored - each reader gets a salted, pseudonymous identity instead, with country resolved in flight. Document analytics from a UK-operated tool that your GDPR review can cover in a paragraph, not a project.

#### Three share channels from every upload

Every document a scenario creates comes back with a share link, a QR code image URL, and an embed code - all keyed to the document itself, never a renameable slug. Replace the file behind the link and the printed QR poster, the embedded viewer, and the emailed URL all keep working.

#### Signed at the source, honest about Make

Every webhook delivery is HMAC-signed by EveryPage. Make modules cannot verify raw-body signatures, so inside Make authenticity rests on the unguessable per-scenario webhook URL Make generates - we say that plainly rather than imply otherwise. The signing secret is stored with the webhook, ready for the day Make exposes raw bodies.

## Instant triggers: when this happens in EveryPage.

Dedicated webhooks push each event into your scenario within seconds of it happening - no polling operations, no missed reads.

### Watch Reads

A reader finished viewing a document - with pages viewed, time spent, country, and link-variant attribution, ready to map into the next module.

### Watch Downloads

A reader (not you) saved a copy. Log it, score it, or follow up on it.

### Watch Form Fills

A viewer completed the email gate or lead form. Every captured field rides along, with the email copied to a top-level key for easy mapping into your CRM.

### Watch Comments

A reader left a comment, with the text and the page it was left on. Route it to Slack or your ticket queue while they are still reading. Only public comments emit an event - switch a document to private comments and nothing fires, by design.

### Watch Events

The scheduled fallback: cursor-walks the events feed for reads, downloads, and form fills. Make prices by operations, so a 15-minute schedule is the sweet spot.

## Modules: make EveryPage do this.

Create, manage, measure, and export tracked documents from any of the 2,000+ apps on Make.

### Upload a File

Map a file from any module and get the share URL, QR code, and embed code back - with the full plan-aware settings surface: viewer mode, passcode, expiry, protection toggles, email gate, vanity slug, watermark, page range.

### Update File Settings

Change any subset of settings on an existing document - only the fields you provide are sent, and the link never changes.

### Get a File / List Files

Look a document up by name or list them all, and feed the result into the rest of the scenario.

### Replace File Content

Swap the PDF behind a live link - the link, QR codes, embeds, settings, and readership history all survive.

### Link Variants

Create, list, update, revoke, and delete per-recipient tracked links - one document, per-person readership, GDPR label redaction included.

### Get a QR Code

The tracked QR code as a PNG file, ready to map into print, merge, or email modules.

### Get a Readership Summary

The plan-shaped analytics rollup for a document - views, readers, completion - as mappable fields.

### List Events

Bulk pulls from the events feed with cursor paging - built for data-store and warehouse scenarios.

### Delete a File

Trash by default - restorable until the purge date - or permanently purge when your workflow decides it is done.

### Get Page Marks

The pick, reject and maybe verdicts readers left on the pages - per-page tallies, a per-viewer breakdown, and document totals as mappable fields.

### Get Annotations

The annotations readers drew on the document, grouped by page, each with the reader and their note.

### Make an API Call

The universal module: any EveryPage API endpoint, with your connection already authenticated.

## Five scenarios to build first.

The scenario templates that ship with the app - each one a pattern you can rebuild in minutes.

Watch Form Fills → CRM

### Gated deck → CRM upsert

A prospect completes the email gate on your deck and lands in your CRM with every captured field - while they are still reading.

Drive / Dropbox → Upload a File → Email

### Client PDF → tracked link → email

A deliverable lands in a Drive or Dropbox folder, becomes a tracked EveryPage link, and goes out by email - so you can prove the client read what you billed for.

Watch Reads → Slack

### Document read → Slack ping

The moment someone finishes reading, the channel hears about it - which document, how many pages, and for how long.

Schedule → Readership Summary → Sheets

### Weekly readership → Google Sheets

Every Monday, pull the readership rollup for the documents you care about into a running spreadsheet - trends without dashboard visits.

Upload a File → List Events → Data store

### Invoice → tracked link → data store

Generated invoices and reports go out as tracked links, and the events feed writes engagement back to a Make data store - a paper trail that includes reading.

## What each plan unlocks.

The Make app is free to connect on every EveryPage plan. Fields that need a higher plan say so in their description, and if a scenario trips a plan gate anyway, the error names the plan and links the upgrade page - never a bare status code.

| In the Make app | Free | Basic | Pro |
|---|---|---|---|
| Watch Reads, Watch Downloads, Watch Comments & Watch Events triggers | ✓ | ✓ | ✓ |
| Upload, Update Settings, Get/List, QR, Readership, Events & Delete modules | ✓ | ✓ | ✓ |
| Protection toggles on upload (block right-click, print, copy) | — | ✓ | ✓ |
| Watch Form Fills (email gate & lead form captures) | — | — | ✓ |
| Link Variants & Replace File Content modules | — | — | ✓ |
| Get Page Marks & Get Annotations modules | — | — | ✓ |

## Make questions.

### What can I automate with the EveryPage Make integration?

Both directions of a document workflow. Instant triggers start scenarios the moment a document is read, downloaded, or unlocks an email gate; modules let 2,000+ Make apps upload PDFs and get tracked links back, update settings on live links, mint per-recipient link variants, replace content behind a link, pull QR codes and readership summaries, export bulk events, and delete files - plus a universal API-call module for everything else.

### Is EveryPage a DocSend alternative with a Make integration?

Yes - and an uncontested one: DocSend has no Make app at all. If tracked document links belong in your scenarios, EveryPage covers the job with instant read, download, and form-fill triggers plus a full set of upload and management modules - at a flat price instead of per-user billing, with analytics that store no reader IP addresses.

### Are the triggers instant or polled?

Reads, downloads, and form fills are instant - EveryPage pushes them over dedicated webhooks within seconds, costing you no polling operations. A Watch Events polling module exists as a fallback (a 15-minute schedule is recommended, since Make prices by operations). Deliveries are HMAC-signed at the source; because Make cannot verify raw-body signatures, authenticity inside Make rests on the unguessable per-scenario webhook URL.

### Is the document analytics GDPR-friendly?

That is the design. Readership is measured first-party inside the EveryPage viewer with no cookies and no third-party scripts, and reader IP addresses are never stored - each reader gets a salted, pseudonymous identity, with country resolved in flight and the address then discarded. EveryPage is UK-operated, and there is nothing here for a consent banner to disclose.

### Is the app live in the Make app directory - and which plans do I need?

The app is built and going through Make's review for a public listing, so it is not in the app directory yet - and until it is, everything on this page is also reachable from Make's HTTP modules against the EveryPage API (see the developer docs). On the EveryPage side every plan connects, free included; Watch Form Fills, Link Variants, and Replace File Content are Pro because the product features they drive are Pro.

### Do tracked links have to expire?

No - expiry is a control you set per document, never a default. Give a link an expiry date, a view budget, or neither - with neither, the link never expires. Scenarios can also manage expiry for you: have your CRM expire the proposal link when the deal closes, straight from Update File Settings.

## Put a tracked link in every scenario.

Connect EveryPage with an API key, drop a module into the flow, and the next document your scenario sends will report back - reads, downloads, and leads, within seconds.

Related: all integrations · the n8n node · raw webhooks · lead capture forms · the DocSend alternative

---
URL: https://everypage.co/integrations/n8n
Title: n8n PDF Tracking Node - Instant Webhooks | EveryPage
Description: The EveryPage n8n community node: binary PDF in, tracked link out, instant HMAC-verified webhook triggers, and AI Agent tool support.

n8n community node

# The document-sharing node for people who read the source

n8n-nodes-everypage turns any PDF in your workflow into a tracked share link: binary in, share URL + QR + embed out, instant HMAC-verified triggers the moment documents are read - and AI Agent nodes can drive the whole thing as a typed tool.

## How the node works.

One node, three resources - File, Link Variant, and Event - plus a trigger node that subscribes to reader activity. The field names match the EveryPage Zapier and Make apps, so workflows translate across platforms without re-learning.

### Install the community node

On self-hosted n8n: Settings -> Community Nodes -> install n8n-nodes-everypage (or npm install it into ~/.n8n/nodes). The package has zero runtime dependencies - a verified-community-node requirement - so what you install is exactly what you can read.

### Connect with an API key

Create a key on your account page (Account -> API keys - it starts with ep_live_) and paste it into a new EveryPage API credential. The node validates it against the API immediately, and the Base URL field only changes when you point at a staging deployment.

### Wire it into the flow

Hand the node binary data from any previous step and it returns the share trio - link, QR code, embed code - for the steps that follow. Activate a trigger and the webhook subscription registers itself; deactivate and it is removed. Nothing to configure on a server.

### Under the hood

#### Every delivery verified

Instant triggers arrive over HMAC-SHA256-signed webhooks, and the node verifies every one - constant-time signature comparison with a five-minute replay tolerance - before your workflow runs. Unverified deliveries are rejected with a 401.

#### Binary-native

PDFs travel as n8n binary data - no upload-by-URL dance. An agent, a Code node, or a download step hands over bytes; the QR code comes back the same way, as a PNG ready for print and merge workflows.

#### Built for self-hosters

A polling fallback with independent per-stream cursors covers instances that cannot receive inbound webhooks, the MIT-licensed source means you can read exactly what runs, and the multipart and HMAC plumbing uses nothing but Node built-ins.

#### Analytics your DPO will wave through

Readership is measured without cookies and reader IP addresses are never stored - each reader gets a salted, pseudonymous identity instead. If you self-host your workflows because you care where data lives, this is the same instinct applied to document analytics.

## Triggers: when this happens in EveryPage.

The EveryPage Trigger node subscribes to nine event kinds over signed webhooks - pushed the moment they happen - with a polling fallback for closed networks. Optionally scope any subscription to a single document.

### Document Read

A reader finished viewing a document - with pages viewed, time spent, country, and link-variant attribution.

### Download

A reader (not you) saved a copy. Log it, score it, or follow up on it.

### Form Fill / Email Gate Capture

A viewer completed the email gate or lead form - every captured field arrives ready to shape and forward, while the lead is still reading.

### Comments & receipts

A reader left feedback on the document or confirmed receipt of it - feedback routed while they are still on the page, proof of delivery for the audit trail.

### Lifecycle events

A link burned out its view budget, content was replaced behind a link, an invite was viewed, a proofing selection changed - the housekeeping events that keep downstream systems honest.

### Polling mode

For instances that cannot receive inbound webhooks: walks the events feed on your schedule with independent per-stream cursors and namespaced event IDs - nothing fires twice, nothing is missed.

## Operations: one node, the whole API.

File, Link Variant, and Event resources with typed, plan-aware fields. Every file-producing operation outputs the share trio - link, QR URL, embed code - keyed to durable identifiers, never a renameable slug.

### Upload

Binary PDF in, tracked link out - with the full plan-tiered settings surface: viewer mode, passcode, expiry or never-expire, email gate, vanity slug, watermark, view limit, page range, protection toggles, notifications.

### Import From URL

The node fetches a PDF from a URL itself - without your EveryPage credentials attached - and uploads it.

### Get / Get Many / Update Settings

Fetch one document or list them all (UUID or short ID), and change any subset of settings in place - only the options you add are sent.

### Replace Content

Swap the PDF behind a link - UUID, short ID, slug, QR, settings, and readership history all survive.

### Get QR Code

The tracked QR code as a binary PNG, ready for print and merge workflows.

### Get Readership

The plan-shaped analytics report - summary, funnel, sessions, contacts - as JSON for the next node.

### Link Variants

Create, list, update, revoke, and delete per-recipient tracked links - one document, per-person readership, GDPR label redaction included.

### Events: Get Many

Bulk pulls from the events feed - view, download, gate - with a since cursor and Return All paging, built for incremental warehouse loads.

### Delete

Trash by default - restorable until the purge date, receipt included - or purge permanently.

## Give your agent a document it can prove was read.

The node ships usableAsTool, so n8n AI Agent nodes can call EveryPage directly as a typed tool: "upload this report and give me the tracked link", "who read the Q3 proposal?". An agent that publishes its work as a tracked link - instead of an attachment - is an agent whose output you can audit.

Schedule → AI Agent → Code → EveryPage → Slack

### Import this workflow: AI report → tracked link → Slack

Every Monday an AI agent writes the weekly report, a dependency-free Code node renders it to PDF, EveryPage returns a tracked link, and Slack gets the link - so you find out whether anyone read what the agent produced. Copy the JSON, then paste it straight onto the n8n canvas (Ctrl/Cmd-V), or use Workflow -> Import from Clipboard.

```
{
	"name": "AI report → EveryPage tracked link",
	"nodes": [
		{
			"parameters": {
				"content": "## AI report → tracked link\nEvery Monday an AI agent writes the weekly ops report, a Code node renders it to a PDF (no dependencies), and EveryPage turns it into a **tracked share link** — so you know whether anyone actually read what the agent produced.\n\nSwap the Slack step for email, Teams, or your CRM. Add `requireEmail: true` in the EveryPage node's options to gate the report (Pro).",
				"height": 260,
				"width": 420
			},
			"id": "a1b2c3d4-0000-4000-8000-000000000001",
			"name": "Sticky Note",
			"type": "n8n-nodes-base.stickyNote",
			"typeVersion": 1,
			"position": [-220, -180]
		},
		{
			"parameters": {
				"rule": {
					"interval": [{ "field": "weeks", "triggerAtDay": [1], "triggerAtHour": 8 }]
				}
			},
			"id": "a1b2c3d4-0000-4000-8000-000000000002",
			"name": "Every Monday 08:00",
			"type": "n8n-nodes-base.scheduleTrigger",
			"typeVersion": 1.2,
			"position": [-220, 60]
		},
		{
			"parameters": {
				"promptType": "define",
				"text": "Write this week's operations report for the team: a short executive summary, then sections for shipped work, metrics, risks, and next week's focus. Plain text, no markdown syntax. Around 500 words.",
				"options": {}
			},
			"id": "a1b2c3d4-0000-4000-8000-000000000003",
			"name": "AI Agent",
			"type": "@n8n/n8n-nodes-langchain.agent",
			"typeVersion": 1.7,
			"position": [0, 60]
		},
		{
			"parameters": {
				"model": { "__rl": true, "value": "gpt-4.1-mini", "mode": "list" },
				"options": {}
			},
			"id": "a1b2c3d4-0000-4000-8000-000000000004",
			"name": "OpenAI Chat Model",
			"type": "@n8n/n8n-nodes-langchain.lmChatOpenAi",
			"typeVersion": 1.2,
			"position": [0, 260]
		},
		{
			"parameters": {
				"mode": "runOnceForAllItems",
				"jsCode": "// Render plain text to a minimal, valid, multi-page PDF - no dependencies.\nconst esc = (s) => s.replace(/\\\\/g, '\\\\\\\\').replace(/\\(/g, '\\\\(').replace(/\\)/g, '\\\\)');\nconst text = String($input.first().json.output ?? $input.first().json.text ?? 'Empty report');\n\nconst lines = [];\nfor (const raw of text.split('\\n')) {\n  let line = raw.replace(/[^\\x20-\\x7e]/g, '');\n  if (line === '') { lines.push(''); continue; }\n  while (line.length > 92) { lines.push(line.slice(0, 92)); line = line.slice(92); }\n  lines.push(line);\n}\nconst pages = [];\nfor (let i = 0; i < lines.length; i += 46) pages.push(lines.slice(i, i + 46));\nif (!pages.length) pages.push(['(empty)']);\n\nconst pageCount = pages.length;\nconst fontObj = 3 + pageCount * 2;\nconst objects = [];\nobjects[1] = '<< /Type /Catalog /Pages 2 0 R >>';\nobjects[2] = `<< /Type /Pages /Kids [${pages.map((_, p) => `${3 + p * 2} 0 R`).join(' ')}] /Count ${pageCount} >>`;\npages.forEach((pg, p) => {\n  const contentObj = 4 + p * 2;\n  objects[3 + p * 2] = `<< /Type /Page /Parent 2 0 R /MediaBox [0 0 595 842] /Resources << /Font << /F1 ${fontObj} 0 R >> >> /Contents ${contentObj} 0 R >>`;\n  let stream = 'BT /F1 11 Tf 56 780 Td 16 TL\\n';\n  for (const line of pg) stream += `(${esc(line)}) Tj T*\\n`;\n  stream += 'ET';\n  objects[contentObj] = `<< /Length ${stream.length} >>\\nstream\\n${stream}\\nendstream`;\n});\nobjects[fontObj] = '<< /Type /Font /Subtype /Type1 /BaseFont /Helvetica >>';\n\nlet pdf = '%PDF-1.4\\n';\nconst offsets = [];\nfor (let n = 1; n <= fontObj; n++) {\n  offsets[n] = pdf.length;\n  pdf += `${n} 0 obj\\n${objects[n]}\\nendobj\\n`;\n}\nconst xref = pdf.length;\npdf += `xref\\n0 ${fontObj + 1}\\n0000000000 65535 f \\n`;\nfor (let n = 1; n <= fontObj; n++) pdf += `${String(offsets[n]).padStart(10, '0')} 00000 n \\n`;\npdf += `trailer\\n<< /Size ${fontObj + 1} /Root 1 0 R >>\\nstartxref\\n${xref}\\n%%EOF`;\n\nconst fileName = `weekly-report-${new Date().toISOString().slice(0, 10)}.pdf`;\nconst binaryData = await this.helpers.prepareBinaryData(Buffer.from(pdf, 'latin1'), fileName, 'application/pdf');\nreturn [{ json: { fileName }, binary: { data: binaryData } }];"
			},
			"id": "a1b2c3d4-0000-4000-8000-000000000005",
			"name": "Render PDF",
			"type": "n8n-nodes-base.code",
			"typeVersion": 2,
			"position": [280, 60]
		},
		{
			"parameters": {
				"resource": "file",
				"operation": "upload",
				"binaryPropertyName": "data",
				"fileName": "={{ $json.fileName }}",
				"options": {
					"viewerMode": "flipbook",
					"notifyOnView": true,
					"expiryHours": 168
				}
			},
			"id": "a1b2c3d4-0000-4000-8000-000000000006",
			"name": "EveryPage",
			"type": "n8n-nodes-everypage.everyPage",
			"typeVersion": 1,
			"position": [560, 60]
		},
		{
			"parameters": {
				"select": "channel",
				"text": "=📄 This week's report is live: {{ $json.shareUrl }}\nEveryPage will tell us who actually reads it.",
				"otherOptions": {}
			},
			"id": "a1b2c3d4-0000-4000-8000-000000000007",
			"name": "Post link to Slack",
			"type": "n8n-nodes-base.slack",
			"typeVersion": 2.2,
			"position": [840, 60]
		}
	],
	"connections": {
		"Every Monday 08:00": { "main": [[{ "node": "AI Agent", "type": "main", "index": 0 }]] },
		"AI Agent": { "main": [[{ "node": "Render PDF", "type": "main", "index": 0 }]] },
		"OpenAI Chat Model": {
			"ai_languageModel": [[{ "node": "AI Agent", "type": "ai_languageModel", "index": 0 }]]
		},
		"Render PDF": { "main": [[{ "node": "EveryPage", "type": "main", "index": 0 }]] },
		"EveryPage": { "main": [[{ "node": "Post link to Slack", "type": "main", "index": 0 }]] }
	},
	"active": false,
	"settings": { "executionOrder": "v1" },
	"pinData": {}
}
```

Self-hosted note: community-node tools need N8N_COMMUNITY_PACKAGES_ALLOW_TOOL_USAGE=true before AI Agent nodes may call them.

## Built for the people who build n8n.

Four workflows the node walks into on day one.

Self-hosted ops

### Events into your warehouse, no middleman

Events: Get Many pages the feed with a since cursor into Postgres or BigQuery - document engagement joins your own analytics stack, with no third-party cloud in the middle.

AI-agent builders

### Reports that prove they were read

The agent publishes its report as a tracked link instead of an attachment - you get notified on the first read, and the readership report says how far anyone actually got.

Gated leads → CRM

### Leads in the CRM while they read

An instant form-fill trigger shapes the captured fields and forwards them to sales - the importable gated-leads-to-crm workflow ships with the node.

Chat agents

### An agent that answers "who read it?"

Attach EveryPage operations as tools on a chat agent and it can list your documents and pull readership on demand - the agent-with-everypage-tool workflow shows the pattern.

## What each plan unlocks.

The node is free to install and connects on every EveryPage plan. Fields above your tier say so in their description and link the pricing page; if a run trips a server-side gate anyway, the error names the plan - never a bare 403.

| In the n8n node | Free | Basic | Pro |
|---|---|---|---|
| Read, download, comment, receipt & lifecycle triggers - webhook and poll | ✓ | ✓ | ✓ |
| Upload, Import, Get/List, Update Settings, QR, Readership, Events & Delete operations | ✓ | ✓ | ✓ |
| Protection toggles on upload (block right-click, print, copy) | — | ✓ | ✓ |
| Form Fill / Email Gate Capture trigger | — | — | ✓ |
| Link Variants & Replace Content operations | — | — | ✓ |

## n8n questions.

### What can I automate with the EveryPage n8n node?

Both directions of a document workflow. Operations turn any binary PDF in a workflow into a tracked share link with QR and embed codes, manage settings and per-recipient link variants, replace content behind live links, and bulk-export reader events for your warehouse. The trigger node starts workflows the moment a document is read, downloaded, commented on, receipted, gated, or burned - over verified webhooks or a polling fallback.

### Is EveryPage a DocSend alternative with an n8n integration?

Yes - DocSend has no n8n node at all. If you want DocSend-style document tracking that lives inside your own workflows, EveryPage covers the job with a binary-native node, instant verified triggers, and GDPR-friendly analytics that store no reader IP addresses - at a flat price instead of per-user billing.

### Are the triggers instant - and are the webhooks verified?

Instant by default: activating the trigger registers a webhook subscription, and events are pushed the moment they happen. Every delivery is verified - HMAC-SHA256 signature, constant-time comparison, five-minute replay tolerance - and unverified deliveries are rejected with a 401. For instances that cannot receive inbound webhooks, poll mode walks the events feed with per-stream cursors so nothing fires twice and nothing is missed.

### How do n8n AI Agent nodes use EveryPage?

The node is marked usableAsTool, so AI Agent nodes can call its operations as typed tools - upload a generated report and return the tracked link, look up who read a document, pull a readership summary. On self-hosted n8n, set N8N_COMMUNITY_PACKAGES_ALLOW_TOOL_USAGE=true; the importable workflows on this page and in the package show working agent setups.

### Can I install it on n8n Cloud - and which plans do I need?

Self-hosted first: the package is n8n-nodes-everypage and installs from the Community Nodes panel as soon as it is live on npm - publication is underway, alongside n8n's community-node verification for Cloud availability. The API the node wraps is live today on every EveryPage plan (see the developer docs). On the plan side everything connects free; the Form Fill trigger, Link Variants, and Replace Content are Pro because the product features they drive are Pro.

### Do tracked links have to expire?

No - expiry is a control you set per document, never a default. Give a link an expiry date, a view budget, or neither - with neither, the link never expires, so the link your workflow published keeps working for as long as you want it to. Workflows can also manage expiry themselves through Update Settings.

## Put a tracked link at the end of every workflow.

Install the node, paste an API key, and the next document your workflow produces will tell you whether anyone read it - page by page, over a webhook you can verify.

Related: all integrations · the Make integration · raw webhooks · the DocSend alternative · sharing PDFs without storing IPs · automation recipes

---
URL: https://everypage.co/integrations/notion
Title: Notion Client Portals with Tracked PDF Embeds | EveryPage
Description: Embed tracked, branded document viewers in any Notion page - and log every read session as a row in an EveryPage Reads database inside your workspace.

Works with Notion

# Client portals with real analytics

Embed tracked, branded document viewers in any Notion page - flipbook page-turns and all - and log every read into your Notion database. The portal your client already has bookmarked becomes the portal that tells you whether they read the work.

## How it works.

Two halves that ship together: embeds need no setup at all - not even a Notion account on our side - and the database sync is a one-time connect from your account settings. Everything on this page works today, on every plan.

### Paste, then choose Embed

Copy the embed link from the share sheet ("Copy embed link for Notion"), paste it into any Notion page, and pick Embed - not Bookmark - from the menu Notion shows. The tracked viewer renders in-page in whichever mode the document is set to - flipbook, swipe, or standard - and every read is attributed to the embed channel.

### Connect your workspace

In Settings -> Account, choose Connect Notion and authorize your workspace, then pick a parent page. EveryPage creates an "EveryPage Reads" database there - every property ready, no template to duplicate, nothing to configure inside Notion.

### Reads become rows

Each reading session is written as one row, moments after the reader closes the document: pages read, minutes spent, read-through, returning or not, source, country, and a link to the full session. A 30-day backfill import covers the reads that happened before you connected.

## The Reads database.

One row per reading session - inserted moments after the session ends, never updated in place - in a normal Notion database you own. Relate it to your Clients database, build board views by engagement, sort follow-ups by read-through. These are the columns:

### Document

The title property: which document this session read.

### Reader

The invite name or gated email where one exists, otherwise a stable pseudonym like "Reader #214". Real names come from the Pro email gate.

### Event

Viewed, Downloaded, or Gate completed - a select, so pipeline boards can filter on it.

### Pages read

How many pages the session actually covered.

### Time spent

Reading time, in minutes.

### Read-through %

Pages read over total pages - the one number worth sorting a follow-up view by.

### Returning

Checked when this reader has read the document before. Second visits are the signal.

### Source

Where the read came from. Embeds are a separately attributed channel, so portal reads are distinguishable from direct link opens.

### Country

Resolved in-flight from the connection; the reader's IP address is never stored.

### Session link

A direct link to the full session in your EveryPage readership dashboard.

### Share link

The document's public share link - the same durable URL every reader gets, ready to copy, open, or roll up into the Clients database it relates to.

### QR code

The share link as a scannable QR image, attached as a file property - show it in gallery cards or print it, and scans are attributed to the QR channel.

### Date

When the session happened.

### Details

On gate-completed rows, the captured lead fields from the email gate (Pro).

## Built for people who run their business in Notion.

Five portals this integration walks into on day one.

Freelance designer

### Hand-offs that feel premium

The client portal shows deliverables in a branded flipbook instead of a flat file preview - and you know whether the client actually reviewed the work before the call.

Consultant

### A pipeline that sorts itself

Each proposal read lands as a row - pages, minutes, returning or not - so the follow-up view orders itself by real engagement, without adopting a CRM. Notion already is one.

Agency PM

### Portals that never go stale

When a deliverable is revised, replace the file behind the link and every embed updates in place - the Notion page is never re-edited, and the client never sees an old version.

Founder hiring

### Know who read the culture deck

The deck embedded in your public hiring wiki is tracked: which candidates opened it, and how far they got - before the interview, not after.

Fractional CFO

### Board packs, still controlled

Watermark the pack and set an expiry, and the embed stays tracked inside the private workspace page. Add a password and the embed deliberately refuses to render in-page, handing readers a direct link where the protection applies - control always wins.

## What each plan unlocks.

Embeds and the database sync work on every plan, including Free. Pro adds identity: reader names come from the email gate, and gate-completed rows carry the captured fields. On Free and Basic the Reader column shows stable pseudonyms - "Reader #214" - never a surprise blank.

| With Notion | Free | Basic | Pro |
|---|---|---|---|
| Embed the tracked viewer in Notion pages - all viewer modes | ✓ | ✓ | ✓ |
| "Copy embed link for Notion" in the share sheet | ✓ | ✓ | ✓ |
| EveryPage Reads database sync - one row per reading session | ✓ | ✓ | ✓ |
| 30-day backfill import when you connect | ✓ | ✓ | ✓ |
| Reader names in the Reader column (email gate) | — | — | ✓ |
| Gate-completed rows with captured lead fields | — | — | ✓ |

## Notion questions.

### My pasted link shows as a Bookmark card - where is the viewer?

Notion asks what to do with a pasted link, and Bookmark - a flat preview card that sends readers to another tab - is easy to hit by accident. Delete the block, paste the link again, and choose Embed: the tracked viewer renders in-page. The "Copy embed link for Notion" button in the share sheet copies the URL best suited to this, with the reminder attached.

### Is this a Notion app?

No - and nobody's is: Notion has no in-page marketplace apps or custom blocks. EveryPage works with Notion through the two surfaces Notion actually offers - the Embed block, which renders the tracked viewer in-page, and the workspace API, which writes read sessions into a database you own. "Works with Notion" is the honest phrasing, and both halves work today.

### What happens on a public Notion page?

A public page means a public embed: anyone who can see the page can read the document, and those views count toward your plan's limits like any other read. Often that is the point - a public wiki with a tracked culture deck. When it is not, keep the page private, or protect the document itself.

### How fast do rows appear - and can they lag?

One row per reading session, written moments after the reader closes the document - not one per page or per click. Notion's API is rate-limited, so a burst of simultaneous reads can queue: rows may trail a busy stretch by a little, and each write is retried automatically for around two hours. If writes keep failing - a renamed database property, say - the sync pauses and emails you: fix the database, resume from Settings, and use Import recent reads to fill the gap.

### What happens if I disconnect?

Disconnecting stops the sync and removes EveryPage's access to your workspace. The Reads database and every row already in it stay yours - it is a normal Notion database, and nothing is deleted. Reconnect later and new sessions resume; the backfill import can cover up to 30 days of the gap.

### Can I embed a password-protected or email-gated document?

Not in-page: a document with a password or an email gate refuses to render inside the embed and shows an "Open document" link to the direct share page instead, where the gate works as designed - an iframe on someone else's page is no place to type a password. For portals, the usual pattern is watermarks and expiry on embedded files, passwords on the ones you share as direct links.

## Put a tracked portal inside Notion.

Paste one link and choose Embed - the next deliverable you hand off will tell you whether the client read it, page by page, in a database inside your own workspace.

Related: all integrations · the Zapier integration · the Make integration · the n8n node · the Notion embed guide

---
URL: https://everypage.co/integrations/close
Title: Close CRM Integration - Proposal Reads on the Lead Timeline | EveryPage
Description: Know who read your proposal, on the lead’s timeline in Close. EveryPage posts reads, downloads and form fills as an activity on the matching lead, with pages read, time spent and read-through.

Works with Close

# Know who read your proposal, on the lead’s timeline in Close

Share proposals, decks and contracts as tracked links. Every read, download and form fill is posted to the matching lead in Close as an EveryPage activity - pages read, time spent and read-through included - so your reps see it where they already work.

## How it works.

One OAuth connection, one setting for which documents sync, and the activities start appearing on leads. No Zap, no spreadsheet, no per-seat add-on.

### Connect Close

From Account, click Connect Close and approve EveryPage in Close. EveryPage creates a custom "EveryPage" activity type in your organization so the events are filterable, not buried in notes.

### Choose which documents sync

Sync every document, a hand-picked set, or nothing for now - and decide whether unknown readers should become new leads. You can change either at any time.

### Reads appear on the lead

When someone opens a tracked link, EveryPage matches their email to a lead in Close and posts the activity to that lead’s timeline: what they read, how far, how long, and whether they came back.

## What lands in Close.

Each activity is a structured record on the lead - the same numbers your EveryPage readership dashboard shows, filed where the deal lives.

### Event

Read, download, or form fill - so a Smart View can pick out exactly the signal a rep should act on.

### Document

The document’s name, so a lead with three proposals in flight shows which one was opened.

### Pages read

How many pages the reader actually reached out of the total - the page-by-page analytics EveryPage records.

### Time spent

Total time in the document across the session. Ten seconds and six minutes are very different signals.

### Read-through

The percentage of the document the reader got through, so you can spot who stopped at the pricing page.

### Returning reader

Whether this reader has opened the document before. A second or third read is often the buying signal.

### Reader email

The email that matched the lead - from the email gate, a form fill, or the per-recipient link they were sent.

### Link

A link back to the full session in EveryPage, page by page, for reps who want the detail.

### Timestamp

When the read happened, in the lead’s timeline order - so it sits between the call before it and the email after.

## Works with what you already use.

The activity is a first-class Close object, so everything Close already does with activities applies to it.

Smart Views

### Build a "read the proposal, hasn’t replied" view

Filter leads by EveryPage activity in the last 7 days with no reply, and hand reps a list of people who are warm right now.

Workflows

### Trigger a follow-up on a read

Enroll a lead in a Close workflow when an EveryPage activity is logged, so the follow-up email goes out while the proposal is still open on their screen.

Per-recipient links

### Send each contact their own link

Send a document to your contacts from EveryPage and every recipient gets a link tied to their email - so reads match the lead without a form in the way.

Email gate

### Capture the email on public links

Turn on the email gate for a document you share widely and every reader identifies themselves before the first page. Unknown emails can become new leads in Close if you choose.

## One flat plan, not one seat per rep.

DocSend-style tools charge per seat, so putting proposal analytics in front of the whole sales team means paying for every rep, whether or not they send documents. EveryPage is a flat plan: connect Close once and every lead in the organization gets the activities, regardless of how many people are on the team.

Reader privacy holds too. EveryPage never stores reader IP addresses and the viewer runs without cookies, so what reaches Close is engagement data tied to an email the reader gave you - not a tracking profile.

Comparing against DocSend? See the full side-by-side - pricing, analytics depth, and what each does with reader data.

## Questions.

### Which EveryPage plan includes the Close integration?

Plan availability mirrors the Notion sync: the connection and activity posting follow the same plan gating, and features that depend on identifying the reader (the email gate, per-recipient links) follow their own plan rules. The pricing page lists exactly what each plan includes.

### What happens to anonymous readers?

They are skipped. EveryPage can only attach an activity to a lead when it knows the reader’s email - from the email gate, a form fill, or a per-recipient link. Anonymous reads still show in your EveryPage readership dashboard; they just don’t reach Close.

### Does EveryPage read my Close data?

Close’s OAuth grants a single full-access scope - there is no narrower one to request. EveryPage only ever uses it to look up leads and contacts by email, create the "EveryPage" activity type, post activities, and - only if you enable it - create leads. It is a one-way push: nothing else in your Close account is read or modified, and your pipeline is never exported.

### Will it create duplicate leads?

No. Lead creation is off by default. If you turn it on, EveryPage first searches Close for the reader’s email and only creates a lead when there is no match. Readers with no email are never turned into leads.

### Can I limit which documents post to Close?

Yes. Choose all documents, a selected set, or pause the sync entirely. Selection is per document, so internal files or drafts never reach a lead’s timeline.

### Can I disconnect, and what stays behind?

Disconnect from Account at any time; you can also revoke EveryPage from Close’s connected apps. Activities already posted stay on the leads in Close - they are your records - and nothing new is sent.

Not sure which plan fits? Compare plans on the pricing page.

## Put proposal reads where your reps already look.

Upload a proposal, connect Close, and the next read shows up on the lead. Free to start, no per-seat pricing when you upgrade.

See also all integrations · the Notion sync · the Zapier integration · the email gate · per-recipient links

---
URL: https://everypage.co/integrations/mcp
Title: MCP Server for PDF Sharing and Read Tracking | EveryPage
Description: Connect Claude, Cursor or any MCP client to EveryPage: upload a PDF, get a tracked share link, and ask who read it, how far they got, and where they stopped.

EveryPage MCP server

# Your assistant can share a document. Now it can tell you who read it

The EveryPage MCP server gives Claude, Cursor, VS Code and any other MCP client a way to turn a PDF into a tracked link - and then answer the question that actually matters: did they read it, how far did they get, and which page did they stop on?

## Set up the EveryPage MCP server in two minutes.

The server runs locally, on your machine, launched by your MCP client. There is nothing to host and nothing to deploy - and because it runs where your files are, it can read a PDF straight off your disk.

### Create an API key

In your EveryPage account settings, create an API key. It starts with ep_live_ and is shown once. Every plan can create one, including the free plan.

### Add the server to your client

Paste the configuration below into your MCP client and restart it. The package is fetched from npm on first run - there is nothing to install by hand. Node 20 or newer is required.

### Ask for what you want

No commands to learn. Ask your assistant to share a document, or ask whether anyone has read one, and it will pick the right tool itself.

mcp config

### Claude Desktop, Cursor, VS Code and friends

Add this to your MCP client's configuration file, replacing the placeholder with your own key. The key stays in your local config and is sent only to everypage.co.

```
{
  "mcpServers": {
    "everypage": {
      "command": "npx",
      "args": ["-y", "everypage-mcp"],
      "env": { "EVERYPAGE_API_KEY": "ep_live_..." }
    }
  }
}
```

Using Claude Code? One command does the same thing:

```
claude mcp add everypage --env EVERYPAGE_API_KEY=ep_live_... -- npx -y everypage-mcp
```

## What the EveryPage MCP server can do.

Fifteen tools, shaped around tasks rather than API endpoints - so "share this and tell me when they read it" is one request, not five. Here are the ones you will use most.

### everypage_share_pdf

Upload a PDF from your machine or a link, and get back a tracked share URL, an embeddable iframe and a QR code - applying a passcode, expiry or download rule in the same step.

### everypage_get_readership

Who read a document and how far they got: views, unique readers, read time, completion, countries, the page where readers drop off, and which page they went back to.

### everypage_list_events

Recent activity across every document - reads, downloads, or leads captured by an email gate - with a cursor so the next check only returns what is new.

### everypage_list_files

List your documents with their links and view counts, filtered by name when you are looking for one in particular.

### everypage_get_file

Look up a single document: its links, whether it is passcode-protected or gated, and whether it is still live. Accepts a share URL pasted straight from the browser.

### everypage_update_file_settings

Change how a document is shared after the fact - passcode, expiry, downloads, viewer mode, email gate, view limit, page range or vanity name.

### everypage_create_variants

Mint a separate tracked link for each recipient in one call, so reads are attributed to a person by name rather than blending into one anonymous total.

### everypage_replace_content

Swap the PDF behind a live link. The link, QR code, settings and readership history all survive - only the document changes.

### everypage_manage_webhook

Create, test or delete a webhook endpoint, and see whether an existing one is still delivering.

### everypage_account

Which account is connected, which plan it is on, and what that plan allows.

## Things worth asking for.

These are ordinary requests, not commands. The assistant works out which tools to call and in what order.

“Share this proposal with a passcode and give me the link.”

One step: the PDF is read off your disk, uploaded, protected, and the share link, QR code and embed snippet come back together.

“Did anyone read the deck I sent on Monday?”

You get a summary rather than a data dump - readers, time spent, completion, and the page where people stopped - with the raw numbers still available underneath.

“Send this to Alice, Bob and Carol with separate links.”

One tracked link per person, labelled with their name, so the next readership check tells you which of them actually opened it.

“Anything new since yesterday?”

A digest of reads, downloads and captured leads across every document, using a cursor so nothing is counted twice.

## How it behaves.

The details that decide whether an integration is pleasant or exhausting to use.

### Paste a link, not an ID

Anywhere a document is named, you can give a share URL copied from the browser, a short link ID, or the full UUID. There is no lookup step and nothing to memorise.

### Your key never leaves your machine

The key lives in your local MCP config and is sent only to everypage.co. When you ask it to share a PDF from someone else's URL, that download is made with no EveryPage credentials attached at all.

### Large files stream

A local PDF is read off disk rather than into memory, so a 2 GB document uploads without the process growing. Files are checked for size and format before anything is sent.

### Deleting is reversible by default

Deleting a document moves it to the trash, and says so; destroying it permanently takes an explicit instruction. Irreversible tools are flagged so clients can ask you first.

## What each plan unlocks.

The MCP server itself is free and works on every plan. What it can do is bounded by the plan the connected account is on - and a refusal always says which plan is needed.

| Capability | Free | Basic | Pro |
|---|---|---|---|
| Share a PDF and get a tracked link | ✓ | ✓ | ✓ |
| Readership summary and activity feed | ✓ | ✓ | ✓ |
| Passcodes, view limits and read notifications | — | ✓ | ✓ |
| Page-by-page drop-off statistics | — | ✓ | ✓ |
| A separate tracked link per recipient | — | — | ✓ |
| Email-capture gate, content replacement, page ranges | — | — | ✓ |

## Questions.

### Which AI clients does this work with?

Any client that speaks the Model Context Protocol. That includes Claude Code, the Claude desktop and web apps, Cursor, VS Code, and a growing list of others. The setup is the same everywhere: point the client at npx everypage-mcp and give it an API key.

### Does my assistant get access to my documents' contents?

No. The tools work with links and readership statistics, not document contents. The one file it reads is the PDF you explicitly ask it to share, and that is read only to upload it.

### Can it delete something by accident?

Deleting a document moves it to the trash, where it can be restored - destroying one permanently requires an explicit instruction. Every irreversible tool is marked as such in the protocol, so clients that support confirmation prompts will ask before running it. If you would rather it could not write at all, set EVERYPAGE_READ_ONLY to true and only the read-only tools are offered.

### Do I need a paid plan?

No. Sharing documents and seeing who read them work on the free plan. Passcodes, view limits and page-by-page statistics need Basic; per-recipient links, the email-capture gate and content replacement need Pro.

### Is this different from the API, Zapier or n8n?

It is the same API underneath. Zapier, Make and n8n are for workflows you build once and leave running; this is for asking in the moment, in conversation. Many people use both - an assistant to share and check, a workflow to route new leads into a CRM.

### Is it open source?

Yes, MIT licensed, on GitHub, and published on npm and in the official MCP registry. The tool surface is snapshot-tested, so a tool cannot be renamed or removed without a deliberate release.

## Ask your assistant who read it.

Create an account, generate an API key, and paste four lines into your MCP client. The next document you share can answer for itself.

Related: all integrations · the developer API · the n8n node · raw webhooks · the DocSend alternative

---
URL: https://everypage.co/word-to-pdf
Title: Convert Word to PDF - Free, No Signup | EveryPage
Description: Convert a .docx to PDF free, no account needed, up to 25MB - and get a share link, QR code and embed for it. Add a password or expiry, and see page-by-page readership if you want it.

Word to PDF

# Convert Word to PDF

Convert a .docx to PDF free, no account needed, up to 25MB - and get a share link, QR code and embed for it. The conversion runs on our servers, and readership is reported page by page if you want it.

Drop your Word document here

or click anywhere in the tray to browse

Word .docx max 25MB · PDF max 20MB

Free · no account needed to start · PDF, or Word .docx up to 25MB

## Convert and share in one motion

Drop in the .docx and come out with a clean, professional PDF link - converted server-side, with no formatting surprises and no email attachment roulette.

## One link, with a QR code and embed

Every converted document comes with a share link, a QR code and an embed snippet. Send the link, print the code, or put the viewer on your own site - and the readership report shows how far each reader got.

## Protected like a PDF should be

Passwords, expiry, download control, watermarking, and gating - the full EveryPage toolkit applies to converted documents like any other.

## Why convert Word to PDF before sharing?

A Word file shared raw is a lottery: fonts substitute, layouts reflow, tracked changes and metadata travel with it, and every recipient gets an editable copy to alter and forward. Converting to PDF freezes the document you actually wrote - and sharing that PDF as an EveryPage link adds what an attachment can never do: control after sending, and readership while it is read.

The result is one URL that opens in any browser, looks identical everywhere, respects your protections, and tells you what happened - without storing a single reader IP address.

## How to convert Word to PDF online, free

1. Upload the .docx. Anywhere you can upload a PDF, you can upload a Word document - the homepage drop zone included. No account needed to try it; documents up to 25MB convert on every plan, the free one included.
2. EveryPage converts it. The conversion runs server-side and produces a fixed-layout PDF - nothing to install, and the original .docx never goes anywhere but to us.
3. Set your rules. Viewer mode, password, expiry, download policy, an email gate if you want names on the register - the same settings screen every EveryPage PDF gets.
4. Share one link. Email, Slack, a QR code on paper - and watch the readership arrive in your dashboard, page by page.

## Is it free?

Yes. Converting a Word .docx up to 25MB is free on every plan, and works without an account - an anonymous upload is shareable immediately and kept for 7 days. The free plan covers up to 3 PDFs with core readership; Basic and Pro add larger files, more documents and deeper reporting.

## Do I need an account?

No. Drop the .docx in the box above and you get the PDF share link, QR code and embed straight away. A free account is what puts the document in your library, lets you change its settings later and shows you the readership report - sign up from the same browser and the upload is claimed into it.

## What can I do with the converted PDF?

The output of the converter is not a second-class attachment - it is an EveryPage document like any other. Open it as a page-turning flipbook, a magazine spread, or a phone-friendly swipe deck; put a QR code on it; gate it behind an email; watermark it per viewer; let it self-destruct after a set number of views.

And because it renders in the EveryPage viewer, the same PDF read tracking applies: a read-through funnel, per-page reading time, and returning readers. Turn the report into a page-turning flipbook if it deserves better than scrolling.

## What happens after the conversion?

Most free Word to PDF converters hand you a file and stop. EveryPage hands you a hosted link: the PDF opens in any browser, with a QR code and embed alongside it, and you can allow downloads, set a password or an expiry, and replace the file later (Pro) without changing the link. Readership - per-page reading time, a read-through funnel, returning readers - is reported on the same link.

Word documents up to 25MB convert free. Once converted, the document follows your plan limits like any PDF - and if you need the reverse trip or heavier editing, prepare the file in your editor of choice first; EveryPage picks up where the writing ends.

## Word to PDF questions.

### How do I convert a Word document to PDF online for free?

Upload the .docx to EveryPage - the homepage drop zone works without an account - and it is converted to PDF server-side. Instead of a file to download you get a share link with readership built in. Conversion is included on every plan, the free one included, for Word documents up to 25MB.

### What Word files can EveryPage convert?

Word .docx documents up to 25MB, uploaded anywhere you can upload a PDF. The conversion happens on our servers, and the resulting PDF gets the full EveryPage toolkit: tracking, flipbook and magazine viewing modes, passwords, expiry, gates, and watermarking.

### Will my formatting survive the conversion?

The conversion renders your document to fixed PDF pages on the server, so fonts, spacing, and layout are frozen at conversion time - every reader sees the same pages you approved, instead of whatever their copy of Word decides to do with a .docx.

### Can I turn the converted document into a flipbook?

Yes. Once converted, the document is a normal EveryPage PDF - choose the flipbook, magazine, or swipe viewer mode, style it with your branding, and share the same link. Page-by-page readership works in every mode.

### Can I see who reads the converted PDF?

Yes. The share link reports views, per-page reading time, a read-through funnel, and returning readers - and with the email gate on, sessions are attributed by name. No reader IP addresses are ever stored.

### Is my document private during conversion?

The conversion runs on EveryPage servers - no third-party converter sees your file - and the resulting PDF is encrypted at rest with AES-256-GCM like every EveryPage document. You control expiry, downloads, and who can open it.

### Do I need an account to convert Word to PDF?

No. The conversion and the share link work without an account, and the upload is kept for 7 days. Signing up from the same browser claims it into your library, where you can set a password or expiry and see who read it.

## Share the document, keep the insight.

Convert the Word file, set your protections, and send one link that reports back.

Related: PDF read tracking · PDF flipbook maker · secure PDF sharing · dynamic links - replace the file, keep the URL · DocSend to PDF converter

---
URL: https://everypage.co/powerpoint-to-pdf
Title: Convert PowerPoint to PDF - Free, No Signup | EveryPage
Description: Convert a .pptx or .ppt to PDF free, no account needed, up to 50MB - and get a share link, QR code and embed for the deck. Add a password or expiry, and see slide-by-slide readership if you want it.

PowerPoint to PDF

# Convert PowerPoint to PDF

Convert a .pptx or .ppt to PDF free, no account needed, up to 50MB - and get a share link, QR code and embed for the deck. The conversion runs on our servers, one page per slide, and readership is reported slide by slide if you want it.

Drop your PowerPoint here

or click anywhere in the tray to browse

PowerPoint .pptx/.ppt max 50MB · PDF max 20MB

Free · no account needed to start · PDF, or PowerPoint up to 50MB

## Convert and share in one motion

Drop in the deck and come out with a clean PDF link - converted server-side, fonts and layouts frozen, no "can you resend that as a PDF?" round trips.

## One link, with a QR code and embed

Every converted deck comes with a share link, a QR code and an embed snippet. Send the link, print the code on the conference table, or put the viewer on your own site - and the readership report shows which slide each reader stopped on.

## Protected like a PDF should be

Passwords, expiry, download control, watermarking, and lead-capture gates - the full EveryPage toolkit applies to converted decks like any other document.

## Why convert PowerPoint to PDF before sharing?

A raw .pptx shared by email is a gamble: fonts substitute on machines without them, animations half-play or block the content, speaker notes travel with the file, and every recipient gets an editable deck to alter and forward. Converting to PDF freezes the slides you actually presented - and sharing that PDF as an EveryPage link adds what an attachment never has: control after sending, and readership while it is read.

The result is one URL that opens in any browser - no PowerPoint, Keynote, or download required - looks identical everywhere, respects your protections, and tells you what happened, without storing a single reader IP address.

## How to convert PowerPoint to PDF online, free

1. Upload the deck. Anywhere you can upload a PDF, you can upload a .pptx - or a legacy .ppt - the homepage drop zone included. No account needed to try it; decks up to 50MB convert on every plan, the free one included.
2. EveryPage converts it. The conversion runs server-side and produces a fixed-layout PDF, one page per slide - nothing to install, and the original deck never goes anywhere but to us.
3. Set your rules. Viewer mode, password, expiry, download policy, an email gate if you want names on the register - the same settings screen every EveryPage PDF gets.
4. Share one link. Email, Slack, a QR code on the conference table - and watch the readership arrive in your dashboard, slide by slide.

## Is it free?

Yes. Converting a .pptx or legacy .ppt up to 50MB is free on every plan, and works without an account - an anonymous upload is shareable immediately and kept for 7 days. The free plan covers up to 3 PDFs with core readership; Basic and Pro add larger files, more documents and deeper reporting.

## Do I need an account?

No. Drop the deck in the box above and you get the PDF share link, QR code and embed straight away. A free account is what puts the deck in your library, lets you change its settings later and shows you the readership report - sign up from the same browser and the upload is claimed into it.

## What can I do with the converted PDF?

The output of the converter is not a second-class attachment - it is an EveryPage document like any other. Present it as a page-turning flipbook, a magazine spread, or a phone-friendly swipe deck; put a QR code on it; gate it behind an email; watermark it per viewer; let it self-destruct after the deadline.

And because it renders in the EveryPage viewer, the same PDF read tracking applies: a read-through funnel, per-slide reading time, and returning readers. Turn the deck into a page-turning flipbook if it deserves better than scrolling.

## What happens after the conversion?

Most free PowerPoint to PDF converters hand you a file and stop. EveryPage hands you a hosted link: the deck opens in any browser - no PowerPoint or Keynote needed - with a QR code and embed alongside it, and you can allow downloads, set a password or an expiry, and replace the file later (Pro) without changing the link. Readership - per-slide reading time, a read-through funnel, returning readers - is reported on the same link.

PowerPoint files up to 50MB convert free - .pptx and legacy .ppt both. Once converted, the deck follows your plan limits like any PDF; if it leans on video or animation, export those slides as stills first, because a PDF page is a still page.

## PowerPoint to PDF questions.

### How do I convert a PowerPoint to PDF online for free?

Upload the .pptx or .ppt to EveryPage - the homepage drop zone works without an account - and it is converted to PDF server-side. Instead of a file to download you get a share link with readership built in. Conversion is included on every plan, the free one included, for decks up to 50MB.

### What PowerPoint files can EveryPage convert?

Modern .pptx and legacy .ppt files up to 50MB, uploaded anywhere you can upload a PDF. The conversion happens on our servers, and the resulting PDF gets the full EveryPage toolkit: tracking, flipbook and swipe viewing modes, passwords, expiry, gates, and watermarking.

### Will my slides survive the conversion?

The conversion renders each slide to a fixed PDF page on the server, so fonts, spacing, and layout are frozen at conversion time - every reader sees the slides you approved, not whatever their copy of PowerPoint decides to substitute. Animations and embedded video become stills, as in any PDF export.

### Can I present the converted deck as a flipbook or swipe deck?

Yes. Once converted, the deck is a normal EveryPage PDF - choose the flipbook, magazine, or phone-friendly swipe viewer mode, style it with your branding, and share the same link. Per-slide readership works in every mode.

### Can I see who reads the deck?

Yes. The share link reports views, per-slide reading time, a read-through funnel, and returning readers - and with the email gate on, sessions are attributed by name. No reader IP addresses are ever stored.

### Is my presentation private during conversion?

The conversion runs on EveryPage servers - no third-party converter sees your file - and the resulting PDF is encrypted at rest with AES-256-GCM like every EveryPage document. You control expiry, downloads, and who can open it.

### Do I need an account to convert PowerPoint to PDF?

No. The conversion and the share link work without an account, and the upload is kept for 7 days. Signing up from the same browser claims it into your library, where you can set a password or expiry and see who read the deck.

## Share the deck, keep the insight.

Convert the PowerPoint, set your protections, and send one link that reports back.

Related: PDF read tracking · PDF flipbook maker · Word to PDF converter · sales deck sharing · DocSend to PDF converter

---
URL: https://everypage.co/docsend-to-pdf
Title: DocSend to PDF Converter - Free, Handles Email & Passcode Gates | EveryPage
Description: A free DocSend to PDF converter that handles email and passcode gates: paste the link you were sent, enter the details the sender gave you, and download the deck as a PDF you can keep.

DocSend to PDF

# DocSend to PDF converter

Paste a DocSend link you were sent, get a PDF you can keep. Free, no account.

Export a deck you were sent

Paste the DocSend link. If the sender asked for an email or passcode, use the one they gave you.

Free · no account needed · single documents up to 20MB

Free · no account needed · single documents, up to 20MB

## For decks you were sent

This is the recipient side of a DocSend link: you already have access, and you want the document in a format you own rather than a browser tab you might lose.

## Email and passcode gates supported

If the sender put the deck behind an email address or a passcode, enter what they gave you and the export continues - the same details you would type into the viewer.

## A PDF and a link

Download the file, or share the hosted link EveryPage creates for it - complete with a QR code and the option to claim it into an account later.

## 3 ways to save a DocSend deck as a PDF

### 1. Use this converter

1. Paste the DocSend link. It should look like docsend.com/view/… - a single document. Multi-document DocSend spaces (docsend.com/s/…) are not supported yet.
2. Enter the details the sender gave you. Many decks ask for an email address, and some add a passcode. The form only appears when the deck actually asks, and what you type goes straight to DocSend - the same as typing it into their viewer.
3. We export the pages. Each page is captured as it renders and assembled into a single PDF. A deck of twenty pages takes a few seconds; a long one takes a little longer.
4. Download it, or share it. You get a PDF to keep and a hosted EveryPage link for the same document. Sign up from the same browser and the link becomes yours to manage, rename, protect, or delete.

### 2. Use the Chrome extension

If the sender enabled DocSend's download button, you do not need a converter at all - take the PDF they offered. What the EveryPage Chrome extension adds is what comes after: right-click any PDF link in the browser, or upload the file from the toolbar popup, and it becomes a hosted EveryPage link with readership built in. For view-only decks with no download button, the converter above is the way in.

### 3. Ask the sender for the file

The shortest route to a copy with selectable text is still the original file. The converter's output is image-based, so when you need to search, quote, or edit, ask the sender for the source - most will send it once they know why you want it. And a deck shared view-only carries a signal worth respecting: keep your copy, and leave forwarding it as the sender's call.

## What this tool does not do

It matters more to be straight about the limits than to oversell the feature, so here they are.

- The output is image-based. Pages are exported as they render, so the PDF looks right but the text is not selectable or searchable. If you need the original file with live text, ask the sender for it.
- It only works with access you already have. If a deck is gated, you need the email or passcode the sender gave you - there is nothing here that opens a document you were not invited to.
- Single documents only, for now. A DocSend Space bundles several files behind one link, and there is no single deck to export; open each document and convert its own link.
- Respect the sender's intent. Someone sharing view-only usually has a reason. Keeping a copy of a deck you were sent is normal; forwarding it onward is the sender's call, not yours - if in doubt, ask them.

## DocSend to PDF questions.

### How do I save a DocSend document as a PDF?

Paste the docsend.com/view/… link into the converter above. If the deck asks for an email address or a passcode, enter the one the sender gave you. EveryPage exports the pages and hands you a PDF to download, plus a hosted link for the same document. It is free and no account is needed.

### Does this work on decks that ask for an email or passcode?

Yes, when you have the details. The converter detects the gate and asks you for the same email or passcode you would type into the DocSend viewer, then continues. It cannot open a deck you have no credentials for, and it does not try.

### Will the PDF have selectable text?

No. Pages are exported as they render, so the PDF is image-based: it looks like the deck, prints like the deck, and can be annotated, but the text is not searchable. If you need live text, ask the sender for the source file.

### Can I convert a DocSend Space with several documents?

Not yet. A Space link (docsend.com/s/…) bundles several documents, so there is no single deck to export. Open each document from the Space and convert its own view link.

### Is it OK to save a copy of a deck someone sent me?

Keeping a copy of a document you were given access to is ordinary - people do it to read offline, annotate, or file it. What is not yours to decide is redistribution: if the sender shared it view-only, treat forwarding it as their call and ask first.

### What happens to the PDF you create?

It is stored encrypted and reachable at the share link you get, kept for 7 days. Nobody can find it without the link. Sign up from the same browser and it becomes a document you own: claiming stops the expiry unless you chose one yourself, and you can change it at any time - including to never - or delete it.

### Is there a converter that handles passcode-protected decks?

Yes - this one. When a deck sits behind a passcode or an email gate, the converter shows the same fields the DocSend viewer would, passes what you type straight to DocSend, and then exports the pages. It needs the passcode the sender gave you: nothing here bypasses a gate you were not invited through.

## Sharing your own deck? Let readers keep it - and still see who read it

If you are on the other side of this - the one sending decks and wondering whether to allow downloads - you do not have to choose between "let people keep a copy" and "know whether they read it."

Share your PDF as an EveryPage link and flip a single per-file toggle to decide whether readers can download it. Either way you get page-by-page reading time, a read-through funnel, and returning-reader detection - without ever storing a reader's IP address.

## Send your next deck as a link that reports back.

Same document, one URL - with readership, access controls, and a download toggle you decide.

Related: DocSend alternative · PDF read tracking · secure PDF sharing · DocSend converter docs

---
URL: https://everypage.co/pdf-read-receipts
Title: PDF Read Receipts - Know They Opened It | EveryPage
Description: Add a read receipt to a shared PDF: the reader taps “Mark as received” and you see who confirmed and when - an explicit acknowledgement, not a tracking pixel. A Basic-plan feature, switched on per document, with an optional email on receipt.

PDF read receipts

# A PDF read receipt the reader confirms

Add a read receipt to a shared PDF: the reader taps "Mark as received" and you see who confirmed and when - an explicit acknowledgement they choose to send, not a tracking pixel. Read receipts are a Basic-plan feature switched on per document; uploading and sharing is free.

Drop your PDF here

or click anywhere in the tray to browse

PDF only · max 20MB

Free · no account needed to start · read receipts are a Basic feature, switched on per document

## A receipt they choose to send

The reader taps "Mark as received" in the viewer. It is an explicit confirmation - not a silent pixel - so a receipt means someone actually acknowledged the document, not that a preview loaded.

## Who, and when

Every receipt is stamped with the moment it was sent and tied to the reading session behind it. Invite readers by name and the receipt carries their name and email instead of an anonymous mark.

## One receipt per reader

A reader confirms once. Returning to the document does not re-fire the receipt, so your list of confirmations stays a clean roll-call rather than a pile of duplicates.

## Optional email-on-receipt

Want to hear about it without watching the dashboard? Switch on email-on-receipt and EveryPage emails you when a reader confirms - throttled so a busy document never buries your inbox.

## What is a PDF read receipt?

An email attachment tells you nothing after you press send: you cannot tell whether the contract was opened, whether the policy handbook was acknowledged, or whether the board pack reached the whole board. A read receipt closes that gap. The reader taps a button to confirm they received the document, and that acknowledgement sits in your report next to the reading session it belongs to - so delivery and readership live in one place.

A receipt is deliberately an explicit act, not a tracking trick. It answers a different question from a view count: not "did the pages load" but "did this person acknowledge the document". Underneath it is the full PDF read tracking you get on every EveryPage link - views, per-page reading time, and returning readers - with the receipt as the human confirmation on top.

## Is a PDF read receipt the same as an email read receipt?

No. An email read receipt is a tracking pixel: a tiny image that fires when a mail client loads the message, whether or not anyone read it, and many mail clients block it. An EveryPage read receipt is the opposite: nothing is sent until the reader taps "Mark as received" in the viewer, so a receipt means a person acknowledged the document. It arrives with a timestamp, the reading session behind it, and the reader’s name and email if you invited them by name - and page-by-page readership sits underneath it separately, so you can still see that a document was opened even if nobody tapped.

## How read receipts work

- Turn it on per document. Read receipts are a per-document toggle in the sharing settings - on for the contract, off for the newsletter. No new link, no new file.
- The reader confirms. A "Mark as received" button appears in the viewer. The reader taps it once to acknowledge the document; nothing is sent until they do.
- You see the confirmation. Each receipt appears in your readership report with a timestamp and, when the reader was invited by name, their name and email - not just an anonymous count.
- One receipt per reader. A confirmation fires once per reader and does not repeat on later visits, so the list of who acknowledged stays accurate rather than inflated.
- Get emailed, optionally. Switch on email-on-receipt to be notified when a reader confirms - the notifications are throttled so a document read by many people sends you a manageable trickle, not a flood.

## When do you need a read receipt on a PDF?

Read receipts turn "I sent it, I hope they saw it" into a record. Send a contract and get an acknowledgement that the counterparty received the terms. Circulate a policy handbook or a compliance notice and collect a confirmation from each employee. Deliver client work as a link and have proof it landed. Distribute a board pack and see which directors have acknowledged it before the meeting rather than chasing round the table.

Receipts sit behind the same gate stack as the file itself, so a document protected by a password or an email gate only ever collects receipts from readers who got past it - and if you distributed the link with secure PDF sharing or sent it to a named list with a named contact list, the receipt inherits that identity automatically.

## Read receipt questions.

### What is a PDF read receipt?

A read receipt is an explicit confirmation from a reader that they received your document. On EveryPage, the reader taps a "Mark as received" button in the viewer, and the confirmation appears in your readership report with a timestamp - and their name and email if you invited them by name. It is an acknowledgement someone chooses to send, not a silent tracking signal.

### How is a receipt different from a view count?

A view count tells you the pages loaded; a read receipt tells you a specific person acknowledged the document. EveryPage records both - full page-by-page readership underneath, and the receipt as a human confirmation on top - so you can distinguish "it was opened" from "they told me they got it".

### Do I see who sent the receipt?

If you invited the reader by name or gated the document behind an email, yes - the receipt carries their name and email. For an anonymous link, you see the receipt and its timestamp tied to the reading session, without a name attached, because EveryPage never stores a reader’s IP address.

### Can one reader send multiple receipts?

No. A reader confirms once; coming back to the document later does not fire another receipt. Your list of confirmations stays a clean roll-call of who has acknowledged the document rather than a count that inflates on every revisit.

### Can I be emailed when someone confirms?

Yes. Turn on email-on-receipt and EveryPage emails you when a reader marks the document as received. The notifications are throttled, so a document confirmed by many people sends you a steady trickle rather than burying your inbox.

### Which plan includes read receipts?

Read receipts are available from the Basic plan ($9/month) and switch on per document. Every plan stores files encrypted at rest and lets you set an expiry; Pro adds named reader identities, the email gate, and per-viewer watermarking on top.

### Is a PDF read receipt the same as an email read receipt?

No. An email read receipt is a tracking pixel that fires when the message loads, whether or not anyone read it. An EveryPage read receipt is sent only when the reader taps "Mark as received" in the viewer - an explicit acknowledgement with a timestamp and, for invited readers, their name and email. Whether the document was merely opened is reported separately by page-by-page readership.

## Get the acknowledgement.

Upload a document, switch on read receipts, and share one link that tells you not just that it was opened - but that someone confirmed they got it.

Related: PDF read tracking · secure PDF sharing · send a PDF to contacts

---
URL: https://everypage.co/google-analytics-pdf
Title: Track a PDF in Google Analytics (GA4) | EveryPage
Description: Add your GA4 Measurement ID to a shared PDF link and views fire gtag events straight into your own Google Analytics property, next to your site.

Google Analytics for PDFs

# Your PDF, in your Google Analytics

Paste your GA4 Measurement ID onto a share link and every non-owner view sends a gtag event into your own Google Analytics property - the same GA4 that measures your website, now measuring your documents too.

Drop your PDF here

or click anywhere in the tray to browse

PDF only · max 20MB

Free to start · GA4 forwarding is a Pro feature · add your Measurement ID on the settings step

## One field: your Measurement ID

Drop your GA4 Measurement ID (the G-XXXXXXXXXX from your own property) onto a link. Non-owner views load gtag with that ID and fire an event - no tag manager, no code on your side.

## Your property, your data

The events land in the GA4 property you own and control. EveryPage never sees your Analytics data - it just carries your ID into the viewer so Google reports the view to you, not to us.

## Alongside your website

Because it is your GA4, document views sit next to your site traffic - same audiences, same reports, same attribution - so a shared deck becomes another page in the property you already watch.

## Owner views excluded

Your own visits to your document do not fire the event, so you are not polluting your own Analytics every time you open the link to check it - the same principle as owner-excluded readership.

## Bring your documents into the property you already watch

You already measure your website in GA4. A PDF you share as a link is, for once, measurable the same way: add your Measurement ID to the link and each non-owner view fires a Google Analytics event into your property. The document shows up in the reports you already read every morning, attributed to the same audiences and campaigns as the rest of your site - no separate dashboard to remember.

It is genuinely your data. EveryPage does not receive, store, or proxy your Analytics - it simply loads Google’s gtag with the ID you provided when a non-owner opens the document. The events go straight from the reader’s browser to Google, into the property you own.

## How to send PDF views to GA4

1. Copy your Measurement ID. In your own GA4 property, grab the Measurement ID - it looks like G-XXXXXXXXXX. It is the same ID your website already uses.
2. Paste it onto the link. Add the ID in the share link’s settings. That link now carries your GA4 into the viewer for anyone who opens it.
3. Non-owner views fire an event. When someone who is not you opens the document, the viewer loads gtag with your ID and sends a page-view style event to your property. Your own views are excluded.
4. Read it in GA4. The events appear in your Google Analytics reports next to your website traffic - realtime, audiences, acquisition, the lot - because it is your property doing the counting.

## Honest about ad-blockers

Here is the part most tools will not tell you: Google Analytics is one of the most heavily blocked scripts on the web. A large share of readers run ad-blockers or privacy browsers that suppress gtag entirely, so a meaningful fraction of your document’s real audience will never show up in GA4 - through no fault of the setup. GA is great for joining documents to the rest of your Google-measured world; it is not a reliable headcount.

That is why EveryPage’s own first-party PDF readership stays the source of truth. It is first-party and privacy-first - no third-party script to block, no reader IP stored - so it counts the views GA4 misses. Use GA4 for the cross-channel picture, and use EveryPage’s readership for the number you actually trust.

## Where GA4 forwarding fits

GA4 forwarding is the marketer’s integration: it puts a gated whitepaper, a pricing PDF, or a campaign brochure into the same funnel as the landing page that links to it, so attribution does not fall off a cliff at the document’s edge. If you would rather push each view into Slack, a spreadsheet, or your own stack in real time, EveryPage’s webhooks do that on any event - a complement to GA4, not a replacement.

Both can run at once: GA4 for the cross-channel report, webhooks for live automation, and EveryPage’s built-in readership as the reliable, ad-blocker-proof count underneath them both.

## Google Analytics for PDFs questions.

### How do I track a PDF in Google Analytics?

Add your GA4 Measurement ID (G-XXXXXXXXXX) to an EveryPage share link in its settings. When a non-owner opens the document, the viewer loads Google’s gtag with your ID and fires an event into your own GA4 property - the same one that measures your website. There is no code to write and no tag manager to configure.

### Whose Google Analytics does the data go to?

Yours. The events go into the GA4 property whose Measurement ID you provided, straight from the reader’s browser to Google. EveryPage never receives, stores, or proxies your Analytics data - it only carries your ID into the viewer so Google attributes the view to you.

### Do ad-blockers affect the numbers?

Yes, significantly. Google Analytics is one of the most widely blocked scripts on the web, so readers using ad-blockers or privacy browsers will not appear in GA4 at all. That is why EveryPage’s own first-party readership - which has no third-party script to block - stays the reliable count, and GA4 is best used for joining documents to your wider Google-measured funnel.

### Are my own views counted?

No. Owner views are excluded from the GA4 event, just as they are from EveryPage’s built-in readership, so opening your own document to check it does not pollute your Analytics with self-visits.

### Do I need to add anything to my PDF or my site?

No. You paste your Measurement ID onto the EveryPage link and nothing else changes - no code in the PDF, no snippet on your website. The viewer handles loading gtag for non-owner views.

### Which plan includes GA4 forwarding?

Sending PDF views to your own Google Analytics is a Pro feature ($29/month). Every plan includes EveryPage’s first-party readership, which counts views GA4 misses; Pro adds the GA4 Measurement ID field and named reader identities. Webhooks are included on every plan.

## Put your documents in GA4.

Upload a PDF, paste your Measurement ID, and share a link that reports into your own Google Analytics - with EveryPage’s reliable readership underneath it.

Related: first-party PDF read tracking · webhooks & Slack

---
URL: https://everypage.co/branded-pdf-viewer
Title: Branded PDF Viewer - Your Logo, Colour & CTA | EveryPage
Description: Put your logo on the PDF viewer, with your accent colour, toolbar theme, and a CTA button, EveryPage badging removed - a Pro feature; flipbook logo and badge removal from Basic. CTA clicks tracked.

Branded PDF viewer

# Put your logo on the PDF viewer

Put your logo, accent colour, and call-to-action button on the PDF viewer and take EveryPage badging off - a Pro feature; flipbook branding with your logo starts on Basic. The reader sees your brand around the pages, not ours.

Drop your PDF here

or click anywhere in the tray to browse

PDF only · max 20MB

Free to start · viewer branding is a Pro feature · style it on the settings step

## Your logo, placed

Upload your logo and set its position and size in the viewer toolbar. It sits with the document on every device, so a client deck opens under your mark, not a generic one.

## Colour & theme

Set an accent colour that carries through buttons and highlights, and choose a light or dark toolbar theme to match your brand - so the frame around the pages looks like it belongs to you.

## A call-to-action button

Add a CTA button to the viewer with your own label, URL, style, and position - "Book a call", "See pricing", "Get in touch" - and every click is tracked, so the document becomes a channel, not a dead end.

## Badging off

Remove EveryPage badging entirely. The viewer reads as yours end to end, which is exactly what a client presentation, a lookbook, or an agency deliverable needs.

## Can I put my own logo on a PDF viewer?

Yes. On Pro, upload your logo and set its position and size in the viewer toolbar, pick the accent colour that runs through buttons and highlights, choose a light or dark toolbar theme, add a call-to-action button with your own label and URL, and remove EveryPage badging entirely. On Basic, flipbook branding already puts your logo in any corner of the viewer, linked back to your site, over a background of your choice.

Branding lives on the link, so the same document can open plainly for an internal draft and fully branded for the client version - no re-export. It pairs naturally with a custom domain: serve the document from docs.yourcompany.com and the URL, the frame, and the pages all carry one identity, with no seam for the reader to notice.

## Can I remove EveryPage branding?

Yes. On Pro, the branded viewer switches EveryPage badging off entirely, so nothing on the page points back to us - the viewer is a white-label surface for your brand alone. On Basic, the flipbook editor lets you remove the EveryPage badge from a flipbook and add your own logo. Pair either with a custom domain (Pro) and the URL, the frame, and the pages all carry one identity.

## What you can brand

- Logo, position and size. Upload your logo and choose where it sits in the toolbar and how large it appears - understated or prominent, your call.
- Accent colour. Pick the colour that runs through the viewer’s buttons and highlights so the interface matches your palette rather than ours.
- Light or dark toolbar. Choose the toolbar theme that flatters the work - a dark frame for photography and lookbooks, a light one for reports and decks.
- Badge position. Decide where the branding badge sits, or take it out of the corners entirely - the layout is yours to arrange.
- A custom CTA button. Set the label, destination URL, button style, and position of a call-to-action on the viewer. Every click is tracked, so you can see the document driving the next step.
- EveryPage badging removed. Switch off our badging so nothing on the page points back to us - the viewer is a white-label surface for your brand alone.

## For agencies, decks, and lookbooks

Branded viewing is what turns a shared PDF into a deliverable. An agency hands clients work that opens under the agency’s mark; a sales team sends a deck framed in company colours with a "Book a call" button on every page; a studio presents a lookbook in a dark, distraction-free frame that lets the photography carry the room. In each case the branding is not decoration - it is the difference between a document that looks sent and one that looks published.

Branding also composes with the way the document reads. Style the frame, then present the pages as a page-turning flipbook that turns like print, or make them an interactive PDF experience with links and hotspots - one branded surface, however you choose to show the work.

## Branded viewer questions.

### Can I put my own logo on the PDF viewer?

Yes. On Pro, upload your logo and set its position and size in the viewer toolbar; combined with your accent colour, a light or dark theme, badge placement, and a custom call-to-action button, the viewer reads as your brand around the document rather than a generic one. On Basic, flipbook branding puts your logo in any corner of the viewer, linked to your site.

### Can I remove EveryPage branding?

Yes. On Pro, the branded viewer lets you switch off EveryPage badging entirely, so nothing on the page points back to us - a white-label surface for a client deck, an agency deliverable, or a lookbook. On Basic, you can remove the EveryPage badge from a flipbook in the flipbook editor.

### What is the call-to-action button?

It is a button you add to the viewer with your own label, destination URL, style, and position - for example "Book a call" or "See pricing". Every click is tracked in your readership report, so the document becomes a channel that drives the next step instead of a dead end.

### Does branding work with a custom domain?

It pairs perfectly. Serve the document from your own domain, such as docs.yourcompany.com, and combine it with viewer branding so the URL, the frame, and the pages all carry one identity with no visible seam. The two features are designed to be used together.

### Can the same document be branded for some links and plain for others?

Branding is configured per document, so you can keep an internal draft plain and turn on full branding for the client-facing version without re-exporting the file. Change the frame any time; the pages stay the same.

### Which plan includes viewer branding?

Custom viewer branding - logo, accent colour, theme, badge control, the CTA button, and badging removal - is a Pro feature ($29/month). Pro also includes custom domains, which pair naturally with branded viewing.

## Make the viewer yours.

Upload a document, add your logo, colour, and call-to-action, take our badging off, and share a link that opens under your brand alone.

Related: custom domains · PDF flipbook maker · interactive PDF

---
URL: https://everypage.co/pdf-folders
Title: PDF Folders with Folder-Wide Analytics | EveryPage
Description: Organise your shared PDFs into folders with drag and drop - a Basic feature, and no share link ever changes. Each folder rolls up views, readers, and completion across the set.

PDF folders

# Organise your PDFs into folders

Organise your shared PDFs into folders by client, campaign, or project - a Basic feature, with drag and drop, and no share link ever changes. Each folder also rolls up the views, readers, and completion of everything inside it.

Drop your PDF here

or click anywhere in the tray to browse

PDF only · max 20MB

Free · no account needed to start · folders and roll-up analytics are a Basic feature

## Folders for your documents

Group related PDFs into a folder - a campaign, a client, a quarter - so your library stops being a flat list and starts being a filing system you can actually navigate.

## Drag and drop

Arrange documents by dragging them into and between folders. Reorganise as work shifts, without renaming files or breaking a single share link.

## Folder-wide analytics

Every folder rolls up the readership of the documents inside it - total views, total readers, and completion across the set - so you can read a whole campaign’s performance at a glance.

## Links stay put

Filing a document into a folder never changes its share link, QR code, or settings. Organisation is for your side of the desk; the reader’s link keeps working exactly as it did.

## What are PDF folders for?

Share enough documents and the library becomes the problem: a long, flat list where the January proposal sits next to the client lookbook next to last week’s menu. Folders give the file room its shelves. Group by campaign, by client, by quarter, or however your work divides, and the documents you need are together instead of scattered - and rearranging is a drag, not a rename.

Because a folder is just an organising layer, it never touches the documents inside it. Every share link, QR code, password, and expiry stays exactly as configured - filing a PDF away is invisible to the people you sent it to.

## How folders work

- Create a folder. Make a folder for a campaign, a client, or a project, and give it a name that means something to you.
- Drag documents in. Drag and drop PDFs into folders and between them. Nothing about the file or its link changes - only where it lives in your library.
- Read the roll-up. Open a folder and see aggregated readership across everything inside it: total views, total readers, and completion for the whole set.
- Drill into any document. The per-document readership is still there - page-by-page reading time, the read-through funnel, returning readers - one click below the folder roll-up.
- Reorganise any time. Move a document to a new folder as priorities change; its history and its share link come with it untouched.

## What are folder-wide analytics?

The roll-up is what makes folders more than tidiness. When a client engagement is five documents or a campaign is a dozen brochures, the question is rarely "how did this one file do" - it is "how did the whole set perform". A folder answers that directly: aggregated views, readers, and completion across every document inside it, so you can compare one campaign against another or report a client’s total engagement without adding up numbers by hand.

Folders build on the same privacy-first per-document readership as every EveryPage document - first-party, no reader IP stored - and pair naturally with a named contact list: send a whole folder’s worth of documents to a named list, then read the folder roll-up to see how that audience engaged across the set.

## Can I share a whole folder as one link?

No. Folders organise your own library; readers never see them. Each document keeps its own share link, QR code, password, and settings, and there is no folder-level link to hand out. To put several documents in front of the same people, send each link to a named contact list, then read the folder roll-up to see how that audience engaged across the set.

## PDF folder questions.

### How do I organise my PDFs into folders?

Create a folder in your EveryPage library and drag documents into it. Folders can represent a campaign, a client, a project, or anything else, and you can drag and drop PDFs between them at any time. Filing a document never changes its share link, QR code, or settings.

### What are folder-wide analytics?

Each folder rolls up the readership of every document inside it into one aggregated view - total views, total readers, and completion across the whole set. Instead of adding up individual files by hand, you read a campaign or a client’s total engagement at a glance, then drill into any single document for its page-by-page detail.

### Does moving a document to a folder change its link?

No. Folders are an organising layer on your side only. A document’s share link, QR code, password, expiry, and every other setting stay exactly as configured when you file it or move it between folders, so the people you shared it with never notice a thing.

### Can I still see analytics for a single document?

Yes. The per-document readership - page-by-page reading time, the read-through funnel, returning readers - is always available, one click below the folder roll-up. Folders add an aggregated layer on top; they do not replace the detail underneath.

### Can I reorganise folders later?

Any time. Drag documents into new folders as your work shifts, and each document’s history and share link move with it untouched. There is no penalty for reorganising - the file room is yours to rearrange.

### Which plan includes folders?

Folders and folder-wide roll-up analytics are available from the Basic plan ($9/month). Every plan stores files encrypted at rest with privacy-first readership; Pro adds named reader identities, custom domains, and viewer branding on top.

### Can I share a whole folder as one link?

No. Folders are an organising layer on your side only - there is no folder-level link for readers. Each document keeps its own share link, QR code, and settings; to send several documents to the same audience, send each link to a named contact list and use the folder roll-up to read their engagement across the set.

## Give your library its shelves.

Upload your documents, group them into folders, and read a whole campaign’s readership in one roll-up - without a link ever changing.

Related: PDF read tracking · send a PDF to contacts

---
URL: https://everypage.co/dynamic-qr-pdf-links
Title: Dynamic QR PDF Links - New File, Same URL | EveryPage
Description: Update the PDF behind a link or printed QR code without changing the URL: short link, QR, password, and slug persist, and versions are kept.

Dynamic links

# One QR code, always the latest PDF

Replace the PDF behind an EveryPage link or printed QR code without changing the URL or reprinting the code - the next scan serves the new file. Free to try, no signup required; replacing the file is a Pro feature.

Drop your PDF here

or click anywhere in the tray to browse

PDF only · max 20MB

Free to start · replacing the file behind a link is a Pro feature

## Print once, update forever

A QR code on a menu, a brochure, or a shop window is expensive to reprint and impossible to recall. Point it at an EveryPage link and the code never goes stale - you update the PDF, the paper stays where it is.

## Everything persists

The short link, the QR code, the password, the email gate and lead form, the vanity slug on your custom domain - every setting rides through a replacement untouched. Only the pages change.

## Version history, kept

Every version you replace is kept in the document's history, so you always know exactly what was live on any given day - useful when the document is a price list or a legal notice.

## Readership per version

Each visit records which version it saw. When the funnel improves after an update, you can prove it was the new pages - not a different audience.

## Do I need to reprint my QR codes when I update the PDF?

No. The QR code encodes the EveryPage share link, not the file. Replace the PDF behind the link and every printed code serves the new version on the next scan - same URL, same short link, same password and settings. Nothing to regenerate, nothing to reprint.

## Printed QR codes that never go stale

Print is where a broken link hurts most: a QR code on a laminated table menu, a property brochure in a rack, signage in a window. The moment the document changes, a static code is a reprint job. A dynamic EveryPage link inverts that - the code on the paper is permanent, and the PDF behind it is whatever you say it is today.

That is the daily workflow for restaurant QR menus - update the dishes, keep the table cards - and for real estate brochures, where the brochure behind the sign changes as the listing does. One code on the printed material, forever; the file swapped from your library in seconds.

## What survives a replacement

- The URL and short link. Every copy of the link anyone ever saved, sent, or bookmarked now serves the new file.
- The QR code. Printed or on screen, the code is unchanged - it points at the link, and the link points at the new version.
- Protections and gates. Password, expiry, download policy, the email gate, lead capture forms, and the domain allowlist all carry over exactly as configured.
- Your domain and slug. A vanity slug on your custom domain keeps resolving - readers on docs.yourcompany.com never see a seam.
- Branding and viewer mode. Flipbook styling, your logo, the CTA button, the chosen reading mode - the presentation is part of the link, not the file.

## Version history and per-version readership

Replacing a file is not overwriting it. EveryPage keeps the version history, and the readership record notes which version every visit saw - so the reporting stays honest across updates. If page 3 stopped losing readers after Tuesday's revision, the funnel will show it, version by version.

That turns a dynamic link into an experiment you can actually read: ship a revised deck behind the same link you already sent, and compare how the new pages perform against the old ones with the same audience.

## Replacing a file revives a burned link

A self-destructing link deletes itself when its view budget is spent - and normally that is the end of the story. Replacing the file behind it starts a new chapter: the link comes back to life serving the new version, with a fresh budget and the full readership record of its previous life intact. One-time delivery, repeatable.

## How to replace the PDF behind a link

1. Open the document in your library. Every document you own has a replace option alongside its sharing settings.
2. Upload the new file. A PDF - or a Word .docx, which is converted on the way in. The old version moves into the history.
3. Done - the link already points at it. No settings to redo, no QR to regenerate, nothing to resend. Readers who open the link now get the new pages.

## Dynamic link questions.

### What is a dynamic PDF link?

A dynamic PDF link is a share link whose underlying file you can replace without changing the URL. On EveryPage, replacing the PDF behind a link keeps the short link, QR code, password, gates, and custom-domain slug exactly as they were - every existing copy of the link, printed QR codes included, serves the new version instantly.

### Can I change the PDF behind a QR code without reprinting it?

Yes. The QR code encodes the link, not the file - so when you replace the PDF behind an EveryPage link, every printed code that points at it serves the new document on the next scan. Menus, brochures, signage, and product inserts never need a reprint for a content change.

### What happens to the old version when I replace a file?

It is kept in the document's version history rather than destroyed, and your readership record notes which version each visit saw - so you can tell how the document performed before and after any update, and what was live on a given date.

### Do passwords, gates, and my custom domain survive a replacement?

Yes - all of it. The password, expiry, download policy, email gate, lead capture form, domain allowlist, branding, viewer mode, and any vanity slug on your custom domain persist through a replacement. Only the file changes.

### Can replacing the file revive a self-destructed link?

Yes. A self-destructing link that has spent its view budget and deleted its file comes back to life when you replace the file behind it - the same URL starts serving the new version, and the readership record of the previous version survives.

### Which plan includes dynamic links?

Replacing the file behind an existing link is a Pro feature ($29/month, or $290/year - two months free). Every plan can create links and QR codes; Pro adds replacement, version history, and per-version readership on top.

### Do I need to reprint my QR codes when I update the PDF?

No. The printed code points at the EveryPage share link, not the file, so replacing the PDF behind the link updates what every existing code opens on the next scan. The URL, short link, password, and settings stay the same.

## Put a permanent code on it.

Upload the document, print the QR once, and never let paper hold your content hostage again.

Related: PDF to QR code · restaurant QR menus · real estate brochures · self-destructing links · custom domains

---
URL: https://everypage.co/use-cases
Title: PDF Sharing Use Cases - Proofing, Menus & Decks | EveryPage
Description: Tracked PDF links by trade and by document type - pitch decks, proposals, brochures, catalogs, menus - with flipbooks, QR codes, and lead capture.

Use cases

# One tracked link, many trades

The same idea - share a PDF as a link you control, and see exactly how it was read - does a different job in every line of work. Find yours below.

Every link carries the same toolkit: a polished in-browser viewer with flipbook, magazine, and swipe modes, page-by-page readership analytics, QR codes, and a security layer that runs from passwords to per-viewer watermarking. What changes is which parts earn their keep - a photographer leans on watermarked proofs and per-page comments, a restaurant leans on a QR code and instant menu updates, a sales team leans on knowing which slide lost the room.

Each page below walks through one trade in detail: the workflow, the features doing the work, and the plan they live on. Files are AES-encrypted at rest and no reader IP address is ever stored - whatever you share, privacy is the default.

## Pick your trade.

Photography proofing

Send proofing galleries as watermarked flipbooks, take comments on individual pages, and let client previews expire on your schedule.

Real estate

Property brochures as flipbooks, QR codes on the For Sale sign, lead capture from every brochure view, and readership that shows real buyer interest.

Sales decks

See which slide loses them, capture the lead before page one, put a book-a-call button on the deck, and let pricing self-destruct after the decision.

Course materials

Gate course PDFs behind an email, scope them to your cohort with a domain allowlist, embed video with hotspots, and collect read receipts.

Restaurant menus

A QR menu that opens as a swipeable flipbook - no app, no reprints. Update the PDF and the code on the table serves the new menu.

Portfolios & lookbooks

Magazine-mode lookbooks on your own domain, styled with your branding, measured with GA4 and page-by-page readership.

## Share any document as a link.

Pick your document type for the features that matter for it.

Pitch deck

See which slide lost the investor

Proposal

Know when the pricing page was read

Brochure

Flipbook plus a QR code that survives reprints

Catalog

One link for every seasonal edition

Price list

Old links always show the current prices

Menu

A QR menu you can change without reprinting

Portfolio & lookbook

Full-bleed flipbook for visual work

Report

Read receipts, then self-destruct

Whitepaper

Gate it behind an email, score leads by read depth

Case study

Follow up the moment a prospect reads it

Ebook

Book-style reading with a completion rate

One-pager

A link and QR code in seconds

## The features doing the work.

Every use case above is assembled from the same parts. Go deeper on any of them:

PDF read tracking · PDF flipbook maker · PDF to QR code · lead capture forms · per-viewer watermarking · self-destructing links · secure PDF sharing · reader comments · interactive PDF hotspots · custom domains · Word to PDF conversion · PowerPoint to PDF conversion · dynamic QR links

## Your document, your rules.

Upload a PDF, pick the viewer mode and protections that fit your trade, and share one link that reports back.

---
URL: https://everypage.co/use-cases/photography-proofing
Title: PDF Proofing Galleries for Photographers | EveryPage
Description: Send photo proofs as a watermarked flipbook link: clients comment on individual pages, previews self-destruct, and you see what held their eye.

Use case: photography

# Proofing galleries clients actually respond to

Export your selects to a PDF, share one flipbook link, and get comments pinned to individual images - with a watermark on every page and an expiry date on the whole preview.

Send your selects for proofing

or click anywhere in the tray to browse

PDF only · max 20MB

Free to try · watermarking is a Pro feature · viewer and protection settings come on the next step

## A gallery that turns pages

The flipbook and magazine modes present your selects like a printed album, not a scrolling file dump - branded, immersive, with real page turns and full-screen viewing in both.

## Comments pinned to the page

Clients leave feedback on the exact image they mean - "this one, but warmer" attached to page 12 - without creating an account. Private to you, or visible to every viewer.

## Watermarked previews

Per-viewer watermarking tiles each page with the viewer's identity and a timestamp, and any downloaded copy is permanently stamped - so unpaid previews stay previews.

## Previews that expire

Set the gallery to self-destruct after a number of views or a date - the classic "proofs available for 14 days" policy, enforced by the link itself.

## The proofing round, without the chaos

Most proofing rounds die in the gap between "here is a folder of files" and "which ones do you want?". Attachments get downloaded once and forgotten; feedback arrives as a jumble of filenames in an email thread; and nobody can say whether the client ever really looked. An EveryPage proofing link closes that gap: one URL opens the whole gallery in the browser, on any device, with nothing for the client to install or sign up for.

Because the gallery is a tracked link rather than a file, you also get the answer to the question every photographer asks after sending proofs: did they look yet? Your readership report shows when the gallery was opened, which pages were viewed, how long each image held their eye, and whether they came back for a second pass - usually the sign a decision is close.

## The workflow, feature by feature

- Export selects to PDF, upload, pick flipbook mode. One image per page works best - each page becomes a commentable, trackable unit. Magazine mode suits albums and duo layouts.
- Turn on per-page comments. Clients pick favourites and request edits on the exact page, signed with their name or anonymous. You read them all in one thread on the document.
- Watermark the preview (Pro). Every page carries the viewer identity and timestamp; allowed downloads are stamped into the file itself. Pair with right-click and print blocking for good measure.
- Set the expiry policy. A view budget, a deadline, or both - and when the final gallery is paid for, share a clean, unwatermarked link that can live as long as you like, including forever.

## Readership as a sales signal

The per-page analytics do double duty as a soft sales tool. When the report shows the client spent four minutes on the canvas-wrap spread and returned to it twice, you know which print upsell to lead with on the follow-up call. When half the gallery was never opened, you know the second round of selects should be smaller.

And because readership is recorded even after a preview link burns, the record of who reviewed which proofs - and when - outlives the gallery itself. Useful the day a client insists they never saw the proofs before the print deadline.

## Photography proofing questions.

### How do I send photo proofs to a client as one link?

Export your selects to a PDF (one image per page works best), upload it to EveryPage, and pick the flipbook or magazine viewer mode. You get a single link that opens the gallery in the browser on any device - no client account, no app, nothing to download.

### Can clients comment on individual photos?

Yes. Reader comments can be attached to a specific page, so feedback lands on the exact image it refers to. Clients comment without an account, and you choose whether comments are private to you or visible to every viewer.

### Can I stop clients keeping unpaid previews?

You can make it genuinely unattractive: per-viewer watermarking (Pro) tiles every page with the viewer identity and timestamp, downloads can be blocked entirely or permanently stamped, and right-click and print blocking stops casual saving. No tool can prevent a photograph of a screen - but a watermarked preview makes a poor substitute for the real files.

### Can the proofing gallery expire automatically?

Yes. Set a view budget or a deadline (or both) and the link deletes itself on cue - a "proofs available for 14 days" policy the link enforces for you. Your readership record of every viewing session survives the expiry.

### Which plan do photographers need?

The free plan covers trying the workflow on a real gallery. Basic ($9/month) adds password protection, self-destructing links, and full per-page analytics. Pro ($29/month) adds per-viewer watermarking, custom branding on the viewer, and your own domain on the link.

## Send the next gallery as a link.

Upload a PDF of your selects, switch on comments and a watermark, and share a proofing round that reports back.

Related: photo proofing & page marks · PDF flipbook maker · per-viewer watermarking · reader comments · self-destructing links · portfolios & lookbooks · automate the proofing feedback · all use cases

---
URL: https://everypage.co/use-cases/real-estate
Title: Real Estate PDF Flipbooks - Tracked Brochures | EveryPage
Description: Turn property brochures into tracked flipbook links: QR codes for signage, lead capture from every view, and readership that shows serious buyers.

Use case: real estate

# Property brochures that report buyer interest

Share every listing brochure as a flipbook link with a QR code on the signage - and know which buyers opened it, how far they read, and who to call first.

Send your next listing brochure

or click anywhere in the tray to browse

PDF only · max 20MB

Free to try · lead capture is a Pro feature · viewer and QR settings come on the next step

## A brochure that turns pages

The flipbook viewer presents a listing the way the print brochure does - full-bleed spreads, page-turn and all - in any browser, on any phone at the kerb.

## QR codes on the signage

Every link comes with a downloadable QR code. Put it on the For Sale board, the window card, and the printed one-pager - every scan opens the tracked brochure.

## Leads from brochure views

Put a lead capture form in front of the brochure and every interested buyer leaves a name and email before page one - straight into your dashboard, CSV export for the CRM.

## Interest you can measure

Per-page readership shows who lingered on the floor plan, who returned three times, and who bounced off the asking price - the difference between a browser and a buyer.

## From window card to warm lead

A property brochure works hardest when you can no longer see the person reading it - stuck to a window, printed on a flyer, forwarded from spouse to spouse. Shared as a static PDF attachment, all of that activity is invisible. Shared as an EveryPage link, every route into the brochure feeds one readership report: the QR scan at the kerb on a Sunday evening, the email link from the portal enquiry, the forward to the co-buyer.

The QR code matters more than it first appears. A passer-by at the sign is the warmest possible audience - they are literally standing at the property - and a scan is the only way they can take the brochure home. EveryPage QR codes are stable PNGs tied to the link, so the same board artwork keeps working even as you update the brochure behind it.

## The workflow, feature by feature

- Upload the brochure, pick flipbook mode. The designed PDF you already produce for print becomes the interactive version - no rebuild, no separate microsite.
- Print the QR code everywhere. Signboard, window card, flyer, portal listing. Scans are tracked as their own source, so you learn which placement actually pulls.
- Gate it with a lead form (Pro). Name, email, phone - your choice of up to five fields. Serious buyers trade details for the full brochure; the readership report attaches their reading behaviour to the contact.
- Work the readership before the follow-up. Returning readers and long floor-plan dwell times are your call-first list. A viewing-day link that has burned through its view budget tells you demand outstripped the slot.

## One brochure, always current

Listings change - price reductions, new photography, an under-offer banner. Because the link is the product, you update the PDF and every QR code, email, and portal link already in the world serves the new version. Nothing is reprinted except nothing: the board at the property keeps working.

For agencies, Pro adds the finish: the viewer carries your branding and accent colour, the link lives on your own domain, and GA4 integration folds brochure traffic into the marketing reporting you already run.

## Real estate brochure questions.

### How do I put a property brochure behind a QR code?

Upload the brochure PDF to EveryPage and download the QR code that comes with the link. Print it on the signboard, window card, or flyer - every scan opens the brochure as a flipbook in the browser, and scans appear in your readership report as their own source.

### Can I capture buyer details from the brochure?

Yes - with a lead capture form (Pro), readers enter their details before the brochure opens: up to five fields, email validated server-side. Captured leads land in your dashboard with their reading behaviour attached, and export to CSV for your CRM.

### What does the readership report tell me about buyers?

When each reader opened the brochure, which pages they viewed and for how long, whether they returned, and how they arrived (QR scan, email, portal). Long dwell on the floor plan and repeat visits are the classic signals of a serious buyer.

### What happens when the listing changes?

Update the PDF behind the link and every QR code and shared link serves the new version immediately. Printed boards, window cards, and portal links all stay current without reprinting anything.

### Can the brochure carry our agency branding?

On Pro, yes - your logo, accent colour, and a custom CTA button on the viewer, plus the link on your own domain. GA4 integration is available if your marketing team wants brochure traffic in their own reporting.

## Put the next listing on a link.

Upload the brochure, print the QR code, and know exactly which buyers read it - before the follow-up call.

Related: PDF to QR code · dynamic QR links · PDF flipbook maker · lead capture forms · PDF read tracking · sales decks & proposals · automate viewing requests · all use cases

---
URL: https://everypage.co/use-cases/sales-decks
Title: Sales Deck Tracking - See Which Slide Loses Them | EveryPage
Description: Share sales decks as tracked links: per-page analytics show which slide loses prospects, lead capture names readers, and pricing self-destructs.

Use case: sales

# Know which slide loses the deal

Send the deck as a tracked link and stop selling blind: see who opened it, where they stalled, who came back to pricing - and put a book-a-call button on every page.

Share your next sales deck

or click anywhere in the tray to browse

PDF only · max 20MB

Free to try · lead capture and the CTA button are Pro features · settings come on the next step

## Per-slide readership

Time on every page and a read-through funnel across the deck. When 80% of readers stall on slide 7, slide 7 is the problem - fix the deck, not the pitch.

## Every reader named

An email gate or lead form (Pro) means no more anonymous "3 views". You know it was the CFO who spent four minutes on pricing - and that the champion forwarded it internally.

## A CTA on the deck

Add a custom button to the viewer - "Book a call", straight to your calendar link. The deck stops being a dead end and becomes the next step in the funnel.

## Pricing that expires

Send the quote on a self-destructing link: a view budget or a validity date, enforced by the link. The offer disappears on schedule; your record of who read it survives.

## The silence after send, solved

Every seller knows the dead air after a deck goes out. Did they open it? Did it get past the first skim? Is the deal stalled or just slow? An attachment answers none of this. A tracked link answers all of it: the moment of first open, every page viewed with its reading time, return visits, and - with the read-through funnel - the exact slide where attention died.

That last number changes behaviour on both sides of the send. Follow-ups stop being "just checking in" and become specific: the prospect who reread the integration slide twice gets the technical case study; the one who never reached pricing gets a shorter deck next time. And across a quarter, the funnel tells you which slides earn their place in the master deck at all.

## The workflow, feature by feature

- Send a link, not an attachment. The deck opens in the browser on any device. You can update it after sending - fix the typo, refresh the pricing - and every copy already in inboxes opens the new version.
- Name the readers (Pro). The email gate attributes every session to a person; the domain allowlist keeps a confidential deck inside the client company. Forwards inside the account show up as new named readers - your buying committee map, drawn for you.
- Put the next step on the page (Pro). A custom CTA button rides the viewer - calendar link, order form, whatever closes. The reader who just finished the case-study slide is one click from the meeting.
- Burn the quote on schedule. "This pricing is valid until Friday" becomes real: the quote link self-destructs on the date, and the readership record proves who saw it and when.

## Notifications, receipts, and the follow-up

View notifications email you the moment the deck is opened - the highest-signal moment to be available - and read receipts let the prospect confirm delivery on the record. Live presence (Pro) shows who is reading right now, which turns the classic "shall I call them?" into a fact rather than a guess.

None of this costs the prospect anything: no account, no download, no plugin. They click a link and read; you stop guessing. Files are encrypted at rest and no reader IP is stored, so the security review at bigger accounts has less to object to.

Sending a proposal rather than a deck? See how to send a proposal as a link.

## Sales deck tracking questions.

### How do I see which slide of my deck loses prospects?

Share the deck as an EveryPage link and open the read-through funnel in your readership report. It shows the percentage of readers who reached each page and the time spent on every slide - the drop-off point is where the deck (or the offer) needs work.

### Can I tell exactly who read the deck?

Yes, on Pro: the email gate requires readers to enter a working email before the deck opens, so every session is attributed to a named person. Add the domain allowlist to keep the deck inside the client company only.

### Can prospects book a call straight from the deck?

On Pro you can add a custom CTA button to the viewer - label and destination are yours, so "Book a call" can point at your calendar link. It stays visible while they read, on every page.

### How do I make a quote expire on a deadline?

Set the link to expire on a date (every plan), self-destruct after a view budget (Basic and up), or both. When it triggers, the link returns "Gone" - but your readership record of who read the quote, and when, stays in the dashboard.

### Do prospects need to install or sign up for anything?

No. The deck opens in the browser on any device from a plain link. Only you need an account; readers just read.

## Send the next deck tracked.

Upload the deck, gate it, put a book-a-call button on it, and know before the follow-up exactly how it was read.

Related: PDF read tracking · send it to a contact list · lead capture forms · self-destructing links · share a PDF with analytics · send a proposal as a link · pitch decks · real estate brochures · automate read alerts · all use cases

---
URL: https://everypage.co/use-cases/course-materials
Title: Share Course Materials as Gated PDF Links | EveryPage
Description: Distribute course PDFs on links you control: email gating, a domain allowlist for cohorts, read receipts, and readership showing what students read.

Use case: education

# Course materials with a register attached

Share workbooks, readings, and handouts on gated links scoped to your cohort - with embedded video, read receipts, and a page-by-page picture of what was actually studied.

Hand out your course pack

or click anywhere in the tray to browse

PDF only · max 20MB

Free to try · email gating and hotspots are Pro features · gate settings come on the next step

## Gated to your students

An email gate puts a register in front of every document; the domain allowlist scopes it to your institution or client domain, so materials stay inside the cohort.

## Video inside the workbook

Draw a hotspot on any page and attach video, audio, an image, or a link - the walkthrough video lives on the page it explains, and every play is counted.

## Read receipts on the record

Students confirm they received and read the material, and the confirmation sits next to their reading session - useful for compliance trainings and prework.

## Who studied, who skimmed

Per-page time and the read-through funnel show which chapters were worked through and which were skipped - before the cohort shows up underprepared.

## Distribution is easy - accountability is the feature

Any LMS can hand a PDF to a student. What it usually cannot tell you is what happened next: whether the prework was opened the night before or never, whether the cohort actually reached chapter four, whether the struggling student is behind because the material is hard or because it is unread. An EveryPage link answers with data: every session, every page, every minute of reading time - per student when the email gate is on.

For paid courses and corporate training, the same gate is the access control. Materials shared as raw attachments are shared forever, with anyone; a gated link checks every reader against the register, and the domain allowlist limits access to the company or campus you sold the course to. When the cohort ends, expire the links - or leave them up forever. Your call, not the file format’s.

## The workflow, feature by feature

- Upload the materials, gate them (Pro). One link per workbook or module. The email gate validates addresses server-side; the allowlist scopes access to your cohort domains.
- Embed the media with hotspots (Pro). Video walkthroughs, audio pronunciation guides, links to exercises - drawn straight onto the page they belong to, played without leaving the document.
- Turn on read receipts (Basic). Students confirm completion in the viewer; the receipt lands next to their session. For compliance modules, that is the audit trail.
- Teach from the readership. The funnel shows where the cohort stalled; per-page time shows which sections dragged. Revise the material where the data says to, not where the loudest student does.

## Updates, comments, and the long tail

Course materials are living documents. Fix an erratum or refresh a chapter and every link already distributed serves the new version - no re-uploads to the LMS, no "please use v3" emails. Reader comments let students ask questions on the exact page that confused them, privately to you or visibly to the class.

Privacy holds up in institutional reviews: readership is measured first-party in the viewer, no student IP address is ever stored, and files are encrypted at rest. You get the register and the reading data without collecting anything a data-protection officer will object to.

## Course material questions.

### How do I restrict course PDFs to enrolled students?

Put the document behind the email gate (Pro) and add your cohort domains to the allowlist - for a university cohort, the campus domain; for corporate training, the client company domain. Readers outside those domains are refused at the gate, and every session inside is attributed to a named student.

### Can I embed video lectures in the course PDF?

Yes - interactive hotspots (Pro) let you draw a region on any page and attach video, audio, an image, or a link. Students play the video right on the page, and every interaction is counted in your readership report.

### How do I know whether students did the reading?

The readership report shows every session per student (with the email gate on): pages read, time per page, and the read-through funnel across the document. Read receipts add an explicit confirmation for compliance-style trainings.

### What happens when I update the materials mid-course?

Replace the PDF behind the link and every student link serves the new version immediately - nothing to redistribute. The readership history carries straight on.

### Which plan do educators need?

Free covers trying it with a handout. Basic ($9/month) adds read receipts, per-page analytics, and password protection. Pro ($29/month) adds the email gate, the domain allowlist, and hotspots for embedded media; on every plan a link never expires unless you set an expiry, so evergreen materials stay up.

## Put the syllabus on links.

Upload a workbook, gate it to your cohort, embed the walkthrough video, and see exactly what was studied.

Related: interactive PDF hotspots · secure PDF sharing · PDF read tracking · send materials to a cohort list · reader comments · restaurant menus · all use cases

---
URL: https://everypage.co/use-cases/restaurant-menus
Title: QR Code Menu from a PDF - Free, No App, No Reprints | EveryPage
Description: Make a QR code menu from a PDF free, no account needed: guests scan and swipe in the browser, no app. Change the menu and every printed code serves the new version (replacing the file is a Pro feature).

Use case: restaurants

# Make a QR code menu from a PDF

Make a QR code menu from a PDF free, no account needed - guests scan with their camera and swipe through the menu in the browser, no app. Change the menu later and every printed code serves the new version (replacing the file behind a link is a Pro feature).

Put your menu behind one QR code

or click anywhere in the tray to browse

PDF only · max 20MB

Free to try · custom branding is a Pro feature · viewer and QR settings come on the next step

## Scan, swipe, order

The swipe viewer is built for one-handed phones at a table: pages flick horizontally, load fast, and read clean. Flipbook mode gives the wine list its page-turn.

## Reprint nothing

The QR code points at the link, not the file. Update prices, 86 a dish, launch the seasonal menu - the code on every table serves the new PDF the moment you upload it.

## No app, no friction

Guests scan with the camera they already have and the menu opens in the browser. No download, no sign-up, no 'please install our app' - the whole thing is one scan.

## Your look, your domain

On Pro the viewer carries your logo, colours, and background - and the link can live on your own domain, so the URL under the code reads like your restaurant, not ours.

## How do I make a QR code menu from a PDF?

Upload the menu PDF - the same artwork you print - and pick the swipe viewer on the next step. You get a share link and a QR code PNG with it: print the code on table cards, window vinyl or delivery inserts, and guests scan it with the phone camera to open the menu in the browser. Swipe mode reads best for single-column menus; flipbook and magazine suit multi-page food and wine books.

The economics are the point. A printed menu change costs a design round and a reprint for every copy in the room; an EveryPage menu change costs uploading the new PDF. The QR codes on the tables, the window, and the delivery flyers never change - they point at the link, and the link always serves the current menu.

## Do I need to reprint the QR codes when the menu changes?

No. The QR code points at the link, not at the file. Replace the PDF behind the link (a Pro feature) and every code already printed serves the new menu on the next scan - the URL, the code and its settings stay exactly as they were.

- Upload the menu PDF, pick swipe mode. Use the same artwork you print. Swipe mode reads best for single-column menus; flipbook and magazine suit multi-page food and wine books.
- Print the QR code once. Table cards, window vinyl, delivery inserts. The code is a stable PNG tied to the link - laminate it and forget it.
- Update by replacing the PDF (Pro). New prices tonight, truffle menu next week - upload the new file and every code in the room is current. No app store, no CMS, no reprint.
- Brand the viewer (Pro). Logo, accent colour, background - and a custom CTA button that can point at your booking page or ordering system.

## Is it free?

Yes. Upload a menu PDF without an account and you get the link and QR code straight away - anonymous uploads are kept for 7 days. The free plan covers up to 3 active PDFs, and the link never expires unless you set an expiry; Basic ($9/month) covers a full menu set; Pro ($29/month) adds replacing the file behind the code, your branding and your own domain.

Every scan is a tracked view, so the readership report doubles as light operational data: how many guests open the menu per service and which pages they linger on. Guests stay anonymous - readership is measured first-party in the viewer and no IP address is ever stored.

## QR menu questions.

### How do I turn my menu PDF into a QR code?

Upload the PDF to EveryPage and download the QR code that comes with the link. Print it on table cards or window vinyl - guests scan with their phone camera and the menu opens as a swipeable viewer in the browser. The whole setup takes a few minutes.

### Do guests need to install an app?

No. The menu opens in the phone browser straight from the camera scan - no app, no account, no download. That is the whole point.

### How do I update prices without reprinting the QR codes?

Replace the PDF behind the link - a Pro feature. The QR code points at the link, not the file, so every printed code immediately serves the new menu. Codes never need reprinting for a menu change.

### Can the menu match our restaurant branding?

On Pro, yes - your logo, accent colour, and background on the viewer, a custom button (for bookings or online ordering), and the link on your own domain so the URL reads as yours.

### What does a QR menu cost?

The free plan works for a single menu with up to 3 active PDFs, and the link never expires unless you set an expiry. Basic ($9/month) covers a full menu set; Pro ($29/month) adds branding and your own domain - a fraction of one print run.

## Put tonight’s menu on a code.

Upload the menu PDF, print the code once, and never pay for a price-change reprint again.

Related: PDF to QR code · dynamic QR links · PDF flipbook maker · custom domains · course materials · all use cases

---
URL: https://everypage.co/use-cases/portfolios-lookbooks
Title: Digital Lookbooks & Portfolios from a PDF | EveryPage
Description: Publish lookbooks and portfolios as magazine-mode links on your own domain: your branding on the viewer, GA4 reporting, and per-page readership.

Use case: portfolios

# A lookbook that looks like you made it

Magazine-mode spreads, your logo and colours on the viewer, your domain on the URL - and a readership report that shows which pages of the portfolio did the convincing.

Share your portfolio or lookbook

or click anywhere in the tray to browse

PDF only · max 20MB

Free to try · branding, custom domains, and GA4 are Pro features · settings come on the next step

## Magazine mode

Two-page spreads around a centre spine shadow, artwork edge to edge - the format lookbooks are designed in. And the pages actually turn: drag a corner and the leaf curls over in 3D, just as the printed book behaves. On phones the same book adapts to single pages, page-turn intact.

## Your name on everything

On Pro the viewer carries your logo, accent colour, and background, and the link lives on your own domain - the client experience is yours end to end, no third-party frame.

## GA4 in your reporting

Connect your GA4 property and lookbook traffic lands in the analytics stack your studio already reports from - alongside the site, not in a silo.

## Readership per spread

Per-page time shows which projects held attention and which got flicked past - so the next portfolio edit is driven by data, not attachment to your favourite project.

## The portfolio send is a pitch - treat it like one

A portfolio or lookbook send is usually the highest-stakes PDF a studio ships: it goes to a prospective client, a buyer, a gallery, and the silence afterwards is total. Sharing it as an EveryPage link keeps the presentation impeccable - magazine spreads that turn like the printed book, artwork edge to edge, on any device - and replaces the silence with a report: opened Tuesday evening, eleven minutes, the editorial project read twice, the brand-identity spread skipped.

That readership is portfolio strategy. Across ten sends you learn which projects consistently hold attention and which never get reached because they sit too deep in the book. The next edit is informed: lead with what lands, cut what gets flicked past, and keep the book short enough that the funnel says people finish it.

## The workflow, feature by feature

- Upload the book, pick magazine mode. The same PDF your printer gets. Spreads render as designed, and readers turn them like the physical book - drag, flick, or tap. On phones the magazine adapts to single-page reading automatically, with the same page turns. For a phone-first audience, choose swipe mode instead: the book reads as a fullscreen story - one page per card under a segmented progress bar, tapped through with a thumb.
- Brand the viewer, claim the URL (Pro). Logo, colours, background, and a custom domain - so the link in your email signature reads portfolio.yourstudio.com, not a vendor URL.
- Wire up GA4 (Pro). Lookbook views flow into the same GA4 property as your site, so campaign attribution and studio reporting see the whole funnel.
- Read the report before the follow-up. Which spreads held them, whether they returned, how they arrived. The follow-up email references the project they actually lingered on.

## Control, without making it precious

A lookbook wants to travel - but on your terms. Download control keeps the high-res book un-saveable when that matters; per-viewer watermarking (Pro) names every copy of an unreleased collection; and a season’s preview can self-destruct the day of the launch. The same link can also live forever: expiry is entirely your choice.

Reader comments turn the send into a conversation - a buyer marking the pieces they want to see in the showroom, page by page. And updating the book behind the link means the URL printed on your business card is never out of date.

## Portfolio & lookbook questions.

### How do I share a lookbook so it keeps its layout?

Upload the print PDF to EveryPage and choose magazine mode - spreads render as two-page pairs around a centre spine, exactly as designed, and readers drag, flick, or tap to turn the pages like the physical book. On phones the same link adapts to single-page reading with the same page turns. Readers need no account or app.

### Can the lookbook live on our own domain?

Yes - custom domains are a Pro feature. Connect your domain and share links like lookbook.yourstudio.com, with your logo, colours, and background on the viewer. The vendor disappears from the client experience.

### Does EveryPage work with Google Analytics?

On Pro you can connect your GA4 property, and lookbook views are reported into your own analytics alongside your site traffic - campaign tags and attribution included.

### Can I see which projects in my portfolio get attention?

Yes - per-page readership shows time spent on every spread and the funnel shows how deep readers get. Over multiple sends this is the data for editing the book: lead with what holds attention, cut what gets skipped.

### Can I protect an unreleased collection?

Yes - block downloads and printing, watermark every page per viewer (Pro), and set the preview link to self-destruct on the reveal date. Your readership record of who saw it survives.

## Ship the book, keep the byline.

Upload the lookbook, put your name on the viewer and the URL, and know which spreads did the convincing.

Related: PDF magazine viewer · PDF flipbook maker · PDF story mode · photo proofing & page marks · custom domains · per-viewer watermarking · PDF read tracking · photography proofing · all use cases

---
URL: https://everypage.co/use-cases/pitch-deck
Title: Share Your Pitch Deck as a Tracked Link | EveryPage
Description: Send your pitch deck as a private link. See which slides investors read, where they dropped off, and update the deck without resending. Free to start.

Share as a link: pitch deck

# Share your pitch deck as a tracked link

Send investors a link instead of an attachment. See the moment it opens, which slides they read and the exact slide where they stopped - then swap in the new version mid-raise without sending another email.

Share your pitch deck

or click anywhere in the tray to browse

PDF only · max 20MB

Free to start · per-slide analytics from Basic, replacing the deck behind the link is Pro · privacy settings come on the next step

## Slide-by-slide drop-off

The read-through funnel (from Basic) shows the share of investors who reached each slide and the time they spent on it, so you know which slide lost them.

## Know the moment it’s opened

A view notification (from Basic) emails you when the deck is opened, so the follow-up lands while the partner is still thinking about it.

## Swap the deck, keep the link (Pro)

Replace the file behind the link and every investor who already has it opens the new version - no v7_final_FINAL attachment chasing the old one.

## Self-destruct after the round

Cap the link at a number of views (from Basic) or set an expiry date, and the deck stops opening once the round is closed - your record of who read it stays.

## See which slide lost the investor

A pitch deck sent as an attachment tells you nothing after it leaves. Sent as an EveryPage link it opens in the browser, and every session is recorded page by page: when it was opened, how long each slide held attention, whether the reader came back. The read-through funnel (from Basic) draws the drop-off across the deck, so "they passed" becomes "they stopped reading at the traction slide".

That is a different kind of feedback from a polite no. If most investors stall on the same slide, the deck has a problem you can fix before the next meeting. If one fund read the financials three times, that is the one to chase. Reader IPs are never stored, so you get the reading data without collecting anything you would have to explain.

## What a fundraising deck link needs

- No reader IPs, ever. Readership is measured first-party in the viewer and no IP address is stored, so tracking the deck never puts an investor’s privacy in question.
- Password or self-destruct for stealth rounds (from Basic). Put a password on the link for a quiet raise, or cap it at a number of views so a forwarded copy runs out before it reaches the wrong fund.
- Upload the PowerPoint as it is. .pptx and .ppt files up to 50MB convert to PDF on upload, so the deck you built in PowerPoint or exported from Keynote goes straight to a link with the slides exactly as designed.
- A link that never expires. Signed-in links have no expiry unless you set one, so the deck link in your intro emails and data room stays live for as long as the raise takes - and after it.

## Update the deck mid-raise without resending

Every founder has sent a deck and found the typo an hour later, or closed a new customer the week after the deck went out. With an attachment the fix is another email and a v7_final_FINAL in every investor’s inbox. With a dynamic link (Pro) you replace the PDF behind the link and every copy already sent opens the new version - same URL, same QR code, readership history intact.

Investors who saved the link see the current deck. Investors who downloaded a copy keep what they downloaded, which is one reason to leave downloads off for a raise. Either way, one link is the deck, and you never chase an old version around.

## Pitch deck sharing questions.

### Is it free to share a pitch deck as a link?

Yes. The free plan covers up to 3 PDFs of 20MB each with core readership - views, readers and time spent - and the link never expires unless you set an expiry. Per-slide analytics and the read-through funnel start on Basic ($9/month); replacing the deck behind the link is Pro ($29/month).

### Can I upload a PowerPoint or Keynote deck?

Upload .pptx or .ppt files up to 50MB and EveryPage converts them to PDF for the link. For Keynote, export to PowerPoint or PDF first - both work, and PDF keeps your fonts exactly as designed.

### Do investors know the deck is tracked?

Nothing is hidden: the deck opens as a normal document link in the browser, with no account, download or plugin. What is recorded is pages and time per session, never an IP address, and a reader is only named if you put an email gate on the link (Pro).

### Can I change the deck after I have sent the link?

Yes, on Pro. Replace the file behind the link and every investor who already has it opens the new version on their next visit - the URL, QR code and readership history stay as they were. On Free and Basic, upload the new deck as a new link.

### Can I stop investors forwarding the deck?

You can make it hard: turn downloads off, add a password and a view limit (from Basic), and on Pro gate it behind an email and restrict it to chosen domains. No tool can stop a screenshot, so a deck that must stay private still needs the meeting, not just the link.

## Send the deck as a link.

Upload the pitch deck, share one link with every investor, and know which slide the round turns on. Selling to customers rather than investors? The sales deck page covers that.

Related: pitch deck investor analytics guide · PDF read tracking · DocSend alternative · PowerPoint to PDF · self-destructing links · one-pagers · sales decks for sales teams

---
URL: https://everypage.co/use-cases/proposal
Title: Send a Proposal as a Link and Track It | EveryPage
Description: Send your proposal as a link instead of an attachment. Know when the client opens it, how long they spend on pricing, and fix typos without resending.

Share as a link: proposal

# Send your proposal as a link, not an attachment

The client gets one link that opens in the browser. You get an alert when it is opened, the time spent on the pricing page, and a way to correct the proposal without a "v2 attached" email.

Send your proposal as a link

or click anywhere in the tray to browse

PDF only · max 20MB

Free to start · page analytics and opened alerts from Basic, revising in place is Pro · access settings come on the next step

## Pricing-page read time

Per-page analytics (from Basic) show how long the client spent on the pricing page and whether they came back to it - the signal a follow-up call should open with.

## Opened alerts

A view notification (from Basic) emails you the moment the proposal is opened, and a read receipt lets the client confirm delivery on the record.

## Fix it without a v2 (Pro)

Replace the file behind the link and the client’s copy is the corrected one - no second attachment, no "please ignore the previous version".

## Expire on the deadline

Set the link to expire on the proposal’s validity date, or cap it at a number of views (from Basic), and the offer closes when you said it would.

## Know when the pricing page gets read

A proposal is really three documents: the scope the client reads once, the pricing page they read several times, and the sign-off page they reach only if the first two worked. An attachment tells you none of this. A proposal sent as an EveryPage link records every session page by page - the first open, the time on each section, the return visits - and per-page analytics (from Basic) put a number on how long pricing held them.

That number changes the follow-up. Four minutes on pricing and no visit to the sign-off page is a negotiation waiting to happen; a thirty-second skim of the whole thing is a client who has not decided to read it yet. Both deserve a different call, and now you know which one to make. Reader IPs are never stored, so the client is measured, not surveilled.

## What a proposal link does that an attachment can’t

- Read receipts (from Basic). The client confirms receipt inside the viewer and the confirmation sits next to their reading session - useful when a deadline turns on "we never got it".
- Page analytics without IPs. Every page view is measured first-party in the viewer and no reader IP is ever stored, so tracking a client’s proposal stays on the right side of your own privacy policy.
- A password for one-client proposals (from Basic). A proposal with a bespoke rate should not travel; a password on the link keeps it with the people you quoted.
- Upload the Word file as it is. .docx proposals up to 25MB convert to PDF on upload, so the document you wrote in Word becomes a link without an export step.

## Revise the proposal without a "v2" attachment

Proposals change after they are sent: a typo in the totals, a scope line the client asked to add, a discount agreed on the call. With an attachment every change is another email, and the client’s inbox ends up holding three versions with no way to tell which one is current. With a dynamic link (Pro) you replace the PDF behind the link, and the one link the client already has opens the revised proposal.

The readership history carries on across the revision, so you can see whether the client re-read the pricing page after the change. Downloads can be turned off per document if you would rather the proposal is always read from the link, and the link never expires unless you set the deadline yourself.

## Proposal sharing questions.

### Is it free to send a proposal as a link?

Yes. The free plan covers up to 3 PDFs of 20MB each with core readership - views, readers and time spent - and no card is required. Per-page analytics, opened alerts, read receipts and passwords start on Basic ($9/month); replacing the proposal behind the link is Pro ($29/month).

### Can I upload a proposal written in Word?

Yes. Upload the .docx (up to 25MB) and EveryPage converts it to PDF for the link, keeping your layout. If your proposal tool exports PDF directly, that works too.

### Will the client know the proposal is tracked?

The client opens a normal link in the browser - no account, no download. Sessions record pages and time, never an IP address, and the client is only identified by name if you put an email gate on the link (Pro). If you turn on read receipts they are asked to confirm receipt, which is visible by design.

### Can I update the proposal after sending it?

On Pro, yes: replace the file behind the link and the client’s existing link opens the revised version, with the URL and readership history unchanged. On Free and Basic, upload the revision as a new link.

### Can the proposal expire after the deadline?

Yes, on every plan: set an expiry date on the link and it returns "Gone" once the validity period ends. From Basic you can also cap it at a set number of views. Your record of who read it, and when, stays in your dashboard either way.

## Send the next proposal as a link.

Upload the proposal, send one link, and know when the pricing page was read before you pick up the phone.

Related: proposal tracking guide · proposal read alerts in your CRM · PDF read receipts · Word to PDF · secure PDF sharing · sales decks for sales teams

---
URL: https://everypage.co/use-cases/brochure
Title: Turn a PDF Brochure into a Link or QR Code | EveryPage
Description: Share your brochure as a flipbook link or QR code. Print the QR once, update the PDF any time, and see which pages people actually read. Free to start.

Share as a link: brochure

# Share your brochure as a flipbook link

Upload the print PDF and get a page-turning flipbook link and a QR code for the printed piece. Readers open it on any phone, you see which pages they read, and the QR code keeps working when the brochure changes.

Turn your brochure into a link

or click anywhere in the tray to browse

PDF only · max 20MB

Free to start · flipbook, magazine and swipe modes on every plan · replacing the file behind a printed QR code is Pro

## Page-turn flipbook

The brochure opens as a flipbook with real page turns, or in magazine mode for two-page spreads, on every plan.

## QR code for print

Every link comes with a QR code PNG - put it on the printed brochure, the stand banner or the shop window, and a phone camera opens the digital version.

## Reprint-proof QR (Pro)

The code points at the link, not the file: replace the PDF behind it and every code already printed opens the new brochure.

## See the pages that sell

Per-page analytics (from Basic) show which spread readers linger on and where they close the brochure, so the next edition leads with what works.

## A brochure that reads like print, on any phone

A brochure is designed as spreads, and a PDF attachment throws that away: the reader gets a vertical scroll of single pages, zoomed to nothing on a phone. An EveryPage link opens the same PDF as a flipbook with page turns, or in magazine mode so facing pages sit together the way the designer laid them out. Swipe mode is there for a single-column brochure read one-handed.

Nothing is installed and nothing is downloaded: the reader scans or taps, and the brochure opens in the browser. Readership is measured first-party in the viewer, with no reader IP stored, so a brochure link at a trade show collects reading data without collecting personal data.

## Built for brochures that live in print and online

- A dynamic QR code (Pro). The printed code stays the same across every edition, because it points at the link and the link serves whatever PDF is behind it.
- Flipbook, magazine or swipe. Pick the viewer mode on the next step: flipbook for the page-turn, magazine for spreads, swipe for phones. All four modes are on every plan.
- A branded viewer. Logo, background and page effects on the flipbook from Basic; accent colour, toolbar theme and your own domain on Pro - so the digital brochure looks like yours from the URL down.
- A link that never expires. Signed-in links have no expiry unless you set one, so the code on a brochure printed this year still opens next year.

## Change the brochure, not the QR code

Printed brochures go stale in a specific way: the QR code on them is fine, but the PDF it pointed to has a last-year price, a discontinued product or an old address. With a static code the only fix is a reprint. With a dynamic link (Pro) the fix is uploading the new PDF - the code on every brochure already in circulation opens the current version on the next scan.

That makes one print run last across editions. Print the code once on the brochure, the stand graphics and the business cards; update the PDF behind it as often as the brochure changes. The readership report carries on across versions, so you can compare how each edition was read.

## Brochure sharing questions.

### Is it free to share a brochure as a link?

Yes. The free plan covers up to 3 PDFs of 20MB each with all four viewer modes and a QR code for every link. Image-heavy brochures often come out of InDesign well over 20MB - export with compressed images, or move to Basic ($9/month) for 200MB files. Replacing the file behind a printed code is Pro ($29/month).

### What file types can I upload?

PDF, plus Word (.docx up to 25MB) and PowerPoint (up to 50MB), which are converted on upload. From InDesign, Affinity or Canva, export to PDF and upload that - the flipbook uses your pages exactly as exported.

### Is tracking OK for people who scan a printed QR code?

The viewer measures pages and time first-party and never stores an IP address, so a scan produces reading data, not personal data. Readers stay anonymous unless you choose to add an email gate on Pro.

### Can I update the brochure after the QR code is printed?

Yes, on Pro. Replace the PDF behind the link and every code already printed opens the new brochure on the next scan - the URL and the code itself never change. On Free and Basic, a new PDF means a new link and a new code.

### Does the flipbook work on mobile?

Yes. The flipbook runs in the phone browser from the camera scan, with no app. For narrow single-column brochures swipe mode reads best on a phone; magazine mode suits spreads on tablets and desktops.

## Put the brochure on a link.

Upload the print PDF, print the QR code once, and let the brochure change as often as the business does.

Related: PDF flipbooks · PDF to QR code · dynamic QR links · magazine mode · branded PDF viewer · real estate brochures

---
URL: https://everypage.co/use-cases/catalog
Title: Share a PDF Catalog Online as a Link | EveryPage
Description: Put your product catalog online as a flipbook link or QR code. Update prices and products in place, keep one link, and see which pages buyers linger on.

Share as a link: catalog

# Put your catalog online as one link

One link for the whole catalog, in flipbook or magazine view, that buyers open on any device. See which product pages hold their attention, and keep the same link across every seasonal edition.

Put your catalog online

or click anywhere in the tray to browse

PDF only · max 20MB

Free to start · large catalogs may need Basic’s 200MB limit · keeping one link across editions is Pro

## Product-page attention

Per-page analytics (from Basic) show which product pages buyers stop on, which they skip, and which they come back to before ordering.

## One link, every season (Pro)

Replace the PDF behind the link when the new edition lands and every buyer, rep and printed order form still points at the current catalog.

## Trade-only access

A password (from Basic) keeps a wholesale catalog with wholesale prices away from retail customers, and downloads can be turned off per document.

## Magazine or swipe view

Magazine mode keeps product spreads together on a desktop; swipe mode turns the same catalog into a one-handed phone read. Both are on every plan.

## See which product pages buyers stop on

A printed catalog tells you what sold, months later, through the order book. A catalog shared as an EveryPage link tells you what was looked at while the season is still running: every session records the pages opened and the time on each, and per-page analytics (from Basic) turn that into a page-by-page picture of buyer attention across the whole range.

That is merchandising data you did not have before. A product page everyone reaches but nobody lingers on is a photography or pricing problem; a page buyers return to before ordering deserves the front cover next edition. Readership is measured first-party in the viewer and no buyer IP is stored, so the data is about pages, not people.

## Made for catalogs that change every season

- Update in place (Pro). Upload the new edition behind the existing link and every copy of the link already sent, embedded or printed opens the current catalog.
- Folders for lines and regions (from Basic). Keep the spring, autumn, trade and export catalogs in folders, with readership aggregated per folder so a whole product line reports as one.
- A QR code for printed order forms. Every link ships with a QR code PNG - put it on the order form, the price sheet or the stand banner and buyers open the full catalog from a phone.
- A link that never expires. Signed-in links have no expiry unless you set one, so the catalog link on your website and in your reps’ signatures stays live from one season to the next.

## Wholesale catalogs behind a password

Many businesses run two catalogs: the retail one anyone may see, and the trade one with wholesale prices that must not leak. Share the trade catalog as its own link with a password (from Basic), keep downloads off so the PDF cannot be saved and forwarded, and on Pro add an email gate so every trade buyer who opens it is a named account.

Reps can send the link with the password in a separate message, or the link can sit behind the login on your own trade portal. When the prices change, the same link and password stay valid - only the PDF behind them changes (Pro).

## Catalog sharing questions.

### Is it free to put a catalog online?

Yes, for catalogs up to 20MB: the free plan covers 3 PDFs with all four viewer modes and a QR code per link. Full-range catalogs with product photography usually run larger - Basic ($9/month) allows 200MB files and Pro ($29/month) 2GB, and Pro adds replacing the file behind the link between editions.

### What is the best format for a digital catalog?

A PDF exported from your layout tool at web quality - compressed images, fonts embedded - gives the smallest file with pages exactly as designed. Word and PowerPoint files are converted on upload if that is where the catalog lives.

### Do you track my customers?

The viewer records pages and time per session, first-party, and never stores an IP address - so you learn which product pages are read, not who read them. Buyers are only identified if you choose to add an email gate on Pro.

### Can I update the catalog without changing the link?

Yes, on Pro. Replace the PDF behind the link when the new edition is ready and the URL, QR code and readership history all stay as they were. On Free and Basic, a new edition means a new link.

### Can I keep separate trade and retail prices?

Share them as two links: the retail catalog open to anyone, the trade catalog with a password (from Basic) and downloads turned off. Both can live in the same folder so readership for the range reports together.

## Put the range on one link.

Upload the catalog, share one link with every buyer, and see which pages sell before the orders come in.

Related: PDF flipbooks · magazine mode · PDF to QR code · secure PDF sharing · PDF folders · price lists

---
URL: https://everypage.co/use-cases/price-list
Title: Share a Price List as a Link or QR Code | EveryPage
Description: Share your price list as one link or QR code. Change prices and the old link shows the new file, so no one quotes from a stale PDF. Free to start.

Share as a link: price list

# Share your price list as a link that never goes stale

One link and one QR code for the current prices. Change the PDF behind it and every customer, rep and counter card already holding the link shows the new prices - nobody quotes from last quarter’s sheet.

Share your price list

or click anywhere in the tray to browse

PDF only · max 20MB

Free to start · replacing the file behind the link is Pro · password and access settings come on the next step

## Replace, don’t resend (Pro)

Upload the new prices behind the existing link and every link ever handed out shows the current file - no "please discard the old list" email.

## QR on the counter

Every link comes with a QR code PNG for the trade counter, the price card or the invoice footer, and a phone camera opens the current list.

## Password for trade prices

A password (from Basic) keeps wholesale and account pricing with the customers you quoted it to, and downloads can be turned off so the PDF is read, not saved.

## Know who’s still looking

Readership shows how often each list is opened and which pages get read, so you know which lists are still in use before the next price change.

## One link, always the current prices

Every business with a price list has the same problem: the PDF gets emailed, saved, forwarded and printed, and six months later a customer quotes a price from a copy nobody can withdraw. A price list shared as an EveryPage link changes what gets passed around. The link is what travels, and with a dynamic link (Pro) the PDF behind it is whatever you uploaded last.

Turn downloads off and the list is always read from the link, never from a saved copy. When prices change, upload the new PDF: the links in old emails, on the website and in the reps’ signatures open the new sheet on the next click, and the readership report shows you the list being read after the change.

## Why a price list link beats an attachment

- Update in place (Pro). One upload replaces the file behind every link and QR code already in circulation, with the URL unchanged.
- A dynamic QR code. Print the code on price cards, shelf edges and delivery notes once; it points at the link, so it survives every price change (replacing the file is Pro).
- Password or self-destruct for a promotion (from Basic). A password keeps account pricing private; a view limit or an expiry date ends a promotional price list on the day the offer ends.
- A link that never expires. Signed-in links have no expiry unless you set one, so the price list link in your standard email template does not need replacing next year.

## A QR code that outlives every price change

A QR code on a printed price card is only useful if it still opens the right prices in a year. Because an EveryPage QR code points at the link rather than the file, the code you print today is still correct after every revision - on Pro you replace the PDF behind it and the code on the counter, the shelf and the trade-show banner opens the new list on the next scan.

For lists that must not travel, keep the code on the counter and the password (from Basic) with the staff; for public lists, put the code on the website and let anyone scan. Either way there is one QR code to print and one link to remember.

## Price list sharing questions.

### Is it free to share a price list as a link?

Yes. The free plan covers up to 3 PDFs of 20MB each with a QR code per link and core readership, and the link never expires unless you set an expiry. Passwords and view limits start on Basic ($9/month); replacing the file behind the link so old links show new prices is Pro ($29/month).

### Can I upload an Excel price list?

Not directly - EveryPage accepts PDF, Word and PowerPoint. Export the spreadsheet to PDF from Excel or Google Sheets (set the print area first so columns do not split across pages) and upload that.

### Is the tracking private?

Yes. The viewer records pages and time per session first-party and never stores an IP address, so you see how the list is used without collecting personal data. Customers are only identified if you add an email gate on Pro.

### Do old links show the new prices?

On Pro, yes: replace the PDF behind the link and every link and QR code already handed out opens the new file, with the URL unchanged. On Free and Basic each new list is a new link, so the old link keeps the old prices until you delete it or set it to expire.

### Can I keep separate retail and trade lists?

Share them as separate links: the retail list open to anyone, the trade list with a password (from Basic) and downloads turned off. Folders (from Basic) keep them together with readership aggregated across the set.

## Put the prices on one link.

Upload the price list, print the QR code once, and never chase a stale PDF around again.

Related: dynamic QR links · PDF to QR code · secure PDF sharing · PDF folders · catalogs · restaurant menus

---
URL: https://everypage.co/use-cases/report
Title: Share a Report as a Secure, Tracked Link | EveryPage
Description: Share reports as a link with read receipts. Password-protect, watermark and self-destruct confidential reports, and see which sections were actually read.

Share as a link: report

# Share your report as a secure link

Send the board pack, the audit findings or the client report as a link instead of an attachment: the reader confirms receipt on the record, the link takes a password and burns after a set number of views, and you see which sections were read rather than skimmed.

Share your report

or click anywhere in the tray to browse

PDF only · max 20MB

Free to start · read receipts, passwords and self-destruct are Basic features · protection settings come on the next step

## Read receipts

The reader taps "Mark as received" in the viewer and the confirmation lands in your dashboard with a timestamp - proof of receipt, not a guess (Basic).

## Self-destructing links

Set a view limit and the report deletes itself after that many reads, so a link forwarded beyond the intended circle finds nothing (Basic).

## Watermark every page

Per-viewer watermarking (Pro) tiles each reader's email or reader ID across every page and stamps it into any download, so a leaked page names its source.

## Section-level reading

Page-by-page time (Basic) shows whether the recommendations got ten minutes or ten seconds, and the exact page where readers stopped.

## Know the report was read, not just delivered

An emailed report tells you nothing after send. The attachment may have been opened, printed, forwarded to the wrong person or left unread until the meeting, and you find out which only when someone asks a question the report answered on page two. A link changes that: a view notification tells you the moment it is opened, and a read receipt gives the reader a "Mark as received" button that records who acknowledged it and when.

That is a different standard of delivery. When the compliance report, the audit findings or the quarterly board pack has a receipt against every name, the "I never saw it" conversation stops happening. And because the confirmation is something the reader chooses to send, it counts as an acknowledgement rather than a tracking pixel firing on a preview.

## Controls for confidential reports

- Password-protect the link. A password (Basic) keeps the report to the people you gave it to; a forwarded link without the password opens nothing. Send the link and the password by separate routes if the contents warrant it.
- Self-destruct after a set number of views. The self-destruct is a view limit (Basic), not a date: allow five reads for five recipients and the sixth attempt finds the link gone, with your readership record intact.
- Watermark each copy (Pro). Every page carries the viewer's email or reader ID and a timestamp, on screen and inside any downloaded copy, so a photographed or forwarded page can be traced to its reader.
- No reader IPs, ever. Readers are identified by a pseudonymous ID unless they enter an email, and EveryPage never stores an IP address. Files are encrypted at rest, which makes the security questionnaire a shorter conversation.

## Which sections got read (and which got skipped)

A report is rarely read cover to cover, and it helps to know which parts were. Page-by-page analytics (from the Basic plan) show the time spent on every page and the read-through funnel across the document: the executive summary read twice, the methodology skipped, the recommendations open for fourteen minutes. If most readers stop at page six, the next report puts the conclusion before page six.

The same report also tells you who came back. A re-read of the financial appendix the day before the board meeting is a signal worth having. The free plan already records views, readers and time spent per document, so the summary is there before you decide whether you need the page-level detail.

## Report sharing questions.

### Is it free to share a report as a link?

Yes. The free plan shares up to three PDFs of 20MB each as never-expiring links, with views, readers and time spent per report. Read receipts, password protection, self-destruct and page-by-page reading come with the Basic plan; per-viewer watermarking is a Pro feature.

### What file types and sizes can I upload?

PDF up to 20MB on the free plan, 200MB on Basic and 2GB on Pro. Word documents (.docx, up to 25MB) and PowerPoint files (up to 50MB) are converted to PDF on upload; a report built in Excel should be exported to PDF first.

### Is sharing a confidential report this way privacy-compliant?

Reader IPs are never stored: each reader gets a pseudonymous ID, and a name or email is attached only if they enter one or you invite them by name. Files are encrypted at rest, and you can delete the report, or let it self-destruct, at any time.

### Can I correct a figure after the report has been sent?

On Pro, yes: replace the PDF behind the link and every copy of the link already sent opens the corrected version, with the readership history carried on. On free and Basic, upload the corrected report and share its new link.

### Can the report expire after the meeting?

Two ways. Set an expiry date on any plan and the link returns "Gone" from that moment, or set a view limit (Basic) so it self-destructs after a set number of reads. Your record of who read it, and when, stays in the dashboard.

## Send the next report as a link.

Upload the report, switch on read receipts and a password, and know before the meeting who has read it and how far they got.

Related: PDF read receipts · self-destructing links · PDF watermarking · secure PDF sharing · send a PDF to contacts · see who read your PDF

---
URL: https://everypage.co/use-cases/whitepaper
Title: Share a Whitepaper as a Gated Link | EveryPage
Description: Turn a whitepaper PDF into a gated link. Capture emails before reading, see how far each reader gets, and swap in the new edition without a new URL.

Share as a link: whitepaper

# Share your whitepaper as a lead-capturing link

Put the whitepaper behind an email gate, see which leads read past the executive summary and which stopped at the cover, and publish the revised edition on the same URL you already put in the campaign.

Share your whitepaper

or click anywhere in the tray to browse

PDF only · max 20MB

Free to start · the email gate, custom domain and in-place updates are Pro features · gate settings come on the next step

## Email gate (Pro)

Readers enter a working email before the first page opens, so every read of the whitepaper is a lead with a name, not a line in an anonymous view count.

## Read depth per lead

Reader identities (Pro) with page-by-page time show which leads read the whole argument and which closed the tab at the executive summary.

## Your domain, your brand (Pro)

The link lives on docs.yourcompany.com with your logo and colours on the viewer, so the whitepaper never looks like it was hosted somewhere else.

## New edition, same link (Pro)

Replace the PDF behind the link when the next edition is ready and every campaign email, ad and partner page already pointing at it serves the new version.

## A whitepaper landing page without the landing page

The usual whitepaper pipeline needs a landing page, a form, a thank-you page, an email with the PDF attached and an automation rule to tie them together. An EveryPage link collapses that into one URL: the reader arrives, enters an email, and the whitepaper opens in the browser. The lead is recorded with the reading session that produced it, and the address is on file before the first page loads.

The lead form (Pro) takes up to five custom fields if you need company and role as well as email, and a domain allowlist can keep a partner-only paper inside the partner companies. Lead webhooks deliver each completed form to your CRM or Slack as it happens, so the sales follow-up can start while the reader is still on page four.

## What you get with every gated whitepaper

- Email capture before reading (Pro). The gate sits in front of the document, not on a separate page. Every reader is attributed to an address, and you can export the list as CSV or send it straight to your CRM.
- Page analytics without IPs. Time on every page and the read-through funnel (from the Basic plan) show where the argument holds attention. EveryPage never stores a reader IP, so the analytics come without the privacy cost.
- Your own domain (Pro). Share from a subdomain you control, with a vanity slug that reads like a page on your site rather than a file ID.
- Upload the Word draft. A .docx up to 25MB converts to PDF on upload, on every plan, so the whitepaper can go out before the designed version exists and be replaced by it later.

## See if leads read past the executive summary

Downloads were never a good measure of a whitepaper. A lead who read the summary and closed the tab counts the same as one who spent twenty minutes on the methodology and came back the next day, and the sales team follows up on both with the same email. Reader identities on Pro separate them: each named lead has a page-by-page record, a total time and a return count.

That turns the whitepaper into a scoring tool. The leads who reached the final chapter get the call; the ones who stopped at page two get the shorter follow-up. Across the campaign, the funnel shows which section loses readers, and the next edition fixes it on the same link.

## Whitepaper sharing questions.

### Is it free to share a whitepaper as a link?

Sharing is free: up to three PDFs of 20MB each on never-expiring links, with views, readers and time spent. The email gate, custom domain, reader identities and replacing the file behind the link are Pro features; page-by-page analytics start on the Basic plan.

### Can I upload the whitepaper as a Word document?

Yes. A .docx up to 25MB is converted to PDF on upload and shared like any other document, on every plan. When the designed PDF is ready, Pro lets you swap it in behind the same link.

### What information do you collect from readers?

Only what the gate asks for: an email address, plus up to five custom fields if you add a lead form. Readers who are not gated get a pseudonymous ID, and EveryPage never stores an IP address either way.

### Can I publish a revised edition on the same link?

On Pro, yes. Replace the PDF behind the link and every existing URL, QR code and embed serves the new edition immediately, with the lead list and readership history carried on. Nothing in the campaign needs updating.

### Can the whitepaper live on our own domain?

Yes, on Pro. Connect a subdomain such as docs.yourcompany.com, brand the viewer with your logo and colours, and give the whitepaper a vanity slug. The link in the campaign reads as yours end to end.

## Gate the next whitepaper.

Upload the PDF, switch on the email gate, and see which leads read the whole argument before the follow-up.

Related: lead capture forms · custom domains · branded PDF viewer · share a PDF with analytics · Word to PDF · ebooks

---
URL: https://everypage.co/use-cases/case-study
Title: Share a Case Study as a Tracked Link | EveryPage
Description: Send case studies as a link and know the moment a prospect reads them. Follow up while it’s fresh, and update the results in place. Free to start.

Share as a link: case study

# Share your case study as a follow-up trigger

Send the case study as a link and get an email the moment the prospect opens it - the best possible time to call. See which results page held them, and update the numbers in place when the client posts a better quarter.

Share your case study

or click anywhere in the tray to browse

PDF only · max 20MB

Free to start · opened alerts and page analytics are Basic features · in-place updates are Pro · settings come on the next step

## Read alerts

A view notification (Basic) emails you when the prospect opens the case study, which is the moment to send the follow-up rather than three days later.

## Which results page resonates

Page-by-page time (Basic) shows whether it was the cost-saving chart or the implementation timeline that held them, so the next call leads with it.

## Update the numbers in place (Pro)

Replace the PDF behind the link when the client reports a new figure and every link already in a prospect’s inbox opens the current version.

## Client-confidential watermark

Per-viewer watermarking (Pro) stamps each copy with the reader’s email, for the case study the client only agreed to share under NDA.

## Follow up the moment they read it

A case study is proof, and proof is most persuasive while it is being looked at. Sent as an attachment, you never know when that is. Sent as an EveryPage link, a view notification lands in your inbox the moment the prospect opens it, and live presence (Pro) shows who is reading right now. The follow-up goes out while the results are on their screen, not when your reminder fires next week.

The readership record tells you what to say. If the prospect spent four minutes on the results page and skipped the background, the follow-up leads with the numbers; if they read it twice, the deal has a champion. Email invites (Basic) attach a name to each link, so the alert tells you which prospect opened it, not just that someone did.

## Case study sharing built for sales teams

- Send it to named contacts. Email invites (Basic) send the link to up to ten prospects at a time, each session attributed to the invited address. Distribution lists and CSV import (Pro) cover the whole pipeline.
- File them by industry. Folders (Basic) keep the fintech, healthcare and manufacturing studies apart, with aggregated readership per folder so you can see which vertical’s proof actually gets read.
- Page analytics without IPs. Time on every page and the read-through funnel, with readers identified by a pseudonymous ID rather than an address. EveryPage never stores a reader IP.
- Links that never expire. A case study link in a sales sequence keeps working for as long as you leave it up. Expiry is a control you can set, not something that happens to the link.

## Group case studies by industry or product

Most sales teams keep a dozen case studies and send three at a time. Folders (Basic) hold them by industry, product line or region without changing a single link, and each folder rolls up the views, readers and completion of everything inside it. The logistics folder tells you at a glance which of its three studies gets opened and which never gets past the first page.

Over a quarter, that folder view is content strategy. The study that is opened in every send but read to the end in none of them needs a rewrite; the one that gets read twice earns the top slot in the sequence. And when a client’s numbers improve, Pro lets you update the study in place, so every link in the pipeline shows the new result.

## Case study sharing questions.

### Is it free to share a case study as a link?

Yes. The free plan shares up to three PDFs of 20MB each, on links that never expire, with views, readers and time spent. Opened alerts, page-by-page analytics, folders and email invites arrive with the Basic plan; in-place updates and per-viewer watermarking are Pro features.

### What formats can I upload?

PDF, plus Word (.docx up to 25MB) and PowerPoint (up to 50MB), which are converted to PDF on upload. A case study designed in InDesign or Canva should be exported to PDF first.

### Will prospects know the case study is tracked?

They open a plain link in the browser: no account, no download, no plugin. Readership is recorded against a pseudonymous reader ID rather than an IP address, and a read receipt, if you switch one on, is a button the prospect chooses to tap.

### Can I update the case study after sending it?

On Pro, yes: replace the PDF behind the link and every copy already in a prospect’s inbox opens the new version, with the readership history intact. On free and Basic, upload the new file and share its link.

### Can I send several case studies together?

Each case study keeps its own link, so put the two or three relevant links in one email or one invite. Folders (Basic) keep them grouped by industry in your library and roll up readership across the set, so you can see which of the three the prospect opened.

## Send the next case study as a link.

Upload it, switch on opened alerts, and follow up the moment the prospect is reading your proof.

Related: PDF read receipts · send a PDF to contacts · PDF folders · PDF watermarking · see who read your PDF · sales decks for sales teams

---
URL: https://everypage.co/use-cases/ebook
Title: Share an Ebook as a Flipbook Link | EveryPage
Description: Share your ebook as a flipbook link, gate it behind an email and see how many readers finish. Update chapters without changing the URL. Free to start.

Share as a link: ebook

# Share your ebook as a flipbook

Give readers a book, not a download: pages that turn, a swipe mode for phones, an email gate for lead magnets, and a completion rate that tells you how many readers reached the last chapter.

Share your ebook

or click anywhere in the tray to browse

PDF only · max 20MB

Free to start · flipbook and swipe modes on every plan · the email gate and in-place chapter updates are Pro features

## Flipbook or swipe reading

Pages turn like a printed book on desktop and read as a swipeable story on phones, on every plan, with no PDF download to lose in a folder.

## Email gate for lead magnets (Pro)

Ask for an email before chapter one opens and the ebook becomes a lead magnet with a named reader behind every open.

## Completion rate

The read-through funnel (Basic) shows the share of readers who reached each chapter and the page where the rest closed the book.

## Watermark to deter resharing

Per-viewer watermarking (Pro) puts each reader’s email on every page and in any download, which is a quiet reason not to forward the file.

## An ebook that reads like a book, not a PDF download

A PDF attachment is the worst way to read a book. It opens in whatever viewer the reader has, the layout fights the screen, and it ends up in a downloads folder with the receipts. Shared as an EveryPage flipbook, the ebook opens in the browser with pages that turn and two-page spreads on wider screens, and on a phone it becomes a swipeable story, one page per card, read with a thumb.

All four viewer modes come with the free plan, and the reader needs no account or app. Interactive hotspots (Pro) let a chapter link to a worksheet, embed a video walkthrough or play an audio note on the page, so the ebook can do things the printed edition cannot. The link never expires unless you decide it should.

## Everything an ebook link needs

- An email gate for lead magnets (Pro). Readers enter an email before the ebook opens, the address lands in your reader list with the session behind it, and a lead webhook passes it to your mailing tool as it arrives.
- A watermark on every copy (Pro). Each reader’s email or reader ID is tiled across the pages and stamped into any download, so a paid ebook that leaks names the copy it leaked from.
- Chapter updates in place (Pro). Fix the typo in chapter three or add the new appendix by replacing the file behind the link; every reader who bookmarked it gets the current edition.
- A link that never expires. The URL in your newsletter, your author bio and your course keeps working for as long as you want it to. Expiry is a setting you choose, not the default.

## Know how many readers reach the last chapter

Downloads tell you how many people wanted the ebook. The read-through funnel (from the Basic plan) tells you how many read it: the percentage of readers who reached each page, the time spent on every chapter, and the point where most of them stopped. If half your readers close the book at chapter two, chapter two is the edit.

Reader identities (Pro) take it to the individual: which subscribers finished, who came back for the worksheet in chapter five, and who never got past the introduction. That is the list for the follow-up email, and the honest measure of whether the ebook is doing its job as a lead magnet or as a product.

## Ebook sharing questions.

### Is it free to share an ebook as a flipbook?

Yes. The free plan shares up to three PDFs of 20MB each in flipbook, magazine, swipe or standard mode, on never-expiring links. An image-heavy ebook may need compressing to fit the free limit; Basic allows 200MB and Pro 2GB. The email gate, watermarking and in-place updates are Pro features.

### Can I upload from Word, Canva or InDesign?

Word documents (.docx up to 25MB) are converted to PDF on upload. From Canva, InDesign or any other layout tool, export a PDF and upload that; the flipbook keeps the layout exactly as exported.

### Is reader tracking private?

Readers are identified by a pseudonymous ID unless they give an email at the gate, and EveryPage never stores an IP address. Files are encrypted at rest, and readers see the book in the browser with no account or app.

### Can I fix a chapter without changing the link?

On Pro, yes. Replace the PDF behind the link and every existing URL, QR code and embed opens the corrected edition, with your readership history carried on. On free and Basic, upload the new file and share its link.

### Can I collect emails before readers open the ebook?

Yes, with the email gate on Pro. Readers enter a working email before the first page, you get a named reader list with reading depth per person, and a lead webhook can send each address to your mailing tool the moment it is captured.

## Publish the ebook as a flipbook.

Upload the PDF, choose flipbook or swipe, and find out how many readers reach the last page.

Related: PDF flipbooks · lead capture forms · PDF watermarking · interactive PDFs · Word to PDF · whitepapers

---
URL: https://everypage.co/use-cases/one-pager
Title: Share a One-Pager as a Link or QR Code | EveryPage
Description: Turn a one-pager PDF into a short link or QR code in seconds. Know when it’s opened, update it in place, and keep the same link forever. Free to start.

Share as a link: one-pager

# Share your one-pager as a link or QR code

Upload the PDF and you have a short link and a QR code to hand out, no account needed. When someone opens a one-pager they have read it, so the opened alert is the whole story - and the link stays the same when the one-pager changes.

Share your one-pager

or click anywhere in the tray to browse

PDF only · max 20MB

Free · no account needed to start · opened alerts are a Basic feature · keeping the link through file changes is Pro

## Link in seconds

Drop the PDF here and copy a short link on the next screen, with no signup, no folder structure and no settings you have to touch.

## QR for handouts

Every link comes with a QR code to print on the business card, the conference flyer or the slide behind you.

## Opened means read

A one-pager has no page six to drop off at, so the view notification (Basic) that says it was opened is the fact you wanted.

## Same link forever (Pro)

Replace the PDF behind the link and the QR code on five hundred printed cards serves the new one-pager without a reprint.

## A one-pager deserves a one-step share

The point of a one-pager is that it is quick: one page, one read, one decision about whether to talk further. The share should match. Upload the PDF, copy the link, paste it in the email - three steps, and no account needed for the first share. The reader opens it in the browser on any device, and the same screen gives you a QR code for the printed version.

Readership is simple for the same reason. With a single page there is no funnel to study; the view notification (Basic) that says it was opened, and the time spent on it, tell you it was read. Reader identities (Pro) add the who, and read receipts (Basic) let the recipient confirm on the record.

## Where a one-pager link goes to work

- The investor intro email. A link reads better than an attachment in a cold email and opens on a phone without a download. You learn when it was opened, and the full deck can follow on its own link once they ask.
- The email signature. A short link under your name that opens the company one-pager, kept current behind the same URL (Pro) so you never have to update every signature in the team.
- The QR code on a business card. Print the code once. On Pro the PDF behind it can change as often as the pricing does; the printed code keeps working.
- The event follow-up. Send the one-pager to the contacts you met, up to ten at a time with email invites (Basic), and see which of them opened it before you book the calls.

## Update the one-pager, keep the link

A one-pager goes stale faster than anything else you send: a new price, a new logo, a new headline number after the funding round. On Pro, replacing the file behind the link means every copy of the link already out there - in signatures, in old emails, on printed cards - opens the current version. The QR code points at the link, not the file, so it never needs regenerating.

The readership history carries across every replacement, so the one-pager link accumulates a record of who opened it over the year rather than starting from zero with each revision. Links never expire unless you set them to, which is the right default for a document that lives in an email signature.

## One-pager sharing questions.

### Is it free to share a one-pager as a link?

Yes. Upload the PDF and share the link without an account; a free account keeps up to three PDFs of 20MB each on never-expiring links with views, readers and time spent. Opened alerts and read receipts arrive with Basic; keeping the same link through file changes is a Pro feature.

### What formats can I upload?

PDF, Word (.docx up to 25MB) and PowerPoint (up to 50MB). A one-pager built as a single PowerPoint slide converts to a one-page PDF on upload, on every plan.

### Is the tracking private for the reader?

Yes. Readers get a pseudonymous ID rather than being logged by address, EveryPage never stores an IP, and nobody needs an account or app to open the link. A name is attached only if you invite them by email or they enter one.

### Can I update the one-pager after sending it?

On Pro, yes: replace the PDF behind the link and every link and QR code already shared opens the new version, with the readership history intact. On free and Basic, upload the new file and share its link.

### Can I print the QR code on a business card and change the PDF later?

Yes. The QR code encodes the link, not the file, so on Pro you can replace the one-pager behind it as often as you like and the printed code keeps serving the current version. Print it once and never reprint for a content change.

## Share the one-pager in seconds.

Upload it, copy the link or the QR code, and know when it is opened.

Related: PDF to QR code · dynamic QR links · PDF read tracking · PowerPoint to PDF · pitch decks · sales decks for sales teams

---
URL: https://everypage.co/alternatives
Title: EveryPage vs the Alternatives - Compare PDF Sharing Tools
Description: Use-case-first comparisons of DocSend, Papermark, PandaDoc, Flipsnack, Smallpdf, Jumpshare and more - and where EveryPage genuinely wins.

The comparison shelf

# EveryPage vs the alternatives

Seven honest comparisons, organised by what you are actually trying to do. No tool wins every job - including this one - so start from the job.

## How to read this page

Every "best DocSend alternative" list on the internet ranks its own product first. This page does not. EveryPage is the right choice for some jobs - flat pricing instead of per-seat billing, page-by-page readership that never stores a visitor IP, flipbook and magazine viewer modes, and sharing that needs no account from your readers - and the wrong choice for others, which is what the sections below are for.

Each recommendation links to a full comparison page with a feature table, dated pricing notes, and the counter-argument: when the other tool is the better pick.

## Pick by job, not by brand

Compliance & data rooms

### Enterprise diligence with folder permissions

For virtual data rooms, enterprise SSO, and compliance-led diligence, DocSend is the stronger tool - that scale is what its per-seat price buys.

E-signatures & proposals

### Documents that end in a signature

If the workflow is generate, approve, sign, PandaDoc is built for exactly that. EveryPage tracks reading; it does not do e-signatures.

Design-first publishing

### Print-style catalogues designed in the tool

Flipsnack is a design studio for flipbooks - templates, a canvas, team workflows. EveryPage takes a finished PDF; it is not a design tool.

Self-hosting

### Running document tracking on your own server

Papermark is open source: full data sovereignty if you operate it yourself. EveryPage is the hosted, nothing-to-run counterpart.

Any-file sharing

### Screenshots, recordings and mixed hand-offs

Jumpshare shares every file type and captures your screen. EveryPage is PDF-only on purpose - depth over breadth.

PDF editing

### Merging, compressing and converting PDFs

EveryPage is not a PDF editor. Edit in Smallpdf or a similar suite, then share the finished file through a tracked link.

Quick deck links

### A lightweight link for a single deck

PDFDeck and Fliplink turn a PDF into a link with minimal fuss. EveryPage earns its keep when you also need analytics, gating, or expiry.

Tracked, flat-priced sharing

### Knowing who read the PDF you sent

Page-by-page readership with no visitor IPs stored, flipbook modes, and flat pricing - this is the job EveryPage is built for.

## The shelf at a glance

Billing models and free plans as publicly listed in August 2026 - they change often, so treat the numbers as "from" figures and check each vendor's pricing page before deciding.

| Tool | Best for | Billing | Free plan | Full comparison |
|---|---|---|---|---|
| EveryPage | Flat-priced PDF tracking, privacy-first | Flat per account (free · $9 · $29) | Yes - 3 PDFs | Pricing |
| DocSend | Data rooms, enterprise compliance | Per user, from ~$15/mo | Limited | vs DocSend |
| Papermark | Self-hosted document tracking | Flat tiers, from ~€29/mo | Yes + open source | vs Papermark |
| PandaDoc | E-signatures & proposal workflows | Per seat, ~$19-49/mo | Limited | vs PandaDoc |
| Flipsnack | Design-first catalogue publishing | Tiered subscriptions | Limited | vs Flipsnack |
| Fliplink | Quick flipbook links | Tiered subscriptions | Limited | vs Fliplink |
| Smallpdf | Editing, converting & compressing | Per user subscriptions | Limited tools | vs Smallpdf |
| Jumpshare | Any-file sharing & screen capture | Per user; free plan | Yes | vs Jumpshare |
| PDFDeck | Single-deck sharing | See their site | See their site | vs PDFDeck |
| Digify | Document DRM & virtual data rooms | Per user, from ~$25/mo | Trial only | — |

## Where EveryPage genuinely wins

- Flat pricing. Free, then $9/month Basic or $29/month Pro per account - a five-person team pays the same as one person, where per-seat tools multiply.
- IP-free page analytics. Page-by-page reading time, a read-through funnel, and returning-reader detection with no visitor IP addresses stored - one less thing in a GDPR review.
- Flipbook, magazine & swipe modes. Document-tracking tools rarely present well; flipbook tools rarely track well. EveryPage does the page-turn and the readership on the same link.
- No-account sharing. Readers open a link in the browser - no sign-up, no app. You can even upload and share without an account yourself, then claim the link later.

## Choosing between them.

### What is the best DocSend alternative?

It depends on the job. For flat-priced, privacy-first PDF tracking, EveryPage; for self-hosting, Papermark; for e-signature workflows, PandaDoc. If you need data rooms and enterprise compliance, staying with DocSend is often the honest answer.

### Is EveryPage the best choice on this page?

Not for everything, no. EveryPage wins on flat pricing, IP-free page-by-page analytics, flipbook viewer modes, and no-account sharing. It loses on e-signatures (PandaDoc), in-tool design (Flipsnack), PDF editing (Smallpdf), data rooms (DocSend), and non-PDF files (Jumpshare).

### Why does flat pricing matter so much in this category?

Because most document-tracking tools bill per user, the sticker price is really the price multiplied by your team. A $15/user/month tool costs a five-person team $75/month; EveryPage Basic costs that team $9/month flat.

### How current are these comparisons?

Each comparison page carries a dated sourcing note (mid-2026 at the time of writing) and links to the competitor’s own pricing page. Competitor features and prices change often, so always check their site before deciding.

### Can I try EveryPage without an account?

Yes - upload a PDF from the homepage and you get a working share link without signing up. Create a free account when you want the readership behind the link.

## Try the flat-priced one.

Upload a PDF, share the link, and see the page-by-page readership on your next send - free, no card, no reader accounts.

See EveryPage pricing · How PDF tracking works

---
URL: https://everypage.co/papermark-alternative
Title: Papermark Alternative - Fully Hosted Tracking | EveryPage
Description: EveryPage is a fully hosted Papermark alternative: privacy-first document tracking with nothing to operate, plus flipbook modes and lead capture.

Papermark alternative

# The Papermark alternative with nothing to operate

Papermark made open-source document sharing credible. EveryPage is the option when you want the same privacy-first tracking as a finished product - no server to run, plus viewer modes and lead capture Papermark does not focus on.

|  | EveryPage | Papermark |
|---|---|---|
| Hosting & maintenance | None - fully hosted | Self-host it yourself, or use their cloud |
| Viewer modes (flipbook, magazine, swipe) | Yes - four modes | — (standard document viewer) |
| Per-page analytics | Yes - time per page + read-through funnel | Yes - page-level |
| Lead capture forms (up to 5 fields) | Yes (Pro) | Email verification gate |
| Interactive hotspots (video, audio, links) | Yes (Pro) | — |
| Per-viewer watermarking | Yes (Pro) | Via higher tiers |
| Self-destructing links | Yes - by time on every plan, by views on Basic+ | Link expiry |

Comparison reflects publicly advertised features as of July 2026. Check papermark.com for current details.

## Why look for a Papermark alternative?

Papermark deserves its reputation: an open-source DocSend alternative you can self-host and audit is a genuinely good thing, and if your team wants to run its own document infrastructure, it is a fine choice. But self-hosting is a commitment, not a checkbox - a server to patch, a database to back up, upgrades to schedule, and downtime that is yours at exactly the moment a prospect clicks your deck.

EveryPage is for everyone who liked the philosophy but not the ops. The privacy stance is the same - readership without storing a single visitor IP address - but as a finished, hosted product: upload a PDF, share the link, read the report. Plans are flat ($9/month Basic, $29/month Pro), not per seat, and there is a free plan to start.

## What EveryPage adds beyond the core

- A presentation layer. Flipbook, magazine, and swipe viewer modes turn brochures, lookbooks, and decks into things worth looking at - not just tracked scrolls. Custom branding and your own domain finish the job.
- Built-in lead generation. A custom gate form (up to five fields, server-validated) in front of any document, a B2B domain allowlist, and CSV export - the whitepaper-to-pipeline loop without a separate form tool.
- The full protection kit. Per-viewer watermarking with stamped downloads, self-destructing links, screenshot deterrence, right-click and print blocking, and read receipts - every document, no plumbing.

## When Papermark is the right call

Honestly: if your organisation requires that documents never leave infrastructure you control, or you want to read and modify the source of your sharing stack, self-hosted Papermark is exactly the tool for that - EveryPage is a hosted service and does not pretend otherwise. Developers who enjoy running their own services will be happy there.

If what you actually wanted was privacy-respecting document tracking that simply works - and viewer modes, lead capture, and watermarking on top - that is the job EveryPage does all day.

## Papermark alternative questions.

### Is EveryPage a hosted alternative to Papermark?

Yes. EveryPage is a fully hosted document-tracking service: no server to run, no updates to apply, no database to back up. You upload a PDF, share the link, and read the per-page readership report. A free plan covers trying it; paid plans are flat-priced at $9 and $29 per month.

### Does EveryPage match Papermark on privacy?

The core stance is the same and then some: EveryPage never stores visitor IP addresses - readers are identified by a salted one-way hash - and files are AES-encrypted at rest. You get returning-reader analytics without holding personal data.

### What does EveryPage have that Papermark lacks?

As of July 2026: flipbook, magazine, and swipe viewer modes; interactive hotspots for video, audio, and links on the page; built-in lead capture forms with up to five custom fields; and per-viewer watermarking with permanently stamped downloads on the standard plans. Check papermark.com for their current feature set.

### Can I move from Papermark to EveryPage?

Yes - your documents are PDFs either way. Upload them to EveryPage, recreate your link settings (passwords, expiry, gating), and share the new links. There is no lock-in in either direction.

### Is EveryPage open source?

No - EveryPage is a hosted commercial product. If open source or self-hosting is a hard requirement, Papermark is the better fit; if you want the outcome without the operations, that is EveryPage.

Compare more: DocSend alternative · PDFDeck alternative · Jumpshare alternative · PDF read tracking · lead capture forms · all alternatives compared

---
URL: https://everypage.co/pdfdeck-alternative
Title: PDFDeck Alternative - More Than Deck Sharing | EveryPage
Description: EveryPage is a PDFDeck alternative beyond deck links: per-page readership with a funnel, watermarking, self-destructing links, and four viewer modes.

PDFDeck alternative

# Beyond deck sharing: every PDF, tracked

Deck-sharing tools do one document type well. EveryPage tracks the deck - and the proposal, the brochure, the lookbook, and the report - with watermarking and self-destruct on top.

|  | EveryPage | PDFDeck |
|---|---|---|
| Document scope | Any PDF - decks, proposals, brochures, reports | Deck-focused sharing |
| Per-page analytics & read-through funnel | Yes - every viewer mode | Limited |
| Viewer modes (flipbook, magazine, swipe) | Yes - four modes | — |
| Per-viewer watermarking + stamped downloads | Yes (Pro) | — |
| Self-destructing links | Yes - by time on every plan, by views on Basic+ | Limited |
| Lead capture forms & email gating | Yes (Pro) | Limited |
| Custom domains | Yes (Pro) | Limited |

Comparison reflects publicly advertised features as of July 2026. Check PDFDeck's site for current details.

## Why look past a deck-sharing tool?

Single-purpose deck tools are appealing for exactly one send: the pitch. But most senders discover the second document within a week - the follow-up proposal, the case study, the pricing one-pager - and each one deserves the same tracked link. A tool scoped to decks either stretches awkwardly or leaves everything else untracked.

EveryPage treats the deck as one PDF among many. The same link machinery covers every document you send: per-page readership with a read-through funnel, view notifications the moment it opens, and a protection kit - watermarking, self-destruct, passwords, gating - that pricing pages and confidential proposals actually need. Flat pricing: free to start, $9/month Basic, $29/month Pro.

## Where EveryPage goes further

- Watermark the sensitive sends (Pro). Every page tiled with the viewer's identity and timestamp; allowed downloads permanently stamped into the file. A forwarded pricing deck names its forwarder.
- Let the quote expire itself (by views: Basic+). A view budget, a validity date, or both - the link burns on cue while your readership record of every view survives.
- Capture the lead before slide one (Pro). A custom form - up to five fields, validated server-side - turns every deck view into a named contact with reading behaviour attached, exportable to CSV.

## Which sends deserve the extra machinery

A rule of thumb from real sending: the moment a document has a next step attached - a call, a decision, a renewal - it deserves more than a bare link. Three sends where that shows fastest:

- The deck with a follow-up call. The sales deck tracking playbook: per-page readership shows which slide lost the prospect before the call does, so the follow-up starts on the right page - and a custom CTA button on the viewer books the meeting.
- The proposal with pricing inside. Give the quote a self-destruct schedule so an old price cannot circulate after the offer lapses, and watermark each viewer’s copy so a forwarded PDF names its forwarder.
- The lookbook or brochure that should generate leads. Put a lead capture form in front of it and every reader becomes a named contact with reading behaviour attached - the page they lingered on is the opening line of your next email.

## An honest note

If a lightweight deck link is genuinely all you need - one deck, a link, a view count - a smaller tool may serve you fine, and simplicity is worth something. EveryPage earns its keep when you care how far readers got, who they were, and what happens to the document after you send it.

It also stays honest about limits: readership requires the in-browser viewer, uploads are PDF-only, and no tool can prevent a photographed screen - watermarking makes it attributable instead.

## PDFDeck alternative questions.

### Is EveryPage limited to pitch decks?

No - any PDF becomes a tracked link: decks, proposals, brochures, reports, lookbooks, menus. Each gets the same per-page readership, protections, and viewer modes.

### Does EveryPage show more than a view count?

Much more: time on every page, a read-through funnel showing where readers stop, returning-reader detection, referrer and device breakdowns, and (on Pro) named reader sessions via the email gate.

### Can I stop a deck being forwarded?

You can make forwarding traceable and expiry real: per-viewer watermarking (Pro) names every copy, downloads can be blocked or stamped, and self-destructing links end access after a set number of views (Basic+) or on a date (every plan).

### What does EveryPage cost compared to deck tools?

EveryPage is flat-priced per account: free to start, $9/month Basic, $29/month Pro - never per user. We do not quote competitor pricing here; check their sites for current numbers.

### Do my readers need accounts?

No. Readers open a link in the browser on any device - no sign-up, no install. Only the sender needs an EveryPage account.

### Can I move my decks over from a deck-sharing tool?

Yes - keep the original PDFs and upload them; each gets a short link, a QR code, and an embed snippet in seconds. There is no importer to wait for because the PDF itself is the portable format.

### What happens to the readership if I replace or expire a deck?

The record survives. Expiry and self-destruct end access, not analytics - every recorded session stays in your dashboard. And with dynamic links (Pro) you can swap a revised deck in behind the same URL; readership notes which version each visit saw.

Compare more: DocSend alternative · Papermark alternative · Jumpshare alternative · PDF read tracking · self-destructing links · all alternatives compared

---
URL: https://everypage.co/flipsnack-alternative
Title: Flipsnack Alternative - Flipbooks + Analytics | EveryPage
Description: EveryPage is a Flipsnack alternative for when the flipbook needs analytics: per-page readership, gating, watermarking - and no IPs stored.

Flipsnack alternative

# Flipbooks, plus the analytics that matter

Flipbook makers nail the page-turn and treat readership as an afterthought. EveryPage gives you the flipbook - and the per-page funnel, gating, and watermarking of a document-tracking tool, privacy-first.

|  | EveryPage | Flipsnack |
|---|---|---|
| Flipbook viewer | Yes - plus magazine & swipe modes | Yes - core product |
| Per-page readership & read-through funnel | Yes - every plan records fully | Via higher tiers |
| Email gating & lead capture forms | Yes (Pro) | Via higher tiers |
| Per-viewer watermarking + stamped downloads | Yes (Pro) | — |
| Self-destructing links | Yes - by time on every plan, by views on Basic+ | — |
| Stores visitor IP addresses | No - pseudonymous reader IDs only | Standard web analytics |
| Entry paid price | $9/month flat per account | See their pricing page |

Comparison reflects publicly advertised features as of July 2026. Check flipsnack.com for current details.

## Why look for a Flipsnack alternative?

Flipsnack and its peers are publishing tools: the flipbook is the product, and it is genuinely polished - design features, embeds, big catalogs. Where they run thin is the other half of the job: knowing what happened after you shared it. Meaningful readership tends to sit in higher tiers, arrive as aggregate view counts, and lean on conventional web tracking underneath.

EveryPage comes at it from the document-tracking side. The flipbook, magazine, and swipe modes give you the presentation; the readership engine underneath treats every page-turn as data - time per page, a read-through funnel, returning readers - on every plan, with a privacy model (no visitor IPs, first-party measurement) that survives a GDPR review. Flat pricing: free, $9 Basic, $29 Pro.

## What the document-tracking side buys you

- A funnel, not a view count. See exactly where readers stop turning pages in your catalog or brochure - the single most actionable number a document produces.
- Gates and leads (Pro). Email gating, a B2B domain allowlist, and custom lead forms in front of the flipbook - the catalog becomes a lead source, not just a viewer.
- Protection worth the name. Passwords, right-click and print blocking, screenshot deterrence, per-viewer watermarking, and self-destructing links - controls publishing tools rarely carry.

## When Flipsnack still fits

If your need is design-first publishing - building the catalog inside the tool, template libraries, team design workflows, or interactive elements authored on their canvas - a dedicated flipbook maker is built for exactly that, and EveryPage does not try to be a design studio. You bring a finished PDF; we make it read well and report back.

If the PDF already exists and the question is "who reads it, how far, and can I gate and protect it?", that is EveryPage’s home ground.

## Flipsnack alternative questions.

### Does EveryPage make real flipbooks?

Yes - upload a PDF and choose flipbook mode for a drag-to-turn book, magazine mode for two-page spreads, or swipe mode for phones. Flipbooks are embeddable on your site and fully tracked page by page.

### How is EveryPage’s analytics different from a flipbook maker’s?

EveryPage is a document-tracking tool at heart: time per page, a read-through funnel, returning-reader detection, source and device breakdowns, and named sessions behind the email gate (Pro) - recorded on every plan, not reserved for top tiers.

### Is EveryPage better for privacy?

EveryPage never stores visitor IP addresses - readers become salted pseudonymous IDs - and measurement is first-party inside the viewer, with no third-party trackers on your document. That model is the default on every plan.

### Can I brand the flipbook and use my own domain?

Yes - Pro adds your logo, colours, background, a custom CTA button, and custom domains, plus GA4 integration if you want flipbook traffic in your own reporting.

### Can I design the catalog inside EveryPage?

No - EveryPage is not a design tool. Bring a finished PDF from InDesign, Canva, or anywhere else; EveryPage turns it into a tracked, gated, protected flipbook link.

Compare more: Fliplink alternative · Smallpdf alternative · DocSend alternative · PDF flipbook maker · PDF read tracking · all alternatives compared

---
URL: https://everypage.co/fliplink-alternative
Title: Fliplink Alternative - Secure Flipbook Links | EveryPage
Description: EveryPage pairs flipbook links with document security: passwords, gating, per-viewer watermarking, self-destruct, and per-page readership.

Fliplink alternative

# Flipbook links with a security suite attached

Turning a PDF into a flipbook link is the easy half. EveryPage adds the half that matters after you share it: gates, watermarks, expiry, and page-by-page readership.

|  | EveryPage | Fliplink |
|---|---|---|
| Flipbook links from a PDF | Yes - plus magazine & swipe modes | Yes |
| Per-page readership & read-through funnel | Yes | Limited |
| Password protection & email gating | Yes (Basic+ / Pro) | Limited |
| Per-viewer watermarking + stamped downloads | Yes (Pro) | — |
| Self-destructing links | Yes - by time on every plan, by views on Basic+ | — |
| Custom domains & branding | Yes (Pro) | Limited |
| Stores visitor IP addresses | No - pseudonymous reader IDs only | Standard web analytics |

Comparison reflects publicly advertised features as of July 2026. Check Fliplink's site for current details.

## Why look for a Fliplink alternative?

Lightweight flipbook-link tools do one conversion well: PDF in, page-turning link out. That is a fine trick until the document is worth something - a price list you would rather not see forwarded, a catalog you want leads from, a preview that should stop working after launch day. At that point the link needs controls, and a converter has none to offer.

EveryPage treats the flipbook as the front end of a document platform. The same link that turns pages also takes a password, an email gate, a per-viewer watermark, a self-destruct timer, and per-page readership - and it does all of it without storing a single visitor IP. Free to start; Basic $9/month; Pro $29/month, flat.

## The security suite, itemised

- Before the first page: passwords (Basic+), the email gate and B2B domain allowlist (Pro), and lead capture forms that name your readers.
- While they read: right-click, print, and copy blocking, screenshot deterrence, and per-viewer watermarking that tiles every page with the reader’s identity (Pro).
- After the send: self-destruct by views or date, on-demand expiry, stamped downloads, and a readership record that survives even a burned link.

## Keep it simple where simple works

If you truly need nothing but a quick flipbook of a harmless document, a minimal converter is not a wrong answer - and EveryPage’s free plan does that job too, three documents at a time, with readership included.

The difference shows the day a document matters: the moment you want to know who read the catalog, gate the price list, or kill the preview link - the controls are already on the same URL, one settings panel away.

## Fliplink alternative questions.

### Does EveryPage convert a PDF into a flipbook link?

Yes - upload the PDF and share the link; readers get a drag-to-turn flipbook in the browser (or magazine and swipe modes, your choice). No software for you, no app for them.

### What security can I put on a flipbook link?

Passwords, download and print blocking, screenshot deterrence, an email gate with a domain allowlist, per-viewer watermarking with stamped downloads, and self-destruction by views or date. All per-document toggles.

### Can I see who read my flipbook?

Yes - per-page reading time, a read-through funnel, returning readers, and (on Pro) named sessions behind the email gate. No visitor IP addresses are ever stored.

### Can a flipbook link expire?

Yes - set a view budget (Basic+), a date, or both, or expire it manually any time. The readership record survives the expiry.

### Is there a free plan?

Yes - up to 3 active PDFs with core readership, no card required. Basic is $9/month and Pro $29/month, flat per account.

Compare more: Flipsnack alternative · Smallpdf alternative · Papermark alternative · PDF flipbook maker · secure PDF sharing · all alternatives compared

---
URL: https://everypage.co/smallpdf-alternative
Title: Smallpdf Alternative for Sharing an Edited PDF | EveryPage
Description: EveryPage is not a PDF editor - it is the step after Smallpdf: share the PDF you just edited as a tracked link with page-by-page readership and gating.

Smallpdf alternative

# Not a PDF editor. The step after one

If you searched "Smallpdf alternative" wanting to merge, compress or edit, EveryPage is not it. If the PDF is finished and now needs to be shared, protected - and actually read - this is the step the editors stop at.

Drop your PDF here

or click anywhere in the tray to browse

PDF only · max 20MB

Free · no account needed to start · drop the PDF you just edited and get a tracked link

or create a free account

|  | EveryPage | Smallpdf |
|---|---|---|
| Edit, convert & compress tools | Word-to-PDF only - otherwise sharing & tracking | Yes - core product |
| Tracked share links with readership | Yes - every link, per-page | Limited |
| Read-through funnel & time per page | Yes | — |
| Email gating & lead capture forms | Yes (Pro) | — |
| Per-viewer watermarking + stamped downloads | Yes (Pro) | Static watermark tool |
| Viewer modes (flipbook, magazine, swipe) | Yes - four modes | — |
| Self-destructing links & expiry control | Yes - time or never on every plan, by views on Basic+ | Limited |

Comparison reflects publicly advertised features as of July 2026, and covers sharing - not editing, where Smallpdf leads. Check smallpdf.com for current details.

## EveryPage is not a PDF editor - on purpose

Most people searching for a Smallpdf alternative want the same toolbox under a different badge: merge, split, compress, convert, e-sign. Let this page be clear about what it is not - EveryPage does none of that. For editing, Smallpdf is genuinely good, and iLovePDF, PDF24, and Adobe Acrobat do the same jobs. Keep whichever editor you like.

The gap none of those editors fill sits one step later. You compressed the proposal, merged the deck, exported the brochure - and then what? You attach it to an email or drop it in a chat, and from that moment the document goes dark: no idea whether it was opened, read to the end, skimmed, or forwarded. EveryPage exists for exactly that step. Free to start; $9/month Basic; $29/month Pro, flat per account.

## What to use after editing in Smallpdf

- Share a tracked link, not an attachment. Upload the finished PDF and send the link instead of the file: you see who opened it, which pages they read, how long they stayed, and who came back - with no visitor IP addresses stored.
- Present it, don’t just deliver it. The same link can open as a page-turning flipbook, a two-page magazine spread, or a phone-first swipe deck - a better arrival than a raw file in a download folder.
- Keep control after you hit send. Add a password or an email gate, watermark each viewer’s copy, block downloads, or let the link self-destruct after a set number of views - all switchable after the link is already out.

## Starting from Word? Skip the converter tab

If your only "editing" step is turning a Word document into a PDF, you can skip the toolbox entirely: EveryPage’s built-in Word to PDF converter accepts a .docx and hands back a tracked share link in one step, converted server-side, free.

However the PDF gets made, the sharing step works the same: upload it, set the rules, send one link. Read how PDF tracking works, or see the flipbook viewer your document can arrive as.

## Use both - the workflow is the answer

The honest recommendation is a two-tool workflow: edit in Smallpdf (or any editor you prefer), then share through EveryPage. There is no overlap to agonise over - the output of one is the input of the other. What does not work is expecting an editor’s share button to answer "did the client actually read it?": that takes per-page readership, and per-page readership is a whole product, not a feature on a toolbox.

One more difference worth naming: EveryPage’s measurement is privacy-first - no visitor IP addresses stored, no third-party trackers on your document - which matters when the readers are your clients.

## Smallpdf alternative questions.

### Is EveryPage a Smallpdf alternative for editing PDFs?

No. EveryPage does not edit, merge, split, compress, or e-sign PDFs. For editing, use Smallpdf, iLovePDF, PDF24, or Adobe Acrobat. EveryPage is the sharing step afterwards: it turns the finished PDF into a tracked, protected link. The one preparation step built in is Word-to-PDF conversion on upload.

### What should I use to share a PDF after editing it in Smallpdf?

Upload it to EveryPage and send the link instead of the file. You get page-by-page readership - who opened it, how far they read, how long they stayed - plus passwords, email gating, watermarking, and expiry on the same link. Free for up to 3 documents.

### Can EveryPage watermark a PDF like Smallpdf can?

Differently, and for a different purpose: Smallpdf offers a static watermark you apply to a file once; EveryPage applies a per-viewer watermark at reading time - each reader sees their own identity tiled on the pages, and downloads are stamped with it (Pro). One brands a file; the other deters leaks.

### Can I convert Word to PDF in EveryPage?

Yes - upload a .docx (up to 25MB) and EveryPage converts it server-side and gives you a tracked share link in one step. That is the one piece of file preparation built in; everything else stays with your editor.

### Do readers need anything installed?

No - links open in the browser on any device, in your choice of standard, flipbook, magazine, or swipe mode. Readers never need an account.

### Is there a free plan to try it?

Yes - 3 active PDFs with core readership, no card required. Basic is $9/month and Pro $29/month, flat per account, never per user.

### Does a link instead of an attachment change anything for recipients?

For them, almost nothing: they tap the link and read in the browser. For you, everything: an attachment reports nothing back, while a tracked link reports readership, can swap in a new version behind the same URL, and can be expired or revoked after sending.

Compare more: Jumpshare alternative · DocSend alternative · Flipsnack alternative · PDF read tracking · secure PDF sharing · Word to PDF converter · all alternatives compared

---
URL: https://everypage.co/jumpshare-alternative
Title: Jumpshare Alternative for PDF Tracking | EveryPage
Description: For documents, EveryPage is the Jumpshare alternative: per-page readership, a read-through funnel, email gating, and per-viewer watermarking.

Jumpshare alternative

# For PDFs, a specialist beats a generalist

Jumpshare shares everything a bit; EveryPage shares one thing deeply. If the files that matter to you are documents, depth wins: per-page readership, gating, watermarking, funnels.

|  | EveryPage | Jumpshare |
|---|---|---|
| File types | PDF - specialised | Any file, screen recordings, screenshots |
| Per-page reading time & read-through funnel | Yes - every viewer mode | — |
| Email gating, domain allowlist & lead forms | Yes (Pro) | Limited |
| Per-viewer watermarking + stamped downloads | Yes (Pro) | — |
| Self-destructing links | Yes - by time on every plan, by views on Basic+ | Yes |
| Viewer modes (flipbook, magazine, swipe) | Yes - four modes | — |
| Stores visitor IP addresses | No - pseudonymous reader IDs only | Standard tracking |

Comparison reflects publicly advertised features as of July 2026. Check jumpshare.com for current details.

## Why a PDF specialist?

Generalist sharing tools are genuinely useful - a screen recording here, a zip there, a quick screenshot link. Jumpshare does that breadth well. But breadth has a price: when every file type gets the same treatment, a document gets the same analytics as a zip file - it was viewed, or it was not. The questions documents raise are more specific: how far did they read, which page stalled them, did the decision-maker come back?

EveryPage answers document questions because it does nothing else. Every page-turn is timed in every viewer mode; the read-through funnel shows where attention dies; the email gate names readers; watermarking makes copies attributable; and the whole apparatus is privacy-first - no visitor IPs, first-party measurement. Flat pricing: free, $9 Basic, $29 Pro.

## The depth, itemised

- Readership, not view counts. Time per page, funnels, returning readers, peak times, source and device breakdowns, live presence (Pro), CSV export - a document analytics suite, not a hit counter.
- Document-grade access control. Passwords, email gating with a B2B domain allowlist, lead forms, download and print control, screenshot deterrence, per-viewer watermarking.
- Document-grade presentation. Flipbook, magazine, and swipe modes, custom branding, your own domain, GA4 (Pro) - because a proposal should not arrive looking like a file dump.

## When Jumpshare fits better

If your day is screen recordings, screenshots, and mixed file hand-offs, a generalist is the right tool and EveryPage will not replace it - we do not host videos or zips at all. Uploads here are PDF-only, deliberately.

The teams that switch (or add) EveryPage are the ones whose important files are documents: proposals, decks, reports, brochures. For those, per-page depth beats any-file breadth every time.

## Jumpshare alternative questions.

### How does EveryPage differ from Jumpshare?

Scope. Jumpshare is a general file-sharing tool with screen capture; EveryPage is a PDF-sharing specialist. The trade is depth: per-page reading time, read-through funnels, email gating, and per-viewer watermarking for documents - but no video hosting or arbitrary file types.

### Can EveryPage share files other than PDFs?

No - uploads are PDF-only by design. That focus is what pays for the per-page analytics and document protections. Export decks and docs to PDF (the Google Workspace add-on and Canva app do this in one step) and share from there.

### Do both have self-destructing links?

Both offer expiring links as of July 2026. EveryPage’s version is document-flavoured: expire by views or by date, combine both, and keep the full per-page readership record after the link burns.

### Is EveryPage better for client documents?

That is its home ground: proposals and reports gated to the client domain, watermarked per viewer, tracked page by page - with no visitor IP storage to explain in a privacy review.

### What does EveryPage cost?

Free for up to 3 active PDFs; Basic $9/month; Pro $29/month - flat per account, never per user. Competitor pricing changes; check their site for current numbers.

Compare more: DocSend alternative · Smallpdf alternative · PDFDeck alternative · PDF read tracking · per-viewer watermarking · all alternatives compared

---
URL: https://everypage.co/docs
Title: Documentation: How to Share & Track PDFs | EveryPage
Description: How EveryPage works, feature by feature: share a PDF as a secure trackable link, see who read it and which pages, set passwords and expiry, and connect your tools.

Documentation

# Every feature, documented.

How EveryPage works, from your first upload to the API — organised by what you're trying to do. Search everything with ⌘K (or Ctrl+K).

## Getting started

What EveryPage is, how to upload and share your first document, and what each plan includes.

5 articles

## Sharing links

Share URLs, vanity slugs, per-recipient variants, QR codes, embeds and custom domains.

7 articles

## The viewer

Viewer modes, page styling, branding, interactive hotspots and in-document navigation.

7 articles

## Security and access

Passwords, email gates, watermarking, expiry, page limits and the privacy model.

10 articles

## Readership

What EveryPage measures, how to read the reports, and how to get the data out.

9 articles

## Reader interaction

Comments, read receipts, page marks for proofing, and annotations.

4 articles

## Your library

Organising documents with folders, trash and recovery, bulk actions and dynamic links.

5 articles

## Distribution

Sending documents to named recipients with tracked invites and saved contact lists.

2 articles

## File conversion

Turning Word, PowerPoint and DocSend documents into tracked PDFs.

3 articles

## Integrations

Connect EveryPage to Zapier, Make, n8n, WordPress, Notion and Slack.

7 articles

## Developers

API keys, scopes, authentication, the events feed, webhooks and OAuth apps.

7 articles

## Account and billing

Signing in, plans and payment, and managing your account.

4 articles

---
URL: https://everypage.co/docs/getting-started
Title: Getting started | EveryPage Docs
Description: What EveryPage is, how to upload and share your first document, and what each plan includes.

# Getting started.

What EveryPage is, how to upload and share your first document, and what each plan includes.

- What EveryPage is Share a PDF via link and measure how it was read without storing visitor IP addresses.
- Uploading a document Upload PDFs and Office files to EveryPage; understand file limits, supported formats, and what happens next.
- Configure and share Tour of the Configure & Share screen—where you customize your document's appearance, access controls, and reader interaction.
- Sharing without an account Upload and share a document without signing up, then claim it into an account for readership reporting and library features.
- Plans and limits Reference for plan features, hard caps, and tier-specific restrictions across EveryPage.

---
URL: https://everypage.co/docs/sharing
Title: Sharing links | EveryPage Docs
Description: Share URLs, vanity slugs, per-recipient variants, QR codes, embeds and custom domains.

# Sharing links.

Share URLs, vanity slugs, per-recipient variants, QR codes, embeds and custom domains.

- Share links and short IDs Understand the three identifier forms in an EveryPage share link and which to use where.
- Vanity slugs Pro Create readable custom URLs for your documents using vanity slugs instead of random short IDs.
- Link variants Pro Create separate tracked links for each recipient, with independent revocation and per-recipient download and page-range overrides.
- QR codes Generate QR codes for your documents that encode durable short-ID links and survive slug renames.
- Embedding a document Use oEmbed or the embed code snippet to display your EveryPage documents on external websites.
- Custom domains Pro Serve your documents from your own branded subdomain with automatic SSL.
- Sharing by email and social Send your document link to recipients by email, or share on social platforms.

---
URL: https://everypage.co/docs/viewer
Title: The viewer | EveryPage Docs
Description: Viewer modes, page styling, branding, interactive hotspots and in-document navigation.

# The viewer.

Viewer modes, page styling, branding, interactive hotspots and in-document navigation.

- Viewer modes Choose how your document is presented to readers, from a plain paged view to page-turn animations to story-style swiping.
- Page style and behaviour Basic Control how pages appear and advance in your viewer, from page turn speed to corner rounding.
- Branding and logo Basic Customize your viewer's appearance with branded backgrounds and logos, and control the EveryPage badge.
- Accent colour, toolbar and call to action Pro Customize your viewer's appearance with a branded accent colour, toolbar theme, and a call-to-action button for Pro accounts.
- Interactive hotspots Pro Draw clickable regions on document pages that link out, jump between pages, or play embedded media.
- Links and navigation How readers navigate your document using PDF links, page thumbnails, and viewer controls.
- Google Analytics on share links Pro Load your GA4 property on a document's viewer page to measure its traffic alongside your website analytics.

---
URL: https://everypage.co/docs/security
Title: Security and access | EveryPage Docs
Description: Passwords, email gates, watermarking, expiry, page limits and the privacy model.

# Security and access.

Passwords, email gates, watermarking, expiry, page limits and the privacy model.

- Password protection Basic Require viewers to enter a password before accessing your document.
- Email gates and lead capture Pro Require viewers to provide contact information before accessing your documents.
- Email domain allowlist Pro Restrict document access to viewers with email addresses on specific approved domains.
- Download control Control whether viewers can save a copy of your document.
- Expiry and retention How long documents stay accessible, how anonymous uploads are retained, and how the cleanup sweep removes them.
- Self-destructing links Basic Set a view limit so a link stops working after it has been opened a set number of times.
- Page-range links Pro Restrict a shared link to show only a window of pages from your document.
- Watermarking Pro Stamp each reader's identity and timestamp on the pages they view and download.
- Viewer protection Basic Soft deterrents that make casual copying harder without claiming to prevent determined access.
- Encryption and privacy How EveryPage stores documents and what data it does and does not record about document viewers.

---
URL: https://everypage.co/docs/readership
Title: Readership | EveryPage Docs
Description: What EveryPage measures, how to read the reports, and how to get the data out.

# Readership.

What EveryPage measures, how to read the reports, and how to get the data out.

- What EveryPage measures Understand what EveryPage records about your document views, why view_count diverges from sessions, and what data persists without a paid plan.
- Summary and trends The headline readership numbers for a document, and how engagement changes over time.
- Read-through funnel Basic The report that shows how far readers get before they stop.
- Page-by-page statistics Basic Track which pages were seen and how long readers spent on each.
- Audience breakdowns Basic Segment a document's read sessions by referrer, attribution source, device, browser, country, viewer mode, reading hour, and link variant.
- Reader identities and live presence Pro Distinguish individual reading sessions and see who is actively reading right now.
- CSV export Pro Export readership data and captured leads to spreadsheet format with formula-injection protection.
- View notifications Basic Get an email when someone opens one of your documents.
- Portfolio overview View aggregated readership across your entire library and scope reports by folder.

---
URL: https://everypage.co/docs/reader-interaction
Title: Reader interaction | EveryPage Docs
Description: Comments, read receipts, page marks for proofing, and annotations.

# Reader interaction.

Comments, read receipts, page marks for proofing, and annotations.

- Comments Pro Enable readers to leave feedback on your documents with per-comment visibility controls and owner moderation.
- Read receipts Basic Ask readers to explicitly confirm they received your document.
- Page marks and proofing Pro Let reviewers rate each page with pick, reject, or maybe verdicts.
- Annotations Pro Let readers highlight regions and attach notes to specific areas of your document.

---
URL: https://everypage.co/docs/library
Title: Your library | EveryPage Docs
Description: Organising documents with folders, trash and recovery, bulk actions and dynamic links.

# Your library.

Organising documents with folders, trash and recovery, bulk actions and dynamic links.

- Your document library Organize and monitor your PDFs from your library—the main screen where you see every document you've uploaded.
- Folders Basic Organize documents into flat categories for scoped analytics and easier navigation.
- Trash and recovery Basic How deleted documents move to trash and how to restore or permanently delete them.
- Bulk operations Basic Act on multiple documents at once instead of changing them one by one.
- Dynamic links (replacing content) Pro Swap the document behind an existing share link without changing the link, and use it to restore burned documents.

---
URL: https://everypage.co/docs/distribution
Title: Distribution | EveryPage Docs
Description: Sending documents to named recipients with tracked invites and saved contact lists.

# Distribution.

Sending documents to named recipients with tracked invites and saved contact lists.

- Email invites Basic Send tracked email invites to named recipients with per-recipient links that attribute opens and satisfy the email gate.
- Contact lists Pro Save and reuse distribution lists for sending tracked email invites in bulk.

---
URL: https://everypage.co/docs/conversion
Title: File conversion | EveryPage Docs
Description: Turning Word, PowerPoint and DocSend documents into tracked PDFs.

# File conversion.

Turning Word, PowerPoint and DocSend documents into tracked PDFs.

- Word to PDF Upload a Word document and receive a tracked, shareable PDF link in seconds—no manual conversion needed.
- PowerPoint to PDF Convert and share your PowerPoint presentations as tracked PDFs.
- DocSend to PDF Convert a DocSend document you have been given access to into a shareable PDF.

---
URL: https://everypage.co/docs/integrations
Title: Integrations | EveryPage Docs
Description: Connect EveryPage to Zapier, Make, n8n, WordPress, Notion and Slack.

# Integrations.

Connect EveryPage to Zapier, Make, n8n, WordPress, Notion and Slack.

- Zapier Connect EveryPage to Zapier to automate document uploads, manage sharing settings, and respond to reader activity.
- Make Use the EveryPage app in Make scenarios to upload PDFs, manage share settings, and react to reader events.
- n8n Workflow automation for document sharing, tracking, and triggered actions using the n8n community node.
- WordPress Upload PDFs to WordPress and share them as tracked, secure links with built-in analytics and embeds.
- Notion Embed documents in Notion, or sync reading sessions to a Notion database.
- Slack Post Block Kit messages to Slack when documents are viewed, downloaded, or gates are completed.
- Close Post document reads, downloads and form fills to the matching lead's timeline in Close CRM as an EveryPage activity.

---
URL: https://everypage.co/docs/developers
Title: Developers | EveryPage Docs
Description: API keys, scopes, authentication, the events feed, webhooks and OAuth apps.

# Developers.

API keys, scopes, authentication, the events feed, webhooks and OAuth apps.

- API keys and scopes Create and manage API keys for programmatic access to your EveryPage account.
- Authenticating with the API How to add credentials to API requests and understand the error responses the API returns.
- Events feed Poll EveryPage for reading activity and form submissions using the events API, an alternative to webhooks.
- Webhooks Send events to your endpoints when documents are viewed, downloaded, or interacted with.
- OAuth apps and oEmbed Build integrations with EveryPage's OAuth 2.0 provider and universal oEmbed embedding.
- MCP server for AI assistants Connect Claude, Cursor or any MCP client to EveryPage so it can share PDFs as tracked links and report who read them.
- API versioning and deprecation policy How the EveryPage API is versioned, what may change inside a version, and how deprecations and sunsets are announced in headers and docs.

---
URL: https://everypage.co/docs/account
Title: Account and billing | EveryPage Docs
Description: Signing in, plans and payment, and managing your account.

# Account and billing.

Signing in, plans and payment, and managing your account.

- Signing up and signing in Create an account, verify your email, and sign in securely to access your document library and advanced features.
- Billing and plans Manage your EveryPage subscription, upgrade plans, and understand billing through Stripe.
- Account settings Manage your profile, subscription, security settings, API access, and integrations from your account dashboard.
- Deleting your account Understand what happens when you permanently delete your EveryPage account and how to prepare.

---
URL: https://everypage.co/docs/getting-started/what-is-everypage
Title: What EveryPage is | EveryPage Docs
Description: Share a PDF via link and measure how it was read without storing visitor IP addresses.

# What EveryPage is

Share a PDF via link and measure how it was read without storing visitor IP addresses.

EveryPage is a document-sharing platform that encrypts your files and gives you a shareable link, plus detailed readership reporting on how pages were viewed. You can upload a PDF, configure privacy and security settings, and share with anyone—while seeing exactly which pages were read and how long they spent on each one.

## How it works

The basic flow is simple:

1. Upload — you upload a PDF (or Word/PowerPoint document, which gets converted to PDF)
2. Get a link — EveryPage generates a short, shareable link to your document
3. Share — send the link to recipients, or configure gates (password, email capture, expiry)
4. Measure — view detailed page-by-page readership analytics

Every document is stored encrypted at rest using AES-256-GCM. Visitor IPs are never stored in your records—instead, readers are identified using a salted pseudonym so you cannot link views to personal data.

## What you can store

EveryPage accepts PDF files only for storage. However, you can upload Word documents (.docx) or PowerPoint files (.pptx and .ppt legacy format), and they are automatically converted to PDF during upload. The converted PDF is what gets stored and shared.

Learn more in Uploading a document.

## How readers experience your document

Every file has a viewer mode that controls how the document is displayed to readers:

- Standard — one page at a time, with previous/next buttons and a page scrubber
- Flipbook — page-turn animation, in a single-page or two-page-spread layout
- Magazine — two-page spreads, navigated a spread at a time
- Swipe — one page at a time as a story-style card, advanced by swiping

All four modes are available on every plan, including free.

## Sharing and security

When you share a link, you control:

- Access — public link, password protection, or email capture gate
- Lifespan — set an expiration date, or choose never to expire (every plan)
- Permissions — allow or prevent downloads
- Page limits — show only a subset of pages (Pro only)
- Branding — custom domain (Pro only) or a short vanity slug (Pro only)

Documents are not ephemeral. Expiry is a feature you enable, not a default—files without an expiration date remain available indefinitely.

## Readership analytics

The analytics dashboard shows:

- Page-by-page views — how many times each page was viewed, and average time on it
- Reading depth — the complete funnel from first page to last
- Viewer modes — which display formats your readers used
- Geographic data — where readers are located (country-level)
- Trends — view volume over time and patterns

Your plan determines what analytics you can access. Free accounts see summary cards; Basic adds trends, the read-through funnel, audience breakdowns, and page-level stats; Pro adds reader identities and session history, live presence, and CSV export.

For details, see What EveryPage measures.

## Getting started without an account

You can upload and share a document without signing up. The file lives for 7 days and can be shared immediately via link. If you create an account later from the same browser session, you can claim the file into your account and unlock additional features like analytics and settings.

## Plans

Three subscription tiers are available:

- Free — up to 3 active documents, 20 MB per upload, summary readership
- Basic — up to 100 active documents, 200 MB per upload, trends and breakdowns, password protection
- Pro — unlimited active documents, 2 GB per upload, reader identities, custom domains, watermarking

For specific limits and feature comparison, see Plans and limits.

## Next steps

- Upload your first PDF
- Configure and share
- Share links and short IDs

---
URL: https://everypage.co/docs/getting-started/upload-your-first-pdf
Title: Uploading a document | EveryPage Docs
Description: Upload PDFs and Office files to EveryPage; understand file limits, supported formats, and what happens next.

# Uploading a document

Upload PDFs and Office files to EveryPage; understand file limits, supported formats, and what happens next.

Upload your documents to EveryPage using the drag-and-drop uploader or file browser. The platform accepts PDFs directly, plus Word and PowerPoint documents that are converted to PDF automatically in flight.

## Supported file types

EveryPage accepts the following file formats:

- PDF (.pdf) — uploaded directly
- Word (.docx) — converted to PDF automatically (requires conversion enabled)
- PowerPoint (.pptx, .ppt) — converted to PDF automatically (requires conversion enabled)
- Legacy .doc — not supported; save as .docx in Word or export as PDF

If the server has Office conversion enabled, the uploader displays "Drop your document here." When conversion is disabled, only PDFs are accepted and the uploader shows "Drop your PDF here."

Query the endpoint GET /api/upload/options to check whether the server accepts Office documents and what the format-specific size caps are.

## File size limits

Upload and storage limits depend on your subscription plan:

| Plan | Max upload size | Max active documents |
|---|---|---|
| Free | 20 MB | 3 |
| Basic | 200 MB | 100 |
| Pro | 2 GB | Unlimited |

These limits apply to the final stored file. For Office documents, source-format caps differ:

- Word documents — up to 25 MB before conversion
- PowerPoint files — up to 50 MB before conversion

If your source document exceeds its format cap, export it as a PDF and upload that instead.

## How the upload works

When you upload a file, EveryPage:

1. Streams the file — the entire file is never held in memory at once; bytes flow from your browser directly to the server and into encrypted storage
2. Converts Office documents — if you uploaded .docx, .pptx, or .ppt, the server streams it to the document conversion service and takes back a PDF, before encryption
3. Encrypts — the file is encrypted with AES-256-GCM and written to disk in chunks
4. Verifies size — once encrypted, the file is checked against your plan's storage cap (the converted PDF size is what counts for Office files)

If any step fails — the file is corrupted, the conversion service is down, or the final size exceeds your limit — the upload is aborted and no partial file is stored.

Conversion failures are reported with a specific status: 413 when the source exceeds its format cap, 422 when the document could not be converted, and 503 when the conversion service is unreachable. In each case the response body carries a message you can act on.

## What you get back

After a successful upload, the response includes:

- UUID — the canonical identifier of your file, used internally and in API calls
- Short ID — a 12-character base62 alias for sharing, always containing at least one uppercase letter; the shareable link is /{shortId}
- Share URL — a complete, ready-built link you can send immediately (e.g., https://everypage.co/Ab3xY9kQ2mZ7)

For anonymous uploads (no account):

- Claim token — a stateless signed token, valid for 30 days, that lets you attach the file to an account later from any browser session
- Manage token — a separate signed token that authorizes the settings write endpoint (PUT /api/v1/files/{uuid}/settings) for as long as the file stays unclaimed; a token caller gets free-tier fields only

## Anonymous uploads and expiry

Documents uploaded without an account are shareable by link immediately — anyone with the link can view it. These files are kept for 7 days before automatic deletion. If you sign up or log in from the same session, the file is claimed into your account. Claiming makes the file yours and clears the deletion date, so it stops expiring—unless you set an expiry yourself through the manage token, which is kept. You can change it afterwards on any plan, including to never.

For per-plan limits and details on claiming uploads, see Anonymous uploads and claiming.

## Next: Configure and share

After upload, you land on the Configure & Share screen where you can:

- Set a share link password or email gate
- Choose a viewer mode (standard, flipbook, magazine, swipe)
- Generate a QR code
- Create an embed code
- Set view limits or expiry dates

See Configure & Share for details.

## Conversion details

When you upload Word or PowerPoint files, EveryPage converts them to PDF before storage. The stored file is an ordinary PDF, so every downstream feature — the viewer, watermarking, readership — behaves exactly as it does for a directly uploaded PDF. The stored name takes the .pdf extension too: report.docx is stored as report.pdf.

Before conversion, the server checks the file's container signature: .docx and .pptx must be OOXML (Zip) files, and legacy .ppt must be an OLE2 compound file. A file whose contents do not match its extension is rejected rather than sent to the converter.

If conversion fails, exporting the document as PDF in Word or PowerPoint and uploading that works around the issue.

For more on format-specific conversion, see:

- Word to PDF
- PowerPoint to PDF

---
URL: https://everypage.co/docs/getting-started/configure-and-share
Title: Configure and share | EveryPage Docs
Description: Tour of the Configure & Share screen—where you customize your document's appearance, access controls, and reader interaction.

# Configure and share

Tour of the Configure & Share screen—where you customize your document's appearance, access controls, and reader interaction.

The Configure & Share screen is where you land after uploading a document. It shows a live preview of your PDF and organized panels for sharing, customizing appearance, and controlling access. Most settings save automatically a moment after you change them; passwords, expiry, vanity slugs, and the Google Analytics ID have their own apply buttons.

Anonymous uploaders can access this screen to share their link and adjust the viewer mode, but most settings require an account. You can claim the document into your account from this screen using the "Claim & unlock readership" form in the sidebar. For more detail, see anonymous uploads and claiming.

## Share

Access your shareable link, generate a QR code, and embed the document on external sites. The Share panel also lets you replace the file with a new version (Pro), set a custom domain link (Pro), and send tracked invites or emails to specific readers.

Learn more about share links and short IDs, QR codes, embedding, and replacing file content.

## Style

Customize the appearance of the viewer: background color, gradient, or image; page shadow depth; border radius; and edge rendering. A Basic plan allows these visual adjustments; they don't affect how the document itself appears, only its frame in the viewer.

Learn more about page style and behaviour.

## Branding

Add your logo to the viewer, position it, link it to your site, and hide the "Made with EveryPage" mark. A Basic plan is required for the panel. Pro adds a brand accent color, toolbar themes, badge positioning, and a call-to-action button. These settings let you mark the document as yours without altering the PDF content.

Learn more about branding and custom logos.

## Behavior

Choose a viewer mode—Standard (one page at a time with previous/next and a page scrubber), Flipbook (page-turn animation), Magazine (two-page spreads), or Swipe (story-style cards advanced by swiping)—and customize its behavior. For Flipbook, set the default layout (auto, 1-up, 2-up), adjust page-turn speed, enable sound, and switch to right-to-left reading. For Swipe, enable auto-advance and set the interval. All tiers can set the viewer mode; customizing behavior requires a Basic plan or higher.

Learn more about viewer modes.

## Hotspots

Draw clickable areas on your pages that open links, jump to another page, or play video, images, and audio. The whole panel is Pro. It shows how many hotspots you have placed and lets you edit them directly on the live preview; hotspot editing swaps the preview to a flat-page editor for precise drawing.

Learn more about interactive hotspots.

## Feedback

Enable comments and annotations, letting readers leave feedback directly on the document (Pro only). You can set whether comments are public or restricted to you, and receive notifications when readers comment. This panel is only accessible to authenticated users.

Learn more about comments and reader interaction.

## Proofing

Turn your document into a review surface where readers can mark pages as pick/maybe/reject (page verdicts) and draw annotations on specific areas (Pro only). Feedback is collected in your Readership dashboard. This panel is only accessible to authenticated users.

Learn more about read receipts and page marks and page marks.

## Privacy & Access

Control who can see your document and what they can do with it. Set a password, require an email to view, restrict viewer domains, capture lead data via a custom form, expire the link after a set period, limit the number of views before the document self-destructs, and control whether downloading is permitted. Configure view notifications to email you when readers open the document. Every plan, Free included, can set any expiry or none, and control downloads; Basic adds password protection, view limits, and view notifications; Pro adds email gates, domain restrictions, and custom lead-capture forms.

Learn more about password protection, self-destructing links, expiry and retention, email gates and lead capture, and view notifications.

## Protection

Add deterrents to prevent copying, printing, and screenshots. Block the right-click menu and text selection, hide the print button, blur pages when the reader's window loses focus (Pro), and apply a watermark with the reader's email or ID tiled across every page (Pro). These are browser-based controls, not encryption—a determined reader can still capture what they see. All deterrents require a Basic plan; watermarking and blur-on-leave are Pro features.

Learn more about watermarking and viewer protection.

## Key limitations

Settings are enforced server-side, so the UI showing a control does not guarantee your plan allows it. Controls for features above your tier are visible but disabled, with upgrade prompts directing you to the pricing page.

Already-expired or self-destructed (burned) documents refuse all settings writes and return an HTTP 410 error. Extend an expiry before it lapses — once a link has expired, the settings write cannot revive it. A burned link is un-burned by replacing its content (Pro), which resets the view counter and reopens settings.

---
URL: https://everypage.co/docs/getting-started/anonymous-uploads-and-claiming
Title: Sharing without an account | EveryPage Docs
Description: Upload and share a document without signing up, then claim it into an account for readership reporting and library features.

# Sharing without an account

Upload and share a document without signing up, then claim it into an account for readership reporting and library features.

You can upload and share a document without creating an account. The file is encrypted and shareable by link as soon as the upload completes. You can then claim it into an account to gain readership reporting, a library entry, and the settings your plan allows.

## Uploading anonymously

An anonymous upload works like an ordinary upload: you select a PDF (or a Word or PowerPoint file, which is converted to PDF in flight), configure sharing options, and receive a shareable link. Anonymous uploads use the Free tier's size cap. The file is encrypted and stored on EveryPage's servers for 7 days, and anyone with the link can view it immediately—no account required on either side.

Anonymous uploads are created in an unclaimed state. This means the document does not appear in your library, you cannot see who reads it, and you have no access to readership reports or settings like password protection. The file is purely public-by-link.

## What you can do without signing in

From the same browser session where you uploaded the file, you can:

- Share the link, generate a QR code, or embed the document
- Download the PDF
- Change the viewer mode (standard, flipbook, magazine, swipe)

Changing the viewer mode is the only setting the uploading browser session can change before the document is claimed. Everything else—readership reporting, a library entry, expiry dates, passwords, watermarks, and lead-capture gates—requires claiming the document into an account.

## The seven-day retention window

Anonymous uploads are kept for 7 days from upload. After that window, the file expires and the link stops working. Claim the document into an account if you want it to outlive that window.

If you claim the document into an account before it expires, it becomes yours and stops expiring: the 7-day deadline (365 days for Canva publishes) is cleared, just as a signed-in upload starts with no expiry. The exception is an expiry you set yourself through the manage token before claiming—that one is kept, so a link you shared on that promise still expires when you said it would. In both cases you can change the expiry afterwards, including to never.

## Claiming the document

You claim an anonymous upload by signing up or logging in from the same browser session. When you complete signup or login, EveryPage automatically attaches the document to your new or existing account.

Once claimed, the document:

- Appears in your library with no expiry, unless you chose one through the manage token (you can change it either way, including to never expire)
- Unlocks readership reports, subject to your plan's tier
- Becomes editable: depending on your plan you can add a password, change the expiry, add a watermark, capture leads, enable comments, and more
- Counts toward your plan's active-file cap (Free: 3 files, Basic: 100 files, Pro: unlimited)

If the claim would push you over your plan's active-file cap, it is refused and the document stays unclaimed. Free a slot or upgrade, then sign in again to complete the claim.

Signing in from a different browser or device does not automatically claim the document, because the session flags are browser-local. To claim on a different device, open the claim link (/api/claim?token=...) built from the claim token in the original upload response.

## Rate limits

Anonymous uploads have two safeguards against abuse:

- Per-uploader cap: one uploader can hold up to 20 live unclaimed uploads at a time. The uploader is a pseudonymous identifier derived from the IP address by a salted HMAC — the address itself is never stored. Claiming, expiry, deletion, or moving to trash frees a slot. Exceeding the cap returns 429.
- Per-IP rate limit: the upload endpoint is rate-limited by IP.

## Tokens and programmatic access

When you upload anonymously, the response includes two tokens:

- Claim token — a 30-day credential that attaches the file to an account, either by opening GET /api/claim?token=... in a browser or by posting it to POST /api/v1/files/claim with an API bearer credential. The Canva import path also uses claim tokens.
- Manage token — a 30-day bearer credential that authorizes PUT /api/v1/files/{uuid}/settings on the anonymous file before it is claimed. It acts as an unauthenticated caller, so it can only set the fields available on the Free tier; content replacement stays closed to it. Once you claim the document, the manage token no longer works.

Both tokens are HMAC-signed and stateless—they carry no server-side state and expire after 30 days whether or not they are used. You cannot extend them.

## See also

- Upload your first PDF
- Configure and share
- Expiry and retention
- Plans and limits

---
URL: https://everypage.co/docs/getting-started/plans-and-limits
Title: Plans and limits | EveryPage Docs
Description: Reference for plan features, hard caps, and tier-specific restrictions across EveryPage.

# Plans and limits

Reference for plan features, hard caps, and tier-specific restrictions across EveryPage.

EveryPage pricing is flat per account. There are no seats, and there is no multi-user or team model: an account is a single login that owns its own files. This page is the hard-limits reference; to compare plans and pricing side by side, or to change plans, use the pricing page.

## Plan comparison

| Feature | Free | Basic | Pro |
|---|---|---|---|
| Price | $0 | $9/month or $90/year | $29/month or $290/year |
| PDF uploads | ✓ | ✓ | ✓ |
| Share links | ✓ | ✓ | ✓ |
| Password protection |  | ✓ | ✓ |
| View notifications |  | ✓ | ✓ |
| Folders |  | ✓ | ✓ |
| Receipt confirmations |  | ✓ | ✓ |
| View limits (self-destruct) |  | ✓ | ✓ |
| Appearance customization |  | ✓ | ✓ |
| Readership trends & analytics |  | ✓ | ✓ |
| Reader identities & live presence |  |  | ✓ |
| CSV export |  |  | ✓ |
| Watermarking |  |  | ✓ |
| Email capture gate |  |  | ✓ |
| Domain allowlist |  |  | ✓ |
| Lead-capture forms |  |  | ✓ |
| Never-expiring links | ✓ | ✓ | ✓ |
| Custom domains |  |  | ✓ |
| Custom link names (slugs) |  |  | ✓ |
| Link variants |  |  | ✓ |
| Page ranges |  |  | ✓ |
| Webhooks | ✓ | ✓ | ✓ |

## Upload and storage limits

| Limit | Free | Basic | Pro |
|---|---|---|---|
| Max file size | 20 MB | 200 MB | 2 GB |
| Active files (live) | 3 | 100 | Unlimited |
| Convert Word (.docx) | Up to 25 MB | Up to 25 MB | Up to 25 MB |
| Convert PowerPoint (.pptx/.ppt) | Up to 50 MB | Up to 50 MB | Up to 50 MB |

The conversion caps apply to the source document and are the same on every plan. The max file size above applies separately to the stored artifact — the converted PDF — so on Free a 25 MB Word file still has to convert down to 20 MB or less.

## Link expiry

Expiry is uncapped on every plan: set any window, or none. A newly uploaded file starts with no expiry until you set one yourself.

Only anonymous uploads carry a fixed lifetime (see below), and an anonymous document edited through a manage token is capped at 7 days with no never-expire until it is claimed.

## Trash and recovery

Deleted files enter trash (recoverable) only on Basic and Pro plans. Free-tier deletions are immediate and irreversible.

| Tier | Recovery window |
|---|---|
| Free | Immediate hard delete (no recovery) |
| Basic | 7 days |
| Pro | 30 days |

## Readership and analytics

Every plan tracks views and downloads. The readership features you can access depend on your subscription tier.

Free: Per-file summary only — view count, total sessions, unique readers, unique countries, average time, and download count.

Basic: Everything in Free, plus trends over time, the read-through completion funnel, referrer/browser/device/country/source/viewer-mode breakdowns, peak-time heatmap, median time, and per-page view statistics.

Pro: Everything in Basic, plus reader identities (pseudonymous reader IDs), recent-session detail, new-versus-returning readers, live-presence reader count, and CSV export of all sessions including captured email, device details, and lead-capture form submissions.

## Webhooks

Webhooks are available on all plans (free, basic, pro). A single account can create up to 25 webhooks. The one exception: deliveries for gate.completed events (when a viewer submits a lead-capture form) require the file owner to be on the Pro plan at the time of the event.

## Anonymous uploads

Unauthenticated (anonymous) browser uploads are retained for 7 days from upload and use the Free tier's size cap. An uploader can hold up to 20 live unclaimed anonymous files at once; claiming, expiry, deletion, or moving to trash each free a slot. Documents published from Canva are retained for 365 days from publishing, republishing a live design restarts that clock, and they have their own budget of 100 live unclaimed files per Canva account.

Once claimed by signing up or logging in from the uploading session, the file moves into the account and counts toward the plan's active-file cap. Claiming makes the document yours: its expiry is cleared and it stops expiring, unless you chose an expiry yourself through the manage token, in which case that is kept. You can change it afterwards either way, including to never.

## Document features and limits

| Feature | Free | Basic | Pro |
|---|---|---|---|
| Comments/reader notes |  |  | ✓ |
| Page marks (verdicts) |  |  | ✓ |
| Annotations |  |  | ✓ |
| Watermarks on pages |  |  | ✓ |
| Email capture gate |  |  | ✓ |
| Domain allowlist |  |  | ✓ |
| Lead-capture forms |  |  | ✓ |
| Variants per file | – | – | 200 max |
| Page ranges (shared excerpt) |  |  | ✓ |
| Assets per file (Basic and above) |  | 10 max | 10 max |
| Hotspots per file |  |  | 300 max |
| Hotspots per page |  |  | 30 max |

Image assets (logo, background, hotspot images) are limited to 5 MB each. Audio assets (hotspot audio) are limited to 10 MB each. The logo and background replace in place, so re-uploading one never adds to the per-file asset count.

## Invitations

| Tier | Daily limit | Per-request limit | Supports lists |
|---|---|---|---|
| Free | 0 | – | No |
| Basic | 50 | 10 direct emails | No |
| Pro | 1,000 | Bounded only by the daily cap | Yes |

Basic-tier users can send up to 10 direct emails per invitation request. Pro users can also send to a saved distribution list. The daily cap counts every invite created since UTC midnight across all of your files; exceeding it returns 429 and the whole send is refused.

## Lead-capture forms

When enabled on a file, a lead-capture form (Pro only) gates viewing behind custom fields. Forms support up to 5 fields total, including exactly one email field. Field constraints:

- Field label: 60 characters max
- Field key (identifier): starts with a lowercase letter, then lowercase alphanumerics and underscores, max 40 characters
- Text/phone/company value: 200 characters max
- Email value: 254 characters max

Email-gate domain allowlists (Pro only) support up to 20 domains, each up to 253 characters.

## Bulk operations

Bulk delete, restore, and move-to-folder operations accept up to 100 files per request. Moving files into a folder in bulk requires Basic or above, because folders themselves start at Basic.

## No per-user/per-seat pricing

All pricing is flat per account. There are no seats to buy and no per-user charges. EveryPage has no team or multi-user accounts: files belong to the single account that uploaded or claimed them, and there is no way to add collaborators to an account.

## Additional resources

- Billing and account management
- Readership reporting details
- Link expiry and data retention
- Trash and file recovery

---
URL: https://everypage.co/docs/sharing/share-links-and-short-ids
Title: Share links and short IDs | EveryPage Docs
Description: Understand the three identifier forms in an EveryPage share link and which to use where.

# Share links and short IDs

Understand the three identifier forms in an EveryPage share link and which to use where.

Every EveryPage file has a shareable link, but that link can take three different forms depending on your settings and plan. Understanding the differences between them helps you choose the right form for each use case.

## The three identifier forms

When you upload a file to EveryPage, the system mints two identifiers for it — a UUID and a short ID. The third form, the vanity slug, is optional and set by you. All three shapes are disjoint by construction:

| Identifier | Format | Notes |
|---|---|---|
| UUID | 36 characters: hex digits and hyphens (e.g., a1b2c3d4-e5f6-7890-abcd-ef1234567890) | Canonical identifier; every file has one. Long but unambiguous. |
| Short ID | 12-character base62 alphanumeric, always containing at least one uppercase letter (e.g., aBcD1ef2gHiJ) | Minted at file creation for all new files. Shorter and easier to read or recite. |
| Vanity slug | Lowercase letters, digits and single hyphens, up to 64 characters (e.g., my-project-proposal) | Pro tier only, optional, and set by you. Unique per owner. Resolves only on your verified custom domain. |

The uppercase requirement in short IDs is by design—it makes them distinguishable from vanity slugs (which are always lowercase) at a glance, so EveryPage's resolver never has to guess which identifier type you handed it.

## Which link form do you get?

When you upload a file, the EveryPage API returns three pieces of information: the uuid, the shortId, and a ready-built shareUrl. You do not have to construct the URL yourself. For newly uploaded files, the share link uses the short ID form, because the file has no vanity slug yet.

If you set a vanity slug on a Pro account (via the file settings), the file's advertised share link switches to the slug form—on the condition that your account has a verified custom domain. Slugs do not resolve on the canonical everypage.co domain; they work only on a custom domain you own and have verified.

## Human-facing vs. durable links

The share URL preference order is:

1. Vanity slug (if set, owner is Pro, and the link is on the owner's custom domain)
2. Short ID
3. UUID (legacy fallback for files created before short IDs existed)

This order applies to any link you share publicly or send to a recipient. However, frozen artifacts—printed QR codes, embed snippets, and the iframe URL returned by oEmbed—always use the durable short-ID form (or UUID), never the slug.

Why? A vanity slug can be renamed at any time. A printed QR code cannot. If a recipient scans a QR code only months later, the slug might have changed hands or been repurposed, and the link would break. The short ID remains stable for the life of the file, so frozen artifacts use it to guarantee durability. When you generate a QR code or embed snippet for a file, EveryPage automatically selects the durable form.

## Session state and identifiers

Session gate flags—password verification, email capture, anonymous upload ownership—are keyed off your file's canonical UUID, never off whichever identifier appeared in the URL. Stored file paths and database writes key off the UUID too. This means a viewer who unlocked a file via one form (e.g., the slug) stays unlocked when accessing it via another form (e.g., the short ID). The URL identifier is only a routing mechanism; the underlying state is independent of how the visitor arrived.

## Rate limiting

Vanity slugs are short and guessable, so public file access is rate limited to 60 requests per minute per visitor IP address. This limit applies to the share URL itself, download requests, QR code requests, embed loads, and oEmbed. Short IDs are 12 random base62 characters and are not practically guessable.

## Storage and custom domains

Vanity slugs are stored in your file's settings and, on the Pro plan, can be changed at any time via the file configuration panel. Changing to a different slug releases the old one for reuse on another of your files. Clearing the slug field returns the file to using the short ID form for human-facing links.

Custom domains are a Pro feature. For details on setting one up and how it affects your share links, see Custom domains. For information on creating custom per-recipient links with their own short IDs, see Link variants.

## Next steps

- Vanity slugs — customize your share link
- QR codes — generate QR codes for your files
- Embedding — embed your files on a website
- Custom domains — serve links from your own domain

---
URL: https://everypage.co/docs/sharing/vanity-slugs
Title: Vanity slugs | EveryPage Docs
Description: Create readable custom URLs for your documents using vanity slugs instead of random short IDs.

# Vanity slugs

Create readable custom URLs for your documents using vanity slugs instead of random short IDs.

A vanity slug is a custom name you assign to a document, replacing its auto-generated short ID with a readable URL. Slugs are Pro-only and only resolve on your verified custom domain —they have no effect on everypage.co.

## Setting a vanity slug

To name a document, open its sharing settings and look for the "Custom Link" field. Type your preferred name (lowercase letters, digits, and single hyphens only; up to 64 characters). When you have an active, verified custom domain, the preview shows you the full URL on your domain—for example, https://documents.example.com/annual-report.

If you don't yet have a verified custom domain, the field is disabled. Add and verify one in your Account settings first; slugs depend on it.

## Character rules and validation

Slugs accept lowercase letters (a–z), digits (0–9), and hyphens. The following rules are enforced:

- Must start and end with a letter or digit (no leading or trailing hyphens)
- Hyphens must be single—no double or consecutive hyphens
- Maximum 64 characters
- Anything you type is lowercased before it is saved, so My-Report and my-report are the same slug
- Unique per owner: you cannot assign the same slug to two different documents on your account
- A slug shaped like a UUID is rejected, because UUID-shaped paths resolve as UUIDs first and the slug would never be reached

If you try to use a reserved word (such as api, docs, pricing, or login), the save is rejected because those paths belong to EveryPage itself.

## Slug resolution and custom domains

This is the critical constraint: a slug only resolves to its document when accessed on your active, verified custom domain. Accessing the same slug on everypage.co returns 404. This is by design—slugs are guessable, so they only work on a host that is bound to one owner (your custom domain), never the public canonical host where thousands of files live.

If your custom domain is not yet verified, or becomes inactive because verification is removed or the account is no longer Pro, slug URLs stop working. Nothing redirects: the slug URL simply stops resolving, and the document remains reachable through its short ID or full UUID, which resolve on every host.

## Renaming and consequences

You can change a document's slug at any time. A renamed slug breaks any link already shared under the old name—visitors who click the old URL get 404. Inform recipients if you rename a link after sharing.

Because of this, slugs are poor choices for permanent shared links. If you need a link that never changes, use the document's short ID instead, which is immutable. Frozen artifacts (QR codes, embedded viewers, and oEmbed) always use the short ID or UUID, never the slug, to ensure those links stay valid even if you rename the document later.

## Clashes and per-owner uniqueness

Each slug you create must be unique within your account. If you try to assign a slug that is already in use on another of your files, the save is rejected (HTTP 409). Rename one of the conflicting slugs and try again.

A document you have moved to trash keeps its slug reserved until it is purged, so the name is not immediately free for another document.

Different owners can use the same slug name on their own custom domains—the uniqueness constraint is per owner, not global.

## See also

- Custom domains —set up the domain first
- Share links and short IDs —the immutable alternatives
- QR codes —use short IDs, not slugs, for permanence
- Embedding —use short IDs in embeds
- Pro plan features —pricing and tier comparison

---
URL: https://everypage.co/docs/sharing/link-variants
Title: Link variants | EveryPage Docs
Description: Create separate tracked links for each recipient, with independent revocation and per-recipient download and page-range overrides.

# Link variants

Create separate tracked links for each recipient, with independent revocation and per-recipient download and page-range overrides.

Link variants let you create multiple tracked links from a single document, one per recipient. Each variant gets its own short link and optional setting overrides, so you can track readers individually and revoke one recipient's access without affecting others.

## How variants work

A variant is a child link on your document with its own 12-character short identifier (the same shape as a file short ID) and an optional recipient label of up to 200 characters. The label is the only personal data stored. Each document supports up to 200 variants. When a reader opens a variant link, the access is attributed to that recipient in readership reporting and webhook payloads. Variant links resolve on your custom domain just like the parent document's own link, so each recipient's link can carry your brand instead of everypage.co.

Variants are managed through the API, not the document settings screen: /api/files/{uuid}/variants for session-authenticated dashboard clients and /api/v1/files/{uuid}/variants for bearer tokens (files:read to list, files:write to create, update and delete). Both surfaces require the Pro plan and ownership of the file.

## Settings overrides

Each variant can override two file-level settings for that recipient alone: download permission and page range. Overrides are optional — a variant without overrides simply inherits the parent file's settings.

### allowDownload

By default, a variant inherits the parent file's download setting. If you set allowDownload: false on a variant, that recipient cannot download the file, even if downloads are enabled on the parent document. This is useful when you want to restrict archiving for a particular recipient but allow others to download.

### pageRange

By default, a variant shows the full document or the page range set on the parent file. You can override this for a variant by setting pageRange: { from: 5, to: 10 } to show only pages 5–10 for that recipient. The pair must satisfy 1 <= from <= to; anything else is rejected with HTTP 400. The explicit override pageRange: { from: 0, to: 0 } clears the override entirely, serving the full document through that variant even when the parent has a range.

Ranged serving rewrites the PDF on every request, so page ranges — on the parent file or on a variant — are refused on documents larger than 100MB.

### Important: overrides are replaced, not merged

When you update a variant's overrides, the entire override object is replaced with exactly what you send — it is never merged with the stored value. This means:

- Sending { "overrides": { "allowDownload": false } } replaces any stored overrides; if the variant previously had a pageRange override, it is removed.
- Sending { "overrides": {} } clears all overrides.
- Omitting the overrides field entirely keeps the stored overrides unchanged.

To remove one override while keeping another, send an overrides object containing only the override you are keeping. This is deliberate: a merge strategy would make it impossible to express "remove this override," because a JSON decoder cannot distinguish between a key that was explicitly set to null and a key that was absent.

## Revoking variants

You can revoke a variant at any time, which immediately blocks access to that link. A revoked variant returns a uniform 404 response — indistinguishable from a link that never existed — so a revoked recipient cannot learn whether the canonical document exists or that their access has been removed.

Revocation is reversible: set revoked: false in an API update to restore the link. Deleting a variant is not.

## GDPR redaction

For compliance with data-protection regulations, you can permanently delete a variant's recipient label by including the ?redact=1 query parameter on a DELETE request. Redaction:

- NULLs the variant's label permanently (the label can never be set again)
- Transactionally scrubs the label from all stored webhook delivery payloads that reference this variant
- Preserves the variant itself and its view history, so readership analytics remain intact

Both forms of DELETE return HTTP 204 No Content on success. Hard deletion (without ?redact=1) removes the variant entirely and scrubs the label from stored webhook payloads in the same way, but the variant's view-session records lose their attribution: the rows survive with their variant reference set to NULL.

## Important limitation: gates and passwords are NOT per-variant

Every gate (email verification, password protection) applies to the entire file, not individual variants. A reader who passes an email gate or enters a password through one variant has satisfied that gate for all of the file's links. You cannot require different passwords for different recipients or set per-recipient email gates. For truly isolated experiences, use separate documents.

## Analytics and webhooks

Each view session records the variant it started on. The per-file readership response then carries a Pro-only variants breakdown — sessions and average read time per variant, with each entry's label, revoked state and redacted state — omitted entirely when the file has no variants. See Audience breakdowns.

Webhook events (file.viewed, file.downloaded) include variantUuid and variantLabel in the payload, so your integrations can route notifications based on which recipient opened the file. variantLabel is absent for unlabelled and redacted variants, and the canonical link's own events carry neither field.

## Known behavior

Any recipient who actually opens their variant link can see the canonical document UUID in the public file metadata response. Revocation therefore only prevents future access; it does not prevent a recipient who has already viewed the document from proving they had access. If you need to truly erase a recipient's knowledge of the file, redaction is not sufficient — you must assume the canonical UUID is known to anyone who opened their link.

## Related

- Share links and short IDs — how short identifiers work and how the system resolves links
- Download control — the parent document's download setting and how variant overrides interact with it
- Page range links — page-range setup and enforcement
- Audience breakdowns — how the Pro-tier Variants breakdown works
- Webhooks — how variant attribution flows into event payloads
- Plans and limits — tier requirements and variant caps

---
URL: https://everypage.co/docs/sharing/qr-codes
Title: QR codes | EveryPage Docs
Description: Generate QR codes for your documents that encode durable short-ID links and survive slug renames.

# QR codes

Generate QR codes for your documents that encode durable short-ID links and survive slug renames.

EveryPage generates QR codes for any document on any plan. Scan the code to open the document in your browser, and the view is attributed to the qr source in your readership analytics. If you just want to turn a document into a scannable code in one step, the PDF to QR code tool does exactly that from a single upload — no account required.

## What the QR encodes

The QR code contains your document's durable short-ID URL with ?via=qr appended. This attribution parameter ensures that views triggered by scanning the code appear as the qr source in your audience breakdowns, distinct from direct link clicks or other referral sources.

The code never encodes your vanity slug. A printed QR code cannot be reissued, but slugs can be renamed, so a code built on a slug would break the first time the slug changed. Encoding the short ID means a rename does not touch it. (Documents without a short ID — those created before short IDs existed — get their UUID instead.)

## Durability across changes

Because the QR links to the durable short-ID form, it also survives content replacement. When you swap out a document's contents, every printed code keeps working — the short-ID always resolves to the current document behind that link.

The host in the encoded link is not fixed, however. If your account has an active custom domain at the moment the code is generated, the code encodes the short-ID link on that domain. A code printed while a custom domain was active therefore depends on that domain staying verified and on Pro — if the domain is removed or the plan drops below Pro, the branded host stops serving and only codes generated on everypage.co keep resolving.

## Downloading and using QR codes

Open a document's Configure & Share page, expand the Share panel and choose "QR Code". The modal shows the code and offers "Download QR Code", which saves it as a PNG. The button is available before a document is claimed, so anonymous uploaders can take a code away with the link.

The image is generated per request at /api/files/{id}/qr-code and served with Cache-Control: public, max-age=86400, so consumers that hotlink it (notably Notion databases, which re-request the image on every table render) cache it for a day rather than re-fetching each time.

The same handler is also mounted at /api/files/{id}/qr-code.png. It serves an identical image and headers; some consumers — including Notion, which renders an external URL as an image thumbnail only when the path carries an image extension — need the extension. Both forms encode the durable short-ID URL.

The same code is available to integrations at GET /api/v1/files/{id}/qr-code with an API key holding the files:read scope.

## Attribution and analytics

Scans report source: qr in your readership data, so codes on printed material can be separated from direct link visits in the source breakdown. Attribution comes from the ?via=qr parameter in the encoded link, so it applies to anyone who opens that exact URL — including someone who copies it out of a scan rather than scanning it themselves.

## Related

- Share links and short IDs — how short-ID links work
- Vanity slugs — custom URL paths and why they do not appear in QR codes
- Dynamic links — content replacement and link durability
- Audience breakdowns — view your readership by source

---
URL: https://everypage.co/docs/sharing/embedding
Title: Embedding a document | EveryPage Docs
Description: Use oEmbed or the embed code snippet to display your EveryPage documents on external websites.

# Embedding a document

Use oEmbed or the embed code snippet to display your EveryPage documents on external websites.

Embedding displays an EveryPage document inside a page on your own site — a blog post, a landing page, a client portal — using an iframe. The embedded viewer is the same viewer as the share page with its surrounding chrome removed, and it is subject to one structural constraint: a cross-site iframe does not carry EveryPage session cookies, so settings that depend on a session gate cannot be satisfied inside an embed.

## How embedding works

EveryPage documents are embedded via a dedicated /embed/ path that serves the same viewer as the share page — honouring your viewer mode — but without the page chrome around it. The /embed/ path is the only one served with a framing policy that permits foreign sites (frame-ancestors *); an ordinary share URL is sent with frame-ancestors 'none' and a browser will refuse to render it in an iframe. Always embed the /embed/ form.

When readers view your document through an embed, their views appear in your readership analytics with source: embed, so you can distinguish between direct visits and embedded visits.

## Embed code and the embed URL

The Share panel on a document's Configure & Share page shows a ready-made snippet:

```html
<iframe src="https://everypage.co/embed/aBcD1ef2gHiJ" width="100%" height="600" style="border:none;"></iframe>
```

The src attribute always uses your document's durable short ID (or its UUID, for documents created before short IDs existed), never a vanity slug. This is a frozen-artifact rule: an embed snippet pasted into a website today must survive a slug rename. The host, however, is whichever base your links use at the time the snippet is generated — if you have an active custom domain, the snippet points at that domain and depends on it staying verified and on Pro.

Some platforms (notably Notion's Embed block) construct the iframe themselves from a pasted URL. For those, copy the bare embed link instead:

```
https://everypage.co/embed/aBcD1ef2gHiJ
```

The Share panel provides both — a "Copy" button for the iframe snippet and a "Copy embed link for Notion" button for the bare URL.

## Limitations with gated documents

The embed viewer refuses to render four kinds of document, and shows a short notice with an "Open document" link to the direct share URL instead:

| Setting | Why the embed refuses |
|---|---|
| Password protection | The password is verified against a session cookie, which a cross-site iframe does not carry |
| Email gate | Same session-cookie constraint; the reader must pass the gate on the direct link |
| Lead-capture form fields | As above, with a message naming the form |
| View limit | Every iframe load would consume one of the document's remaining views |

Password protection also removes the embed code from the Share panel entirely, replacing it with a note that embedding is disabled for password-protected PDFs. The other three settings still show the snippet — the refusal happens when a reader loads the frame.

If a document needs access control, share the direct link rather than an embed.

## oEmbed auto-embedding

oEmbed is a discovery protocol that lets a platform turn a pasted link into an embedded viewer without you writing any HTML. WordPress is the main consumer that uses it against EveryPage. The platform calls the endpoint with your link:

```
GET /oembed?url=https://everypage.co/aBcD1ef2gHiJ
```

The endpoint is public and unauthenticated. It accepts all three identifier forms — short IDs, UUIDs and vanity slugs — plus link-variant short IDs and /embed/ URLs, and returns a type: rich JSON payload whose html is an 800×600 iframe on the /embed/ path. As with the copied snippet, that iframe is built from the parent document's durable identifier, never a slug and never the variant.

Vanity slugs are resolved against the host in the url you pass, so a slug only resolves when the link was written on the owner's own custom domain. Every dead shape — unknown identifier, expired, burned, or a slug presented under the wrong host — answers the same 404, with no detail that would distinguish them. Requesting format=xml (or any format other than json) answers 501; omitting url answers 400.

### WordPress

WordPress treats an unknown oEmbed provider as untrusted and renders it in a sandboxed iframe with an opaque origin. The EveryPage viewer cannot boot inside that sandbox, because its requests for assets and public read endpoints fail the origin check. This is a real limitation, not a configuration mistake: a plain paste on a site without the plugin will not render the document.

The EveryPage WordPress plugin fixes it by registering everypage.co as a trusted provider on the site it is installed on, so the iframe is not sandboxed and the viewer loads normally.

### Notion

Notion does not need oEmbed. Paste the bare embed link (not the iframe snippet) into a Notion page and choose Embed — not Bookmark — from the menu Notion offers. Notion builds the iframe itself and the viewer loads.

### Discovery

Consumers find the endpoint in two ways, both automatic:

1. A static oEmbed <link> in the served HTML shell. WordPress reads raw HTML without running JavaScript, so this is the tag it uses; it appends ?url= to the endpoint itself.
2. A per-document oEmbed <link> that the viewer page injects at runtime, for consumers that execute JavaScript.

## Availability

Embedding — both the snippet and oEmbed — is available on every plan, including free, and on unclaimed anonymous uploads. Apart from the four settings listed above, file settings behave on an embed exactly as they do on the share page, and embed views are recorded as source: embed.

## Related

- Share links and short IDs — how short-ID links work
- Vanity slugs — custom URL paths and durability
- QR codes — generate QR codes for your documents
- WordPress integration — set up trusted embedding on WordPress sites
- Audience breakdowns — track views by source including embeds

---
URL: https://everypage.co/docs/sharing/custom-domains
Title: Custom domains | EveryPage Docs
Description: Serve your documents from your own branded subdomain with automatic SSL.

# Custom domains

Serve your documents from your own branded subdomain with automatic SSL.

A custom domain serves your share links from a subdomain you own, such as docs.yourcompany.com, instead of everypage.co. Share links, QR codes and embed snippets generated while the domain is active all point at it. One domain per account. Adding and verifying a domain requires Pro.

## Setting up a custom domain

Custom domains are subdomains only — a root domain (example.com, example.co.uk) is rejected, because routing to it would need an A record. You will need to add two DNS records at your domain provider.

1. Add your domain on the Account page, under Custom domain. Enter a subdomain like docs.yourcompany.com and click "Add domain".
2. Create two DNS records. Both target values are printed on the Account page once the domain is added — copy them from there rather than from any documentation, as the CNAME target is set per deployment:
  - A CNAME record pointing docs.yourcompany.com at the CNAME target shown on the Account page
  - A TXT record at _everypage.docs.yourcompany.com whose value is the verification token shown on the Account page

If your DNS provider proxies records (for example, Cloudflare's orange-cloud setting), set the CNAME to "DNS only" instead of proxied. Providers that flatten CNAMEs into ALIAS records also verify, as long as the name resolves to the same addresses as the target.

3. Verify ownership with "Verify domain" on the Account page. Both records are checked; if either is missing, the page names which one. DNS changes can take up to an hour to propagate. Once both checks pass, EveryPage registers the hostname with Cloudflare, which issues the HTTPS certificate.

Until then the status reads "Waiting for DNS verification". After verification it shows "Verified · certificate provisioning…" while the certificate is being issued, then "Verified & active".

## What a custom domain serves

A custom domain is a document-serving surface only; it does not mirror the rest of the account. Anything outside an explicit allowlist of viewer paths returns 404 on that host, so sign-in, billing and account pages can never execute on a customer hostname.

The allowlist covers:

- Document share links (/<identifier>) and the viewer pages behind them
- The embed path (/embed/<identifier>)
- The viewer's own API calls — metadata, download, password verification, view and page telemetry, notes, receipts, page marks, annotations, hotspots, reporting
- oEmbed discovery (/oembed), so consumers can resolve links written on your domain

Sign-in, signup, account settings, upload, billing, readership dashboards and admin all live on everypage.co only. A custom domain also serves only its own owner's documents: another account's link pasted under your host returns 404.

## Vanity slugs and custom domains

Vanity slugs (all-lowercase custom identifiers like /reports) resolve only on your verified custom domain. On the canonical everypage.co domain, share links use short IDs instead.

A slug is only usable while the domain is active — that is, verified and on Pro. If the domain is removed or the plan drops below Pro, slug links stop resolving, and the short-ID form on everypage.co is what still works.

## Permanent links and frozen artifacts

QR codes and embed snippets use the durable short-ID path, never a vanity slug, so they survive a slug rename.

The host is a separate question. Both are generated against whichever base your links use at that moment, so an artifact produced while a custom domain is active carries that domain — and stops working if the domain is later removed or the account drops below Pro, because an inactive custom host serves nothing. Artifacts produced before you added a domain point at everypage.co and keep working regardless. If you print codes or hand out embed snippets, do it after the domain decision is settled.

## Managing your domain

### Removing a domain

"Remove" on the Account page deletes the domain and releases its Cloudflare hostname registration, which also removes the certificate. New links revert to everypage.co immediately, slug links stop resolving, and any QR code or embed snippet already produced on the branded host stops working.

Removal itself is not tier-gated — the endpoint accepts the request on any plan — but the Account panel that exposes the control is replaced by an upgrade prompt below Pro. In practice, remove or change a domain before downgrading; after a downgrade the domain stays on file, stops serving, and cannot be removed from the interface until Pro is restored.

### Downgrading below Pro

The domain record is kept, but it goes inactive: the host serves nothing, share links go back to the everypage.co short-ID form, and slug links stop resolving. Restoring Pro reactivates the same domain without re-verifying.

### Replacing a domain

Remove the current domain first, then add the new one — the Account page only offers the entry field when no domain is configured. The replacement starts its verification from scratch with a fresh token.

## DNS troubleshooting

If verification fails, check:

- The CNAME record points to the exact target value shown (spaces or typos prevent routing)
- The TXT record is at the exact host _everypage.<your-domain> with the exact token value
- DNS changes have propagated (this can take up to an hour)
- If your provider proxies by default (like Cloudflare's orange cloud), the CNAME must be set to "DNS only"

Verification is a live DNS check, so once both records are correct, click "Verify domain" again — there is no waiting queue.

Adding a domain can also fail before verification starts: "That domain is already in use" means another EveryPage account has registered the same hostname, and "root domains aren't supported" means you entered a registrable domain rather than a subdomain of one.

## Related topics

- Vanity slugs customize short link identifiers
- Branding and logo add your company appearance to the viewer
- Plans and limits compare Pro and other features

---
URL: https://everypage.co/docs/sharing/share-by-email
Title: Sharing by email and social | EveryPage Docs
Description: Send your document link to recipients by email, or share on social platforms.

# Sharing by email and social

Send your document link to recipients by email, or share on social platforms.

EveryPage can hand your share link to someone for you: by email, sent from EveryPage with a personal note, or through a social network's own share composer. Both send the same link a reader would get from anywhere else.

## Share by email

Send your document link to one recipient with an optional personal message. The "Email" button is in the Share panel on the document's Configure & Share page; it appears only when you are signed in. There is no email-share action in the library.

The form asks for a recipient name and a recipient email — both are required — plus an optional message. The email that goes out is addressed to the recipient by name, states that you shared a PDF with them, quotes your message if you wrote one, and carries the link.

You can only email links to your own documents: the endpoint checks ownership and refuses anything else, so it cannot be used to send mail about someone else's file. Sends are rate limited to 10 requests per minute per IP address.

Recipients get the ordinary share link, so the document's settings apply as usual — a password or email gate is presented to them exactly as it would be on any other visit.

Available to: Any signed-in account, on any plan. Anonymous uploaders must claim their document first; before that the button is replaced with a prompt to create an account.

## Social share row

The "Share On" row in the same Share panel links out to six destinations:

- LinkedIn
- WhatsApp
- Telegram
- Facebook
- Email (a plain mailto: link)

Each opens that platform's own share composer in a new tab with your share link filled in; X, WhatsApp, Telegram and the mailto: link also carry the document's filename as the text or subject. These are plain intent links — nothing is posted on your behalf, and no third-party script is loaded. Available on all plans, and on unclaimed anonymous uploads.

## When to use each option

Share by email sends the message from EveryPage, addressed to one recipient, and marks the resulting visits as email. Social sharing hands the link to another application to distribute and adds no attribution.

Neither option tells you who opened the document. To attribute a view to a named recipient, use email invites, which send a per-recipient tracked link. To give one recipient a link you can revoke or restrict — different download or page-range rules on the same document — use link variants.

## How links work

Both routes send your document's standard share URL, built in the order vanity slug → short ID → UUID. The slug form is only used when a custom domain is serving your links, since slugs do not resolve on everypage.co; otherwise recipients get the short-ID link.

The email share appends ?via=email to that link, so opens from it are attributed to the email source in your audience breakdowns. The social destinations carry the bare link with no attribution parameter, so those opens are recorded as ordinary link visits and cannot be distinguished from someone pasting the URL directly.

---
URL: https://everypage.co/docs/viewer/viewer-modes
Title: Viewer modes | EveryPage Docs
Description: Choose how your document is presented to readers, from a plain paged view to page-turn animations to story-style swiping.

# Viewer modes

Choose how your document is presented to readers, from a plain paged view to page-turn animations to story-style swiping.

Your document can be presented to readers in one of four modes: standard, flipbook, magazine, and swipe. All four are available on every plan, including free — the mode is stored on the document itself and is not a plan feature.

## Standard mode

Standard mode is a plain paged document view: one page at a time, rendered on a canvas below a toolbar. Readers navigate with previous and next buttons or by dragging the page scrubber slider, which previews pages as it moves and commits the jump on release. The toolbar also shows the current page and the total page count.

Best for: Reports, proposals, instructions, contracts, any document readers prefer to navigate at their own pace.

Devices: Works on all screen sizes; desktop and mobile render the same interface.

## Flipbook mode

Flipbook mode uses a page-turn animation that mimics flipping through a bound document. It renders either a single page (1-up) or a two-page spread (2-up); the default layout you choose can be adaptive, and readers can pin 1-up or 2-up for their session using the toolbar toggle on wider screens. The toolbar also has a thumbnail rail, zoom buttons, and fullscreen; on touch screens, pinch-to-zoom works in place of the zoom buttons. Page-turn speed, sound, and reading direction are configurable. You can try a flipbook without an account by dropping a document onto the PDF flipbook maker.

Best for: Magazines, brochures, catalogs, printed materials, any document that benefits from a magazine-like reading experience.

Devices: Best on larger screens where two-page spreads render comfortably; the 1-up layout adapts to phones.

## Magazine mode

Magazine mode presents the document as a flat-lay two-page spread around a centre spine, for content laid out as spreads rather than as individual pages. The scrubber moves a spread at a time, and the toolbar carries thumbnails, zoom, and fullscreen. Page-turn speed, sound, and reading direction apply here as they do in flipbook; the 1-up/2-up layout preference and the page cosmetics do not — spreads are the mode's identity.

Best for: Printed magazines, annual reports, layout-heavy content, books and documents designed for a spread-based reading experience.

Devices: Suited to medium-to-large screens; on a narrow stage the spread collapses to a single page automatically.

## Swipe mode

Swipe mode presents the document as a story—one page at a time, with a segmented progress bar instead of a toolbar. Readers advance by swiping or flicking left and right, or by tapping the left and right edges of the page. The stage is full-bleed on touch and narrow screens and a bordered portrait card on desktop. Auto-advance can be enabled so pages turn automatically at a set interval.

Best for: Decks, presentations, event schedules, slide shows, any document meant to be viewed one page at a time in sequence.

Devices: Designed for mobile and tablets; on desktop it renders as a centered card.

## Readership tracking

Each view session records the mode it was read in, and the viewer-mode breakdown appears in your readership analytics on Basic and above.

## Choosing a mode

Set the viewer mode under Behavior in the Configure & Share step. The mode itself is never locked — the panel around it gates the flip and swipe behaviour settings, not the choice of mode.

If you are uploading anonymously (without an account), the viewer mode is the one setting you can persist before claiming the document; unclaimed documents are treated as free tier, so they render in your chosen mode with stock styling. Claimed documents can have their mode changed at any time from the file's settings.

Readers see the mode you set and cannot switch to another one — the viewer loads the document's stored mode and renders only that.

## Related

- Page style and behaviour — Page-turn speed, sound, auto-advance, and page appearance
- Branding and logo — Customize background colors and add logos
- Readership analytics — See which modes your readers actually use
- Sharing without an account — Set viewer mode on an unclaimed upload

---
URL: https://everypage.co/docs/viewer/page-style-and-behaviour
Title: Page style and behaviour | EveryPage Docs
Description: Control how pages appear and advance in your viewer, from page turn speed to corner rounding.

# Page style and behaviour

Control how pages appear and advance in your viewer, from page turn speed to corner rounding.

You can fine-tune the appearance and motion of pages in your document viewer. Each setting takes effect only in the viewer modes that use it; the last section of this article lists which. The page cosmetics live under Style in the Configure & Share editor and the motion settings under Behavior; both require Basic or above.

## Page appearance

The page cosmetics below adjust how individual pages render visually. Page shadow and rounded corners apply in every viewer mode; stacked edges are flipbook-only; cover page alone applies in flipbook and magazine.

| Setting | Range | Default | Effect |
|---|---|---|---|
| Page Shadow | 0–3 | 0 (Default) | Depth of the shadow cast under the page or book. Steps: Default, Soft, Medium, Deep. Default keeps each viewer mode's own stock shadow rather than removing it. |
| Rounded Corners | 0–3 | 0 (Square) | Corner radius of the outer page corners. Steps: Square, Subtle, Medium, Round. In flipbook and magazine only the outer corners round, so the centre spine stays a straight join. |
| Stacked Page Edges | On/Off | Off | Layered paper-edge effect on the outer sides of the book, simulating a stack of sheets. |
| Cover Page Alone | On/Off | On | Whether the cover displays solo (On) or pairs with page 2 like a calendar spread (Off). |

## Page-turn behavior

The following settings control how pages transition and sound. Page turn speed, sound, and right-to-left reading apply in flipbook and magazine; the default layout applies in flipbook only.

| Setting | Range | Default | Effect |
|---|---|---|---|
| Page Turn Speed | 200–1200 ms | 450 ms | Duration of the page-flip animation. Lower values feel snappier; higher values feel more deliberate. |
| Page Turn Sound | On/Off | Off | Play an audible page-turn sound when readers flip. Turning it on adds a mute button to the reader's toolbar; their choice is remembered in their browser and applies to every EveryPage document they open. |
| Right-to-Left Reading | On/Off | Off | Open the document from the other side and advance backwards, for Arabic, Hebrew, and Japanese documents. |
| Default Layout | Auto / 1-up / 2-up | Auto | Auto shows one page on narrow screens and a two-page spread on larger ones. 1-up always shows one page; 2-up always shows a spread. Readers can override it for their session with the flipbook toolbar toggle. |

## Auto-advance in swipe mode

The auto-advance controls only appear while the document's viewer mode is set to swipe, and only swipe mode acts on them:

| Setting | Range | Default | Effect |
|---|---|---|---|
| Auto-Advance Pages | On/Off | Off | Enable automatic page progression. When On, pages turn at the interval below. Readers pause it by pressing and holding anywhere; it also pauses while the browser tab is hidden, while a hotspot or call-to-action sheet is open, and it stops on the last page rather than looping. |
| Seconds Per Page | 3–30 seconds | 6 seconds | Time each page displays before advancing. Stored only while auto-advance is On. |

## Tier eligibility

The free tier is not "settings ignored" — it is "defaults only". EveryPage stores an appearance blob per document, and a free account may only store one that is entirely default.

- Free: A save is accepted only if every appearance setting is left at its default. Any non-default value is rejected with a 403 and an upgrade prompt, so the stored appearance stays empty and readers always get the stock viewer.
- Basic and above: All the page style and behaviour settings on this page are saved and applied when readers open the document.
- Pro: Adds the accent colour, toolbar theme, badge position, and call-to-action button on top.

The tier is re-checked when a reader opens the document, not just when you save. If your plan changes, the viewer immediately falls back to what your current plan allows: a Basic document keeps its background, logo, page styling, and auto-advance but drops the Pro-only settings, and a free document renders stock.

## Viewer-mode specificity

Each setting is read only by the modes that use it:

Page shadow and rounded corners are read by all four modes. The rest are mode-specific:

- Flipbook: stacked edges, cover page alone, page turn speed, sound, right-to-left, and default layout.
- Magazine: page turn speed, sound, right-to-left, and cover page alone. Stacked edges and the default layout are ignored.
- Swipe: auto-advance and its interval. No flip settings apply.
- Standard: no flip or auto-advance settings. Background, logo, and badge still apply — see branding and logo.

Embedded viewers are not a separate mode: an /embed/ link renders the document's own viewer mode and follows the same table.

## Related

- Viewer modes — Flipbook, magazine, swipe, and standard
- Branding and logo — Custom backgrounds, logos, and accent colors
- Plans and limits — Feature availability by tier

---
URL: https://everypage.co/docs/viewer/branding-and-logo
Title: Branding and logo | EveryPage Docs
Description: Customize your viewer's appearance with branded backgrounds and logos, and control the EveryPage badge.

# Branding and logo

Customize your viewer's appearance with branded backgrounds and logos, and control the EveryPage badge.

Background, logo, and badge settings apply in all four viewer modes: they are painted in a frame around whichever viewer the document uses. The background lives under Style in the Configure & Share editor; the logo and badge live under Branding. All of it requires Basic or above — on the free tier the settings cannot be saved and the viewer is served stock.

## Background

Your viewer's background is one of three types: a solid colour, a named gradient preset, or an uploaded image. Only the payload for the selected type is stored, so switching type discards the settings of the one you left.

Solid colour: Pick any hex colour (#RRGGBB format) and the viewer fills its background uniformly.

Gradient presets: Choose from six gradients named dusk, sand, slate, forest, blush, and mono.

Image background: Upload a PNG, JPEG, or WebP file (up to 5 MB). The file type is determined by inspecting the file's contents, not its name or declared type. Once uploaded, you control three properties:

- Fit: Cover (crops to fill the viewer, the default) or Contain (letterboxes to fit within it)
- Blur: Soften the image with 0–20 pixels of blur (default 0)
- Darken: Darken the image with a 0–80% overlay, keeping pages readable (default 0)

Each document stores only one background image: uploading a new one replaces the previous asset and deletes it.

## Logo

Upload your logo as a PNG, JPEG, or WebP image (up to 5 MB). Once uploaded, three settings control its appearance:

Position: Anchor the logo to a corner — top-left, top-right, bottom-left, or bottom-right. The default is bottom-right. Top corners sit below the viewer toolbar in the modes that have one, and at the top edge in swipe mode, which has none.

Size: S, M (default), L, or XL.

Logo link: Optionally add a click-through URL. Readers who click your logo open the link in a new tab. The URL must begin with http:// or https://.

Position, size, and link are only stored while a logo image is set; removing the image clears them.

Like your background, each document stores only one logo. Uploading a new one replaces and deletes the previous asset.

## Hiding the badge

By default, viewers display a "Made with EveryPage" badge in the bottom-left corner. Basic and Pro accounts can hide it with the Hide EveryPage Badge toggle under Branding. Free-tier documents always show the badge, and so do unclaimed anonymous uploads, which are treated as free tier.

## Advanced branding (Pro)

Pro accounts can additionally customize the viewer's accent colour, toolbar theme, and badge position.

- Accent colour: A custom hex colour for the viewer's accented controls — the scrubber thumb, focus rings, the swipe progress bar, and the call-to-action button when no separate button colour is set.
- Toolbar theme: Set the viewer's toolbar strip to auto (the default, following light/dark), light, or dark.
- Badge position: Move the badge to any of the four corners instead of the default bottom-left.

You can also add a call-to-action button to your viewer — see accent, toolbar, and call-to-action button for details.

## Limits and storage

Each document can store up to 10 auxiliary assets — logos, backgrounds, and hotspot media combined. Logos and backgrounds are exempt from the cap because they replace in place: a document already holding 10 assets can still swap its logo or background.

Every asset is encrypted at rest under its own key, so the viewer can display it without the owner's encryption key. Asset requests pass the same gates as the document itself: a password-protected or email-gated document does not leak its logo or background to someone who has not passed the gate.

## Related

- Accent, toolbar, and call-to-action button — Pro customization for the viewer's controls and conversion elements
- Viewer modes — Flipbook, magazine, swipe, and standard presentations
- Custom domains — Serve your viewer from your own domain

---
URL: https://everypage.co/docs/viewer/accent-toolbar-and-cta
Title: Accent colour, toolbar and call to action | EveryPage Docs
Description: Customize your viewer's appearance with a branded accent colour, toolbar theme, and a call-to-action button for Pro accounts.

# Accent colour, toolbar and call to action

Customize your viewer's appearance with a branded accent colour, toolbar theme, and a call-to-action button for Pro accounts.

The Pro plan adds extended viewer branding controls beyond the Basic logo and background customization. You can set an accent colour for the viewer's controls, choose a toolbar theme, move the EveryPage badge, and add a call-to-action button that points viewers at a specific URL. All four live in the Branding panel of Configure & Share.

Every field described here is Pro-gated and enforced server-side; saving any of them from a Free or Basic account is rejected with 403 Forbidden.

## Accent colour

The accent colour recolours the viewer's own controls: the page scrubber thumb and its focus outline, and the progress bar in swipe mode. It does not restyle toolbar buttons, document text, or links inside your PDF. You provide the value as a hexadecimal colour code in the form #RRGGBB, where each pair of characters represents the red, green, and blue channels in hexadecimal (0–F). For example, #FF6B35 is a vibrant orange, and #1E3A8A is a dark blue.

The colour must be exactly six hexadecimal digits following the hash, in either case. No shorthand (like #F63), RGB notation, or named colours are accepted.

If you set no accent colour, the controls use the stock EveryPage accent.

## Toolbar theme

The toolbar—the strip above the page carrying the page controls, and in flipbook and magazine modes the zoom and fullscreen buttons—respects your choice of light or dark appearance, or keeps the stock theme.

| Value | Behavior |
|---|---|
| light | White toolbar and buttons |
| dark | Dark toolbar with light text |
| auto | The stock toolbar (default) |

If you do not set a toolbar theme, it defaults to auto, which is stored as an empty value—the stored setting only records an explicit light or dark. EveryPage does not follow the reader's system light/dark preference; auto means the stock appearance, not an automatic switch.

Swipe mode renders no toolbar, so the theme has no visible effect there.

## Badge position

The EveryPage badge—a small "Made with EveryPage" mark linking back to EveryPage—sits in a corner of the viewer. Repositioning it is Pro; hiding it entirely is a Basic feature described in branding and logo. Free-tier documents always show it.

The badge position takes one of four values: tl (top left), tr (top right), bl (bottom left), or br (bottom right). If you do not set a position, it sits in the bottom-left corner.

## Call-to-action button

A call-to-action button is a clickable element overlaid on your document that directs viewers toward a specific URL—typically a sign-up form, a product page, or a contact link. This is a Pro feature and is rendered only for viewers of Pro-owned files. It opens in a new tab.

In swipe mode the button is replaced by a persistent swipe-up affordance at the bottom of the screen that opens the same call to action in a story-style sheet; the position setting below does not apply there.

### Required fields

The CTA requires two fields, and the button is withheld from the viewer until both are valid:

- Label: The button text (1–40 characters, counted in characters rather than bytes). This is what viewers see and click.
- URL: The destination link. It must be an https:// URL with a host— http:// and every other scheme are rejected. This is stricter than the logo link, which also accepts http://, because the CTA is the one control the viewer is actively pushed to click.

### Style

The button style determines its visual presentation:

| Value | Appearance |
|---|---|
| solid | Filled button (default) |
| outline | Light fill, with the colour on the border and label |

If you do not set a style, it defaults to solid.

### Colour

The button colour is set as a hexadecimal code in the form #RRGGBB, using the same format as the accent colour. This colour is applied to the button fill (for solid style) or to the border and text (for outline style). If you do not set a colour, the button uses your accent colour; with neither set, it falls back to the stock EveryPage accent.

### Position

The button position determines where it appears on the viewer:

| Value | Position |
|---|---|
| tl | Top left corner |
| tr | Top right corner |
| bl | Bottom left corner |
| br | Bottom right corner (default) |
| bar | Full-width bar at the bottom of the viewer |

If you do not set a position, the button sits in the bottom-right corner. The bar option spans the full width along the bottom edge of the viewer.

## Plan tier enforcement

The server validates your plan at save time and rejects the whole settings save if your account is on Free or Basic. The plan is checked again when the viewer page loads, so a downgrade takes effect immediately rather than at your next save:

- Pro → Basic: the accent colour, toolbar theme, badge position, and CTA stop being served; the Basic appearance settings (background, logo, page styling, swipe behaviour) keep rendering.
- Pro → Free: no viewer customization is served at all, and readers see the stock viewer.

Nothing is deleted in either case. Your stored settings survive the downgrade and render again as soon as you return to Pro.

## Related guides

- Branding and logo — customize your background and logo, and hide the EveryPage badge
- Viewer modes — choose how your document is displayed
- Plans and limits — reference for Pro features and restrictions

---
URL: https://everypage.co/docs/viewer/interactive-hotspots
Title: Interactive hotspots | EveryPage Docs
Description: Draw clickable regions on document pages that link out, jump between pages, or play embedded media.

# Interactive hotspots

Draw clickable regions on document pages that link out, jump between pages, or play embedded media.

Interactive hotspots turn static pages into interactive experiences. You draw rectangular regions on your document and configure what each region does when clicked—open a link, jump to another page, or play embedded video, audio, or image content. Taps on each region are recorded and reported per hotspot.

## Drawing and editing hotspots

When you enable hotspot editing, you work on a flat-page view of your document. Drag to draw rectangular regions, then select each region to configure its action. The editor displays existing hotspots and lets you move and resize them by dragging. Coordinates are stored as normalized 0–1 values, so hotspots scale automatically across different viewer modes and zoom levels.

Each page supports up to 30 hotspots, and your entire document can contain up to 300 hotspots total. Half-configured hotspots—for example, a link without a URL—do not save; the editor prunes them when you finish editing.

## Hotspot kinds

Each hotspot performs one of five actions when clicked:

Open a link — visitors follow an HTTP or HTTPS URL, in a new tab (the default) or the current tab, as you specify.

Go to a page — visitors jump to another page in your document.

Play a video — you paste a YouTube or Vimeo link, and EveryPage stores the provider and video ID from it. Those two are the only providers accepted. Playback uses the providers' privacy-friendly embed hosts (youtube-nocookie.com and player.vimeo.com).

Show an image — displays an image you upload. Captions are optional and are truncated at 200 characters.

Play audio — plays an MP3 file you upload. In standard, flipbook, and magazine modes, audio plays in a small floating card at the bottom right of the viewer.

Video and image hotspots open in a centred modal in standard, flipbook, and magazine modes. In swipe mode every media kind—including audio—opens in the story-style bottom sheet instead.

## Media assets

Image and audio hotspots rely on the per-document asset system. You can upload and store up to 10 assets per document, shared across logos, background images, and hotspot media. A document has at most one logo and one background, and re-uploading either replaces the previous file, so swapping them never consumes an extra slot.

Image files accept PNG, JPEG, and WebP formats, with a maximum size of 5 MB. Audio files must be MP3 format, with a maximum size of 10 MB.

For details on asset management and other asset types (logos and backgrounds), see Branding and logo.

## Recording hotspot taps

When a viewer clicks a hotspot, EveryPage records the tap. The activation is attributed to the hotspot, the page, and the viewer's session, and a tap referencing a hotspot that does not belong to the document is rejected. Recording is never plan-gated—taps are banked on every tier, so an upgrade reveals the history—but the report itself is Pro: per-hotspot activation counts appear in the document's readership page alongside reader sessions.

## Content replacement and hotspots

When you replace a document's content with a new PDF, hotspots are cleared by default—new pages may not align with the old ones, and page-anchored regions become meaningless. Page-anchored reader notes are cleared in the same pass. You can opt to keep both by passing ?clearAnchors=false (or ?clearAnchors=0) on the content-replace request, accepting any mismatch. Notes that are not anchored to a page always survive a content replacement.

For details on dynamic links and content replacement, see Dynamic links.

## Plan requirements

Interactive hotspots are a Pro feature, enforced on both sides:

- Writing: saving a hotspot set from a non-Pro account is rejected with 403 Forbidden.
- Reading: when the document's owner is not Pro, the viewer receives an empty hotspot set, so nothing renders.

The read-side check runs on every visit, so hotspots stop rendering as soon as you downgrade. Your stored hotspots are not deleted, and they render again—with their tap counts intact—as soon as you return to Pro.

For plan details and feature comparison, see Plans and limits.

---
URL: https://everypage.co/docs/viewer/pdf-links-and-navigation
Title: Links and navigation | EveryPage Docs
Description: How readers navigate your document using PDF links, page thumbnails, and viewer controls.

# Links and navigation

How readers navigate your document using PDF links, page thumbnails, and viewer controls.

PDF hyperlinks embedded in your source document are interactive in the viewer. Readers can click links to visit external websites, send emails, or jump to another page within your document. Beyond these embedded links, the viewer provides navigation tools—thumbnails, page controls, fullscreen, and zoom—whose availability depends on the viewer mode.

## PDF embedded links

Your PDF's own hyperlinks—created in your PDF authoring software—are preserved and clickable in the viewer. All four viewer modes support them without additional configuration. Link areas large enough to cover most of a page are ignored: a page-sized link box would swallow every page-turn gesture on that page.

External links — links to websites or email addresses open in the expected way. Only http:, https:, and mailto: links become clickable; every other scheme in the PDF is ignored. HTTP and HTTPS links open in a new browser tab with rel="noopener noreferrer", so the opened page has no handle on the viewer window. Mailto links hand off to the reader's mail client without opening a tab, avoiding a blank browser tab left behind after the handoff.

External links work even when your document is embedded in another site's iframe, such as a WordPress page or Notion database. Other JavaScript-based link techniques fail silently inside sandboxed iframes; EveryPage's real anchor elements survive those restrictions.

Internal links — links that point to another page in the same document become page jumps. Clicking an internal link navigates the reader to the target page in your current viewer mode without any mode change. Internal links work across all four viewer modes consistently.

## Navigation controls

The viewer provides several ways to move through your document.

Thumbnail rail — Available in flipbook and magazine modes, a toggleable side panel displays page thumbnails at a glance. Tapping a thumbnail jumps to that page. If your PDF includes a table of contents (bookmarks), the rail also shows a Contents tab listing those entries, allowing readers to navigate directly by section.

Page scrubber — Standard, flipbook, and magazine modes place a slider in the toolbar, next to a page counter; it appears only when there is more than one page (or, in magazine mode, more than one spread) to move between. In standard mode, dragging the slider previews pages live and commits the jump on release; in flipbook and magazine modes the jump happens when you release. Swipe mode has no scrubber—it shows a story-style segmented progress bar across the top instead.

Next and previous buttons — Standard mode's arrows step one page. Flipbook and magazine arrows move a whole spread, which is one or two pages depending on the layout: flipbook offers an explicit 1-up/2-up toggle on wider screens, and magazine uses spreads except on narrow screens, where it falls back to single pages. Swipe mode has its own previous/next affordances at the edges of the card.

Deep links to a page — You can open a document at a specific page by appending #page/N to its URL. Opening /embed/abc123#page/5 takes the reader directly to page 5 when the document loads, and the hash updates as the reader moves through the document, so copying the address bar always shares the page on screen.

## Zoom

Flipbook and magazine modes offer zoom controls in the toolbar: +/− buttons that step by 0.5×, hidden on narrow screens. Pinch-to-zoom (and ctrl/cmd-scroll) works in flipbook, magazine, and swipe modes; while zoomed in, dragging pans the page. Zoom ranges from 1× (fit-to-page) to a maximum of 3× in every mode that supports it. Zooming scales the page overlays with the page—hotspots and PDF link boxes stay glued to the content they sit on. The watermark overlay is painted over the whole viewer rather than the page, so it does not scale with zoom.

Standard mode has no zoom control of any kind. It fits each page to the width of the viewer and re-renders when the container resizes.

## Fullscreen

Flipbook and magazine modes put a fullscreen button in the toolbar; swipe mode has a floating one in the top-right corner, since it renders no toolbar. Standard mode has no fullscreen control. Fullscreen is particularly useful on phones and tablets for a more immersive reading experience.

In native fullscreen the browser paints only the element that went fullscreen, so anything outside it disappears. EveryPage therefore fullscreens the whole viewer wrapper rather than the page canvas: the page content, watermark, reader annotations, call-to-action button, logo, and EveryPage badge all live inside that wrapper and stay visible and correctly positioned. Media hotspot players (video, image, audio) and the swipe-mode call-to-action sheet mount inside it too, so they are not clipped or hidden. The reader-action rail—the reader-feedback and read-receipt buttons—sits outside that wrapper and is not shown while fullscreen is active.

## Distinguishing PDF links from hotspots

PDF embedded hyperlinks are different from interactive hotspots, which are rectangular regions you draw yourself in EveryPage. Both are clickable, but they serve different purposes:

- PDF links come from your source document and are fixed to the content. Readers can click them without any special setup. Taps on them are recorded, but there is no report for them yet—only hotspot and call-to-action taps are surfaced in readership today.
- Hotspots are defined by you in EveryPage after upload. You draw each region and configure its action (open a link, jump to a page, or play media). Hotspots are a Pro feature; PDF links are available to all plans.

## Related

- Viewer modes — Choose how your document is presented (standard, flipbook, magazine, or swipe)
- Interactive hotspots — Draw custom clickable regions for links, page jumps, and media
- Watermarking — Add a watermark overlay to your document
- Embedding — Embed your document on another website

---
URL: https://everypage.co/docs/viewer/google-analytics
Title: Google Analytics on share links | EveryPage Docs
Description: Load your GA4 property on a document's viewer page to measure its traffic alongside your website analytics.

# Google Analytics on share links

Load your GA4 property on a document's viewer page to measure its traffic alongside your website analytics.

You can attach your Google Analytics 4 measurement ID to a document so its viewer page loads the Google tag and reports visits to your GA4 property, alongside your other site data. GA4 and EveryPage's built-in readership measurement see different facets of the same audience.

## Add your GA4 measurement ID

Open a document's sharing settings and enter your GA4 measurement ID under Google Analytics. The ID must match G- followed by 4 to 14 uppercase letters or digits—for example G-AB12CD34EF. Lowercase letters and other prefixes are rejected. You can find your measurement ID in Google Analytics under Admin, in the details of the web data stream for your property.

Once applied, the viewer page for that document loads Google's gtag.js and sends a page view. The measurement ID is set per document, not per account, so each document you want measured needs its own entry. It applies to embedded viewers as well as the standalone share link, and because the viewer carries no owner signal, your own visits to your share link register in GA4 too.

## How GA4 and EveryPage readership differ

Adding GA4 is a supplement to EveryPage's built-in readership reporting, not a replacement. They complement each other:

- Google Analytics sees page views: when someone loads or reloads the viewer, GA4 records an event.
- EveryPage readership sees per-reader activity: how long they spent on each page, which pages they viewed, whether they reached the end, and (on Pro) their email or identity.

GA4 does not measure read depth, dwell time per page, or the read-through funnel—those insights live only in EveryPage. Both systems count the same visitor, but they answer different questions. Use GA4 to understand traffic volume and source (via acquisition reports) and EveryPage to understand how deeply readers engage with the document itself.

## Ad blockers and tracking

Readers who have ad blockers or tracking-prevention tools enabled typically do not send data to Google Analytics: gtag.js is fetched from googletagmanager.com, a third-party host that blocklists cover by default. Those same readers usually still register in EveryPage's own readership, which is captured by first-party requests to the document's own origin rather than a third-party script. If you see a gap between your GA4 page views and EveryPage view sessions, ad blocker adoption in your audience is a likely reason.

## Privacy and third-party data

Adding a GA4 property to your share links changes the privacy posture of those links. EveryPage's own readership reporting never stores visitor IP addresses—each address is mapped to a pseudonymous, salted identifier and then discarded—and EveryPage loads no third-party tracker into the viewer on its own.

Connecting GA4 adds one. The reader's browser fetches Google's script and sends the visit to Google, which processes that data as a third party under its own data practices and privacy policies —separate from, and not covered by, EveryPage's. If your documents reach people in jurisdictions with strict data protection laws (such as the EU), the consent and disclosure obligations for that processing are yours, not EveryPage's; EveryPage shows readers no consent banner for it. For details on EveryPage's own privacy model and what data it collects, see Encryption and Privacy.

## Requirements

Google Analytics integration is available on Pro plans and requires an active GA4 property. Saving a measurement ID on a Free or Basic account is rejected, and the plan is re-checked when a viewer loads the document—so if you downgrade from Pro, the tag stops loading immediately. The stored ID is kept and starts working again if you return to Pro. Free and Basic owners still get EveryPage's own readership reporting.

---
URL: https://everypage.co/docs/security/password-protection
Title: Password protection | EveryPage Docs
Description: Require viewers to enter a password before accessing your document.

# Password protection

Require viewers to enter a password before accessing your document.

Password protection requires viewers to enter a password before accessing your document. This gate runs before bytes are served—an unverified reader receives no document content, regardless of which link form they use.

## How password protection works

When you set a password, it is stored using bcrypt hashing and never stored in plain text. Viewers who enter the correct password receive an unguessable verification token, which is held in their session and keyed to your document's canonical UUID. This means a reader who unlocks the document through one link identifier (short ID, custom slug, or full UUID) automatically remains unlocked when accessing it through any other identifier.

Signed-in owners bypass the prompt on their own documents. That bypass requires a real owner account, so an anonymous (unclaimed) document never treats an anonymous visitor as its owner.

Password protection is a Basic+ feature. Setting a password on a free-tier account is refused server-side with HTTP 403; the control is visible but disabled in the UI.

## Passwords are per-document, not per-variant

Passwords apply to the entire document, not to individual link variants. If you share the same document through multiple variant links with different recipients, each recipient who unlocks the document gains access to it through all of its link forms. Link variants can override other settings like download permission or page ranges, but the password gate applies uniformly.

## Verification flow

When a reader attempts to view a password-protected document:

1. They receive a password prompt and enter the password
2. The backend verifies the password against the stored hash
3. If correct, the response carries a verification token, and a copy is stored in the reader's session under the document's canonical UUID
4. On every subsequent request that serves file-derived bytes, the reader presents that token — as an X-Verification-Token header, or as a token query parameter where a header cannot be set — and it must match the session copy
5. Without a matching token, the viewer receives HTTP 401 and no document content

Expired and burned links are checked before the password, so a dead link reads as dead rather than as password-protected.

## What is readable before the password

The password gate withholds document content, not the document's existence. The public metadata endpoint deliberately stays open for a live protected document — the viewer needs it to know that a prompt is required — so anyone holding the link can read the file name, size, page count, viewer mode, and which gates apply before entering the password. Treat the file name as public. Expired, burned, and unclaimed links return an error from that endpoint instead, so it confirms nothing about them.

## Embedding and password protection

The embed code is not offered for a password-protected document, and the embedded viewer refuses to render one: it shows a short message with a link to open the document directly instead. An embed is a cross-site iframe, so the session cookie that holds the verification token does not ride its requests, and the gate can never be satisfied inside the frame. The embedded viewer refuses documents with an email gate, a lead-capture form, or a view limit for the same reason.

## Expiry and burnout interaction

Password settings cannot be modified after a document has expired or been burned (reached its view limit). Attempts to change settings on an already-dead link return HTTP 410 Gone.

## How this differs from email capture

A password proves that a viewer knows a shared secret. An email gate does not prove identity: it collects a self-asserted address, checks it is plausibly formatted (and optionally on an allowed domain), and lets the viewer through — nothing is sent to that address to confirm it. Email capture is a Pro feature and gives you a list of the addresses readers typed; password protection is Basic+ and collects no address at all, though the visit is still recorded as a pseudonymous reader either way. You can combine both: require a password and an email, or neither.

See email gates and lead capture for more.

## Related topics

- Link variants — how per-recipient links work and what can be customized
- Embedding documents — when embedding is available and limitations
- Expiry and retention — setting link expiry and burn limits
- Plans and limits — what features are available on each tier

---
URL: https://everypage.co/docs/security/email-gates-and-lead-capture
Title: Email gates and lead capture | EveryPage Docs
Description: Require viewers to provide contact information before accessing your documents.

# Email gates and lead capture

Require viewers to provide contact information before accessing your documents.

An email gate blocks document access until a viewer provides their email address or answers a multi-field form. The gate lives on the Privacy & Access panel of a document's Configure & Share page and is toggled by the Require Email to View checkbox. That checkbox is the single "gate is active" switch: a document gates on email if, and only if, it is on.

## Two gate shapes

The gate takes one of two forms:

Plain email prompt. A single input asking only for an email address. When the viewer submits, their address is stored on the view session and watermarking can use it to mark every copy with the reader's identity (see reader identities).

Lead-capture form. A custom multi-field form that supersedes the plain prompt. You build it by checking the Custom Gate Form checkbox, which creates the fixed email field, then adding fields of type text, phone, or company. A form must contain exactly one email field; it is always moved to the front and forced required, and it cannot be renamed or removed. Fields you add are required too — the builder has no optional toggle. A form holds at most 5 fields including the email field. When a viewer submits, the captured data flows into your readership contacts and is accessible via your events feed (see events feed). The lead capture for PDFs overview shows what a gated document looks like from the viewer's side before you set one up.

Saving any lead-capture fields forces the gate on— Require Email to View is set server-side, so a form can never exist behind an inactive gate. Clearing the form, and turning the gate off, are deliberately un-gated: an account that has dropped below Pro can always switch the gate off even though it could not switch it on.

## Tier requirements

| Action | Tier |
|---|---|
| Turn on the email gate | Pro |
| Add or modify lead-capture form fields | Pro |
| Set a domain allowlist | Pro |
| Read lead captures via the readership page or API | Pro |
| Turn the gate off, clear the form, or clear the allowlist | All tiers |

Enabling a gate requires Pro; collecting through one that is already on does not. If your plan drops below Pro, a document whose gate is on keeps gating and keeps recording captures — what you lose is the ability to enable new gates and to read the captures. They persist and become readable again when you re-upgrade.

## Domain allowlist

You can restrict the gate to viewers with email addresses on specific domains. The Restrict Viewer Email Domains section appears once the gate is on; add bare hostnames like acme.com one at a time (up to 20 domains). Matching is domain-aware: alice@acme.com and bob@sub.acme.com both pass if you've allowed acme.com, but eve@evilacme.com does not.

Leave the list empty to accept any email address. See email domain allowlist for the matching rules and what the check does and does not prove.

## How data is stored

Plain-email captures (address only, no form) are stored on the view session record in your readership data but NOT in the events feed. If you later add a lead-capture form, existing plain-email captures remain queryable through the readership sessions interface, but they do not appear in the gate responses stream.

Lead-capture form submissions (one or more custom fields) are stored as contact records in the gate_responses stream. You can export them as CSV from the readership page or query them via /api/v1/gate-responses when you hold a Pro plan.

The validated email address from either gate shape is stored on the view session and can watermark the PDF.

## Invited recipients

A viewer arriving via an email invite link (the ?i= token) pre-satisfies the gate. The interactive gate is skipped entirely on the server: nothing the viewer submits is validated or captured, no gate response is recorded, and no gate.completed event fires — an invited open emits invite.viewed instead. The invitee's email from the invitation itself becomes the session identity for watermarking. The current viewer still renders the gate form to an invited recipient before opening the document; submitting it changes nothing. See email invites for details.

## Owner access

Signed in as the document owner, you bypass the gate and see the full document. The bypass requires a real owner account: an anonymous document (uploaded without logging in) has no owner, so an anonymous visitor is never matched against it as one.

## Field constraints

Label: 1–60 characters. Value (text, phone, company): up to 200 characters. Email value: 3–254 characters, and it must contain an @ with a dotted domain after it. This is a plausibility check, not RFC-complete validation, and not proof the mailbox exists.

Field keys are auto-derived from labels (lowercase, snake_case, 1–40 characters, starting with a letter) and must be unique within the form. The email field's key is email. A submission is accepted or rejected as a whole: any field error rejects the request with the per-field messages, no session row is written, and the gate stays shut. Values for keys the form does not define are discarded rather than stored.

## Webhooks

The gate.completed event fires when a viewer actively passes the gate and is not arriving from an invite. The event payload includes the source (link, qr, email, or embed) and the captured email and/or form fields.

Delivery requires a Pro plan at the moment the event fires: the check runs when deliveries are queued, so an event raised while your plan is below Pro is never queued and is not delivered later. Re-upgrading resumes future deliveries; it does not replay the ones that were skipped. The capture itself is unaffected — the lead is still recorded and becomes readable again through the readership page and the pull APIs. The event never fires for owner access, for invite-satisfied sessions, or for a document with no owner account.

See webhooks for integration setup.

## Disabling and clearing

Unchecking Require Email to View disables the gate immediately. Existing captures remain in your readership data. If you later re-enable the gate, the same form configuration (or plain email prompt) takes effect again.

Captured rows cannot be deleted individually. Gate responses are tied to the document: deleting the document deletes them with it, as does deleting your account. Export what you need first — the readership CSV export carries the captured contacts as a second section after the session rows.

---
URL: https://everypage.co/docs/security/email-domain-allowlist
Title: Email domain allowlist | EveryPage Docs
Description: Restrict document access to viewers with email addresses on specific approved domains.

# Email domain allowlist

Restrict document access to viewers with email addresses on specific approved domains.

When you enable an email gate on a document, you can restrict access to viewers whose email address belongs to specific domains. This is useful for organizations that want to limit sharing to company email addresses or a set of approved partner domains.

## How it works

The domain allowlist appears under Restrict Viewer Email Domains when you enable the email gate for a document. You enter bare hostnames like company.com or partner.org one at a time, pressing Enter after each; they appear as removable chips. An entry must be a plain hostname of at least two dot-separated labels — anything carrying an @, a scheme, a path, or a space is rejected on save rather than silently repaired, because a typo here locks out every viewer. When a viewer submits their email address, the domain of that address is checked against your list. The viewer passes if their domain exactly matches an allowed domain or is a subdomain of one.

For example, if you allow company.com:

- alice@company.com passes
- bob@dept.company.com passes (subdomain)
- eve@notcompany.com does not pass

The subdomain match is boundary-aware — a domain qualifies only if it equals an allowed entry or ends with a dot followed by it — so notcompany.com cannot pass as company.com on a plain suffix match.

Matching is case-insensitive: entries are lowercased when saved and the submitted address is lowercased when checked. If you leave the domain list empty, the email gate accepts any email address.

## Limits

You can specify up to 20 domains. Each domain name can be up to 253 characters (the DNS limit). Setting an allowlist requires Pro; clearing it does not, so an account that drops below Pro can always remove the restriction.

## Rejection messages

A rejected address gets an explicit error rather than a silent failure. When your list holds exactly one domain, that message names it (Please use your @company.com email address) — a deliberate trade for usability, and worth knowing if the domain itself is sensitive. With two or more domains the message is generic (Please use an approved email address), so repeated attempts do not enumerate the list.

## Threat model

The allowlist checks the domain of a self-asserted email address. Nothing is verified: no confirmation mail is sent, no link is clicked, and no check is made that the mailbox exists or that the viewer can receive mail there. Anyone holding the link who types any syntactically plausible address on an allowed domain passes the gate and reads the document. The address is then recorded as that reader's identity and can be stamped onto watermarked pages, so unverified input also flows into your readership data.

Treat this as a boundary that stops accidental and casual out-of-scope access, not as identity verification or access control. If a document must only reach specific named people, pair the gate with a password, send per-recipient email invites, or both.

## With password protection

If a document has both a password gate and a domain allowlist, both must pass, and in that order: the password is verified before a viewer can submit an address at all.

## Integration with lead-capture forms

If you use a lead-capture form instead of a plain email gate, the domain allowlist applies to the form's email field. The other fields are checked only for their length cap, never against the allowlist, and a domain rejection is returned as an error on the email field alongside any other field errors.

## With email invites

Viewers arriving via an email invite link pre-satisfy the email gate and so bypass the domain allowlist entirely — including invitees whose address is not on it. The invitee's email from the invitation becomes their session identity. Check the allowlist and your invite list agree if the restriction matters.

## Related

- Email gates and lead capture — the parent email gate feature
- Password protection — other ways to gate document access
- Email invites — sending documents to specific recipients
- Plans and limits — which features are included in each plan

---
URL: https://everypage.co/docs/security/download-control
Title: Download control | EveryPage Docs
Description: Control whether viewers can save a copy of your document.

# Download control

Control whether viewers can save a copy of your document.

Download control lets you toggle whether readers can save a copy of your document to their device. When downloads are disabled, readers see your document in the viewer but cannot export or save a local copy. This control is available on every plan, including free tier, and is treated as a safety feature rather than a tier-locked capability.

## How download control works

By default, documents allow downloads. When you disable downloads, readers who attempt to save the file receive an HTTP 403 error. The restriction applies only to explicit save requests (initiated by the ?dl=1 query parameter); the reader's browser must still receive the page content in order to display it in the viewer. Owners can always download their own documents, regardless of the setting.

Download control is a per-document binary toggle—it either allows downloads for all viewers or denies them for all viewers (except per-recipient overrides). Use the file settings to enable or disable downloads; changes take effect immediately for all active and future viewers.

## Link variants and per-recipient download control

If you use link variants to share with multiple recipients, you can override the parent document's download permission for each variant independently. One recipient can be allowed to download while another is prevented from doing so, even though both access the same document through different variant links.

When you create or update a variant, set allowDownload in the variant's settings overrides. The override works in both directions: false blocks downloads for that recipient alone, true allows them even when the parent document has downloads turned off. A variant with no allowDownload override inherits the parent document's setting. This per-recipient control is only available with link variants, which require a Pro plan.

Updating a variant replaces its whole overrides object rather than merging into it, so an update that omits allowDownload drops the override and returns that recipient to the parent document's setting.

## Understanding the threat model

Disabling downloads removes the download affordance—the UI control and the HTTP 403 response prevent casual saving. However, readers whose browsers have rendered the page have access to the unencrypted content in their browser memory. Download control is a user-experience deterrent, not digital-rights management. A determined user with browser developer tools could extract the content after viewing it.

The controls that pair with it work differently. Viewer protection adds further deterrents in the same category—friction for the uninvested reader, nothing more. Watermarking is the one that changes the outcome: it stamps each reader's identity and access timestamp onto the pages they view and download, so a copy that escapes can be traced back to the reader it came from.

## Expiry and burn interaction

Download settings cannot be modified after a document has expired, or after it has been burned (its view limit reached and its bytes destroyed). Attempts to change the download permission on an already-dead link return HTTP 410 Gone. The same 410 applies on the full settings endpoint and the viewer-mode endpoint.

Expired or burned documents also refuse download requests with HTTP 410, regardless of the download permission setting, because the link itself is no longer valid.

## Related topics

- Link variants — create separate tracked links with per-recipient setting overrides
- Watermarking — stamp each reader's identity and access time onto the pages they see
- Viewer protection — further deterrents against casual copying
- Page-range links — serve only a window of pages to viewers
- Expiry and retention — how long a link stays accessible
- Self-destructing links — cap how many times a link can be opened
- Plans and limits — what features are available on each tier

---
URL: https://everypage.co/docs/security/expiry-and-retention
Title: Expiry and retention | EveryPage Docs
Description: How long documents stay accessible, how anonymous uploads are retained, and how the cleanup sweep removes them.

# Expiry and retention

How long documents stay accessible, how anonymous uploads are retained, and how the cleanup sweep removes them.

A document with an expiry is removed from access and deleted the instant it passes. Expiry is a control you set from Share Settings on every plan, including Free: pick any window, or none at all. Only anonymous uploads carry a fixed lifetime.

## Setting document expiry

Every upload is created with a starting expiry, which you then change from Share Settings on the Configure & Share screen. A signed-in upload starts with no expiry at all, on every plan, so a document is never born with a shorter life than you would have chosen for it — set a window yourself if you want one. The starting values are:

| How the document was created | Starting expiry |
|---|---|
| Uploaded while signed in (any plan) | Never expires |
| Uploaded anonymously in the browser (no account) | 7 days |
| Published from Canva (unclaimed) | 365 days |

Change the expiry by picking a new window from the expiry selector and applying it; the new window is measured from the moment you apply it, not from upload. The selector offers 1 hour, 12 hours, 24 hours, 7 days, 30 days, 365 days and Never on every plan.

Once the expiry instant passes, the document is inaccessible immediately, even if the cleanup process has not yet run.

## What readers see

While the link is live, the viewer shows a running Expires in countdown beside the Download button, so a reader knows how long they have. It appears only on documents that expire, and you can switch it off per document with Show expiry to readers in Share Settings, directly under the expiry selector. With the countdown off, the public metadata no longer carries the expiry at all.

Once the link has lapsed, a reader who opens it sees a page naming the document and the date it expired, rather than a bare "not found". Where the expiry was one of the no-account defaults, the page also says so: anonymous uploads expire after 7 days, Canva documents published without an account after a year, in each case with a pointer to creating or connecting an account. An expiry you set yourself is stated as your choice, with no nudge. The same page appears for a document that reached its view limit, or that was deleted, with the wording adjusted; in those cases it gives the name and date only.

The name is withheld if the document was password-protected or behind an email gate when it went, so an old link to a gated document confirms nothing about what it was. Link previews in chat apps and social networks stay generic for any dead link, for the same reason.

The page is served for as long as the record of the deletion exists, which is indefinitely. On a custom domain a dead link answers a plain not-found instead.

## Expiry limits

Signed-in accounts have no expiry cap on any plan: schedule any window, or choose Never, which stores no expiry at all and exempts the document from the cleanup sweep.

The one cap is on anonymous documents edited through a manage token (the credential the API returns alongside an anonymous upload). Those writes are held to 7 days from now and cannot set never-expire; anything longer is rejected with HTTP 403. Claim the document into an account to lift the cap.

## Automatic cleanup

A background process runs every 60 seconds to remove expired documents from disk and the database. A document that has passed its expiry instant returns HTTP 410 (Gone) on any download request immediately—it does not wait for the next cleanup cycle. The public metadata endpoint answers the same 410 with a JSON body (reason, why, endedAt, and originalName unless the document was gated) before and after the sweep alike, which is what the viewer's expired page is built from; every other endpoint answers with plain text. Because the cleanup runs periodically, an expired document's database row can survive up to a minute, so every write lane refuses expired documents with 410 as well: the settings endpoint (on all of its authentication lanes), the download-permission toggle, the viewer-mode endpoint, and content replacement. Without those refusals, a write inside that window could push the expiry into the future and resurrect a link that had already answered 410 to its readers.

Extending the expiry of a document that has not yet lapsed is the supported flow and is not affected—the refusal applies only to documents that are already past their expiry instant.

## Anonymous uploads and expiry

Unclaimed anonymous documents (uploaded without an account or shared before signing up) are retained for 7 days. This window starts from the document's creation and allows shared links to remain live even after the uploading session ends. Documents published from Canva are the exception: they are retained for 365 days from publishing, and republishing a live design restarts that clock. Claiming an anonymous document by signing up or logging in makes it yours, and it takes on the signed-in default: the expiry is cleared and the document stops expiring. The one exception is an expiry the uploader chose explicitly through the manage token—that is kept, because the link may already have been shared on that promise. Either way the share link keeps working, and once claimed you change the expiry from Share Settings like any other document, including to never.

See Anonymous uploads and claiming for details on how claiming works.

## Expiry when restoring from trash

When you restore a document from trash, its expiry is handled like this:

Restored documents keep their stored expiry on every plan, never-expire included. If that expiry lapsed while the document sat in trash, it is cleared instead—the restored document never expires until you set a new expiry.

The lapsed-expiry re-basing matters because the cleanup sweep deliberately skips trashed documents, so a stored expiry can pass while a document is in the trash. Without the re-base, the restore would succeed and the next sweep would delete the document moments later, with the expired-document 410 on the settings endpoint blocking any rescue in between.

See Trash and recovery for more details on the restore process.

## Expiry vs. view limits

Expiry and view limits are separate controls:

- Expiry: Time-based. The document becomes inaccessible after a specific date and time, regardless of how many times it has been viewed.
- View limit: Count-based. The document becomes inaccessible after a set number of viewing sessions have been served, regardless of time.

Both can be combined on the same document. See Self-destructing links for details on view limits.

## Plans and limits

For an overview of your plan's capabilities, see Plans and limits.

---
URL: https://everypage.co/docs/security/self-destructing-links
Title: Self-destructing links | EveryPage Docs
Description: Set a view limit so a link stops working after it has been opened a set number of times.

# Self-destructing links

Set a view limit so a link stops working after it has been opened a set number of times.

A view limit caps how many times a document can be opened. Once the limit is reached the link stops working, and shortly afterwards the stored file is destroyed — after that nobody can open it, including you, even with the link in hand. If you are new to view budgets, start with the self-destructing links feature overview — the rest of this page covers exactly how views are counted and when destruction happens.

## Setting a view limit

View limits are available on the Basic plan and above; a Free account setting one is refused with HTTP 403. After you upload a file, open the link settings and set a View limit to the number of times the document can be opened. Setting the limit to 0 clears it and removes the restriction; a negative value is rejected with HTTP 400.

A view is consumed once per viewing session, and only at the point where the document's bytes are about to be served: after the password and email gates have passed, after the download-permission check has allowed the request, and after the stored file has opened and decrypted. A reader who abandons the password prompt or the email gate, or whose request fails for any other reason, does not spend a view. Once a session has consumed its view, that session can refetch the bytes freely, so page reloads and range requests within it cost nothing further. Your own views as the owner never count. If you set a limit of 3, three viewing sessions consume the document and the fourth is refused.

## What happens when the limit is reached

As soon as the last view is consumed, further viewers are refused with an HTTP 410 error — "This link has reached its view limit". Nothing has been deleted yet at this point.

Destruction happens shortly afterwards. A background sweep runs every 60 seconds and destroys the encrypted file on disk once the limit has been reached for at least 30 minutes. That grace window exists so readers who are mid-session when the limit is hit can finish reading. Only the encrypted bytes are removed; the document's database record, its settings, and its readership history are all left in place.

Once the sweep has destroyed the file, the 410 applies to everyone, including you as the document owner — you can no longer preview or download it. During the grace window before the sweep runs, the document is still readable by you as the owner, because owners never consume views and the bytes still exist.

This is by design: the view limit is a hard boundary, not a soft warning. If you need to review the document after sharing it, do so before you run out of views.

Destruction also flips every settings lane closed: once a document is burned, the settings endpoint, the download-permission toggle, and the viewer-mode endpoint all answer 410. Content replacement is the deliberate exception (see below).

## Readership data survives the burn

Even though the document bytes are gone, your readership data remains. The burn destroys only the encrypted file; the document's row and every record attached to it survive — view sessions, viewer countries, timestamps, per-page statistics, and any captured emails or lead-form responses. Preserving that evidence is the point: the feature exists so you can learn who opened a document, not so the record of it disappears with the file.

## Extending or removing the limit

You can change the view limit at any time while the document is still live. Increasing it allows more sessions; clearing it (setting it to 0) removes the restriction entirely, leaving the link live until its expiry. Consumed views are not reset by a settings change, so raising a limit of 3 to 5 grants two further sessions rather than five.

Once a document has burned, the settings endpoint refuses writes with 410, so the limit can no longer be changed there.

## The un-burn path: replacing content

If a document burns but you want the link to work again, replace the document's content. Uploading new content to an already-burned link brings it back to life: the burn state is cleared and the consumed-view counter is reset, while the URL, short ID, vanity slug, settings, and readership history all survive. The view limit itself is kept, so the new document is subject to the same cap from zero.

This is the only way to resurrect a burned link, and it is deliberate — content replacement refuses documents that have expired with 410, but accepts burned ones. Note that content replacement requires a Pro plan, so a Basic account can set a view limit but cannot un-burn the resulting link.

## Related features

- Expiry and retention — Set a time-based expiration instead of or in addition to a view limit
- Dynamic links — Replace document content and use content replacement to un-burn a link
- Webhooks — Receive a file.burned event, emitted by the sweep at the moment it destroys the file, not when the limit is reached
- Readership analytics — Understand what data survives after a document burns

---
URL: https://everypage.co/docs/security/page-range-links
Title: Page-range links | EveryPage Docs
Description: Restrict a shared link to show only a window of pages from your document.

# Page-range links

Restrict a shared link to show only a window of pages from your document.

A page-range link lets you share only a portion of your PDF. When you set a range, recipients receive exactly the pages you specify — no more, no less. The hidden pages never reach their browser: the trimming happens on EveryPage servers before any bytes are streamed, so this is a server-side restriction rather than a viewer-side one. The public viewer metadata still reports the document's total page count when it is known, so a recipient can tell that pages exist outside the window — they simply never receive them.

## Setting and clearing ranges

You control page ranges in the file settings. Narrow a link to specific pages by entering a start and end page number. The Pro plan allows you to set ranges; any plan can clear a range by leaving both fields empty or resetting them to 0.

Ranges can only be set on files up to 100 MB. A ranged serve rewrites the whole document through pdfcpu on every request, so the same size cap that applies to watermarked downloads applies here.

A page-range restriction stays in place even if your subscription downgrades. This prevents accidental disclosure: if you've already sent a link to pages 5–12, downgrading from Pro to free will not suddenly expose the full document to recipients who followed the earlier link. The restriction remains until you deliberately remove it.

Clearing a range is un-gated, so a downgraded account can always undo the restriction.

## How enforcement works

The PDF is physically trimmed using the pdfcpu library before any bytes leave the server. The serve handler decrypts the document to a temporary file, applies the page-range trim, streams only the trimmed result, and deletes the temporary files on return. This is the same pipeline that handles watermarking, with the trim step running first so watermarks appear only on the pages viewers see.

Enforcement fails closed: if the trim operation encounters an error — whether from a malformed range, a document structure the library cannot parse, or any other fault — the request fails with an error rather than falling back to serving the full document. A trim that resolves to zero pages is also treated as a failure, so a stale page count can never cause an empty file to be served in place of the window. A stored range pair the server cannot interpret triggers a 500 for non-owners instead of silently widening access.

Trimming uses pdfcpu's reduced-feature output: annotations, outlines and some complex page-tree entries are dropped from the served window. The pages a recipient reads are intended for viewing, not archival.

## Variant overrides

When you use link variants to send customized links to different recipients, you can set a different page range for each variant. The variant's range overrides the document-level setting, so one recipient might see pages 1–5 while another sees pages 10–15, both from the same file.

## What owners always see

File owners always receive the complete document when downloading their own file, regardless of any page-range setting. This ensures you can verify the full content you've shared and check that the range restriction is working as intended.

## Analytics and reporting

Telemetry reflects what recipients actually saw. A reader on a page-ranged link only ever sees the trimmed document, so their session never writes the document's stored page count — a five-page window must not overwrite the real total. Readership responses for a ranged file also carry the window size, so the read-through funnel is labelled against the pages you shared instead of implying that readers dropped off before pages they were never sent.

## When ranges fail

If a stored page range becomes invalid — for instance, if the range ceiling is lowered in a future version and your old range exceeds it — the document remains protected: non-owner requests return an error. The range pair remains visible in your file settings so you can review and correct it, and it is hidden from the public viewer metadata.

A file that carries a range but is larger than the 100 MB transform cap also refuses to serve to non-owners, for both inline viewing and download. The settings form will not create that state — it can only arise on a file whose range predates the cap, or one whose content was later replaced with a larger document. Clearing the range restores access to the full file.

---
URL: https://everypage.co/docs/security/watermarking
Title: Watermarking | EveryPage Docs
Description: Stamp each reader's identity and timestamp on the pages they view and download.

# Watermarking

Stamp each reader's identity and timestamp on the pages they view and download.

Watermarking adds a visible mark to every page a reader is served, displaying an identity for that reader and the UTC timestamp of access. It is a deterrent against redistribution: the mark travels on the copy, so a forwarded file carries it. It is not an access control and it records nothing — EveryPage does not store the text it stamped, so the mark is evidence on a recovered copy, not an audit log you can query.

Watermarking is a Pro feature. If the file owner's plan drops below Pro, the watermark stops being applied to new requests. For an introduction to per-viewer watermarks and when to reach for them, see the PDF watermarking feature page.

## How watermarking works

When watermarking is enabled on a file, every non-owner request is marked. For files up to the size cap below, the mark is stamped into the PDF itself server-side — for inline viewing in the browser and for explicit downloads alike, so the bytes that reach the reader already carry it. The owner never sees a watermark on their own views or downloads, regardless of the setting.

The watermark text follows a three-tier identity precedence:

1. Invited via email — If the viewer accessed the file through an email invite link, the watermark displays their invited email address.
2. Captured by a gate — If the viewer entered an email address to pass an email gate or lead-capture form, that captured address appears on the watermark.
3. Pseudonymous viewer key — If neither applies (anonymous viewing), the watermark shows Viewer a1b2c3: the first six characters of a random per-viewer key minted for that browser session. It is opaque, and it is not derived from the reader's IP address or any other identifier. It is stable only for as long as that browser session lasts — a reader who clears cookies, uses a private window, or opens the link on another device is marked as a different viewer.

Every watermark includes a UTC timestamp (2026-08-06 14:30 UTC).

## Checking how it looks

Because you are exempt, opening your own share link shows clean pages — that is working as designed, not a broken setting. To see the mark, use the live preview in Configure & Share: with the watermark on, it tiles a sample line over the preview at the opacity and density you have chosen, so you can check legibility against your own artwork before sharing the link.

## Downloaded files carry the watermark

Downloads are stamped into the PDF server-side using pdfcpu before the bytes leave EveryPage's servers, so the saved file on the viewer's computer carries the mark rather than relying on anything the browser draws.

The mark lives in the page content stream, so it survives forwarding, re-saving, and printing to PDF. It does not prevent copying, and it is not tamper-proof: anyone willing to edit the PDF or re-render its pages can remove or obscure it.

## Size limit for stamped output

Because server-side stamping requires decrypting and rewriting the entire PDF, large files incur a significant processing cost. Watermarking combined with download permission is refused for files larger than 100 MB. If you try to enable both watermark and download permission on a file over this threshold, the settings form rejects the change until one of the two is disabled; a file that somehow already carries that combination refuses the download instead of serving unstamped bytes.

Above the cap, inline viewing is still allowed but the mark is no longer stamped into the bytes — the viewer draws it over the pages in the browser instead. That overlay is cosmetic: a reader can remove it with browser developer tools, and it is absent from any copy of the file taken outside the viewer. Treat watermarking on files over 100 MB as a visual deterrent only.

## Appearance options

You control how prominent the watermark appears to viewers:

### Opacity

The opacity slider ranges from 0.05 to 0.5 (barely visible to moderately opaque). The default is 0.12, which is subtle enough not to obstruct reading but visible enough to serve as a deterrent.

Any value below 0.12 applies to the browser overlay only. Every stamped PDF — inline view or download — is floored back to 0.12 before stamping, because a setting that is legible as crisp CSS text can be invisible once rasterized on a small screen. The effective range for stamped output is therefore 0.12 to 0.5.

### Density

For stamped PDFs, density controls how many instances of the watermark are placed on each page:

- Sparse — One instance: a large diagonal across the center of the page
- Normal (default) — Three instances: the center diagonal, plus smaller marks near the top-left and bottom-right
- Dense — Five instances: the center diagonal plus all four corners

In the browser overlay (used above the size cap), the same setting changes how tightly the mark is tiled rather than how many fixed instances are drawn.

## Combining watermarking with page ranges

If a file has both a page-range limit and watermarking enabled, both transforms apply in a single server pass. The page range is trimmed first, then the watermark is stamped onto the trimmed pages. The two failure modes are deliberately different: a trim failure always fails the request, while a stamp failure on an inline view falls back to serving the already-trimmed file unstamped. Pages outside the range are never served either way.

On an explicit download, a stamp failure fails the request rather than handing over an unstamped copy.

## Related

- Email invites — Control access by email and set the invited address that appears on the watermark
- Email gates and lead capture — Require visitors to enter an email before viewing, which then appears on the watermark
- Download control — Prevent or allow viewers to download the file
- Page-range links — Limit viewer access to a subset of pages
- Plans and limits — Watermarking is a Pro feature

---
URL: https://everypage.co/docs/security/viewer-protection
Title: Viewer protection | EveryPage Docs
Description: Soft deterrents that make casual copying harder without claiming to prevent determined access.

# Viewer protection

Soft deterrents that make casual copying harder without claiming to prevent determined access.

The viewer-protection settings are deterrents against casual copying, not DRM. Your browser necessarily receives the page content in order to display it, so anyone determined to capture it can do so—with a screenshot, a phone camera, or a print-to-PDF tool. What these controls do is raise friction for the uninvested reader.

Every one of them runs in the reader's browser, inside the EveryPage viewer. None of them changes the bytes that are served, and none survives leaving the viewer: a reader who requests the document's URL directly gets the PDF in their browser's own PDF viewer, where right-click, selection, printing and screenshotting all work normally. Watermarking is the one setting in the same panel that changes the served document itself, and even it marks a copy rather than preventing one.

## How protection works

Protection lives in the editor's Protection panel, alongside the watermark setting. Three toggles cover viewer protection:

- Block Right-Click & Copying — one switch that sets both the context-menu and text-selection flags
- Block Printing
- Blur When Window Loses Focus

Each flag is stored on the server as part of the file's viewer settings and re-checked against the owner's plan when a viewer loads the document, so a downgrade takes effect for readers immediately.

### Block right-click and copying

One toggle, two stored flags. Right-clicking the document produces no menu, and the document area is rendered with user-select: none, so a reader cannot triple-click to select, drag to highlight, or Shift+click. They can still copy via keyboard shortcuts where the browser allows it, read the rendered text, screenshot it, use developer tools to inspect the underlying DOM, or open the PDF outside the viewer. This deters the path-of-least-resistance copier and stops no one motivated.

Tier: Basic and above.

### Block printing

When enabled, the viewer intercepts the print and save shortcuts (Ctrl+P / Cmd+P and Ctrl+S / Cmd+S) and suppresses the keyboard action, and a @media print rule hides the document from print output, so menu-driven printing and print-to-PDF produce a blank page rather than the document.

Both halves are viewer-side CSS and JavaScript. A reader who disables JavaScript or CSS, opens the PDF outside the viewer, or screenshots the pages and prints those is unaffected. Print blocking prevents the accidental "oops I printed it" moment, not the intentional one.

Tier: Basic and above.

### Blur when the window loses focus

When enabled, the pages blur (a 14px CSS blur) behind a dimmed veil whenever a reader switches to another tab, minimizes the window, or the window loses keyboard focus. It clears on return. This deters screen-sharing and over-the-shoulder exposure while a reader is away from the document, but it does not prevent capture. A reader can screenshot while the tab is active, use a screen recorder, or photograph the monitor.

Tier: Pro. If the owner's plan drops below Pro, this flag stops being sent to viewers.

## Summary table

| Control | Effect | Tier |
|---|---|---|
| Block right-click & copying | Suppresses the context menu and text selection in the viewer; does not prevent keyboard copy, DOM inspection, or reading the PDF outside the viewer. | Basic+ |
| Block printing | Blocks print/save shortcuts and blanks the document in print output; does not prevent printing a screenshot or the file opened elsewhere. | Basic+ |
| Blur on focus loss | Blurs the view when the window or tab loses focus; does not prevent screenshots or recording while the tab is active. | Pro |

## When these work and when they don't

Protection works best when your readers are:

- Browsing casually and don't want to be bothered with workarounds
- Viewing on a trusted device in a secure context (an office, a closed meeting)
- Relying on the viewer interface, not the underlying bytes

Protection does not work if your reader is:

- Taking a screenshot or screen recording
- Using developer tools to inspect the page
- Requesting the document's URL directly instead of using the viewer
- Motivated to circumvent friction

## Best practice: combine with watermarking

To leave a trace on a leaked copy, enable watermarking as well as, or instead of, these toggles. The watermark is stamped into the served PDF, so a forwarded copy carries an identity line and a timestamp. How useful that identity is depends on what the reader gave you: an invited or gate-captured email address names a person, while an anonymous reader gets only an opaque per-session key. Watermarking marks a copy; protection only adds friction to casual copying. Neither prevents a leak.

Related:

- Watermarking
- Download control
- Page-range links
- Plans and limits

---
URL: https://everypage.co/docs/security/encryption-and-privacy
Title: Encryption and privacy | EveryPage Docs
Description: How EveryPage stores documents and what data it does and does not record about document viewers.

# Encryption and privacy

How EveryPage stores documents and what data it does and does not record about document viewers.

EveryPage encrypts your documents at rest and discards visitor IP addresses, replacing them with pseudonymous reader identities. This is encryption at rest, not end-to-end encryption: EveryPage holds the keys. This page explains what that protects against and what it does not.

## Document encryption at rest

Your documents are encrypted with AES-256-GCM before being written to disk. Which key is used depends on how the file arrived:

- Files uploaded to an account are encrypted with that account's own encryption key, generated when the account is created and versioned thereafter. The key itself is wrapped (encrypted) with a master encryption key and stored in the database — the plaintext key is never at rest.
- Anonymous uploads get a random key generated for that one file, wrapped with the same master key and stored on the file's database row. Claiming an anonymous upload into an account does not re-encrypt it: it keeps the key it was uploaded with, which is why the shared link keeps working.

The upload never holds the whole document in memory. As bytes arrive from your browser they are streamed into a chunked encryption format — a 16-byte header followed by chunks of up to 1 MiB of plaintext each, sealed individually. Chunk nonces are constructed, not random: a random per-file prefix, then a chunk counter, then a final-chunk flag. The counter makes reordered chunks fail authentication and the flag makes truncation detectable, so a stream cut short by accident or attack does not decrypt as a valid shorter document. The header is used as additional authenticated data for every chunk, binding each one to this file's parameters.

When a viewer opens or downloads your document, EveryPage reads and decrypts it on demand using the same streaming format. If the file carries a watermark or a page range, the decrypted document is written to a temporary file so it can be rewritten through pdfcpu before streaming; that temporary file is deleted when the request ends. Files with neither transform are streamed straight through without ever being fully materialized.

Important limitation: this is encryption at rest, not end-to-end encryption. EveryPage holds the keys and can read your documents. The protection this provides is against someone who obtains the stored files without the master key — a stolen disk, a backup, a compromised storage provider. It provides nothing against an attacker who obtains the EveryPage server or the master encryption key, and nothing against EveryPage as the operator. If your threat model includes the platform itself, you need end-to-end encryption, where only you hold the key, and EveryPage does not offer it.

## Visitor identification without IP storage

When someone views your document, EveryPage does not store their IP address. Instead, the address is run through a salted HMAC-SHA256 and only that hash is kept, as the key to a stable pseudonymous reader identity. Historical rows that predated this were converted to reader identities and their stored addresses scrubbed.

The salt is configured per deployment and can be changed. Changing it changes the hash of every address, which re-buckets every reader under a new pseudonymous identity — existing readership history stays attached to the old identities. You cannot look up a reader's IP address from your readership data, because the address was never stored, and the mapping is not reversible. If you need to block a specific address, that is not something your readership data can tell you.

The address is still processed in flight while the request is being handled. Rate limiting and abuse caps operate on it, and country lookup sends it to an external geoip service (ip-api.com) over plain HTTP. The address is discarded afterwards, but it does leave the server for that lookup.

The country that lookup returns is stored, on the same view-session and access rows that carry the pseudonymous reader identity — that is what makes the country breakdowns in your readership reports possible. So a country is associated with a reader identity; what is not stored is the address it was derived from.

This approach gives you stable returning-reader detection and per-page timing without holding visitor addresses. It costs you the ability to look up or block a specific address later.

## Lead-capture data and consent

If you enable an email gate on your document, every viewer who submits the gate provides contact information that you chose to collect. That captured email address and any additional form fields (name, company, phone) are personal data you control, and they are stored in your readership data and events feed. Lead data is Pro-tier for viewing; you cannot see captured leads if you downgrade.

See Email gates and lead capture for details on how to set up, manage, and export captured data.

## Link-variant labels

If you create link variants (personalized links sent to specific recipients), each variant carries a recipient label as its only personal field. That label can be redacted on request, which NULLs it from stored analytics and webhook payloads containing that variant's data.

See Link variants for details on creation, attribution, and redaction.

## Key versioning and the rotation limitation

Per-account encryption keys are versioned. Each file records the key version it was encrypted under, and that version is unwrapped when the file is served.

There is no self-service key rotation: rotating an account's key is not exposed in the app or the API on any plan. The underlying operation exists on the platform side, and it carries a limitation worth stating plainly — rotating a key creates a new version but does not re-encrypt existing documents. Files keep the version they were written with, so every old key version must remain unwrappable for as long as any file still uses it. Old wrapped keys are therefore retained in the database rather than deleted.

The consequence: if a key version were compromised, existing files encrypted under it could not be retroactively protected by rotating. Only files uploaded after the rotation would use the new version. Documents do not all age out on their own, either — signed-in documents never expire unless the owner sets an expiry, and unclaimed documents published from Canva are retained for a year.

## Transparency and limits

For a full picture of what EveryPage measures about your readership, see What EveryPage measures.

For technical details on how reader identities work and how they flow through your readership reports, see Reader identities.

For integration-specific measurement, see Google Analytics.

---
URL: https://everypage.co/docs/readership/what-everypage-measures
Title: What EveryPage measures | EveryPage Docs
Description: Understand what EveryPage records about your document views, why view_count diverges from sessions, and what data persists without a paid plan.

# What EveryPage measures

Understand what EveryPage records about your document views, why view_count diverges from sessions, and what data persists without a paid plan.

EveryPage collects readership data the moment someone opens your document. You receive session-level telemetry, page-by-page engagement signals, and reader location information — all recorded in the same way regardless of your plan. What you can see and act on depends on your tier, but the underlying data is captured equally for everyone. This page covers the measurement mechanics in detail; for a feature-level view of what tracking gives you, start with the PDF tracking overview.

## How data collection works

When a reader opens your document, EveryPage records a view session: their device type, browser, referrer source, and country. Country is resolved from the IP by a geolocation lookup that runs asynchronously after the session row is written, and it is best-effort — a lookup that fails or is skipped under load leaves the country blank. As they read, the viewer reports page-turn events with time spent on each page. When the reader closes the tab or navigates away, their session ends via a keepalive request — the viewer itself determines when to report the close, not a server-side timeout.

All of this happens regardless of your plan. A reader on a free account accumulates sessions, unique readers, page-level metrics, and geographic data in exactly the same way a Pro owner does. The moment you upgrade, that history is already there.

## The reader identity model

Readers are never identified by IP address. Instead, EveryPage computes a stable pseudonymous identifier for each visitor using a salted HMAC of their IP, then discards the IP itself. This means you can track that Reader #7 returns multiple times to your document without ever storing or seeing their actual address. Because the identifier derives from the address alone, its granularity is the network, not the person: several people behind one office IP resolve to one reader, and one person moving between home, office and mobile resolves to several. For more detail on how this protects privacy, see encryption and privacy.

## The critical distinction: view_count vs. sessions

This is the single most important point in readership measurement. view_count is not a readership count. It diverges from session data by design and tells you something very different.

view_count measures bytes actually served to readers. It has exactly one writer in the system: a single counter increment in the download handler, positioned after every gate check — custom domain, expiry, burn, password, email, the download-disabled refusal — and after the stored blob has been opened and decrypted, immediately before streaming starts. Nowhere else touches the column.

Two transformations run after that increment: the page-range trim and the watermark stamp. Both fail closed and send no bytes when they fail, so a request that dies in the transform still leaves the counter one higher.

### What view_count over-counts

No deduplication exists. Every refresh, every SPA reload, every embed load, every time you preview your own document — each one increments the counter. If Reader #3 opens your document, scrolls through five pages, closes the tab, and immediately re-opens it, that counts as two views. The counter does not know which bytes were the "real" reads.

### What view_count under-counts

A reader can appear in your sessions table but never increment view_count:

- A reader starts a session (a row is written to view_sessions).
- They pass the email gate, or no gate exists.
- But then the document fetch fails — the blob is corrupted, the file is missing, or decryption fails.
- Their session is recorded with full attribution (country, device, pages they claimed to view).
- view_count stays unchanged because no bytes were served.

The same happens if a reader abandons after submitting the email gate but before the document loads: they appear in your session counts — and, where you use a lead-capture form, in your captured contacts — but they never appear in view_count.

### The key consequence

A document can show real sessions, unique readers, countries visited, and captured leads — while view_count sits at zero. Never use view_count to answer "has this been read?" Use session data instead.

## Reporting is tier-gated; capture is not

EveryPage records sessions and page events on every plan — free, basic, and pro. The gates that control what data you can see sit in the reporting layer, not the capture layer. A free-tier owner sees the summary cards, average time included. Upgrading to basic unlocks trends, the read-through funnel, per-page stats, the audience breakdowns, and the extra summary figures (median time, completion rate, re-read share). Pro adds reader identities (pseudonymous IDs to track individuals), live reader count, CSV export, captured contacts, and email-capture gating.

Importantly, this means upgrading an account reveals history you already accumulated while on the free tier. You were collecting sessions the whole time; you just could not see them. The moment you upgrade, they appear.

## Gates do apply to capture

While capture is plan-ungated, it is not gate-ungated. Every telemetry endpoint runs the same viewing gate stack as the download handler: a reader who cannot open your document cannot write telemetry against it. A visitor without a valid password, one arriving on a custom domain that does not serve the document, or one holding an expired or burned link cannot fabricate analytics entries.

The session-start request is the one deliberate exception, and only for the email gate: it runs every other gate, then validates the submitted address (or lead-capture form) server-side. That request is what satisfies the email gate. A rejected submission writes nothing — no session row, no captured contact.

## Plan tiers at a glance

See plans and limits for the full breakdown and pricing. The analytics ladder is:

- Free: Total views, unique visitors, average time per session, the count of distinct countries, and downloads.
- Basic: Everything free, plus median time, completion rate, re-read share, views over time, the read-through funnel, per-page stats, and the audience breakdowns (source, referrer, browser, device, location, viewer mode, reading hours).
- Pro: Everything basic, plus reader identities (to track returning visitors), live active-reader counts, per-variant readership, captured contacts, CSV export of all sessions, and email-capture gating.

## Related pages

- Summary and trends
- Read-through funnel
- Reader identities

---
URL: https://everypage.co/docs/readership/summary-and-trends
Title: Summary and trends | EveryPage Docs
Description: The headline readership numbers for a document, and how engagement changes over time.

# Summary and trends

The headline readership numbers for a document, and how engagement changes over time.

Every document has a readership page that opens with a row of summary cards, then — on paid plans — a trend chart and a set of deeper metrics. Reader activity is recorded identically on every plan; what differs is how much of it you are shown.

## Summary cards

These appear on every plan, including free.

Total views counts bytes actually served, not readers. Reloads, embed loads and your own previews all increment it, and it is not deduplicated. Read what EveryPage measures before you rely on this number — it is the single most misread figure in the product.

Unique visitors counts distinct pseudonymous readers. Each reader is a stable identifier derived from their IP address without storing it, so a returning reader on the same network is recognised as the same reader. The identifier derives from the address alone: two colleagues behind one office IP count as one visitor, and one person reading from home and then from mobile counts as two.

Average time is the mean session duration over sessions with a recorded duration greater than zero. A session that never reported an end has no duration and is left out of the mean rather than dragging it down as a zero. A session that did report an end but no measurable time is left out on the same rule.

Countries counts the distinct countries sessions were resolved to. The lookup runs asynchronously after the session is recorded and is best-effort, so sessions whose lookup failed or was skipped carry no country and count toward nothing here.

Downloads counts explicit downloads, and includes the ones you make yourself — it is not a non-owner-only figure. Turning downloads off stops readers from downloading, but your own downloads still count.

## Trends and extended metrics

Basic and above adds a views-over-time chart covering the last 30 whole UTC days. It plots reading sessions started per day, not the Total views figure above. Days with no sessions are drawn as zero rather than collapsed, so the window is always a continuous 30 days.

Basic also adds:

- Median time, the midpoint of session durations — same exclusion as the average, and more resistant to outliers
- Completion rate, the share of sessions that reached the document's final page
- Re-read rate, the share of page turns that went backwards, out of the turns whose direction was recorded — readers going back over content rather than straight through it

Pro adds:

- New versus returning sessions
- Call-to-action clicks, if you configured a CTA button
- Invited but not viewed, for recipients of tracked invites who have not opened the document

## How plan gating is presented

The readership response carries a tier field naming your plan, and omits the sections above it — a free-tier response has no trend, funnel or breakdown data in it at all. The page renders what it received and, in place of the missing sections, an upgrade card naming the plan that unlocks them. Gated metrics are not shown locked or blurred; they are simply absent until you upgrade.

## Data is captured on every plan

Sessions, page-level activity and geography are recorded the same way regardless of your plan. A reader opening a document owned by a free account produces the same record as one opening a Pro account's document.

The consequence is worth knowing: upgrading does not only start collecting more, it reveals the history you have already accumulated. Funnels, breakdowns and per-page stats populate retroactively over a document's whole life. The trend chart is the exception, and only because of its own window — it never looks back further than 30 days, on any plan.

## Related

- What EveryPage measures
- Read-through funnel
- Audience breakdowns
- Portfolio overview
- Plans and limits

---
URL: https://everypage.co/docs/readership/read-through-funnel
Title: Read-through funnel | EveryPage Docs
Description: The report that shows how far readers get before they stop.

# Read-through funnel

The report that shows how far readers get before they stop.

The read-through funnel measures reader persistence by showing, for each page, the share of reading sessions that reached at least that page. A flat curve means readers stay engaged throughout. A sharp drop signals a specific page where engagement falls off, so you can identify which content needs revision.

Its unit is the session, not the reader: someone who opens the document three times contributes three sessions to the funnel, each counted at the deepest page that session reached.

## How to read the funnel

The funnel displays a horizontal bar for each page. Long documents are sampled to at most 30 evenly spaced steps, with the final page always appended so completion stays visible. The bar's width is the percentage of all sessions on the document that reached at least that page.

The denominator is every session, including sessions that reported no page activity at all. Those count toward the total but reach nothing, so they pull every bar down.

A sharp cliff on one page—where the percentage suddenly drops—indicates that specific page caused readers to stop. This might be a dense section, a tone shift, or simply the point where they found what they needed. Recurring cliffs across multiple files suggest a pattern worth addressing.

A gentle decline across all pages indicates readers are gradually finishing the document but not abandoning it at any one spot. This is typical of longer materials where attrition is natural.

A plateau near 100% through the later pages means nearly everyone who started continued all the way to the end—a strong engagement signal.

When no session has reached a page yet, the bar shows 0%.

The funnel needs a known page count to draw at all. That count is reported by the viewer when a reading session ends, so a document nobody has finished a session on yet shows no read-through data rather than an empty chart.

## Completion rate

Your summary also displays a completion rate: the percentage of sessions that reached the document's final page. It shares the funnel's denominator — every session on the file — so a completion rate of 60% means 60% of reading sessions ran to the last page.

## How ranges affect the funnel

When you share a page-range link, the recipient receives a trimmed document and their viewer numbers it from 1. Share pages 5–15 and the recipient reports pages 1 through 11: the page numbers recorded are positions in the excerpt, not in the source document.

Recipients of a ranged link also never write the document's total page count. A reader of an 11-page excerpt cannot shrink a 100-page document's stored count — only you and readers of the full document report it.

The consequence is that the funnel's axis stays the full document while a ranged recipient's deepest page can never exceed the window's size. A recipient who read the whole excerpt registers as having reached page 11 of 100 and does not count toward the completion rate, which is measured against the document's final page rather than the window's. Read the funnel for a ranged link within the window: the first bars are the real drop-off, and the cliff immediately after them is the range boundary, not abandonment.

When a range is active, the readership API response carries an effectivePages field — the size of the shared window, clamped to the known page count — so an API consumer can label the funnel with the context. The readership page does not currently render a label from it.

## Basic and above

The read-through funnel is available on the Basic plan and higher, and so is the completion rate that shares its denominator. Free-tier accounts see only the summary cards — total views, unique visitors, average time, countries and downloads. See plans and limits for the full feature breakdown.

## Related pages

- What EveryPage measures
- Page-range links
- Plans and limits

---
URL: https://everypage.co/docs/readership/page-by-page-stats
Title: Page-by-page statistics | EveryPage Docs
Description: Track which pages were seen and how long readers spent on each.

# Page-by-page statistics

Track which pages were seen and how long readers spent on each.

EveryPage records a turn event every time a reader leaves a page, and rolls those events up per page number: how often each page was seen, how long readers stayed on it, and how often they came back to it.

## Metrics per page

The page-stats endpoint (GET /api/v1/files/{uuid}/readership/pages) returns three numbers for every page that has data, plus the document's total page count:

- Views — how many times a reader's time on that page was recorded, across all sessions
- Average time — mean dwell time on the page (avgDurationMs, in milliseconds; the dashboard chart rounds it to seconds in the bar tooltip)
- Back turns — how many of those records show the reader arriving at the page by navigating backward, the re-read signal

The dashboard plots views as the "Page-by-page" bar chart, and ranks the pages with the most back turns in a separate "Most re-read" list. The file-level share of backward turns out of all directional turns appears in the summary cards.

## Reading dwell time

Views and average time answer different questions. A page with many views and two seconds of average dwell was passed through; a page with fewer views and thirty seconds was read. Turns that recorded no measurable time are excluded from the average, so the figure describes the turns that actually dwelled on the page.

## How page data is captured

As readers navigate your document, the viewer posts turn events to /api/files/{uuid}/page-turns. That path is deliberately neutral: EasyPrivacy and similar ad-blocker filter lists block URL segments such as "analytics", "stats", "tracking" and "page-view", and a blocked request fails silently, so every capture route avoids those words.

Each event describes the page the reader has just left: the page number, the milliseconds spent on it, and how the reader had arrived at it — forward or back (empty for the session's opening page, which counts as neither). A final event is flushed when the reader closes the tab or navigates away. Values arrive from an unauthenticated endpoint, so implausible page numbers and durations are rejected or clamped before they are stored.

## Page range links and reported data

If you've shared a page-range link — a Pro feature that limits readers to a window of pages — those readers are served a trimmed document, and their page numbers are relative to what they received. A reader restricted to pages 5–10 reports pages 1 through 6, which is where their turns land in the per-page stats.

The page count itself stays honest: a reader who only saw a window is never allowed to write the document's total page count, so a 6-page preview never shrinks a 50-page document.

## Funnel vs. page-by-page breakdown

The read-through funnel answers "how many readers reached page N?" It shows drop-off: the percentage of sessions that made it through your entire document. Page-by-page statistics instead show "how long did readers spend on each page?" They complement the funnel but measure different things.

A funnel might show that 80% of readers reached page 3 but only 20% finished. Page stats tell you whether those who did reach page 3 read it carefully (high dwell) or skipped past it (low dwell). Together, they reveal both where readers exit and how they engage with the content they do see.

## Availability

Page-by-page statistics are available on the Basic plan and above; free accounts see only the summary cards. Capture is not tiered — page turns are recorded on every plan, so upgrading exposes the history a document already accumulated. See plans and limits for feature availability.

## Related

- Read-through funnel — understand where readers drop off
- What EveryPage measures — overview of all readership data
- Page-range links — limit reader access to specific pages

---
URL: https://everypage.co/docs/readership/audience-breakdowns
Title: Audience breakdowns | EveryPage Docs
Description: Segment a document's read sessions by referrer, attribution source, device, browser, country, viewer mode, reading hour, and link variant.

# Audience breakdowns

Segment a document's read sessions by referrer, attribution source, device, browser, country, viewer mode, reading hour, and link variant.

A document's read sessions are grouped into eight breakdowns: referrer, source, device type, browser, country, viewer mode, reading hour, and link variant. Every breakdown counts sessions, not page views or bytes served. All of them are Basic and above, except the variants breakdown, which is Pro.

## Referrer breakdown

The referrer breakdown shows where readers clicked to reach your file. Raw referrer URLs are normalized to their hostname, so all links from the same website group together. Sessions that arrived with no referrer header are counted as "Direct". The dashboard lists the top ten referrers by session count.

## Source attribution

The source breakdown attributes each read session to the channel the reader arrived through. The viewer reports the channel from the ?via= parameter on the link, and the server accepts exactly four values — anything else, including a missing value, is stored as link:

- link — a shared link with no ?via= tag, and the fallback for any unrecognized value
- qr — a QR code scan; the generated QR image encodes the share link with ?via=qr
- email — a link EveryPage sent: share by email and tracked email invites both append ?via=email
- embed — a view through the /embed/ viewer, which reports embed for every session it starts

Email invites additionally carry an ?i= token identifying the individual recipient. That attribution is separate from the source breakdown: it names the reader in the session list, which is a Pro surface.

## Device and browser breakdowns

Both breakdowns are derived from the session's User-Agent header. The device breakdown sorts readers into mobile, tablet, bot and desktop — desktop is the default for anything the parser does not identify as one of the first three. The browser breakdown lists the top ten browser names, with sessions whose User-Agent yields no name grouped as "Unknown".

## Geography

The "Top locations" breakdown shows the ten most common reader countries. Country is resolved by an in-flight lookup when a session starts: the address goes to the geolocation service, the country name comes back and is written to the session row, and the IP itself is never stored. Sessions that cannot be resolved are labelled "Unknown"; private and loopback addresses resolve to "Local". For details on how EveryPage handles IP addresses, see Encryption and privacy.

## Viewer mode distribution

The viewer mode breakdown groups sessions by the viewer mode the reader was served — standard, flipbook, magazine or swipe. A document has one mode at a time, set by you, so this breakdown is a record of what was in effect when each session ran: after you switch a document from standard to flipbook, the split shows how the readership divides across that change. Sessions that reported no mode count as standard.

## Peak reading hours

The "Reading hours" heatmap counts sessions by day of week and hour of day, bucketed by session start time and labelled in UTC. It is not converted to your account's local time, so read the grid with that offset in mind.

## Link variants breakdown (Pro only)

When you create link variants to share the same file with different recipients, each session records the variant it arrived through. The variants breakdown returns, per variant, its UUID, its recipient label, the number of sessions, the average read time, and whether the variant is revoked or its label redacted. It is Pro-only, it is served with the rest of the file's readership data, and it is omitted entirely for files that have no variants.

## Accessing breakdowns

Breakdowns come back with the file's readership data (GET /api/v1/files/{uuid}/readership) and, apart from variants, each has its own card on the readership page. Basic and Pro accounts get all of them except variants, which needs Pro. Free accounts get the summary cards only; the underlying sessions are still recorded, so upgrading exposes the breakdowns for reads that already happened.

Pro accounts can also download the per-session rows and captured contacts through CSV export. That export is a session-level dump, not a copy of the breakdown tables.

---
URL: https://everypage.co/docs/readership/reader-identities
Title: Reader identities and live presence | EveryPage Docs
Description: Distinguish individual reading sessions and see who is actively reading right now.

# Reader identities and live presence

Distinguish individual reading sessions and see who is actively reading right now.

EveryPage identifies readers pseudonymously, so a document's readership resolves into individual sessions and repeat visitors rather than a single total. Live presence reports which of those sessions are open right now. Both are Pro features; the underlying sessions are recorded on every plan.

## Pseudonymous identities

A reader identity is a salted HMAC of the visitor's IP address. The address is used to compute the hash and then discarded — it is never written to the database — so the same visitor maps to the same reader id on a later visit without EveryPage holding their IP. Because the input is the IP, visitors sharing one address (an office network, a mobile carrier NAT) collapse into a single reader, and one visitor on several networks appears as several readers.

The pseudonymous ID appears in your readership session list as "Reader #N" alongside the view timestamp, source, device, browser, country, pages viewed, and time spent. If a reader has already been named (see below), their name or email replaces the ID.

A session is tagged "Returning" when the same reader has an earlier session on the same document. That comparison is per document: a reader who has read three of your files, but this one only once, is not returning here.

## Named readers: three paths

A reader becomes named when they tell you who they are. EveryPage supports three routes:

Email gate. When you enable email gates and lead capture, viewers submit an email address before the document is served. The validated address is stored on the view session and shown in place of the pseudonymous ID. If the gate uses a custom form rather than a plain email prompt, the address still names the session; the other fields the form collected (name, company, and so on) land in the separate "Captured contacts" table, not in the session row.

Email invites. Tracked links from email invites carry an ?i= recipient token. A session opened through a valid token is attributed to that invitee's name and email from your invite list and flagged "Invited"; the invitee identity wins over any gate-captured address. A valid invite also satisfies the email gate, so an invited reader is never prompted.

Link variants. Each link variant can carry an optional recipient label. Sessions record the variant they arrived through, and the label names them in the Pro variants breakdown and in file.viewed / file.downloaded webhook payloads. The label does not replace the reader ID in the session list — variant attribution is per link, not per reader.

The three routes are independent. A gate captures anyone who opens the document; invites and variants name a recipient only where you supplied one.

## Session data

The "Recent views" table holds the 20 most recent sessions, newest first. Each row carries:

- Reader identity — invitee name and email, captured gate email, or the pseudonymous "Reader #N"
- Started at — when the session began
- Time spent — total reading time reported by the viewer
- Pages viewed — how many distinct pages the reader opened
- Device — desktop, mobile, tablet or bot
- Browser — resolved from the User-Agent
- Country — resolved by in-flight IP lookup
- Source — link, qr, email or embed
- Flags — "Invited" for sessions that came through an invite token, "Returning" for a repeat reader of this document

CSV export covers every session for the document, not just the most recent 20, and adds the operating system column that the table does not show.

## Live presence

The readership page shows a "● N reading now" badge while at least one reader is active. A session counts as active when it started within the last five minutes and has not yet reported its end, so a reader who closes the tab drops out on their final beacon, and one who leaves the document open ages out of the count after five minutes. The page polls the count every 30 seconds from a dedicated endpoint (/readership/live). Live presence is Pro-only, like the session list.

## Retroactive history

Capture is not tiered. Sessions, readers, page turns, and gate submissions are recorded on free, Basic and Pro alike; only the owner-facing reports are gated. Free accounts see the summary cards, Basic adds trends, the funnel, page stats and the breakdowns, and Pro adds the per-session identities, live presence, captured contacts and CSV export.

Because the rows were always written, upgrading is retroactive: the sessions recorded while the document sat on a lower plan appear as soon as the plan allows them. The same applies in reverse — a downgrade hides the reports, it does not delete the history.

## Related

- What EveryPage measures — overview of all readership signals
- Email gates and lead capture — collecting names and contact info
- Email invites — sending tracked links to named recipients
- Link variants — per-recipient tracking and overrides
- CSV export — downloading session and lead data
- Encryption and privacy — how reader hashes protect privacy
- Plans and limits — tier comparison and feature availability

---
URL: https://everypage.co/docs/readership/csv-export
Title: CSV export | EveryPage Docs
Description: Export readership data and captured leads to spreadsheet format with formula-injection protection.

# CSV export

Export readership data and captured leads to spreadsheet format with formula-injection protection.

Download your document's readership data and lead captures as a CSV file for analysis in Excel, Sheets, or other spreadsheet tools. Every CSV export is a Pro feature, and viewer-supplied text in them is escaped so it cannot execute as a spreadsheet formula.

## Export readership sessions

The Export CSV button on a document's readership page downloads one row per viewing session, followed by a second section listing the contacts captured by your email-capture gate. The button only appears on Pro; the endpoint also rejects lower tiers with HTTP 403.

The sessions section has eleven columns:

- reader — The pseudonymous reader label, in the form Reader #<id>. Blank when no reader identity was resolved for the session.
- email — The email captured for that session, from the email gate, the lead-capture form, or an email invite. Blank otherwise.
- source — Attribution for how the reader arrived: link, qr, email, or embed. Unrecognised values are recorded as link.
- device — Device class derived from the user agent: desktop, mobile, tablet, or bot
- browser — Browser name (e.g., Chrome, Safari)
- os — Operating system (e.g., iOS, Windows)
- country — Country resolved by IP geolocation at view time (the address itself is never stored)
- pages_viewed — Number of pages the viewer read
- duration_ms — Time spent reading in milliseconds
- started_at — Session start timestamp (RFC 3339, UTC)
- ended_at — Session end timestamp (RFC 3339, UTC)

If at least one contact has been captured, a blank row separates the sessions section from the contacts section. The contacts section includes:

- contact_captured_at — Timestamp when the contact was captured (RFC 3339, UTC)
- One column per field in your document's current gate form (e.g., name, company, phone)
- Any additional keys found in stored submissions but no longer in the form — appended alphabetically after the current fields, so contacts captured under an older version of the form keep their values

## Export proofing reports

If you enable page marks or annotations for your document, you can also export those reports as CSV. Both features and both reports are Pro.

Each of these reports is one endpoint that returns JSON by default and CSV when called with ?format=csv. The proofing sections of the readership page have their own export buttons, which navigate to that CSV form.

Page marks export contains:

- viewer — The invitee's email address, or Anonymous reader <key> (a truncated pseudonymous viewer key) for viewers who were not invited
- page — Page number
- mark — Verdict (pick, reject, or maybe)
- updated_at — Timestamp of the mark (RFC 3339, UTC)

Annotations export contains:

- viewer — Same identity label as the page marks export
- page — Page number
- note — Annotation text
- x, y, w, h — Rectangle coordinates, normalized to the 0–1 range against the page. Blank if the stored rectangle is missing a component.
- created_at — Annotation timestamp (RFC 3339, UTC)

## Formula-injection safety

Viewer-supplied values are escaped so they cannot execute as formulas when the file is opened in a spreadsheet application: if a cell value's first character is =, +, -, or @, it is prefixed with a single quote ('), which makes the spreadsheet treat the whole cell as literal text. Those four characters are the complete set that triggers the prefix.

The escaping is applied to every field a reader can influence: in the readership export, the email, source, device, browser, os, and country columns plus every captured contact value; in the page marks export, the viewer and mark columns; in the annotations export, the viewer and note columns. Server-generated fields — reader labels, page numbers, durations, coordinates, and timestamps — are written unescaped because their values cannot be attacker-controlled.

## Programmatic access

If you need to retrieve readership data via code rather than downloading a file, use the events feed API, which lets you fetch view sessions, download records, and captured leads with cursor-based pagination.

## Related

- Reader identities
- Page marks
- Annotations
- Email gates and lead capture
- Events feed API
- Plans and limits

---
URL: https://everypage.co/docs/readership/view-notifications
Title: View notifications | EveryPage Docs
Description: Get an email when someone opens one of your documents.

# View notifications

Get an email when someone opens one of your documents.

View notifications email you when a reader opens a document you have shared, at most once per hour per document. The setting is per document, not account-wide.

## Enable notifications for a document

View notifications are a Basic plan feature and above. To turn them on:

1. Open the document's Configure & Share page
2. Open the Privacy & Access panel
3. Tick Email Me When Viewed
4. Save your changes

Free accounts cannot enable the setting — the server rejects the change with HTTP 403. The plan is also re-checked when a notification is about to be sent, so a downgrade to free stops the emails on documents where the setting is still on.

## What the notification contains

When someone opens your document, you receive an email with:

- The name of your PDF
- Who opened it — their email address if one was captured for that session by the email gate, the lead-capture form, or an email invite; otherwise "A reader"
- How the reader arrived: link, qr, email, or embed
- A link to that document's readership page

## Throttling: one email per hour per document

To prevent inbox flooding when a popular document gets many readers at once, notifications are throttled to at most one email per document per hour. The window is per document, not per reader or per link variant: every reader of the same document draws on the same hourly allowance.

The clock starts when a notification is sent, and only when one is sent — suppressed opens do not extend it. If your document receives five opens in 45 minutes and then another open 20 minutes later, you receive two emails: one triggered by the first of those five opens, and one triggered by the reader at 65 minutes. The four suppressed opens are not summarized in either email; they are only visible in the readership reports.

The throttle is a single conditional database update that stamps the last-notified time and reports whether it succeeded, so concurrent opens race for one claim and exactly one wins. There is no window in which two readers can both trigger an email. The claim is consumed at that moment, before the email is handed to the mail provider, so a delivery failure is not retried and still uses up the hour.

## Your own views don't trigger notifications

A visit is compared against the document's owner before any notification is considered, so opening your own document never emails you and never consumes the hourly window. The comparison is made against the account signed in for that request: opening your own link while signed out — in a private window, or on another device — is indistinguishable from a reader's visit and does notify you.

## Turn off notifications

Untick Email Me When Viewed in the same Privacy & Access panel and save. Future opens stop sending email immediately.

## For more granular controls

View notifications are throttled and email-only. If you need unthrottled alerts routed to Slack, Zapier, Make, n8n, or any other system, use webhooks, which are available on all EveryPage plans and deliver one file.viewed event per reading session.

## Related settings

View notifications are separate from two other alerting features:

- Comment notifications — Pro feature. Get an email when a reader adds a comment to your document. See Comments.
- Read receipts — Basic+ feature. Request confirmation from readers that they've seen your document. See Read receipts.

---
URL: https://everypage.co/docs/readership/portfolio-overview
Title: Portfolio overview | EveryPage Docs
Description: View aggregated readership across your entire library and scope reports by folder.

# Portfolio overview

View aggregated readership across your entire library and scope reports by folder.

The portfolio overview is the cross-file readership rolled into your library: three totals above the document list, per-file counts on each row, and — on Pro — a recent-activity table below. It can be scoped to a single folder.

## Aggregate readership across all files

Three totals are reported across every document you own:

- Total Reads — Reading sessions across the library
- Unique Readers — Distinct pseudonymous reader identities that opened any of your documents
- Downloads — Download count across the library

These aggregates are available on every plan, including free. Sessions are recorded identically on every tier, so upgrading exposes the history that was already being collected rather than starting a new count.

## Per-file counts

Each row of the document list carries that file's own counts:

- Reads — Reading sessions on that file
- Readers — Distinct reader identities for that file
- Downloads — Download count for that file

These let you compare documents without opening each report. They come from the same tables as the file's own readership page, so a file's Reads here matches its session count there. Note that Reads counts sessions, not view_count — see what EveryPage measures for why those two numbers differ.

## Recent reader activity (Pro only)

On Pro, a Recent activity table appears below the document list, listing recent reading sessions across the whole library, newest first. Each row shows:

- Document — The file the session belongs to, linking to its readership page
- Reader — The pseudonymous reader label (Reader #<id>), or - when no reader identity was resolved
- Source — How the reader arrived: link, qr, email, or embed
- Location — Country resolved by geolocation, or "Unknown"
- Time Spent — Session duration
- Date — When the session started

This is the only part of the overview that is tier-gated. Free and Basic accounts receive the aggregates and the per-file counts; on those plans the response carries no session rows at all, so the table does not render. Pro adds the per-session reader identities.

## Scope the overview to a folder

Selecting a folder re-scopes the overview to that folder: the three aggregates, the per-file counts, and the recent-activity table are all recomputed over the files it contains. The folder is resolved and ownership-checked on the server, so a folder belonging to another account returns HTTP 404 rather than any data.

Folder scoping therefore requires folders, which are Basic and above — a free account has no folders to scope by. It carries no tier requirement of its own: the same Pro gate on recent activity applies whether you are looking at the full library or one folder.

## Related

- Reader identities
- Summary and trends
- Plans and limits
- Folders

---
URL: https://everypage.co/docs/reader-interaction/comments
Title: Comments | EveryPage Docs
Description: Enable readers to leave feedback on your documents with per-comment visibility controls and owner moderation.

# Comments

Enable readers to leave feedback on your documents with per-comment visibility controls and owner moderation.

Comments let your readers leave feedback directly on a document. Each comment is owned by its author but subject to your moderation—you decide which comments appear publicly to all viewers and which remain private between you and the commenter. Comments are a Pro feature only.

## Enabling comments on a document

To allow readers to leave feedback, open the document's Configure & Share page and turn on "Collect Comments" (commentsEnabled). Two further settings sit alongside it:

- Allow Public Comments (commentsAllowPublic): When on, readers can choose whether their feedback is private (visible to you only) or public (visible to all viewers). When off, all comments are forced private regardless of the reader's choice.
- Email Me on New Feedback (notifyOnComment): When on, you are emailed when a reader leaves any comment (private or public). At most one notification is sent per document per hour, even if multiple comments arrive in that window. Your own comments never notify you.

Enabling or disabling comments does not delete existing feedback. Comments are served only while you still hold Pro: on a downgrade the feedback panel stops being offered to viewers, new comments are refused, and the moderation list is no longer shown to you—but nothing is deleted, and it all comes back if you return to Pro.

## Comment visibility: private vs. public

When a reader leaves a comment, they choose its visibility:

- Private comments (the default) are visible only to you, in the Readership page for that document. The commenter sees their own private comment echoed in the feedback panel immediately after posting, but it is not served back on a later visit. No other viewer ever sees it.
- Public comments are visible to you and to all viewers of that document. Anyone who opens the sharing link sees every public, unhidden comment in the feedback panel.

If you have turned off "Allow Public Comments", every comment is forced private at submission time whatever the reader asks for, and the compose form shows a notice that only the document owner will see the comment.

## Owner moderation: hide, make private, and delete

After a comment is posted, you moderate it from the Readership page for that document, which lists every comment including private and hidden ones:

- Hide / Unhide removes a comment from viewers' sight without deleting it. It stays in your list and can be unhidden later.
- Make private / Make public flips a comment's visibility. A private comment made public becomes visible to all viewers.
- Delete permanently removes the comment. Deletion cannot be undone.

Hiding and visibility changes are independent of each other. Viewers pick up a moderation change the next time the feedback panel loads its comments—there is no live push to open viewers.

## Comment submission limits and character constraints

Comments are subject to the following limits:

- Body length: 2,000 characters per comment. The viewer-facing form shows a character counter.
- Author name: 80 characters. Readers can leave their name or submit anonymously.
- Rate limit: 20 comments per viewing session in any rolling hour. Further submissions from that session are refused until earlier ones fall outside the one-hour window.

A comment may be attached to a specific page or left against the document as a whole.

## Notifications and webhooks

When a reader submits a public comment, EveryPage fires a note.created webhook event to your configured endpoints. The payload carries the commenter's name (author), their feedback text (body), and pageNumber when the comment is attached to a specific page. Three cases never fire the event: private comments (feedback between a reader and you stays between you), comments you post yourself on your own document, and any later moderation of an existing comment.

Owner email notifications are separate from webhooks and cover private comments too: with "Email Me on New Feedback" on, you receive at most one email per document per hour, regardless of how many comments arrive in that window. The email quotes the comment and links to the Readership page for the document.

## Related

- Annotations — let readers box a region of a page and note it
- Read receipts — ask readers to confirm they received a document
- Webhooks — automate workflows with document events
- View notifications — receive alerts when a reader opens your document
- Plans and limits — Pro feature comparison

---
URL: https://everypage.co/docs/reader-interaction/read-receipts
Title: Read receipts | EveryPage Docs
Description: Ask readers to explicitly confirm they received your document.

# Read receipts

Ask readers to explicitly confirm they received your document.

Read receipts capture an explicit confirmation from your reader that they received a document. Unlike the passive observation of readership analytics, a receipt is an action the reader has to take. It is not legally binding and it is not identity-verified: it records only that someone with access to the link clicked the confirmation button, plus whatever name they chose to type.

## Enable receipts for a file

To turn on read receipts, open the file's Configure & Share page and enable "Ask Readers to Confirm Receipt" (askReceipt). Once enabled, your viewers see a "Mark as received" button in the document viewer. When they click it, they may optionally enter their name (up to 80 characters) and submit the confirmation. Confirmations are listed on the Readership page for that document.

Read receipts require your account to be on a paid plan—Basic or higher. If you downgrade to free, the confirmation button stops being served and no new receipts are collected, but existing receipts are preserved. Upgrading restores the button.

## How confirmation works

When a reader confirms receipt, they are making an explicit choice. The confirmation form prompts for an optional name; if provided, that name is recorded alongside the receipt timestamp. The reader can dismiss the confirmation panel without confirming—no automatic tracking is involved.

Each reader can confirm receipt only once per document. Receipts are stored one per (document, viewer key), so a repeat confirmation is absorbed: no second row, no second notification, no second webhook. The viewer key is minted per reader per document and stored in the reader's browsing session, so it holds across repeat visits from the same browser for as long as that session lasts. It is not shared between browsers or devices, so the same person confirming from a second device produces a second receipt.

## Owner notifications

You are notified by email when a reader confirms receipt of your document. The notification includes the reader's name (if they provided one) and a link to the Readership page for that file. These notifications are throttled—at most one email per document per hour, even if several readers confirm within that window. Only fresh confirmations notify, and confirming from your own signed-in session never does. There is no separate notification switch: turning off "Ask Readers to Confirm Receipt" is what stops the emails.

## Webhook events

A fresh confirmation fires a receipt.confirmed webhook event; the payload carries the reader's name (empty when they did not provide one). Repeat confirmations from the same viewer key are absorbed and do not re-emit, and confirmations made from your own signed-in session never emit. See the webhooks documentation for configuring endpoints.

## Related topics

- Readership analytics — what we measure and how
- Comments and interaction — other ways readers can respond
- Plans and limits — feature availability by tier
- Webhooks — receipt events in your integrations

---
URL: https://everypage.co/docs/reader-interaction/page-marks
Title: Page marks and proofing | EveryPage Docs
Description: Let reviewers rate each page with pick, reject, or maybe verdicts.

# Page marks and proofing

Let reviewers rate each page with pick, reject, or maybe verdicts.

Page marks let each reviewer rate every page of a document with one of three verdicts— pick, maybe, or reject —without leaving a written note. This suits contact-sheet selection, layout review, and page-by-page approvals. Verdicts are restored when a reviewer returns, and follow them across devices when they arrive through an email invite.

## How viewers mark pages

When you enable page marks, viewers see a compact "Rate page" control near the top right of the viewer. It shows three buttons: Pick (✓), Maybe (~), and Reject (✕). Viewers click to set a verdict on the page they are on; setting a different verdict replaces the previous one, and clicking the active verdict again clears the page's rating altogether.

A viewer's own marks are loaded back into the control whenever they reopen the document; see Persistence and durability below for how far that reaches.

Annotations are a separate toggle in the same Proofing settings. When both are on, reviewers can mark pages and draw region-specific notes, and either action counts as proofing activity for the webhook below. See Annotations for details.

## Reviewing verdicts

Once viewers have marked pages, you see aggregated results in Readership. The summary shows:

- Per-page counts: for each page, how many reviewers picked, marked maybe, or rejected it
- Per-reviewer breakdown: each reviewer's own tally of picks, maybes and rejects. Reviewers who arrived through an email invite are identified by their email address; everyone else appears as an anonymous reader with a short opaque key

You can export the full results as CSV—one row per mark, with the columns viewer, page, mark and updated_at. Identities are escaped against spreadsheet formula injection.

To reach the report, open the Readership page for a document with page marks enabled: the Proofing section holds the per-page table, the per-reviewer breakdown and a Download CSV button. See CSV export for the other exports.

## Persistence and durability

Marks are keyed to the viewer's durable identity rather than to a single visit, and the viewer's own marks are reloaded whenever they reopen the document. How far that identity reaches depends on how the reader got in:

- Via an email invite: the identity is derived from the invite (its tracked link, or the invite email recorded earlier in that browsing session), so it is the same person on every device. A reviewer who marked pages on their phone sees those marks on desktop. See Email invites.
- Via a plain share link: the identity is a per-viewer key held in the reader's browsing session. Marks survive repeat visits in that browser but do not follow the reader to another browser or device.

Only you ever see who a viewer key belongs to; identities are never exposed to other viewers.

## Limits and webhooks

Page marks are Pro-only. You must be on Pro and enable the "Page verdicts" toggle (marksEnabled) in the Proofing settings on the Configure & Share page. Marking is rate-limited to 1000 marks per viewer per document in any rolling hour, which covers bulk marking on long documents; clearing a verdict is not counted against it.

Marking stays live only while the owner holds Pro. If you downgrade, the control stops being served and no new marks are recorded, but existing marks are kept and reappear if you return to Pro. Turning the toggle off has the same effect and deletes nothing.

The first time a viewer leaves any proofing feedback on a file—a mark or an annotation—EveryPage fires a proofing.updated webhook event to your configured endpoints, with kind (mark or annotation), pageNumber and viewer. It fires once per viewer per file, not once per action, so a reviewer marking 200 pages triggers exactly one event. Your own marks on your own document never emit. See Webhooks for the full event reference.

## Reading marks from the API

Because proofing.updated fires only once per viewer and carries no verdicts, it tells you that someone has started marking—not what they decided. Read the verdicts with GET /api/v1/files/{uuid}/page-marks, which returns per-page tallies, a per-viewer breakdown and document totals. Add ?format=csv for the same data as the Download CSV button. The endpoint is Pro-only and owner-only, and takes the readership:read scope.

The pattern for an automation is therefore: trigger on proofing.updated (or on a new comment), then pull the marks. All four integrations expose it— Zapier as the Get Page Marks search, Make as Get Page Marks, n8n as File → Get Page Marks, and the MCP server through everypage_get_readership with includeProofing. The photo proofing automation guide walks through a full workflow.

Treat the response as personal data: a reviewer who arrived through an email invite is identified by their email address.

For plan details and feature access, see Plans and limits.

---
URL: https://everypage.co/docs/reader-interaction/annotations
Title: Annotations | EveryPage Docs
Description: Let readers highlight regions and attach notes to specific areas of your document.

# Annotations

Let readers highlight regions and attach notes to specific areas of your document.

Annotations let your readers draw a box around any region of a page and attach a note to it. This is useful for document review, feedback, and markup workflows where you need point-specific comments tied to exact locations rather than whole-page reactions.

## How annotations work

When annotations are enabled, a reader clicks Annotate on the page they are reading and drags a box over any region of it. The region is stored as a normalized rectangle— x, y, w and h as proportions of the page (0 to 1 on both axes) rather than pixel coordinates—so the box stays on the same spot when the reader zooms, resizes the window, or opens the document on another screen. A rectangle must have positive width and height and lie inside the page; a request whose coordinates fall outside that is rejected. The reader can then attach an optional note (up to 2000 characters) before saving.

## Visibility and access control

Each reader sees only their own annotations—never another reader's, and never any identity. When you open the same document while signed in as its owner, you see every reader's annotations, and your reports group them by page and label each one with the reader's identity: the email address for readers who arrived through an email invite, otherwise an anonymous reader label built from a short opaque key. This is the distinction from comments, which are threads a commenter can choose to make public, and from page marks, which record one verdict per page with no free text.

A reader's own annotation appears immediately after they save it, and it is reloaded on their next visit, where they can open the note and delete it. Only the reader who created an annotation and the document owner can delete it.

Annotations key to the same durable viewer identity as page marks: readers who arrive through an email invite keep their annotations across devices, while readers on a plain share link keep theirs for as long as their browsing session lasts.

## Exporting and reporting

The Proofing section of the Readership page lists every annotation grouped by page, and a Download CSV button exports the same data. The CSV columns are viewer, page, note, x, y, w, h and created_at; identities and note text are escaped against spreadsheet formula injection. See CSV export for the other exports.

## Rate limits and webhooks

Each reader is limited to 300 annotations per document in any rolling hour. Further saves are refused until earlier annotations fall outside the one-hour window.

A reader's first annotation on a document also fires the proofing.updated webhook event, shared with page marks —once per reader per document, whichever proofing action came first.

## Availability and setup

Annotations are Pro only and are enabled per document, with the "Annotations" toggle (annotationsEnabled) in the Proofing settings on the Configure & Share page. Once enabled, an Annotate button appears over the page in the viewer.

Turning the toggle off stops the button being served and deletes nothing. The same is true of a downgrade: annotations are served only while the owner still holds Pro, so on a downgrade readers stop seeing the control and no new annotations are accepted, while existing ones are preserved and return if you go back to Pro.

## Reading annotations from the API

GET /api/v1/files/{uuid}/annotations returns every annotation on the document grouped by page, each with the marked region, the reader's note and when it was left. Add ?format=csv for a flat export. Pro-only, owner-only, scope readership:read.

As with page marks, the proofing.updated webhook fires only once per viewer and carries no content, so automations trigger on it and then pull. The endpoint is available as the Get Annotations search in Zapier, Get Annotations in Make, File → Get Annotations in n8n, and via includeProofing on the MCP server 's everypage_get_readership tool.

Annotation identities are personal data: a reviewer who came through an email invite is identified by their email address.

Learn more about Pro features and plan limits on the plans and limits page.

---
URL: https://everypage.co/docs/library/file-library
Title: Your document library | EveryPage Docs
Description: Organize and monitor your PDFs from your library—the main screen where you see every document you've uploaded.

# Your document library

Organize and monitor your PDFs from your library—the main screen where you see every document you've uploaded.

Your library is the main dashboard where you upload, organize, and track your documents. It shows a list of every PDF you own, with key metrics and actions at a glance.

## Document list

Your documents appear in a table with the following columns:

- Document — the original filename, plus status indicators. A "Burned" badge appears when the document's view limit has been reached and the file is no longer accessible, and a "X of Y views used" line appears when a view limit is set
- Size — the file size
- Filed — when the document was uploaded
- Reads — the number of reading sessions recorded for the document
- Readers — the number of unique readers who have accessed it
- DLs — downloads. This count includes your own downloads of the document

On narrow screens the table collapses: size, upload date and reads move under the filename, and the remaining columns are hidden.

Next to each row are action buttons:

- Settings icon — configure and share the document
- Analytics icon — view detailed readership data
- Eye icon — preview the PDF
- Download icon — toggle whether viewers can download it. When disabled, the icon turns red
- Trash icon — delete the document

## Activity overview

Above the document list are three cards showing your entire library's activity:

- Total Reads — the sum of all reading sessions across all documents
- Unique Readers — the total number of distinct readers who have opened any of your documents
- Downloads — the total downloads across all documents

Below the list, a "Recent activity" table shows the most recent reading sessions across the library, with the document, reader, source, location, time spent and date. Selecting a folder re-scopes all of this to that folder's documents.

## View limits and self-destructing documents

A document's row shows progress toward its view limit (if set). The display reads "X of Y views used." When the limit is reached, the document burns—it becomes inaccessible to new viewers, and a "Burned" badge marks it in the list. The document's row and its readership data survive; only the link itself dies. A burned document can be brought back by replacing its content — see Dynamic links.

## Bulk operations

Select multiple documents by checking their checkboxes. A sticky bar appears with bulk actions:

- Clear — deselect all
- Move to folder — file the selected documents into a folder, or into "Unfiled" (Basic and above)
- Move to trash — send all selected documents to the trash. On a free account the button reads Delete and the deletion is permanent

On the Trash tab the same bar offers Restore and Delete forever instead.

For more details, see Bulk operations.

## Organizing with folders

On Basic and Pro accounts, a folder rail appears above the document list once you have at least one document. Folders let you group documents for easier navigation. Click a folder chip to show only its documents, or drag a document row onto a chip to file it there. An "All" chip shows everything and an "Unfiled" chip shows documents not assigned to any folder.

To create a folder, click "+ New folder" at the end of the rail. To rename or delete a folder, select its chip first — Rename and Delete links then appear beside the rail.

For more details, see Organizing with folders.

## Active document limits

Your plan determines how many documents you can keep at once: 3 on Free, 100 on Basic, unlimited on Pro. See Plans and limits. The cap is enforced on upload, on claiming an anonymous upload, and on restoring from trash — if you are at your limit you must delete a document or upgrade first. Trashed and burned documents do not occupy a slot.

## Trash and recovery

On Basic and Pro accounts, a "Trash" tab appears next to "My PDFs." Deleted documents move there first instead of being permanently removed. You can restore them within the window your plan allows (7 days for Basic, 30 days for Pro). Free accounts have no trash: a delete is immediate and permanent.

For more details, see Trash and recovery.

## Who sees documents here

Only documents you own appear in your library. If you upload a PDF without signing in, it creates an unclaimed anonymous document—it remains shareable by link, but does not appear in a library because it has no owner yet. Claiming the document (by signing up or logging in from the same browser session) moves it into your library and unlocks owner features like settings, analytics, and folders.

For more details, see Anonymous uploads and claiming.

---
URL: https://everypage.co/docs/library/folders
Title: Folders | EveryPage Docs
Description: Organize documents into flat categories for scoped analytics and easier navigation.

# Folders

Organize documents into flat categories for scoped analytics and easier navigation.

Folders help you organize documents into categories within your library. Grouping related documents makes navigation easier and enables folder-level analytics reporting. Folders come with the Basic plan; the PDF folders feature page summarizes what they add if you are deciding whether to upgrade.

## Structure

Your library uses a flat folder structure—every document lives at the top level, optionally filed into exactly one folder. There is no nesting: a document cannot appear in multiple folders or in a subfolder.

## Owner-scoped organization

Folders are owner-scoped: you see only your own folders. Another user's folders do not appear in your library, and you cannot file a document into another user's folder.

## Creating and managing folders

The folder rail above your document list displays all your folders with live file counts, alongside an "All" chip and an "Unfiled" chip. To create a folder, click "+ New folder" and enter a name (1 to 100 characters, after leading and trailing whitespace is trimmed). The folder is created immediately and appended to the end of your list.

Select a folder chip to rename or delete it: Rename and Delete links appear beside the rail for the selected folder.

File a document into a folder by dragging its row onto the folder chip. Dragging a document onto the Unfiled chip removes it from any folder. You can also file documents in bulk using the "Move to folder" dropdown in the multi-select bar.

## Deleting a folder

When you delete a folder, its documents move to Unfiled—they are not deleted. This preserves your documents and their full analytics history while removing the organizational grouping. The deletion is permanent, but your documents survive it.

## Analytics by folder

When you select a folder, your portfolio summary cards (total reads, unique readers, downloads) update to show data for just that folder's documents, as do the per-document rows and the recent activity table.

Folder scoping applies to the library-wide portfolio view only. Read-through funnels, viewer breakdowns, per-page stats and CSV export are per-document reports, and are not scoped by folder.

For details on portfolio reporting and analytics, see Portfolio Overview.

## Bulk operations

You can move multiple documents to a folder in a single action. Select the documents you want to move, then choose the target folder from the "Move to folder" dropdown in the selection bar.

For more on bulk document operations, see Bulk Operations.

## Availability

Folders are available on the Basic plan and above. Every folder operation is gated the same way — listing, creating, renaming, deleting, and assigning a document to a folder (individually or in bulk) all require Basic or Pro. Free accounts can view and manage their full library without folder organization.

---
URL: https://everypage.co/docs/library/trash-and-recovery
Title: Trash and recovery | EveryPage Docs
Description: How deleted documents move to trash and how to restore or permanently delete them.

# Trash and recovery

How deleted documents move to trash and how to restore or permanently delete them.

When you delete a document from your library, what happens depends on your plan. EveryPage keeps deleted files in a recoverable trash for Basic and Pro accounts, but the free plan removes them immediately and permanently.

## Deleting a document

When you delete a document from your library, you remove it from active use. Deleted documents no longer appear in your file list and are inaccessible to viewers — any share link or embed returns a 404 immediately, even though the file still exists in your account's trash. This exclusion is applied in the lookup that resolves a share URL, so it holds for every identifier form: the UUID, the short ID, a vanity slug on a custom domain, and any per-recipient link variant pointing at the document.

The delete action is available as a single operation or as part of a bulk operation.

## Trash on free accounts

Free-tier accounts have no trash. Deleting a file removes it immediately and permanently — the encrypted blob, any branding assets, the database row, and the document's readership records all go at once. You cannot recover deleted files on a free plan. If you accidentally delete something important, you must re-upload the document, which produces a new link with no history.

## Trash on Basic and Pro accounts

Basic and Pro accounts retain deleted files in trash for a limited time, allowing you to restore or permanently delete them:

- Basic: Trashed files are kept for 7 days
- Pro: Trashed files are kept for 30 days

After this window expires, the file is hard-deleted automatically by the system. You can view your trash on the Trash tab of your library, which lists each file's original name, when it was deleted, and the date it stops being restorable.

The window is measured against your plan at the time you look, not the plan you were on when you deleted. Upgrading from Basic to Pro extends the deadline on documents already in the trash; downgrading shortens it.

## Restoring a document

To restore a trashed document to your active library:

1. Go to Trash in your library
2. Find the document you want to restore
3. Click Restore

When you restore a document, two things happen:

Active-file limit: Your plan has a maximum number of active documents (3 on Free, 100 on Basic, unlimited on Pro). A trashed document does not occupy a slot, so restoring one is treated like a new upload: it fails with a 409 if it would push you over the cap. If you reach the limit, delete another file first or upgrade your plan.

Expiry: Restoring keeps the document's stored expiry as it stands. There is no per-plan expiry cap, so a document set never to expire comes back that way whatever plan you restore it on.

An expiry that lapsed while the document sat in the trash is handled separately, because the expiry sweep skips trashed rows and would otherwise destroy the document moments after you restored it. A lapsed expiry is cleared entirely, so the restored document never expires until you set a new one. For details on how expiry works, see Expiry and retention.

You can restore multiple documents at once using bulk operations.

## Emptying trash

To permanently delete all files in your trash at once:

1. Go to Trash
2. Click Empty Trash

This deletes trashed files irreversibly — the blobs, the rows, and their readership records. They cannot be recovered afterwards.

One request purges at most 500 documents, so a very large trash is emptied over several passes; the interface repeats the call for you and tells you if any documents are still left. You can also permanently delete individual files from the trash without emptying it entirely. Permanent deletion is included in bulk operations.

## Related topics

- Bulk operations — Delete, restore, or move multiple files at once
- Expiry and retention — How document expiry works across plans
- Your library — Organize and manage your documents
- Plans and limits — Understand your plan's limits

---
URL: https://everypage.co/docs/library/bulk-operations
Title: Bulk operations | EveryPage Docs
Description: Act on multiple documents at once instead of changing them one by one.

# Bulk operations

Act on multiple documents at once instead of changing them one by one.

Bulk operations let you apply the same action to multiple documents in your library in a single request. Instead of deleting, restoring, or moving documents one at a time, select a batch and apply the action to all of them together.

## Selecting documents

Every document row in your library and trash carries a checkbox. Tick the checkbox for each document you want to act on. A sticky selection bar appears above the list showing how many documents are selected, with options to Clear the selection or operate on it.

You can also select all visible documents at once using the checkbox in the column header (on desktop). The selection applies only to documents on the current tab—your active library or your trash—and respects any active folder filter. Switching tabs or changing the folder filter clears the selection, and only documents currently rendered on screen are ever submitted.

## Available operations

The operations you can perform depend on which tab you are on.

In your active library:

- Delete — Move documents to trash (Basic and Pro) or permanently delete them (free). Basic accounts' trashed files are kept for 7 days; Pro accounts keep them for 30 days. Free accounts have no trash, and deletion is permanent. Deleting a document that is already in the trash succeeds as a no-op rather than reporting an error.
- Move to folder — File multiple documents into a single folder, or use "Unfiled" to remove them from any folder. This operation requires the Basic plan; the others do not.

In your trash:

- Restore — Return trashed documents to your active library. Restoring counts toward your plan's active-file limit and may fail per document if the limit is reached. Each restored document keeps its stored expiry (a lapsed one is cleared), exactly as a single restore does — see Trash and recovery.
- Delete forever — Permanently and irreversibly delete documents from trash, along with their readership records.
- Empty trash — Permanently delete everything in the trash (also available as a button above the trash list). One request purges at most 500 documents; the interface repeats the call until the trash is empty and tells you if anything is left over.

## Limits and how they work

You can include up to 100 documents in a single bulk request; a larger list is rejected. If you select more than 100 documents, the interface automatically breaks them into chunks of 100 and sends them in sequence, so the cap is invisible in normal use.

Bulk requests are rate limited to 10 per minute per IP address. All four bulk endpoints — delete, restore, move to folder, and empty trash — draw on the same allowance. Because the interface chunks at 100 documents per request, a single selection larger than about 1,000 documents can exhaust the allowance mid-run: the chunks that already landed took effect, and every document after the cut-off is reported as failed with reason "failed". The lists are re-read from the server afterwards so what you see is accurate; wait a minute and repeat for the remainder.

## Per-item results

A bulk operation never fails as a whole because one document in it failed. The response reports each document individually as either done or failed, and every failure carries a reason.

When every document succeeds, the operation completes silently and the list updates. When some fail, a message appears counting the successes and grouping the failures by reason — for example, "Restored 4 of 6 — 2 would exceed your plan's PDF limit — delete a file or upgrade first."

The reasons are:

- Couldn't be found — The document does not exist, belongs to another user, or is in the wrong state for the operation (for example, moving a trashed document to a folder, or restoring a document that is not in the trash).
- Would exceed your plan's PDF limit — The operation would push you over your plan's active-file cap. This occurs during restore when your account is full. Delete another file or upgrade your plan to proceed. The cap is evaluated against live account state at the moment each document is written, not against a snapshot taken when the batch started, so a batch cannot slip an account past its limit.
- Failed — Processing that document did not complete. Try again; if the problem persists, contact support.

Ownership failures deliberately report as "couldn't be found" rather than "permission denied," matching the single-document endpoints. A bulk response therefore cannot be used to discover which document IDs exist outside your own account.

Bulk endpoints accept a document's UUID or its short ID, and echo back whichever identifier you sent. Naming the same document twice — once by each form — processes it once.

## Recovery

If an operation partially succeeds, the documents that were processed have been processed — there is no rollback. The interface refreshes your library, trash and folder counts after the operation, so the lists reflect what actually happened; re-select whatever is still there and try again.

## Related topics

- Trash and recovery — Understand how deleted documents are retained and restored
- Folders — Organize documents into categories
- Your library — Manage and navigate your documents
- Plans and limits — Understand your plan's limits and features

---
URL: https://everypage.co/docs/library/dynamic-links
Title: Dynamic links (replacing content) | EveryPage Docs
Description: Swap the document behind an existing share link without changing the link, and use it to restore burned documents.

# Dynamic links (replacing content)

Swap the document behind an existing share link without changing the link, and use it to restore burned documents.

Dynamic links let you replace a document's content in place—upload a new PDF to an existing link without changing the link itself. The UUID, short ID, vanity slug, QR code, embed code, all settings, and your complete readership history survive the swap. What changes is the document itself, and by default the decorations anchored to its pages.

This is useful when you need to update a shared link with a newer version of a document, correct an error, or restore a burned link to active status.

## What survives a content replacement

When you replace a document's content, everything about the link persists:

- Identifiers: UUID, short ID, vanity slug (if set), and any link variants
- Sharing artifacts: QR codes and embed code snippets remain valid; no need to re-distribute them
- Settings: Password protection, expiry date, view limits, page ranges, watermarks, and all other document settings stay in place
- Readership data: Viewer sessions, captured emails, page-level statistics and every other readership record survive unchanged
- Link history: The document maintains a revision history recording each superseded version

Three things do change besides the bytes. The filename and file size become those of the new document. The page count is recalculated. And the counter behind the view limit resets to zero — the limit itself is kept, so it applies afresh to the new document. Page-anchored decorations are the fourth, and they are described below.

This makes content replacement ideal for published documents—a printed QR code or an embed already deployed on another site continues to work after you swap the content.

## How to replace content

Open any document in your library and go to the sharing panel. In the "Replace File" section, choose a new PDF (or Word/PowerPoint document if Office conversion is enabled). If the current document has page-anchored hotspots or comments, you are prompted to decide whether to keep or clear them. Confirm the replacement, and the new document is uploaded and served immediately from the same link.

## Page-anchored decorations and the clearAnchors option

By default, content replacement clears page-anchored hotspots and comments because the new document may have a different number of pages or layout. These decorations are anchored to specific page numbers, which may no longer make sense with new content.

The behaviour is controlled by a clearAnchors query parameter on the replacement endpoint. It defaults to true; passing clearAnchors=false (or clearAnchors=0) keeps the anchored decorations. In the interface, the choice appears as a prompt — but only when the current document actually has hotspots or page comments to strand. With none, replacement proceeds straight away.

Document-level notes (comments not tied to a specific page) always survive a replacement, regardless of this setting.

Keeping anchors is intended for a minor update — a corrected version of the same document with the same pagination — such as fixing a typo or refreshing a graphic. Note that keeping them keeps all of them: no filtering is applied to the new page count, so an anchor pointing past the end of a shorter replacement document is retained and will simply never be reachable.

## Revision history

Every time you replace a document's content, a revision record is written for the version being superseded. It records that version's number, filename, file size and page count, together with the time the replacement happened. The sharing panel lists this history newest first, and a version badge (v2, v3, …) appears beside "Replace File" once a document has been replaced at least once.

The revision record describes the document, not who read it. Readership records are not partitioned by content version, so the history tells you what each version was, not which version a given reader saw.

## Restoring burned documents

If a document reaches its view limit and burns—becoming inaccessible to new viewers—you can restore it to active status by replacing its content. Upload a new document (or the same one again), and the link returns to life: the burned marker is cleared and the consumed-views counter resets to zero, so the existing view limit starts over. The UUID and all readership records survive.

Content replacement accepts burned documents on purpose — it is the un-burn path, and every other write to a burned document is refused with a 410.

Expired documents are the deliberate asymmetry: replacement refuses them with a 410, both before the upload begins and again immediately before the swap is committed. An expired link has reached its time-based deadline and is queued for deletion, so it cannot be revived; create a new link instead.

## Availability and permissions

Content replacement is a Pro feature available to document owners only. Anonymous uploads cannot use it: the manage tokens issued alongside an anonymous or Canva upload act as a free-tier caller, so the Pro gate refuses them. Claim the document into a Pro account first.

API keys and OAuth tokens holding the files:write scope can call the endpoint on behalf of a Pro owner, at /api/v1/files/{uuid}/content. The uploaded document is bounded by the owner's plan size cap, and PDF, Word and PowerPoint files are all accepted where Office conversion is available — the same rules as a normal upload.

## Webhook events

When you replace a document's content, EveryPage emits a content.replaced webhook event if you have webhooks configured. Its data carries the new content version alongside the document's UUID and filename. The API response itself is more detailed: it also returns the new size, whether anchors were cleared, and how many hotspots and notes were removed.

For details on subscribing to webhook events, see Webhooks.

## Related features

- QR codes — QR codes survive content replacement without re-generation
- Embedding a document — embed code remains valid after content replacement
- Interactive hotspots — page-anchored regions and the clearAnchors option
- Self-destructing links — set view limits and un-burn links through content replacement
- Webhooks — receive content.replaced events
- Plans and limits — Pro tier features

---
URL: https://everypage.co/docs/distribution/email-invites
Title: Email invites | EveryPage Docs
Description: Send tracked email invites to named recipients with per-recipient links that attribute opens and satisfy the email gate.

# Email invites

Send tracked email invites to named recipients with per-recipient links that attribute opens and satisfy the email gate.

Email invites let you send a document to specific people while tracking exactly who opened it. Each recipient receives their own tracked link with a unique token, so views are attributed to them by name in your readership analytics.

## How invites work

When you send an invite, the system creates a unique, unguessable link for each recipient. That link carries a per-recipient token (?i=<token>) which serves three purposes: it attributes the view session to that person, it satisfies the email gate server-side so nothing the recipient types is validated or captured, and it supplies their identity for watermarking — the invitee's email is stamped onto watermarked pages, taking precedence over any email captured by the gate.

Each recipient gets their own invite record with a token generated from 192 bits of cryptographic randomness. The tracked link is built from your file's durable short identifier (never the custom-domain slug, which can be renamed or removed) plus the recipient's token and an email attribution source parameter.

Emails are dispatched asynchronously from the request, so invite rows are created synchronously first (and count toward your daily cap immediately). The system throttles outbound sends to respect email rate limits.

## Tiers and limits

Invite sending requires the basic plan or higher. Free-tier users cannot send invites at all.

### Basic plan

You can send up to 10 direct email addresses per send request. Distribution lists require Pro, so on basic you enter addresses directly. Your plan has a daily cap of 50 invites across all your files. The daily cap is per-user and resets at UTC midnight.

If you send multiple emails in a single request and any of them fail validation (malformed address, or a duplicate of another address in the same send), those addresses are silently skipped and do not count toward the per-request limit or the daily cap.

### Pro plan

You can send invites directly, with no per-request limit, or use a distribution list — a saved contact list that you manage separately. When sending via a list, you send to everyone in that list at once. Either way, only the daily cap applies.

Your plan has a daily cap of 1000 invites across all your files. The daily cap is per-user and resets at UTC midnight.

## Exceeding the cap

If a send request would push you over your daily cap, the entire request is rejected with an HTTP 429 (Too Many Requests) response. The response body includes your daily ceiling and how many invites you have already sent today, so you can plan your next send. Try again after midnight UTC, or consider upgrading your plan for a higher daily allowance.

## The invite.viewed webhook

The first time an invitee opens their tracked link, EveryPage emits an invite.viewed webhook event to your subscribed endpoints. The payload carries the document's fileUuid and fileName plus the invitee's email and name.

It fires once per invite — the first open only, not on subsequent visits — and never for a view by the document's own owner. Because the token satisfies the gate server-side, no gate response is recorded, so an invited open emits invite.viewed rather than gate.completed.

Note a current rough edge: on a document with an email gate, the viewer still renders the gate form to an invited recipient even though their token has already satisfied it server-side. Whatever they type is neither validated nor captured, and the token — not the typed address — remains the identity used for attribution and watermarking.

## Invites vs. share-by-email

Email invites and share-by-email are two different ways to distribute your document:

- Email invites create a tracked link unique to each recipient. The recipient's identity is carried in the URL token, views are attributed by name, and the token satisfies the email gate on their behalf.
- Share-by-email sends the ordinary share link to one recipient at a time, with an optional note. The recipient is not identified; they receive the same link anyone with the URL can access. If your document has an email gate or a password, they must still pass it to open the document.

Use email invites when you want to know exactly who opened your document and attribute views to individuals. Use share-by-email to quietly notify someone of a shared document without per-recipient tracking.

## Related

- Contact lists — save and reuse distribution lists for bulk invites
- Email gates and lead capture — how invites interact with email verification
- Watermarking — how invite tokens supply recipient identity for watermarks
- Webhooks — subscribing to invite.viewed and the other event kinds
- Reader identities — how invites appear in your readership analytics
- Plans and limits — overview of tier features and caps

---
URL: https://everypage.co/docs/distribution/contact-lists
Title: Contact lists | EveryPage Docs
Description: Save and reuse distribution lists for sending tracked email invites in bulk.

# Contact lists

Save and reuse distribution lists for sending tracked email invites in bulk.

Contact lists are saved distribution sets that you can send tracked email invites to in bulk. Each list is owned by you and can be reused across multiple documents, letting you build and maintain distributions without re-entering addresses every time.

## Creating and managing lists

Create a new list in your account settings by entering a name (up to 100 characters) and clicking "New list". Once created, you can add members individually or import them from a CSV file.

To add a member manually, provide an email address (required) and an optional name. Names are capped at 120 characters and help you identify people in your readership analytics.

## Bulk import via CSV

To import many members at once, prepare a CSV file and click "Import CSV". The system reads two columns:

- Column 1 (required): Email address. The system validates each address and skips malformed or empty rows without counting them against your cap.
- Column 2 (optional): Contact name. If provided, it is trimmed and truncated to 120 characters.

Two caps bound each import:

- File size: 1 MB maximum
- Members per import: 1,000 maximum

Both are ceilings rather than hard failures — an oversized file or a run of more than 1,000 valid addresses stops the import at the limit and reports what was added, so split larger sets across several files.

Within a single import, the system automatically deduplicates addresses. If the same email appears twice in your CSV, only the first row is added. Addresses already on the list are not added again. The import reports two totals — how many members were added and how many rows were skipped — and both intra-file duplicates and addresses already on the list land in the skipped count.

Header rows and blank rows fail email validation, so they are skipped without counting toward your cap.

## Access levels by plan

Contact list access follows an asymmetric model designed to let downgraded accounts clean up their data. The operations that grow a list are Pro-only; the ones that read or shrink it are not.

Pro only:

- Create a new list
- Add a member
- Import members from CSV

Any plan (Free, Basic, or Pro):

- List your saved lists and view their members
- Remove a member from a list
- Delete a list and all its members

If you downgrade from Pro, your lists are not deleted and you can still read them and remove members or whole lists. You cannot create new lists or add members until you are back on Pro. Note that the Contact lists panel in account settings is only rendered for Pro accounts — on a lower plan these read and cleanup operations remain available through the API.

## Sending invites to a list

Lists exist to streamline bulk email invites. On the Configure & Share screen, when you open the invite panel, you can choose to send to a specific list instead of typing individual addresses. Sending to a list is a Pro feature and counts toward your daily invite cap (1,000 invites per day for Pro; see Plans and limits for detailed tier breakdowns).

Each recipient in your list receives their own unique tracked link. Views are attributed to them in your readership analytics, and opening the tracked link satisfies the email gate so they are never asked for their address.

## Related

- Email invites — send tracked links to named recipients
- Account settings — where the Contact lists panel lives
- Plans and limits — overview of per-tier caps and features

---
URL: https://everypage.co/docs/conversion/word-to-pdf
Title: Word to PDF | EveryPage Docs
Description: Upload a Word document and receive a tracked, shareable PDF link in seconds—no manual conversion needed.

# Word to PDF

Upload a Word document and receive a tracked, shareable PDF link in seconds—no manual conversion needed.

EveryPage accepts Word documents (.docx) and converts them to PDF in flight, storing the result as a fully-featured PDF so every tracking, sharing, and reader interaction feature works identically to a native upload. You get a shareable link immediately—no desktop software required.

## How Word conversion works

When you upload a .docx file, EveryPage checks that it carries the Zip container signature every OOXML document has, streams it to a LibreOffice conversion service, and stores the resulting PDF. From that point on, the document behaves exactly like any other PDF: you can share it with a tracked link, watermark it, add hotspots, capture lead data, or enable commenting, depending on your plan.

Conversion is available to all EveryPage users on every plan, including the free tier. Your document is converted once, during the upload request, and the share link is returned in the upload response.

## File size and format requirements

Your Word document must be a .docx file (the modern OOXML Word format, standard since Microsoft Office 2007). Legacy .doc files (pre-2007 binary format) are not accepted —save your document as .docx and upload again. PowerPoint is the exception to this rule: legacy .ppt files are accepted. See PowerPoint to PDF.

Two separate caps apply:

- The source cap: 25MB. This is the limit on the .docx you upload, and it is the same on every plan.
- Your plan's per-file upload cap. This applies to the whole upload request and to the converted PDF that gets stored. On the free plan it is 20MB, so a free-plan Word upload is effectively limited to 20MB—the plan cap is reached before the 25MB source cap. See plans and limits for your tier's figure.

If your document exceeds whichever cap applies to you, export it as a PDF from Word and upload the PDF directly instead.

## Conversion fidelity

LibreOffice handles the conversion, so complex layouts, embedded graphics, embedded fonts, tracked changes, and other advanced Word features may render differently in the resulting PDF than they appear in Microsoft Word. The document is readable and usable, but visual fidelity is not guaranteed pixel-for-pixel.

Before sharing a document publicly, download the PDF and check that it looks correct. If the conversion does not meet your needs, export the document as a PDF from Word and upload that instead—you have direct control over how Word renders it.

## Availability

Conversion depends on the document conversion service being reachable. When it is not configured, uploads are PDF-only and the upload screen does not advertise Word or PowerPoint support—a .docx is rejected with "Only PDF files are allowed". When it is configured but temporarily unreachable or overloaded, the upload fails with "Document conversion is temporarily unavailable"; your document is fine and the same upload will work once the service recovers.

GET /api/upload/options reports the current state as convertEnabled, along with the source caps for Word (docxMaxBytes) and PowerPoint (pptMaxBytes).

## Next steps

Once your document is converted and stored, you can:

- Share the tracked link with readers and monitor who opened it.
- Set a custom viewer mode (Flipbook, Magazine, or another style).
- Add password protection or an email gate.
- Enable a watermark with the reader's email.
- Add interactive hotspots (Pro).

See also: PowerPoint to PDF

---
URL: https://everypage.co/docs/conversion/powerpoint-to-pdf
Title: PowerPoint to PDF | EveryPage Docs
Description: Convert and share your PowerPoint presentations as tracked PDFs.

# PowerPoint to PDF

Convert and share your PowerPoint presentations as tracked PDFs.

EveryPage accepts PowerPoint files (.pptx and .ppt) and converts them to PDF in flight. The converted file is stored as a PDF, so all downstream features—viewer modes, analytics, watermarking, and sharing controls—work identically to a native PDF upload.

## Supported formats

Both modern (.pptx) and legacy (.ppt) PowerPoint files are accepted. This differs from Word support, which accepts only .docx files: the legacy .ppt format is included because LibreOffice's .ppt import filter is mature and older presentations remain common. Files are validated by their internal container signature—Zip (OOXML) for .pptx and OLE2 for .ppt—before conversion proceeds.

## File size limit

PowerPoint source files are capped at 50 MB. This limit applies only to the original presentation; the converted PDF may be smaller or larger depending on content.

That cap is separate from your plan's per-file upload cap, which applies to the whole upload request and to the converted PDF that gets stored. On the free plan the per-file cap is 20 MB, so it is reached well before the 50 MB source cap. See plans and limits for your tier's figure.

If your deck exceeds whichever cap applies to you, export it to PDF yourself and upload that instead.

## Conversion process

Your presentation is converted to PDF by LibreOffice, running as a service alongside EveryPage. Conversion happens synchronously, inside the upload request: the deck streams to the converter, the returned PDF is encrypted and stored, and the upload response carries the share link. Large decks therefore make the upload request take longer, and the converter allows up to 60 seconds for one conversion.

## Slides to pages

LibreOffice's default PDF export renders one slide per page, so each slide in your presentation becomes one page in the final PDF. This maps naturally to EveryPage's swipe and flipbook viewer modes, which let your viewers navigate page-by-page. See the viewer modes guide for details on how your audience can interact with your deck.

## Fidelity notes

LibreOffice renders the presentation, so animations and slide transitions are lost. Complex layouts, embedded media, or unusual fonts may not render exactly as they appear in PowerPoint—LibreOffice may substitute fonts or adjust spacing. If precise visual fidelity is critical, export your deck to PDF in PowerPoint and upload the result instead. The PDF-to-PDF path preserves all formatting without LibreOffice rendering.

## Availability

PowerPoint conversion is available on all plans, including the free tier, and requires no account. It depends on the document conversion service being reachable: when it is not configured, uploads are PDF-only and a .pptx is rejected with "Only PDF files are allowed"; when it is configured but temporarily unreachable or overloaded, the upload fails with "Document conversion is temporarily unavailable" and the same deck will upload once the service recovers. The generated PDF is then subject to your plan's ordinary file size and active-file limits. See plans and limits for your tier's restrictions.

## Tracking and sharing

Once converted, your deck behaves as a full EveryPage document. The upload response carries the share link, and every readership and access feature applies exactly as it does to a PDF you uploaded directly—including the plan gating: view counts and summary readership on every tier, page-by-page stats and audience breakdowns from Basic, reader identities and the email capture gate on Pro, and webhooks on all tiers. Readers see the EveryPage viewer with your chosen viewer mode enabled.

## Next steps

- Upload your first PDF covers the general file upload flow
- Viewer modes explains how readers interact with your pages
- Word to PDF describes Word document conversion, which follows the same process

---
URL: https://everypage.co/docs/conversion/docsend-to-pdf
Title: DocSend to PDF | EveryPage Docs
Description: Convert a DocSend document you have been given access to into a shareable PDF.

# DocSend to PDF

Convert a DocSend document you have been given access to into a shareable PDF.

This tool converts a DocSend document you already have access to into a PDF you can host, embed, and share through EveryPage. You supply the link and any credentials the sender provided (email address or passcode), and the converter returns a ready-to-use PDF. You can run it without an account at the DocSend to PDF converter page.

## How it works

You paste a DocSend link, and if the document is gated, you enter the email address or passcode the sender gave you—nothing more. The link must be a single-document view link (docsend.com/view/…); Spaces links (docsend.com/s/…) are rejected as unsupported.

Everything after that runs on EveryPage's servers. The converter:

1. Opens the DocSend viewer page to detect whether it is gated
2. Submits your credentials if required, establishing a session with access to the document
3. Fetches each page image from DocSend's CDN
4. Decodes the images (handling JPEG, PNG, WebP, GIF, and TIFF formats)
5. Assembles them into a single PDF using pdfcpu

One conversion has a 4-minute budget. If the work is not finished by then, the request times out and you can retry.

## What you can convert

Any single DocSend document link you have permission to view converts. This includes:

- Public decks — no credentials required, any visitor can convert the same link
- Gated decks — you supply the email address and/or passcode the sender gave you, and those exact credentials authorize the conversion
- Decks up to 300 pages — the page count is checked before any page is downloaded, and a longer deck is refused there
- Decks up to roughly 20 MB — the budget is measured on the page images as they are assembled into the PDF, not on the compressed bytes DocSend sends, so a deck of WebP pages can exceed it once re-encoded. The assembled PDF is re-checked against the same limit before it is stored
- Pages up to 10 MB each — a single oversized page image fails the conversion with its own message, separately from the deck budget

The tool does not circumvent access controls. It converts a document you have already been given access to, using the credentials the sender gave you. Nothing here guesses or brute-forces a gate: the converter only submits credentials you type in, and a credential DocSend rejects is reported back to you as rejected. If you do not have those credentials, the conversion fails rather than attempting to get around the gate.

## The PDF you get

The output is a standard PDF—one image per page, in the order they appear on DocSend. Images are embedded directly for JPEG and PNG; WebP and other formats are decoded and re-encoded as JPEG at quality 85 for legibility at screen size.

Once created, your PDF is treated like any other EveryPage upload: you can download it, share it with a link, configure passwords and expiry, track who views it, and add a watermark. If you were signed in during the conversion, the PDF belongs to your account, is encrypted with your key, counts toward your plan's active-file limit, and appears in your library.

If you converted anonymously, the PDF is shareable by link and kept for 7 days while unclaimed. Signing up or logging in from the same browser claims it into your account, and the result screen also offers a claim link that works from any browser.

## Rate limits

The converter accepts 10 requests per minute from one IP address; past that you are rate-limited and told to wait a minute. Note that a gated deck costs more than one request—the first submission detects the gate, and the one carrying your email or passcode is a second request.

The server also runs at most 4 conversions at once. Requests beyond that queue rather than fail, and only give up if no slot frees before the 4-minute deadline, at which point you are told the converter is busy and to try again.

## Limitations

- Single documents only — DocSend Spaces (multi-document bundles) are not supported
- Page images only — the conversion captures what renders as page images in the viewer, not any embedded videos or interactive elements
- Image format dependent — document quality depends on how DocSend renders the pages; highly stylized or media-heavy documents may have lower fidelity than the original
- No searchable text — the output is image-based, not OCR'd, so text is not selectable or searchable

## Next steps

Once your PDF is created, see Upload your first PDF for how to configure sharing settings and What is EveryPage for an overview of the platform.

---
URL: https://everypage.co/docs/integrations/zapier
Title: Zapier | EveryPage Docs
Description: Connect EveryPage to Zapier to automate document uploads, manage sharing settings, and respond to reader activity.

# Zapier

Connect EveryPage to Zapier to automate document uploads, manage sharing settings, and respond to reader activity.

The EveryPage Zapier app uploads documents, updates sharing settings, starts Zaps from reader activity, and pulls readership summaries.

## Access

The app is usable but not listed in the Zapier App Directory — searching Zapier for "EveryPage" will not find it. Access is by invite link: sign in to EveryPage, open your Account page, and use the Zapier early-access link in the banner above your API keys. Opening that link adds the app to your Zapier account.

## Authentication

To connect your EveryPage account to Zapier, you need an API key. API keys are master credentials—treat them like a password.

1. Sign in to your EveryPage account and go to Account.
2. Under API keys, create a new key (or copy an existing one).
3. In Zapier, when setting up an EveryPage action or trigger, paste this key into the API Key field.
4. Zapier tests the key against your current-user endpoint to confirm it works.

For more details on API keys, see the API keys guide.

## Triggers

Triggers fire when a specified event happens to one of your documents. Each trigger can optionally filter to a single document or watch all your documents.

| Trigger | Type | Description | Availability |
|---|---|---|---|
| New Document Read | Polling | Walks the view events feed; one event per completed read session | Free |
| New Document Read (Instant) | Webhook | Same event delivered instantly — a file.viewed webhook fires when a non-owner read session ends | Free |
| New Download | Webhook | Fires when a reader saves your PDF to disk. Your own downloads as the owner never fire it | Free |
| New Form Fill | Webhook | Fires when a reader completes an email gate or lead-capture form on your document | Pro |
| Link Expired / Self-Destructed | Webhook | Fires when a document link self-destructs after reaching its view limit | Free |
| New Reader Comment | Webhook | Fires when a reader leaves a feedback note on your document | Free |
| Receipt Confirmed | Webhook | Fires when a reader confirms receipt of your document | Free |

The polling trigger (New Document Read) checks for new reads at Zapier's standard interval, walking the events feed with a stored cursor. Webhook triggers fire instantly. EveryPage attempts each delivery up to 5 times (1 minute, 10 minutes, then hourly backoff) before abandoning it; see webhooks for the full retry and auto-disable policy.

Webhook triggers are powered by EveryPage webhooks, which are available on all plans. Only the form-fill trigger carries a plan requirement: your account must be on Pro at the time the event fires—upgrading later does not retroactively fire past events.

Deliveries are signed with X-Everypage-Signature. The Zapier app verifies the signature and rejects mismatches whenever Zapier hands it the raw request bytes; where the raw body is not available it accepts the delivery rather than dropping it.

## Actions

Actions perform work on your behalf—they upload documents, modify settings, or create variants. Unless otherwise noted, actions are available to all plan tiers.

| Action | Description | Pro feature |
|---|---|---|
| Upload PDF & Get Tracking Link | Uploads a PDF to EveryPage and returns a ready-to-share link | — |
| Update File Settings | Modifies an existing document's sharing settings (passcode, expiry, download permission, viewer mode, and more) | Some fields |
| Create Link Variant | Mints a per-recipient tracked link, attributing readership to that recipient | Yes |
| Replace Content | Swaps the PDF behind an existing share link—the link, QR code, settings, and analytics all survive | Yes |
| Delete File | Moves a document to trash (see the note below—the action's own description overstates this) | — |

When you update file settings, you can set only the fields you need to change—omitted settings keep their current value. This is useful for workflows like "when a CRM deal closes, expire the proposal link."

The Zapier app builds its share link, QR code URL, and embed code from the document's UUID rather than its short ID. Both forms resolve to the same document; the Make and n8n apps prefer the short ID. The QR URL is the public, unauthenticated /api/files/{uuid}/qr-code path so downstream apps can render it without an EveryPage key.

### Create Link Variant

Creating link variants is a Pro-only feature. Each variant receives its own short link and optional recipient label, so you can send individual links to each recipient and track them separately. Variants also support optional per-recipient overrides for download permission and page range (allowDownload, pageFrom, pageTo); the overrides object replaces the variant's existing overrides wholesale rather than merging into them.

Zapier offers Create only. Listing, updating, revoking, and deleting variants are not available as Zapier actions—use the Make or n8n apps, the API, or the EveryPage dashboard.

### Replace Content

Content replacement is Pro-only and is the primary way to un-burn a link. When you replace a document's PDF, the share URL, QR code, and all readership history remain intact—only the bytes change. This is useful for workflows like "new version uploaded to Drive → automatically update the shared link without losing the history."

### Delete File

The action's own description in Zapier says it "PERMANENTLY deletes," but it sends a plain DELETE, which the API soft-trashes. On Basic and Pro the document lands in trash and stays restorable (7 days on Basic, 30 on Pro); on Free, which has no trash, the delete is immediate and permanent. There is no purge option on the Zapier action. See trash and recovery.

## Searches

Searches retrieve information about a single document or pull readership data.

| Search | Description |
|---|---|
| Find File | Locates a document by file name (case-insensitive substring match). Returns the document's UUID, short ID, size, page count, viewer mode, and share link. |
| Get Analytics Summary | Fetches a document's readership report: total views, sessions, unique readers, countries, average time spent, downloads, completion rate, and active readers. |
| Get Page Marks | Fetches the pick, reject and maybe verdicts readers left on the document's pages (Pro). Returns document totals, comma-joined page lists you can drop straight into an email or a Notion row, and a per-viewer breakdown as line items. |
| Get Annotations | Fetches the annotations readers drew on the document (Pro), flattened into one list with the page, reader and note for each. |

The analytics summary response includes a tier field naming the plan the report was built at. The API omits sections above your tier, so those fields come back empty: median read time and completion rate need Basic, and active readers, new sessions, and returning sessions need Pro.

Proofing feedback is a pull, not a push: the proofing.updated event fires once per viewer, on their first mark, and carries no verdicts. Trigger on it (or on a new comment) and then read the marks. See page marks and the photo proofing automation guide.

## Important details

### Form fill requires Pro at event time

The "New Form Fill" trigger fires when a reader completes an email gate or lead-capture form. Because the payload carries captured lead data, EveryPage only delivers gate.completed while the account is on Pro at the moment of the event. Rather than let you turn on a Zap that would silently never fire, the app checks your plan when you enable the Zap and refuses with an upgrade prompt if you are below Pro.

## Webhooks and availability

Zapier webhook triggers rely on EveryPage webhooks under the hood. Webhooks are available on all plans and do not require a Pro account—only gate.completed (the New Form Fill trigger) carries a plan requirement. Turning a Zap on registers the webhook subscription; turning it off deletes it.

## Related

- API keys — create and manage your API keys
- Webhooks — how event delivery and retries work
- Events feed — the data structures for views, downloads, and captured leads
- Link variants — creating and managing per-recipient tracked links
- Trash and recovery — how soft delete and permanent purge work
- Plans and limits — tier requirements and API rate limits

---
URL: https://everypage.co/docs/integrations/make
Title: Make | EveryPage Docs
Description: Use the EveryPage app in Make scenarios to upload PDFs, manage share settings, and react to reader events.

# Make

Use the EveryPage app in Make scenarios to upload PDFs, manage share settings, and react to reader events.

The EveryPage Make app provides modules for uploading PDFs, managing share settings and link variants, pulling readership data, and starting scenarios from reader events.

## Access

The app is deployed and usable but not publicly listed in Make's app directory — searching Make for "EveryPage" will not find it. Access is by invite link: sign in to EveryPage, open your Account page, and use the Make early-access link in the banner above your API keys. Opening that link installs the app into your Make organisation, where it becomes available in the module picker.

## Authentication

You need an EveryPage API key to connect. Navigate to Account > API keys on everypage.co and copy an ep_live_ key. Paste it into the Make connection panel; it will be sent as a bearer token on all requests. The connection is validated immediately against the current-user endpoint and labeled with your email and plan tier.

For details on API keys and rotation, see API keys.

## Instant triggers

These webhooks fire in real time when events occur on your documents. EveryPage automatically registers and removes the webhook URL when you add or delete the trigger from your scenario.

| Module | Event | Plan |
|---|---|---|
| Watch reads | file.viewed — a reader finishes a viewing session. Includes pages viewed and time spent. | All plans |
| Watch downloads | file.downloaded — a reader (not you) saves the PDF to disk. | All plans |
| Watch form fills | gate.completed — a viewer completes the email gate or lead form, with the captured fields. | Pro |
| Watch comments | note.created — a reader leaves a comment on a page, with the comment text and the page it was left on. | All plans |

EveryPage webhooks are available on every plan. The only plan requirement is on gate.completed: Watch form fills registers successfully on Free and Basic, but the server never delivers those events, so the trigger never fires. Note also that Make cannot verify delivery signatures — see Webhook signature verification below.

These four are the only instant triggers Make offers. The receipt.confirmed, file.burned, content.replaced, invite.viewed, and proofing.updated kinds are available through the API and the n8n node, but have no Make module yet.

Watch comments only fires for comments a reader can leave publicly. If you switch a document's comments to private, every comment becomes private and no note.created event is emitted at all — by design, so private feedback never leaves the document.

## Polling trigger

Watch events walks the EveryPage event feed (GET /api/v1/events) using an event-ID cursor, not a timestamp: each cycle asks for events with an ID above the highest one already seen. You choose the event type (read, download, or form fill), optionally scope it to one document, and set how many events to process per cycle (default 10; the rest stay queued for the next cycle).

Cursors are per event type, so changing the type re-baselines the trigger — run one scenario per event type rather than switching. Because Make charges per operation, the module's own guidance is a 15-minute schedule.

See Events feed for cursor semantics and payload structure.

## Modules

### File operations

| Module | What it does | Plan |
|---|---|---|
| Upload a file | Multipart PDF upload with optional settings (file name, viewer mode, passcode, expiry or never-expire, protection toggles, view limit, receipt request, email gate and domain allowlist, page range, watermark, vanity slug). Outputs the share link, QR code URL, and embed code. | All plans; individual settings are tiered |
| Update file settings | Modify sharing settings on an existing document. Only the fields you fill in are sent; the rest keep their current values. Re-fetches the document afterwards so the returned links and QR code reflect the live state. | All plans; individual settings are tiered |
| Get a file | Fetch a single document's metadata and sharing settings by UUID or short ID. | All plans |
| List files | List your documents newest first, optionally filtered by file name (case-insensitive substring). The upstream list is unpaginated, so the name filter and limit are applied by Make. | All plans |
| Delete a file | Moves the document to trash by default. Turn on Permanently delete (purge) to destroy it instead — that cannot be undone. | All plans |
| Replace file content | Swap the PDF bytes of an existing document while keeping the link, QR code, settings, and readership history intact. Page-anchored hotspots and notes are cleared by default; keep them only when the new PDF has the same page layout. Re-fetches the document afterwards. | Pro |
| Get a QR code | Fetch the QR code as a PNG (binary data, default file name qr-code.png). | All plans |
| Get a readership summary | Retrieve a document's readership rollup: views, sessions, unique visitors, countries, downloads, time-on-page, and completion. Sections above your plan tier are omitted; the tier output says which tier the report was built at. | All plans |
| Get page marks | Retrieve the pick, reject and maybe verdicts readers left on the document's pages, as per-page tallies, a per-viewer breakdown and totals. | Pro |
| Get annotations | Retrieve the annotations readers drew on the document, grouped by page, with each reader's note. | Pro |

Proofing feedback is a pull, not a push: the proofing.updated event fires once per viewer, on their first mark, and carries no verdicts. Trigger on it (or on a new comment) and then read the marks. See page marks and the photo proofing automation guide.

### Link variants (Pro only)

Variants are per-recipient child links off one document: each gets its own short link and an optional recipient label, so readership attributes to the individual you sent it to. Overrides are limited to download permission and page range — per-variant passcodes and email gates are not supported; those settings live on the parent document and apply to every variant.

| Module | What it does |
|---|---|
| Create a link variant | Mint a per-recipient link, with an optional label and optional allowDownload / page-range overrides. Returns the variant UUID, short ID, and URL. |
| List link variants | Fetch all variants of a document. |
| Update a link variant | Change a variant's label, revoked state, or overrides. Setting any override field replaces the whole overrides object, it never merges — re-state every override you want to keep. |
| Revoke a link variant | Stop a variant's URL from resolving without deleting it. Revoked links return a uniform 404, not a 410 — a revoked recipient must not learn the canonical link exists. Set Revoked to No on Update to reverse it. |
| Delete a link variant | Removes the variant. With GDPR-redact the recipient label turned on it does the opposite: the variant is not removed, its label is erased in place and its readership rows are anonymised. The deleted and redacted outputs say which happened. |

### Event and data operations

| Module | What it does |
|---|---|
| List events | Bulk query one event stream (read, download, or form fill), optionally scoped to a document, with a since event-ID cursor. One run makes one request, capped at the API's 100 events; to go further, feed the highest ID seen back into Since on the next run. Cursors are per event type and never portable between types. Gate event IDs are 64-bit—map them through as text, unmodified. |
| Make an API call | Direct access to any EveryPage API endpoint. Use it for endpoints with no dedicated module. |

## Output contract

Every file-producing module returns three standard fields:

- Share link (shareUrl): https://everypage.co/{shortId} (or UUID if no short ID exists)
- QR code URL (qr_url): https://everypage.co/api/files/{uuid}/qr-code (always UUID-keyed and public)
- Embed code (embed_code): <iframe> snippet for embedding on web pages (uses the /embed/ path)

Upload also returns uuid, shortId, and fileName (the display name you set, or document.pdf if you left it blank). Settings updates and content replacement re-fetch the document afterwards, so the returned links reflect the post-update state.

Share links and embed codes never use a vanity slug. Slugs are renameable and resolve only on a custom domain, so module outputs — which end up in emails, CRM notes, and printed QR codes — always use the short ID or UUID.

## Limitations and notes

### Webhook signature verification

EveryPage signs every webhook delivery with HMAC-SHA256 (X-Everypage-Signature), but the Make app cannot verify that signature. Make's integration language has no cryptographic primitives, and webhook bodies arrive already parsed rather than as raw bytes, so there is nothing to compute an HMAC over. Authenticity therefore rests entirely on the unguessable webhook URL Make generates for each trigger — treat that URL as a secret and do not share or publish it.

The Zapier app and the n8n node do verify signatures; n8n additionally fails closed, rejecting any unverified delivery. If signature verification matters to your threat model, use one of those. See webhooks for the signature specification.

### No import-from-URL module

The API's /files/import endpoint is host-allowlisted, so there is no Make module that imports a PDF straight from a URL. The Make-native pattern is HTTP > Get a file → EveryPage > Upload a file: fetch the bytes with Make's own HTTP module, then map them into the upload module's PDF file field.

### Re-fetching on update

When you update file settings or replace content, Make automatically re-fetches the document to return accurate share URLs and QR codes. This adds a second API call per operation but ensures outputs match the live state.

## Related

- API keys
- Webhooks
- Events feed
- Link variants
- Plans and limits

---
URL: https://everypage.co/docs/integrations/n8n
Title: n8n | EveryPage Docs
Description: Workflow automation for document sharing, tracking, and triggered actions using the n8n community node.

# n8n

Workflow automation for document sharing, tracking, and triggered actions using the n8n community node.

The n8n-nodes-everypage community node brings EveryPage document management and event-driven workflows to n8n. Upload PDFs and generate tracked share links, access readership analytics, and trigger workflows instantly when documents are read, downloaded, or unlock lead gates.

## Install

The package is published on npm and approved by n8n — it is generally available, with no invite or early-access step.

On self-hosted n8n, go to Settings → Community Nodes → Install and enter:

```
n8n-nodes-everypage
```

Or install it on the host directly:

```bash
cd ~/.n8n/nodes
npm install n8n-nodes-everypage
```

On n8n Cloud, search for EveryPage in the nodes panel on the canvas.

Once installed, create an EveryPage API credential. Generate an API key at everypage.co/account under API Keys (keys start with ep_live_), paste it into the credential, and optionally set the Base URL — only needed when pointing at a staging or self-hosted EveryPage deployment. The key is sent as a bearer token and validated against GET /api/v1/user.

## Authentication

Credentials require a valid EveryPage API key. For details on generating and managing API keys, see API Keys.

## File actions

The File resource handles document uploads, imports, updates, deletions, and analytics retrieval. All file-producing operations return shareUrl, qr_url, and embed_code alongside uuid and shortId. The share link and embed code prefer the short ID and never use a vanity slug; qr_url is the public, unauthenticated QR endpoint keyed on the UUID, so downstream steps can render it without an API key.

| Operation | Description | Plan |
|---|---|---|
| Upload | Upload a PDF and create a tracked share link with full settings control | Free |
| Import From URL | Fetch a PDF from a URL (without credentials) and upload as a tracked link | Free |
| Get | Retrieve a document by UUID or short ID | Free |
| Get Many | List your documents. The upstream list is unpaginated, so Limit (default 50) and Return All are applied by the node. There is no name-filter input — filter with an expression or a Filter node | Free |
| Update Settings | Modify viewer mode, expiry, passcode, gates, protections, and other settings | Free |
| Delete | Move a document to trash (restorable) or purge permanently | Free |
| Replace Content | Swap the PDF behind a link in place; UUID, settings, and readership history survive | Pro |
| Get QR Code | Download the tracked QR code as a PNG for print or embedded workflows | Free |
| Get Readership | Fetch the analytics report (summary, funnel, sessions, contacts) as JSON | Free |
| Get Page Marks | Fetch readers' pick / reject / maybe verdicts: per-page tallies, a per-viewer breakdown, and totals | Pro |
| Get Annotations | Fetch the annotations readers drew, grouped by page, with each reader's note | Pro |

Upload and Import From URL accept all plan-tiered settings in their Options parameter: viewer mode, passcode, email gates, domain allowlists, watermark, page ranges, protection toggles, expiry/never-expire, view limits, and more. Update Settings applies only the options you specify; omitted fields retain their current values.

Proofing feedback is a pull, not a push: the proofing.updated event fires once per viewer, on their first mark, and carries no verdicts. Trigger on it (or on a new comment) and then read the marks. See page marks and the photo proofing automation guide.

Import From URL fetches the file without your EveryPage API key, so your credentials never travel to a user-supplied host, and checks the downloaded bytes actually start with a PDF header before uploading them.

Delete trashes by default (recoverable through the trash and recovery flow). Enable Purge Permanently to remove the document and all associated share links and readership data irreversibly.

Replace Content swaps the PDF behind an existing link while preserving its UUID, short ID, slug, QR code, settings, and readership history. Enable Keep Page-Anchored Hotspots and Notes only when the new PDF has identical page layout to the original; anchors are cleared by default to prevent broken references.

## Link variant actions (Pro)

The Link Variant resource creates per-recipient tracked links, so readership attributes to the individual you sent each link to. Every operation takes the parent document; all but Create also take a variant UUID.

| Operation | Description |
|---|---|
| Create | Mint a new variant with a recipient label and optional per-recipient overrides |
| Get Many | List a document's variants (Limit default 50, or Return All) |
| Update | Change a variant's label, revoked state, or overrides |
| Revoke | Deactivate a variant so its URL stops resolving (recipients who already opened it know the canonical link) |
| Delete | Remove a variant, or with Redact Label GDPR-redact it in place instead |

When updating variant overrides (allowDownload, pageFrom, pageTo), providing any override field replaces the whole overrides object rather than merging. Re-state every override you intend to keep. See Link Variants for the full variant contract.

Overrides are limited to download permission and page range. Per-variant passcodes and email gates are not supported — those settings live on the parent document and apply to every variant.

The Delete operation supports GDPR label redaction, and the two paths do opposite things. With Redact Label off, the variant is removed. With it on, the variant is not removed: its recipient label is scrubbed from the variant, readership history, and stored webhook payloads, while the variant keeps working and its anonymised analytics survive. The deleted and redacted outputs report which happened. A redacted label cannot be re-set afterwards.

## Event bulk pulls

The Event resource pulls analytics events in bulk for warehouse loads and incremental syncs. The Get Many operation walks one event stream at a time from a since cursor you supply — each stream has its own independent ID sequence. Use the trigger node instead when you want workflows to fire on new events. Supported event types are:

| Event Type | Description |
|---|---|
| View | Read sessions with pages viewed and time spent |
| Download | Explicit PDF downloads (includes your own saves) |
| Gate | Email-gate and lead-form completions with captured fields (Pro-gated) |

Cursor logic: since = 0 (the default) returns a single newest-first window, descending, capped at 100 — there is no way to page further back from it. Supply a since above 0 and the node walks forward in ascending order from that event ID, pulling 100 at a time until it reaches your Limit or the feed runs out; Return All removes the limit. Cursors are per-stream: a view cursor is meaningless against the gate stream. Gate event IDs are 64-bit — pass them through unmodified.

## Trigger node

The EveryPage Trigger node fires workflows when documents are read, downloaded, gated, commented on, or burned. Choose between instant webhook delivery (default) or polling for firewalled self-hosts.

### Webhook mode (instant)

On activation, the node subscribes to your selected events; deactivating it deletes the subscription. Every delivery carries X-Everypage-Signature — HMAC-SHA256 over <timestamp>.<raw body>, keyed with the webhook secret returned once at subscribe time — and the node verifies it and fails closed: a missing stored secret, a missing signature, a mismatch, or a timestamp outside the 5-minute tolerance all return 401 and the delivery never reaches your workflow. Comparison is constant-time. This is a real advantage over the Make app, which cannot verify signatures at all.

EveryPage webhooks are available on every plan. The only plan requirement is on gate.completed, which the server delivers only while the account is on Pro at the time of the event.

Webhook mode covers all nine event kinds:

- file.viewed — read sessions with pages viewed, time spent, and link-variant attribution
- file.downloaded — reader downloads (non-owner only; the feed includes your own saves)
- gate.completed — email-gate or lead-form completion with captured fields (Pro at event time)
- note.created — reader feedback note with author, body, and page number
- receipt.confirmed — confirmation of receipt by a viewer who was asked
- file.burned — self-destructed link (view limit reached)
- content.replaced — PDF swapped behind a link
- invite.viewed — invited recipient opened their invite link
- proofing.updated — proofing review decision changed

Optionally scope the subscription to a single document.

### Poll mode (fallback)

For self-hosted n8n instances unable to receive inbound webhooks. Walks the events feed on your configured Poll Times with independent per-stream cursors, advancing a cursor only after a fetch that actually returned events. Poll mode covers the three feed-backed streams only: view, download, and gate. Event IDs are namespaced as <type>:<id> so a view and a gate event sharing a numeric ID cannot collide. Manual executions fetch a small newest-first sample without moving the cursors, so testing in the editor never skips a live workflow forward.

## Bundled workflows

Three example workflows are included:

- ai-report-to-tracked-link — AI agent generates a report, a Code node renders it to PDF, EveryPage creates a tracked link, Slack receives the share URL
- gated-leads-to-crm — instant gate.completed webhook triggers lead capture, shapes fields, and forwards to CRM
- agent-with-everypage-tool — chat agent with EveryPage attached as tools for document listing and readership lookup via $fromAI

On self-hosted n8n, enable N8N_COMMUNITY_PACKAGES_ALLOW_TOOL_USAGE=true to let AI Agent nodes call EveryPage directly.

## Plan-tiered features

Fields above your plan tier are labeled in their descriptions and link to Pricing. The node maps server-side tier checks (403 responses) to user-friendly errors that name the plan and upgrade path. Size caps: Free 20 MiB, Basic 200 MiB, Pro 2 GiB. Rate limit: 120 requests/minute per key. Enable Retry On Fail in the node settings for resilience under rate limiting.

## Related

- API keys — create and manage your API keys
- Webhooks — signatures, delivery, and retries
- Events feed — stream shapes and cursor semantics
- Link variants — the full variant contract
- Trash and recovery — how trash and purge differ
- Plans and limits — tier requirements and API rate limits

---
URL: https://everypage.co/docs/integrations/wordpress
Title: WordPress | EveryPage Docs
Description: Upload PDFs to WordPress and share them as tracked, secure links with built-in analytics and embeds.

# WordPress

Upload PDFs to WordPress and share them as tracked, secure links with built-in analytics and embeds.

The EveryPage WordPress plugin uploads PDFs to your EveryPage account from wp-admin, gives you tracked share links, and embeds documents inline or as buttons. Readership is readable in two places: a per-file report on the EveryPage Files screen, and an "EveryPage - Recent reads" widget on the WordPress dashboard.

Version 1.1.0 is awaiting review by WordPress.org, so the plugin is not yet in the plugin directory — searching wp-admin for "EveryPage" will not find it. Install it from the plugin zip instead (Plugins → Add New → Upload Plugin), or by copying the everypage folder into /wp-content/plugins/, then activate it.

## Requirements and setup

The plugin requires WordPress 6.6 or later and PHP 7.4 or later. After activating, go to EveryPage → Settings, paste your API key (it starts with ep_live_), and save. Create a key from your EveryPage account page.

The key is stored in WordPress options and used only server-side: every call to EveryPage is made by PHP over HTTPS. The block editor and the Media Library screens never hold the key — they go through the plugin's own REST proxy (everypage/v1), which makes the upstream call for them. The one place the key appears in a page is the Settings field itself, which is prefilled for the administrator who set it.

Permissions follow WordPress capabilities: reading files and uploading PDFs needs upload_files; changing a document's viewer settings, and rewriting post content, needs manage_options. The EveryPage admin pages themselves are manage_options.

## Settings screen

The Settings screen holds the API key field. Once a key is saved, it shows the connection state beneath it — either "Connected as <email> (<plan> plan)" or the error EveryPage returned, such as an invalid or revoked key. Account details are cached briefly, so after changing a key on the EveryPage side, re-save the settings to refresh what is shown.

## Files screen

The Files screen lets you upload a PDF and lists your documents with their name, view count and expiry date. Every row has the same three share actions:

- Copy the share link. This is your custom-domain vanity URL when the document has both a slug and a verified custom domain, and the durable short-ID link otherwise.
- Show the QR code, and download it as a PNG.
- Copy a ready-made iframe embed snippet. The snippet always uses the durable /embed/ URL, never a vanity slug.

Click the settings icon on a row to open that file's settings drawer.

## Per-document settings

The settings drawer on the Files page is where you control per-document behaviour — everything your EveryPage plan includes. It has four sections:

Viewer: viewer mode (Standard, Flipbook, Swipe or Magazine), background colour and image effects, page style, mode-specific options (flip speed and layout, page-turn sound, right-to-left reading, swipe auto-advance), logo placement, and branding such as accent colour and toolbar theme.

Protection: allow or block downloads, disable the right-click menu, suppress printing, disable text selection, blur pages when the tab loses focus, set a password, cap the number of views before the link burns, and watermark pages with the reader's email.

Capture: require an email address to read, restrict the gate to specific email domains, attach a lead-capture form, get an email when someone reads the file, and ask readers to confirm receipt.

Link: expiry date or never-expire, a vanity slug, and a page range that limits which pages are served.

Controls your plan doesn't include are disabled rather than hidden, so you find out before you have embedded the document in a post rather than after.

## EveryPage Document block

In the Gutenberg editor, add the EveryPage Document block from the Embed category. Pick one of your existing PDFs or upload a new one directly from the editor.

Choose how it displays in the Mode & height panel:

- Embedded viewer: renders the tracked document viewer inline in an iframe. Height is adjustable from 240 to 1200 pixels and defaults to 600.
- Button / link: renders a styled button or a plain link, with your own label, that opens the document in a new tab.

The block's Viewer panel carries the viewer settings — mode, theme colours, background effects, page style, flipbook and swipe options, logo, on-screen protection and toolbar theme. It does not carry password, expiry, view limit, gate or slug settings; those live on the Files-screen drawer. Changing a viewer setting here writes it to the document itself, so it applies everywhere that document is shared, not just in this block. Because the key is shared across the whole site, only administrators can change these.

Match my theme's colours reads your theme's colour palette and suggests a viewer background, plus an accent colour on Pro. It shows the swatches it picked before writing anything, and it needs at least a Basic plan to apply them. Themes that expose no palette produce no suggestion.

The block is dynamic: the front end renders through the same shared renderer as the shortcode, so block and shortcode output can never drift apart. Inline embeds always point at the /embed/ path with the short ID or UUID — never a vanity slug — because the bare share page refuses to load in a frame.

## Media Library integration

Any PDF already in your WordPress Media Library can be shared via EveryPage. You'll find the sharing option in three places:

- A "Share via EveryPage" row action on each PDF in the Media list
- A button in the attachment details pane (visible in the Media modal and the attachment edit screen)
- A bulk action when you select multiple PDFs

The row action and the attachment button open a modal holding the share link, its QR code (viewable and downloadable), and a "Copy embed code" button. The Media list also gains an EveryPage column showing the view count of each shared PDF, or "Not shared".

Sharing a Media Library PDF uploads a copy of it to your EveryPage account, so it counts against your plan's file count and per-file size limit.

### Replace links in content

The "Replace links in content" tool finds posts and pages whose content links to the original attachment file and repoints those URLs at the tracked EveryPage share link. Open it from the Replace links in content… button inside the share modal, after the PDF has been shared. Only administrators can run it.

It runs in two steps. First a dry run lists every affected post and page with its link count, and nothing is changed. After you confirm, the links are rewritten with wp_update_post, so each updated post's revision history keeps the version from before the change.

## Shortcode

Use the [everypage] shortcode where the block editor is unavailable — the classic editor, or a widget.

```
[everypage uuid="550e8400-e29b-41d4-a716-446655440000" text="View proposal" button="yes"]
```

Attributes:

- uuid (required): the document's identifier. A full UUID, a short ID, or a vanity slug. An identifier containing any other character is rejected and the shortcode renders nothing, rather than silently producing a broken link.
- text (optional): link text or button label. Defaults to "View document".
- button (optional): yes, true or 1 renders a styled button. Anything else, including the default, renders a plain text link.

The shortcode only ever produces a link or a button, never an inline viewer — for that, use the block's embedded-viewer mode. It shares the block's renderer, so a shortcode button and a block button are identical.

## oEmbed

Paste an everypage.co share link on its own line in the editor and the tracked viewer embeds automatically. The plugin makes this work by registering everypage.co as a trusted oEmbed provider on activation.

The registration is what matters. Without the plugin, WordPress still discovers the oEmbed endpoint from the page's HTML, but an unregistered provider is untrusted, so WordPress wraps the result in a sandboxed iframe. That gives the frame an opaque origin, and the viewer cannot boot inside it — cross-origin requests for its assets and public endpoints are refused for a null origin. Registering the provider skips the sandbox, and the embed renders like any first-class provider's.

The registered pattern covers everypage.co links only. A share link on your own custom domain is not matched and will not auto-embed; use the block or the embed snippet for those.

## Plan limits

The plugin is a client for your EveryPage account, so your plan's limits apply unchanged: 3 active files on Free, 100 on Basic, unlimited on Pro, each with its own per-file size cap. Summary readership is available on every plan; trends, the read-through funnel, breakdowns and per-page stats need Basic, and reader identities, CSV export and the email-capture gate need Pro.

The plugin reads your plan from the API and disables the controls above it, with a link to upgrade. See Plans and limits for the full table.

## Related documentation

- API keys
- Embedding documents
- Password protection
- Email gates and lead forms
- Vanity slugs

---
URL: https://everypage.co/docs/integrations/notion
Title: Notion | EveryPage Docs
Description: Embed documents in Notion, or sync reading sessions to a Notion database.

# Notion

Embed documents in Notion, or sync reading sessions to a Notion database.

EveryPage integrates with Notion in two independent ways: embed documents directly into Notion pages with no setup required, or sync your document reading analytics to a Notion database.

EveryPage is a published Notion integration — you can find it in Notion's integration gallery.

## Embeds

Paste an EveryPage /embed/ link into Notion's Embed block and the document renders inline. No authentication or connection is needed. Views of embedded documents are attributed with source=embed in your readership analytics.

For guidance on creating embed links, see embedding documents.

## Database sync

Connect your EveryPage account to Notion via OAuth, then either let EveryPage create an "EveryPage Reads" database on a page you choose, or point the sync at a database you already have. Each synced event then writes one row into it.

### Setup

1. Go to Account and find the Notion card.
2. Click Connect Notion and authorize EveryPage. On Notion's consent screen, share the pages you want EveryPage to be able to use as a parent — only shared pages appear in the picker.
3. Choose Create a new database, pick a parent page and click Create database. EveryPage creates "EveryPage Reads" there and starts with a default sync: all three event types, all documents. (Or choose Use an existing database — see below.)
4. Adjust the sync settings that appear below the card, then click Save sync settings:
  - Events: Viewed, Downloaded, Gate completed (any combination; at least one).
  - Scope: all documents, or up to 20 hand-picked documents.
5. Optionally click Import recent reads to backfill history. See Backfilling history.

### Use an existing database

Instead of creating a fresh database, you can point the sync at one that already exists — typically the Proposal tracker that ships with the EveryPage Notion template, which adds its own formula columns and views on top of the Reads schema. Duplicate the template into your workspace, then:

1. In Notion, share the database with EveryPage: open the database's ··· menu → Connections → add EveryPage. Only shared databases appear in the picker.
2. On the Notion card, choose Use an existing database, pick it from the list and click Use this database.

EveryPage reads the database's schema and checks that these columns exist with these Notion property types:

| Column | Notion type |
|---|---|
| Document | Title |
| Event | Select |
| Date | Date |
| Reader | Text |
| Pages read | Number |
| Time spent | Number |
| Read-through % | Number |
| Returning | Checkbox |
| Source | Select |
| Country | Select |
| Session link | URL |
| Details | Text |

Column names are matched exactly, including case and spacing. Share link (URL) and QR code (Files & media) are optional: add them if you want those cells filled, leave them out if you don't. Any extra columns are ignored — formulas, rollups, statuses and relations you add for your own tracking are never touched, and rows only ever write the columns above.

If a column is missing or has the wrong type, the card refuses the database and lists exactly what to fix (for example "Date: expected Date, found Text"). Correct the property in Notion and try again; nothing is changed on your connection until the check passes. A database that does not appear in the list, or is refused as "not found or not shared", has not been shared with the EveryPage connection yet.

Adopting a database keeps your existing event and scope settings. Once it is connected, click Send test row — that is the way to verify the columns are wired up: the sample row lands in the database with every cell EveryPage can fill.

Change location can also point the sync at an existing database: choose Use an existing database in the picker it opens. New reads sync to the new database; rows already in the old one stay where they are.

### Database columns

The "EveryPage Reads" database is created with these columns:

- Document (title) - The file's name.
- Reader (text) - The reader's identity, in order of preference: the invite name, the invite email, the email captured by a gate, or Reader #N for a pseudonymous reader.
- Event (select) - Viewed, Downloaded, or Gate completed.
- Pages read (number) - Pages viewed in the session.
- Time spent (number) - Duration in minutes, to one decimal place.
- Read-through % (percent) - Pages read divided by the document's page count, capped at 100%. Left empty when the page count is unknown.
- Returning (checkbox) - Whether this reader has read this document before.
- Source (select) - How the document was reached: link, qr, email, or embed.
- Country (select) - The reader's country, resolved in flight from their IP address, which is never stored.
- Session link (URL) - The document's readership page in EveryPage.
- Share link (URL) - The durable share link to the document: its short ID, or its UUID if no short ID exists.
- QR code (files) - The document's QR code image, pointing at the public QR endpoint for its durable share link.
- Date (date) - The event time in UTC. For an imported session, this is when the session started, not when you ran the import.
- Details (text) - Captured form fields from a gate completion, one field: value per line.

Not every column is filled on every row. Only Viewed rows carry session detail (Reader, Pages read, Time spent, Read-through %, Returning, Source, Country); Downloaded rows carry only the document, event, date and links; Gate completed rows carry the Reader, Source and Details. A Viewed row whose session cannot be found still writes, with the basics only.

### Plan support

The Notion integration is available on all plans. One exception: gate.completed events (which carry captured lead data) require a Pro subscription at the time the event occurs. Gate events from free or basic accounts are not synced.

See plans and limits for subscription details.

### Sync scope and limits

You can sync all your documents or hand-pick up to 20 specific documents. Changing the scope affects future events only; rows already written stay in the database.

### Backfilling history

Import recent reads writes past reading sessions into the database. It covers the last 30 days, up to 250 sessions, newest first, and it imports Viewed sessions only — past downloads and gate completions are not backfilled.

A session is skipped if this connection has already delivered it, or has a delivery for it still in flight. Sessions whose deliveries were abandoned are deliberately re-importable, so an import is the recovery path after a spell of failed syncing.

The database must exist before you can import, and only one import can be in flight at a time: starting a second while the first is still delivering is refused.

### One connection per user

Each EveryPage account holds a single Notion connection. Reconnecting to the same workspace refreshes the token and keeps your database and settings — this is how you recover from revoked access. Reconnecting to a different workspace clears the stored database and parent page, because the old database lives somewhere the new token cannot reach; your event and scope choices survive, but you must create a database again.

### Schema management

The database schema is version-gated. A database created today is born at the current version and is never patched. Databases created before an optional column existed (Share link, QR code) are patched exactly once, when a delivery first notices the version is behind.

After that one-shot upgrade, a column you delete in Notion stays deleted. EveryPage never re-adds it: rows write only the properties the database still has, and the missing one is skipped silently.

This keeps sync from breaking over cosmetic columns. If EveryPage cannot read your database's schema when a row is due, it omits the optional columns for that row rather than failing the write.

### Share links and QR codes

The "Share link" column stores the document's durable short-ID URL, never a vanity slug. A Notion row is a permanent record, and a slug is not: it can be renamed or dropped, and it only resolves on a custom domain, so a slug in this cell would go stale.

The "QR code" column holds an image file. Notion renders external files as image thumbnails only when the URL path has an image extension (e.g., .png), so EveryPage uses a /qr-code.png alias for this endpoint. The QR image is cached for 24 hours.

### Failure handling

When syncing cannot continue, EveryPage pauses the connection and emails you the reason. Your configuration — database, events, scope — is kept, and the Notion card shows the state:

- Authorization revoked: Notion rejected the token, which is how it signals that access was removed. Click Reconnect Notion to resume.
- Database missing: Notion could not find the "EveryPage Reads" database — it was deleted, or moved out of EveryPage's reach. Create a new database or point the sync at an existing one to resume.
- Delivery failing: 20 deliveries in a row exhausted all their retries. Fix whatever is refusing the writes, then click Resume syncing.

Only the delivery-failing state is resumable in place; the other two need a reconnect or a new database. To stop syncing entirely, click Disconnect — this removes the connection and its queued rows, but leaves the Notion database and everything already written in it.

### Testing the connection

Once the database exists, click Send test row to push one sample Viewed row through the real delivery path. It confirms EveryPage can write to your database and lets you check the column names and types.

### Reconnecting and moving the database

To connect a different workspace, click Reconnect Notion on the Notion card.

To put the Reads database somewhere else, click Change location. Pick a new parent page to create a new "EveryPage Reads" database there, or choose Use an existing database to sync into one you already have (see Use an existing database). Either way, new reads sync to the new database and rows already in the old one stay where they are.

### Lead capture

If you use email gates to capture reader emails, gate completions with captured emails appear in your Notion database. The "Details" column shows the captured form fields. These rows require Pro; gate completions from free or basic accounts are logged but not synced.

See email gates and lead capture for more on capture gates.

### Session tracking

A Viewed row is written once per completed reading session: the event fires when the reader's session ends, not when they open the document. Reading the same document twice writes two rows. Your own reads never produce rows — owner activity does not raise events.

See reader identities for how EveryPage identifies readers across sessions.

### Related docs

- Embedding documents
- QR codes
- Webhooks
- Email gates and lead capture
- Reader identities

---
URL: https://everypage.co/docs/integrations/slack
Title: Slack | EveryPage Docs
Description: Post Block Kit messages to Slack when documents are viewed, downloaded, or gates are completed.

# Slack

Post Block Kit messages to Slack when documents are viewed, downloaded, or gates are completed.

There is no EveryPage Slack app. Slack support is a format option on an outgoing webhook: you provide a Slack Incoming Webhook URL, add it as an EveryPage webhook, and choose the Slack format. EveryPage then posts Block Kit messages to that channel. There is no slash command, no link unfurling, and no Slack App Directory listing.

## Setup

1. In Slack, create an Incoming Webhook for the channel you want EveryPage messages in, and copy its URL. Slack's own documentation covers the current steps.
2. In EveryPage, go to Account → Webhooks → Add webhook
3. Paste the Slack webhook URL into the Endpoint URL field
4. Choose the Slack format (not JSON)
5. Select which events trigger messages
6. Click Add webhook

The endpoint URL must be HTTPS, and it may not resolve to a private or loopback address.

For the full webhook reference—including test endpoints, other formats, and how to configure per-file webhooks—see Webhooks reference.

## Events and messages

Every event type produces a formatted message with:

- A header stating the event (e.g., "Document viewed", "Gate completed - new contact")
- A fields section: the document name first, then the event's remaining payload keys in alphabetical order, with camelCase keys relabelled ("pagesViewed" becomes "Pages viewed")
- A link to the document's readership page, when the event payload carries a file identifier

Available events:

- Document viewed — a non-owner's reading session ended
- Document downloaded — a non-owner explicitly saved a copy
- Gate completed — a reader passed an email or lead-capture gate (Pro at event time)
- New feedback note — a viewer left a public note on the document
- Receipt confirmed — a reader confirmed receipt of the document
- Document burned (view limit reached) — the view limit was reached and the blob was destroyed
- Document content replaced — the owner swapped the document's content in place
- Invite opened — an email invitee opened the document for the first time
- New proofing feedback — a viewer left their first page mark or annotation
- Test event from EveryPage — sent when you click "Send test" on the webhook

## Signing and security

Slack Incoming Webhook URLs authenticate by URL alone—the URL itself is the secret. Because of this, Slack-format deliveries are deliberately unsigned. Unlike the JSON format, which carries an X-Everypage-Signature header for verification, Slack messages have no HMAC signature: possession of the URL is what Slack accepts as proof, so an additional signature would add nothing Slack can check.

Creating a Slack-format webhook therefore does not show you a signing secret, as the JSON format does.

If you need signed delivery for security auditing or compliance, use the JSON format instead and verify the signature at your endpoint.

## Text and rendering

Message text is escaped for Slack's markup syntax (ampersands, angle brackets), so file names and user-provided text render safely. Field values are rendered as plain text in Slack's block syntax. Slack caps a section at 10 fields, so EveryPage sends at most 10 and drops any remaining payload keys.

## Reliability and retries

Webhooks are delivered with retry and backoff:

- First attempt: immediate
- Failed attempts: retry on a fixed backoff schedule
  - After the 1st failure: wait 1 minute
  - After the 2nd failure: wait 10 minutes
  - After the 3rd and subsequent failures: wait 1 hour
- Max attempts: 5, after which the delivery is abandoned
- Auto-disable: after 20 consecutive abandoned deliveries (each having used all 5 attempts), the webhook is switched off and you receive an email

Any successful delivery resets the failure counter. A webhook that has been auto-disabled cannot be switched back on: delete it and add it again once the endpoint is fixed. Sending a test does not re-enable it.

## Limitations

- Your own actions never fire events. If you (the owner) view your own document or complete a gate on it, EveryPage does not send a webhook message.
- There is no Slack OAuth flow. You must create an Incoming Webhook URL directly in Slack and paste it here.
- A webhook cannot be edited after creation. Changing the URL, the format or the event list means deleting it and adding a new one.
- An account may hold 25 webhooks.

## Plans

Webhooks are available on every plan, Slack format included. The single exception is gate.completed: those deliveries require Pro at the moment the event occurs, because their payload carries captured lead data. On Free and Basic the event is recorded but no Slack message is sent.

## Related

- Webhooks reference — all webhook formats, signature verification, per-file scoping
- View notifications — email alerts as an alternative
- Email gates and lead capture — how lead data is handled and protected
- Plans and limits — tier features and constraints

---
URL: https://everypage.co/docs/integrations/close
Title: Close | EveryPage Docs
Description: Post document reads, downloads and form fills to the matching lead's timeline in Close CRM as an EveryPage activity.

# Close

Post document reads, downloads and form fills to the matching lead's timeline in Close CRM as an EveryPage activity.

EveryPage connects to Close over OAuth and posts each read, download and form fill on your tracked documents to the matching lead in Close as a custom EveryPage activity. Reps see who read the proposal, how far they got and how long they spent, on the lead timeline they already work from, and can filter on it in Smart Views and Workflows.

## Setup

1. Go to Account and find the Close card.
2. Click Connect Close and approve EveryPage in Close.
3. On connect, EveryPage creates one custom activity type called EveryPage in your organization, with the fields listed under What lands in Close. The sync starts with the default scope: all documents.
4. Adjust the sync settings that appear below the card, then click Save sync settings:
  - Which files: all documents, up to 20 hand-picked documents, or off.
  - Create leads for unknown readers: when a reader's email matches no contact in Close, create a lead (named after the email domain) with that contact and log the read as its first activity. Off by default.
5. Click Test connection to confirm the connection end to end. EveryPage calls Close with your token and checks that the EveryPage activity type and its fields exist, creating them if not. No activity is posted, because an activity needs a lead to attach to.
6. Optionally click Import recent reads to backfill history. See Backfilling history.

One EveryPage account connects to one Close organization. Reconnecting with a different organization replaces the connection.

## How reads are matched to leads

A Close activity must belong to a lead, so EveryPage needs an email for the reader. The email comes from whichever of these applies:

- the per-recipient link the reader was sent (email invites and contact lists),
- the email gate on a public link,
- a form fill on the document.

EveryPage searches your Close contacts for that exact email. On a match, the activity is posted to the contact's lead, with the contact set so multi-stakeholder leads show who read. Matching is by exact email only; EveryPage never falls back to matching a company by email domain.

If there is no match and Create leads for unknown readers is off, the event is skipped. Anonymous reads with no email are always skipped, since there is nothing to attach them to. Skipped events are settled, not retried, and never count against the connection.

## What lands in Close

Each event becomes one EveryPage activity on the lead with these fields:

| Field | Type | Meaning |
|---|---|---|
| Event | Choice | Read, Download or Form fill. |
| Document | Text | The document's name. |
| Link | Text | The share link the reader opened. |
| Pages read | Number | Pages the reader reached in the session. |
| Total pages | Number | The document's page count. |
| Time spent (minutes) | Number | Time in the document, in minutes. |
| Read-through % | Number | Pages read divided by total pages, capped at 100. |
| Returning reader | Choice | Whether this reader has opened this document before. |
| Reader email | Text | The email that matched the lead. |
| Session | Text | A link to the readership page for the session in EveryPage. |

The activity's timestamp is the event time, so it sits in the lead's timeline between the call before it and the email after.

Because these are standard custom activity fields, everything Close does with activities applies: Smart View filters such as "EveryPage activity with Read-through % over 80 in the last 7 days and no reply", Workflow triggers on a new EveryPage activity, and the Activity Overview report.

## Events synced

The Close sync subscribes to a fixed set of three event kinds:

- Viewed: a reader opened the document. Posted as Event = Read.
- Downloaded: a reader downloaded the file. Posted as Event = Download.
- Gate completed: a reader submitted the email gate or a form on the document. Posted as Event = Form fill.

The connection and activity sync are available on every plan. The email gate itself is a Pro feature, so gate-completed events, and the lead-creation option that depends on them, only fire for accounts on Pro.

## Backfilling history

Import recent reads posts past sessions as activities. You choose a window of 1 to 30 days and the import covers up to 250 sessions. The import is refused while a previous import or earlier deliveries are still pending, so wait for the queue to drain and try again.

Backfilled activities carry the time the session started, not the time you ran the import.

## Pausing, errors and reconnecting

Close access tokens are short-lived and EveryPage refreshes them automatically. If Close revokes access, for example because the authorizing user was removed from the organization, the card shows Close access was revoked with a Reconnect Close button. After reconnecting, check the sync settings below the card.

If posting to Close fails repeatedly, EveryPage pauses the sync and the card explains why. The usual cause is the EveryPage activity type or one of its fields having been deleted in Close. EveryPage recreates a missing type or field on the next delivery, so click Resume syncing to continue. Deliveries that failed while paused are not replayed; use Import recent reads to fill the gap.

EveryPage respects Close's rate limits and spaces its requests per connection, so a document that goes viral will not starve your other Close integrations.

## Disconnecting

Click Disconnect on the Close card. EveryPage revokes its tokens with Close and deletes the connection and its sync settings. Activities already posted stay on your leads; the EveryPage custom activity type is left in place in Close so existing Smart Views keep working. Delete it from Close's settings if you no longer want it.

## Privacy

EveryPage posts only the fields listed above. Reader IP addresses are never stored or sent to Close, and EveryPage sets no cookies on your readers. Close grants every OAuth app full API access; EveryPage uses that access only to search contacts by email, create the activity type and post activities, and, when you turn the option on, to create leads.

---
URL: https://everypage.co/docs/developers/api-keys
Title: API keys and scopes | EveryPage Docs
Description: Create and manage API keys for programmatic access to your EveryPage account.

# API keys and scopes

Create and manage API keys for programmatic access to your EveryPage account.

An API key authenticates a script or integration as your account against the platform API (/api/v1/). Create a key from your account settings, then send it in the Authorization: Bearer header of every request.

## Creating and managing keys

Create a new key on your account settings page under API keys. Name the key so you can tell which integration holds it, and copy it immediately when it appears—it is displayed exactly once and is never retrievable afterwards, because only its SHA-256 hash is stored. The key begins with the prefix ep_live_ and functions like a password: store it in a secrets manager, never commit it, and replace it if anyone else has seen it.

The key list shows each key's name, its first 12 characters (ep_live_ plus four characters, enough to identify it) and a last-used timestamp; the secret itself never appears. The last-used timestamp is written at most once every five minutes, so it is an activity indicator, not a precise audit log.

Keys do not expire. Revoking one takes effect immediately—the next request presenting it gets 401. There is no per-account limit on how many keys you hold.

## Security: keys carry full account access

An API key resolves to the wildcard scope *, so it passes every scope check. A key cannot be narrowed: there is no way to create a read-only key, a webhooks-only key, or a key scoped to one document. Any key can read and write files, manage webhooks, read readership data, and read your account profile. Every scope EveryPage adds in future is held by all existing keys automatically, with no further consent step.

If different integrations need different permissions, use OAuth instead. An OAuth access token holds only the scopes granted at authorization time—an app that displays readership can hold only readership:read, while a document-capture automation holds only files:write. OAuth tokens are narrowed by scope; API keys never are.

## Understanding scopes

Scopes gate individual endpoints. EveryPage defines five:

| Scope | Endpoints it unlocks |
|---|---|
| files:read | List files, read one file, fetch its QR code, list its link variants |
| files:write | Upload, import, claim, configure, replace content, delete; branding assets, hotspots, link variants |
| readership:read | /events, /gate-responses, per-file readership and per-page stats |
| webhooks:manage | List, create, delete, and test webhook subscriptions |
| profile | GET /api/v1/user (account email and plan) |

These names apply to OAuth tokens, which hold only the scopes granted at authorization. API keys hold * and satisfy all five—the table describes what a key can reach, not a choice you make when creating one.

## Rate limits

Requests to /api/v1/ are limited to 120 per minute, keyed on the value of the Authorization header. That means the bucket is per token, not per IP: integrations sharing an egress IP do not share a budget, and two keys on the same account get a budget each. Over the limit the API returns HTTP 429.

Two exceptions:

- POST /api/v1/webhooks/{uuid}/test carries an additional 10-per-minute limit on the same per-token key, because each call fires a synchronous outbound request.
- The /api/v1/canva/* endpoints are not bearer-authed and are limited per IP instead.

## Plan-based endpoint access

API keys are available on every plan, including free. Creating a key has no plan check.

Individual endpoints still enforce their own plan requirements, and a key never lifts them: /events?type=gate and /gate-responses require Pro, per-page readership requires Basic or higher. A request below the required plan returns HTTP 403 with a plain-text body such as This feature requires the pro plan or higher.

## Viewing the API reference

The full OpenAPI schema is published at /openapi.json and /openapi.yaml (also reachable as /api/openapi.json). Swagger UI, Postman, VS Code REST Client, SDK generators, and LLM function-calling bridges all accept it by URL; every operation carries an operationId. The developers page lists the available operations.

## Next steps

- Authentication — learn how Bearer tokens work and how to add them to requests
- OAuth and oEmbed — create OAuth apps for narrowed permissions
- Webhooks — subscribe to events via API
- Events feed — stream view sessions, downloads, and gate responses
- Plans and limits — see which features require each plan

---
URL: https://everypage.co/docs/developers/authentication
Title: Authenticating with the API | EveryPage Docs
Description: How to add credentials to API requests and understand the error responses the API returns.

# Authenticating with the API

How to add credentials to API requests and understand the error responses the API returns.

The EveryPage API uses Bearer token authentication: include your API key or OAuth token in the Authorization header of every request. The /api/v1/ prefix is not just a version marker—it is what selects the permissive, credential-less CORS policy (so the API is callable from any origin) and the exemption from the same-origin CSRF check. Nothing under /api/v1/ authenticates by session cookie.

## Bearer tokens and token lanes

The API accepts two kinds of bearer tokens, distinguished by their prefix:

API keys begin with ep_live_ and resolve to the wildcard scope *, so they pass every scope check and carry full account access. They cannot be narrowed. Use them for your own scripts and server-side integrations.

OAuth access tokens begin with ep_at_ and carry only the scopes granted at authorization. Use them for third-party apps whose access should be limited—for example, an integration that only uploads documents holds files:write and not readership:read.

Both arrive in the same Authorization: Bearer <token> header, and the prefix is what selects the lane. A token with neither prefix, or one that is unknown, revoked, or expired, is rejected with 401—there is no fallback that could grant unintended access.

## Making a request

```bash
curl https://everypage.co/api/v1/files \
  -H "Authorization: Bearer ep_live_..."
```

GET /api/v1/files lists the files on your account and needs the files:read scope. Replace ep_live_... with your own key; OAuth tokens use the same header with the ep_at_... prefix.

## HTTP status codes

The API returns standard HTTP status codes. This table covers the most common ones and what they mean in this API:

| Code | Name | Meaning |
|---|---|---|
| 200 | OK | Request succeeded. The response body carries the result. This includes POST /api/v1/files and POST /api/v1/files/import —uploads answer 200, not 201. |
| 201 | Created | Returned by POST /api/v1/webhooks and POST /api/v1/files/{uuid}/variants. |
| 400 | Bad Request | The request is malformed or violates a constraint (e.g. not a PDF, malformed body, unknown type on the events feed). |
| 401 | Unauthorized | The Authorization header is missing or malformed, or the token is unknown, revoked, or expired. |
| 403 | Forbidden | Your OAuth token lacks the required scope (insufficient_scope: requires <scope>); your plan does not include the feature (This feature requires the pro plan or higher); or you do not own the target file on a write or readership endpoint. |
| 404 | Not Found | The identifier does not resolve. It is also returned deliberately in place of 403 where a 403 would confirm that a document exists: GET /api/v1/files/{uuid} answers 404 for a file you do not own, and the manage-token settings and content lane answers 404 once a file has been claimed. Note the asymmetry—write and readership endpoints answer 403 for a file owned by someone else. |
| 409 | Conflict | The request conflicts with existing state: the slug you asked for is already used by another of your files, the file was already claimed by a different account, or a concurrent change invalidated a design-lane republish (retry). |
| 410 | Gone | The link is dead—expired, or burned by its view limit. Both refuse settings changes. POST /api/v1/files/{uuid}/content refuses only expired links: replacing the content is the documented way to un-burn a link. |
| 413 | Payload Too Large | The upload or converted result exceeds your plan's size limit. |
| 429 | Too Many Requests | Rate limit exceeded. Wait before retrying. |

Send Content-Type: application/json with JSON request bodies; multipart file uploads (e.g. POST /api/v1/files) use Content-Type: multipart/form-data instead.

## Identifying documents

Endpoints that address a specific document accept either identifier in the path—both resolve to the same file:

- UUID: the canonical xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx identifier
- Short ID: a 12-character base62 code (e.g. aB3xY9kQ2mZ7) that appears in share links

Vanity slugs are not accepted by the API. A slug resolves only on its owner's active custom domain, on the viewer surface; API calls must use the UUID or the short ID. See Share links and short IDs for the identifier rules.

## Rate limiting

Requests to /api/v1/ are limited to 120 per minute, keyed on the value of the Authorization header—so the bucket is per token, and integrations sharing an egress IP do not share a budget. Over the limit the API returns HTTP 429.

POST /api/v1/webhooks/{uuid}/test carries an additional 10-per-minute limit on the same key.

If a 429 is returned, wait before retrying; exponential backoff (e.g. 1s, 2s, 4s) is a reasonable strategy.

## Error responses

Every error under /api/v1/ is an RFC 9457 Problem Details document with Content-Type: application/problem+json. Requests to unknown paths under /api/ get the same shape. For example:

```json
{
  "type": "https://everypage.co/docs/developers/authentication#insufficient-scope",
  "title": "Forbidden",
  "status": 403,
  "detail": "insufficient_scope: requires files:write",
  "instance": "https://everypage.co/api/v1/files",
  "code": "insufficient_scope",
  "hint": "Reconnect with a token that grants files:write. API keys (ep_live_) hold every scope."
}
```

Branch on status or code, never on detail. detail is the human-readable message and may be reworded; code is stable. type links to the matching section below, instance is the request URL, and hint says what to do next. Rate-limited responses also carry Retry-After and the X-RateLimit-* headers; 401 and 403 responses carry an RFC 6750 WWW-Authenticate: Bearer … challenge.

Codes not listed here are derived from the HTTP reason phrase in lower snake case (for example precondition_required) and may be added without notice.

### Missing token

401, code missing_token. No Authorization header, or one that is not Bearer <token>. The response carries WWW-Authenticate: Bearer realm="EveryPage API". Create an API key under Account → API keys.

### Invalid token

401, code invalid_token. The token is unknown, revoked, or expired. The challenge is WWW-Authenticate: Bearer realm="EveryPage API", error="invalid_token". Rotate the key, or refresh the OAuth access token.

### Insufficient scope

403, code insufficient_scope. An OAuth token without the scope the route needs; detail names it (insufficient_scope: requires files:write) and the challenge is WWW-Authenticate: Bearer error="insufficient_scope", scope="files:write". API keys hold every scope and never see this error.

### Plan required

403, code plan_required. The feature is above the account's plan; detail names the plan (This feature requires the pro plan or higher). Upgrade at Pricing.

### Forbidden

403, code forbidden. Any other refusal: not the owner, a plan limit reached (file count, webhook count), or a manage token used on a plan-gated field.

### Validation error

400, code validation_error. Malformed JSON, a missing field, or an invalid value; detail says which.

### Not found

404, code not_found. Unknown id, or a file you do not own on routes where 404 replaces 403 to avoid leaking existence. Ids are the file UUID or its 12-character short id.

### Method not allowed

405, code method_not_allowed. The Allow header lists the supported methods.

### Conflict

409, code conflict. A vanity slug already in use, a file already claimed by another account, or a concurrent content replacement.

### Gone

410, code gone. The link is dead: expired or burned. Settings cannot revive it; a burned link is un-burned by replacing its content.

### Payload too large

413, code payload_too_large. The upload, the converted PDF, or a JSON body is above the limit for your plan.

### Unsupported media type

415, code unsupported_media_type. Reserved; no route returns it today (an unrecognised upload is a 400).

### Unprocessable

422, code unprocessable. A Word or PowerPoint file could not be converted to PDF.

### Rate limited

429, code rate_limited. Over the 120-per-minute budget for this token (10 per minute on webhook tests). Wait for the number of seconds in Retry-After before retrying.

### Internal error

500, code internal_error. Something failed on our side; retrying is safe for reads. Please report it with the instance URL.

### Service unavailable

503, code service_unavailable. A dependency (the document converter, Canva key verification) is down. Retry with backoff.

Outside /api/v1/ the shapes differ: /oauth/token returns the RFC 6749 { "error": "…", "error_description": "…" } object, and the public oEmbed and QR endpoints return plain text.

## API reference

This article covers the conventions common to all routes. For the endpoint listing, see:

- OpenAPI schema — the machine-readable specification (also at /openapi.yaml; consumable by Swagger UI, Postman, SDK generators, and LLM function-calling bridges)
- Developers page — operation summaries

## Next steps

- API keys and scopes — create and manage your credentials
- OAuth and oEmbed — grant narrowed permissions to third-party apps
- Webhooks — subscribe to file events via HTTP callbacks
- Events feed — fetch view sessions, downloads, and gate responses
- Share links and short IDs — understand document identifiers

---
URL: https://everypage.co/docs/developers/events-feed
Title: Events feed | EveryPage Docs
Description: Poll EveryPage for reading activity and form submissions using the events API, an alternative to webhooks.

# Events feed

Poll EveryPage for reading activity and form submissions using the events API, an alternative to webhooks.

The events feed lets you poll EveryPage for activity on your files without setting up webhooks. Use it for batch processing, backfilling historical data, or integrating with systems that cannot accept inbound requests.

## The API

```
GET /api/v1/events
```

Returns events across your files as a JSON array. Requires the readership:read scope (an API key holds it). Each event has a stable id that lets clients dedupe and page without gaps. Events belonging to trashed documents are excluded from every stream.

## Stream selection

The type parameter selects one of three independent event streams:

| Type | Description | Plan |
|---|---|---|
| view | Reading sessions (one row per session) | Free |
| download | Explicit save-to-disk downloads | Free |
| gate | Completed viewing-gate form submissions | Pro |

Omit type or pass type=view to read the view stream. Any other value returns 400 (unknown type: must be view, download, or gate). There is no type=all —a request must name one stream.

type=gate requires the Pro plan; below it the API returns 403 with the plain-text body This feature requires the pro plan or higher. GET /api/v1/gate-responses is a thin alias of ?type=gate, with the same rows, cursor, parameters, and Pro gate.

Cursors are per-type and not portable across streams. Each stream numbers its rows from its own sequence, so id 500 in the view stream and id 500 in the download stream are unrelated records. Passing a cursor from one stream to another silently returns the wrong window—no error. Maintain a separate since marker per stream.

## Pagination

The since parameter controls both the window and the ordering:

- since=0, omitted, or unparseable: return the newest events first (descending). Use this for a first call.
- since=<id>: return events with id greater than <id>, in ascending order. Use this to poll forward without gaps or duplicates.

The limit parameter defaults to 50 and is clamped to the range 1–100—out-of-range and unparseable values are clamped or defaulted, never rejected.

To poll without missing events, store the highest id you have seen in each stream and pass it as since on the next call.

Cursor width differs by stream: view and download ids are 32-bit and a larger since is clamped to 2147483647; gate ids are 64-bit.

## Filtering by file

Pass ?file=<identifier> to return events for only one file. The identifier accepts:

- UUID (the canonical file id)
- Short ID (12-character base62 identifier)

The file is ownership-checked. An unknown identifier, or one belonging to another account, returns an empty array ([]) with 200—never a 404 or 403. This is intentional: the parameter must not work as a file-existence oracle. An empty array therefore means "no matching events", not "no such file".

## Event shape

Each event is an object. Keys appear in this order:

```json
{
  "id": 42,
  "fileUuid": "550e8400-e29b-41d4-a716-446655440000",
  "fileName": "proposal.pdf",
  "readAt": "2024-10-15T14:22:33Z",
  "country": "US",
  "pagesViewed": 5,
  "timeMs": 47000,
  "type": "view"
}
```

| Field | Type | Present on | Notes |
|---|---|---|---|
| id | integer | All | Unique within its stream only. Use as the cursor. |
| fileUuid | string | All | Canonical file UUID, even when the file was reached by short ID. |
| fileName | string | All | The document's original file name. |
| readAt | ISO 8601 datetime | All | When the event occurred. Omitted on the rare view row with no recorded start time. |
| country | string | view, download | Two-letter country code resolved from the IP at capture time. Omitted when unavailable, and never present on gate events. |
| pagesViewed | integer | view | Pages the reader opened. |
| timeMs | integer | view | Milliseconds spent on the document. |
| type | string | All | "view", "download", or "gate". |
| fields | object | gate | String key-value pairs from the submitted form. Omitted when empty or undecodable. |

View rows always carry pagesViewed and timeMs, including when both are 0, so the no-parameter response stays byte-stable for Zapier and similar tools. Download and gate rows omit them entirely. New fields are appended after type, so treat key order as a stable prefix rather than a fixed shape.

## Important behaviors

### The download stream includes your own downloads

The download stream records every explicit download, including downloads you make yourself as the file's owner. This is a deliberate divergence from the file.downloaded webhook, which never fires for owner actions.

The two sources therefore do not reconcile: a document you downloaded twice yourself shows two extra rows in the feed that the webhook never delivered. Anything that compares or merges the two—backfills, download counters, alerting—has to account for it.

### The gate stream excludes plain email captures

The gate stream carries only completed gate form submissions. When a viewer clears a plain email-prompt gate, the address is stored on the view session instead, and no gate event is produced. This exclusion is deliberate: those captures have their own id sequence, and mixing them in would break the single-cursor contract.

To read plain email captures, use the per-file readership endpoint (GET /api/v1/files/{uuid}/readership, Pro), whose recent sessions carry the address as email, or the readership dashboard.

## Example: Polling for new views

```bash
# Fetch the 10 most recent view sessions
curl -H "Authorization: Bearer YOUR_API_KEY" \
  "https://everypage.co/api/v1/events?type=view&limit=10"

# Store the highest id from the response, then poll forward
# (results now ascend from the cursor)
curl -H "Authorization: Bearer YOUR_API_KEY" \
  "https://everypage.co/api/v1/events?type=view&since=12345&limit=10"
```

## Example: Backfilling a single file

```bash
# The 50 most recent gate submissions for one file (Pro)
curl -H "Authorization: Bearer YOUR_API_KEY" \
  "https://everypage.co/api/v1/events?type=gate&file=550e8400-e29b-41d4-a716-446655440000"
```

To walk the whole history, repeat the call with since=<highest id seen> until it returns an empty array.

## Webhooks vs. polling

Choose webhooks if you need low latency —events arrive in your system within seconds. Choose the events feed if you need batch processing (run hourly), backfill (recover missed events), or integration with systems that cannot receive webhooks (many automation platforms, business intelligence tools, data warehouses).

Both methods are supported, and neither is exactly-once: a webhook delivery is retried up to five times, so your endpoint must tolerate repeats, and a polling client re-reads the same rows until it advances its cursor. Dedupe on the event id (feed) or the delivery payload (webhooks).

Learn more about webhooks in Webhooks.

## Authentication and limits

Send an API key or an OAuth token in the Authorization: Bearer header. An OAuth token needs the readership:read scope; an API key holds every scope. Like the rest of /api/v1/, the endpoint is limited to 120 requests per minute, keyed on the Authorization header value—so the budget is per token, not per IP.

The gate stream requires the Pro plan. Free and Basic accounts can read the view and download streams.

---
URL: https://everypage.co/docs/developers/webhooks
Title: Webhooks | EveryPage Docs
Description: Send events to your endpoints when documents are viewed, downloaded, or interacted with.

# Webhooks

Send events to your endpoints when documents are viewed, downloaded, or interacted with.

Create HTTPS endpoints to receive events from EveryPage. When someone views a file, completes a form, or takes another action, a delivery is queued to each of your matching endpoints and POSTed asynchronously, normally within a few seconds. Webhooks work on every plan.

## Event kinds

EveryPage fires nine subscribable event kinds. You subscribe to the ones you care about when you create a webhook.

| Event | Fires when |
|---|---|
| file.viewed | A visitor completes a viewing session on a document |
| file.downloaded | A visitor downloads a PDF from the share page |
| gate.completed | A visitor passes an email-capture or custom form gate |
| note.created | A visitor leaves a public comment or note on a document |
| receipt.confirmed | A visitor marks the document as received |
| file.burned | A view-limited document's encrypted bytes are destroyed by the burn sweep, 30 minutes after the cap is reached |
| content.replaced | You replace a document's content while keeping the same link |
| invite.viewed | An email invitee opens the document for the first time |
| proofing.updated | A viewer leaves their first page mark or annotation on a document — once per viewer per file, not once per action |

A tenth kind, webhook.test, exists but is not subscribable: it is only ever sent by the /test endpoint described below, and rejecting it in events[] at creation is deliberate.

Important: Owner actions never fire events. Every visitor-triggered kind (file.viewed, file.downloaded, gate.completed, note.created, receipt.confirmed, invite.viewed, proofing.updated) is guarded on "acting user is not the file owner", so your own views, downloads, notes, receipts and marks are never delivered. If you're testing a webhook, visit the document while logged out or from a different account. content.replaced is an owner action by definition and does fire; file.burned has no actor.

## Gate-completed deliveries and plan limits

All event kinds fire on every plan. The single exception: gate.completed payloads carry captured lead data (email, form responses), which requires a Pro account. The check runs at event time, when the delivery would be queued — a non-Pro owner's gate completions are never enqueued at all, rather than queued and later dropped. Capture itself stays plan-ungated: a downgraded account's gates keep recording, and deliveries resume on re-upgrade.

## Creating and configuring a webhook

POST to /api/webhooks or /api/v1/webhooks with the following body:

```json
{
  "url": "https://yourapp.com/webhooks/everypage",
  "events": ["file.viewed", "file.downloaded"],
  "format": "json"
}
```

URL: HTTPS only, no userinfo, 2048 characters maximum. Private IPs, loopback addresses, and link-local hosts are rejected at registration and re-checked by the dispatcher before every send. Paste a Slack Incoming Webhook URL and choose format: "slack".

Events: An array of one or more event kinds from the table above. Unknown kinds are a 400.

Format: Either json (signed HTTP POST) or slack (Block Kit message, unsigned). Defaults to json when omitted.

Optional file scope: Add "fileUuid": "..." to receive events only for that file. The value may be the canonical UUID or the short ID; a file you don't own is a uniform 404. Unscoped webhooks receive all events for your account.

The response includes a secret (shown exactly once), of the form whsec_<64 hex characters>. For JSON webhooks, save this secret to verify the request signature on delivery. Slack webhooks have no signature—the webhook URL itself is the secret.

## Signature verification

JSON format webhooks include an X-Everypage-Signature header with every delivery:

```
X-Everypage-Signature: t=1721340000,v1=6e4c37a7c8e9f2b1d3a5c8e1f4a7b9c1d3e5f6a8b9c0d1e2f3a4b5c6d7e8f9a0
```

The signature is an HMAC-SHA256 of the string <t>.<request_body> — the decimal t value from the header, a literal., then the raw body bytes — keyed with your webhook secret. v1 is the MAC hex-encoded in lowercase. Verify the signature to confirm the delivery came from EveryPage.

Two details an implementation must get right:

- The key is the full secret string, including the whsec_ prefix, taken as UTF-8 bytes. Do not strip the prefix and do not hex-decode the value.
- t is the time the request was signed, taken fresh on each attempt — not the timestamp field inside the body. A retry of the same event carries a different t and a different v1. Use t for your replay window; use the body's timestamp for the event's own time.

The body is the raw JSON bytes, including line breaks and spacing exactly as we sent it. Most webhook libraries parse the JSON after verification, which changes the byte representation and makes the signature fail. Verify against the raw request body, then parse it for your application.

Every delivery also carries Content-Type: application/json and User-Agent: EveryPage-Webhooks/1.0.

Implementation pseudocode:

```javascript
const crypto = require('crypto');

function verifyWebhookSignature(rawBody, secret, signatureHeader) {
  const [tsStr, sigStr] = signatureHeader.split(',').reduce((acc, part) => {
    const [key, val] = part.split('=');
    if (key === 't') acc[0] = val;
    if (key === 'v1') acc[1] = val;
    return acc;
  }, [null, null]);

  const timestamp = parseInt(tsStr, 10);
  const signedString = `${timestamp}.${rawBody}`;
  
  const hmac = crypto.createHmac('sha256', Buffer.from(secret, 'utf8'));
  hmac.update(signedString, 'utf8');
  const computed = hmac.digest('hex');

  if (computed.length !== sigStr.length) return false;
  return crypto.timingSafeEqual(Buffer.from(computed), Buffer.from(sigStr));
}
```

rawBody here is the request body as received. If your framework hands it to you as a Buffer, hash the Buffer rather than interpolating it into a template string.

Slack webhooks carry no signature—authentication happens through the webhook URL itself.

## Request body

JSON format payloads contain three top-level fields:

```json
{
  "event": "file.viewed",
  "timestamp": "2024-07-18T15:30:45Z",
  "data": {
    "fileUuid": "550e8400-e29b-41d4-a716-446655440000",
    "fileName": "Quarterly Report.pdf",
    "pagesViewed": 8,
    "timeMs": 125000,
    "sessionId": 41822
  }
}
```

timestamp is RFC 3339 in UTC. The data object always contains fileUuid and fileName, plus kind-specific keys:

| Event | Additional data keys |
|---|---|
| file.viewed | pagesViewed, timeMs, sessionId; variantUuid and variantLabel when the session came through a link variant |
| file.downloaded | variantUuid, variantLabel when the download came through a link variant; otherwise none |
| gate.completed | source; email when an address was captured; fields when a custom form was submitted |
| note.created | author, body; pageNumber when the note is anchored to a page |
| receipt.confirmed | name |
| file.burned | none |
| content.replaced | contentVersion |
| invite.viewed | email, name |
| proofing.updated | kind (mark or annotation), pageNumber, viewer |

Treat new keys as additive: they are appended over time and your parser should ignore unknown ones. Slack payloads render the same events as Block Kit cards, with the file name, the kind-specific keys as fields, and a link to the file's readership page.

## Delivery and retries

EveryPage attempts to deliver each webhook up to 5 times on a fixed backoff schedule:

- 1st failure: retry after 1 minute
- 2nd failure: retry after 10 minutes
- 3rd failure: retry after 1 hour
- 4th failure: retry after 1 hour
- 5th failure: abandoned

A failure counter is incremented once per abandoned delivery — that is, once per event that burned all 5 attempts, not once per attempt. After 20 consecutive abandoned deliveries the webhook is automatically disabled. You'll receive an email notification, and the webhook row shows Active: false with the failure count.

A successful delivery (HTTP 2xx response) resets the failure counter to zero.

Delivery timeout: 10 seconds per request. The dispatcher polls for due deliveries every 5 seconds, so a queued event is normally sent within a few seconds of the action that produced it.

## Testing a webhook

Use the /test endpoint to send a sample webhook.test event through the same delivery pipeline:

```
POST /api/webhooks/{uuid}/test
```

The test fires regardless of per-file scope (it's an endpoint-reachability check) and returns the result synchronously:

```json
{
  "delivered": true,
  "status": 200,
  "latencyMs": 145
}
```

The test delivery uses the same body builders and the same signature as a real one, so it is a valid end-to-end check of your verification code.

The test endpoint is rate limited to 10 calls per minute. On /api/v1/webhooks/{uuid}/test the bucket is keyed on the bearer token; on the session route /api/webhooks/{uuid}/test it is keyed on the caller's IP.

## Notion format (internal only)

A third format, notion, is used by the built-in Notion integration. It syncs reading sessions to a Notion database, is unsigned (it authenticates with the connection's Notion token), and is not available for direct subscription — notion is rejected at creation and its rows are hidden from the webhook list, the account cap, and /test.

## Special cases: Make and n8n

Make does not verify webhook signatures. Make's webhook steps pre-parse the JSON body and then re-serialize it, which changes the byte representation and makes HMAC verification fail. The Slack format works reliably with Make because it carries no signature.

n8n provides native signature verification. The n8n webhook trigger receives the raw body, verifies the X-Everypage-Signature header, and fails the trigger on signature mismatch.

## Limits and quota

- Maximum webhooks per account: 25 (file-scoped and account-wide endpoints share this one cap)
- Maximum delivery attempts: 5
- Delivery timeout: 10 seconds
- Auto-disable threshold: 20 consecutive abandoned deliveries
- Test endpoint rate limit: 10 per minute (per token on /api/v1, per IP on the session route)

## See also

- Events API — long-term event history and backfill
- API keys — authentication and scopes
- Plans and limits

---
URL: https://everypage.co/docs/developers/oauth-and-oembed
Title: OAuth apps and oEmbed | EveryPage Docs
Description: Build integrations with EveryPage's OAuth 2.0 provider and universal oEmbed embedding.

# OAuth apps and oEmbed

Build integrations with EveryPage's OAuth 2.0 provider and universal oEmbed embedding.

EveryPage provides two complementary APIs for integrating with documents: OAuth 2.0 for granting third-party apps controlled access to user accounts, and oEmbed for turning any share link into an embedded viewer.

## OAuth 2.0

EveryPage acts as an OAuth 2.0 provider, allowing third-party applications to access a user's EveryPage account without handling their credentials. This is fundamentally different from API keys, which carry full account access and cannot be scoped—an OAuth token's permissions are narrowed to exactly what a user grants.

### Endpoints and flow

You implement the authorization-code flow with PKCE (RFC 7636). The three endpoints sit at the site root, not under /api:

- GET /oauth/authorize — User consent screen. Redirect users here with client_id, redirect_uri, response_type=code, code_challenge, code_challenge_method=S256, scope, and optionally state. response_type=code and code_challenge_method=S256 are the only accepted values; the redirect_uri must exactly match one registered for the client, and an unregistered one is rejected with a rendered error rather than a redirect.
- POST /oauth/token — Exchange an authorization code for tokens, or refresh an access token. Form-encoded. Submit grant_type (one of authorization_code or refresh_token), then either code + redirect_uri + code_verifier, or refresh_token. Client credentials go in HTTP Basic auth, or as client_id / client_secret in the body; a confidential client must present a matching secret. The code_verifier must be 43–128 characters.
- POST /oauth/revoke — Revoke an access or refresh token per RFC 7009. Submit the token and client credentials.

/oauth/authorize requires a signed-in EveryPage session. A signed-out user is redirected to the login page and returned to the same authorize request afterwards, so your app does not need to handle that case. Once signed in, the browser lands on the consent screen; approving redirects back to your redirect_uri with code and state, and denying redirects back with error=access_denied.

The authorization code expires in 5 minutes and is single-use — it is consumed before the client and PKCE checks run, so a failed exchange cannot be retried. Access tokens expire in 1 hour; refresh tokens in 60 days.

Refresh tokens rotate: each refresh returns a new refresh token and retires the old one. Presenting an already-used refresh token revokes the whole grant and returns invalid_grant. A refresh may pass scope to narrow the grant, never to widen it.

### Scopes

The consent screen lists every scope the app requested; the user approves or denies the request as a whole, not scope by scope. The available scopes are:

- files:read — Read file list and share links.
- files:write — Upload files, modify file settings, delete files.
- readership:read — Read readership analytics and viewer sessions.
- profile — Read the user's email address and subscription plan.
- webhooks:manage — List, create, delete, and test webhook endpoints.

A client can only request scopes it was registered for; anything outside that set fails with invalid_scope.

An OAuth token holds only the scopes the user granted. By contrast, an API key holds all scopes—so OAuth is the preferred surface for third-party integrations that need only a subset of capabilities.

### Client registration

Client registration is not self-service — it is administered by EveryPage, and there is no public registration endpoint. Contact EveryPage to register an OAuth client. Provide your app's name, one or more redirect URIs, and the scopes your integration needs. EveryPage will issue you a client_id and, if your app is confidential (not a browser SPA), a client_secret.

Redirect URIs are matched by exact string comparison. There is no prefix, wildcard, or port-relaxed matching, so register every URI you intend to use — including any local development callback — verbatim.

### User revocation

Users see and revoke active OAuth grants under "Connected apps" on their account settings page. Revoking immediately invalidates all tokens for that app.

## oEmbed

The GET /oembed endpoint is a public, unauthenticated, per-IP rate-limited oEmbed provider (type rich). It sits at the site root and also answers on owners' custom domains. When a user pastes an EveryPage share link into a consumer that supports oEmbed—WordPress, Notion, or other tools—the consumer queries this endpoint to turn the link into an embedded viewer.

### Endpoint

```
GET /oembed?url=https://everypage.co/{id}&format=json
```

The url parameter must be an absolute http or https URL pointing to any of EveryPage's identifier forms: the canonical UUID, a 12-character short ID, a variant short ID, or a vanity slug (Pro, on the owner's custom domain). The identifier is read from the first path segment, and an /embed/{id} link is accepted too, so a copied embed src resolves like a share link. A missing or unparseable url is a 400. The endpoint responds with JSON:

```json
{
  "version": "1.0",
  "type": "rich",
  "provider_name": "EveryPage",
  "provider_url": "https://everypage.co",
  "title": "Document title",
  "html": "<iframe src=\"https://everypage.co/embed/{shortId}\" width=\"800\" height=\"600\" frameborder=\"0\" allowfullscreen title=\"Document title\"></iframe>",
  "width": 800,
  "height": 600
}
```

The default iframe dimensions are 800×600; consumers may restyle them.

### Identifier resolution

The oEmbed endpoint resolves every identifier form:

- UUID — Resolves on everypage.co and on the owner's own custom domain.
- Short ID — Same as the UUID.
- Variant short ID — Resolves to the parent file; the emitted embed points to the parent, not the variant.
- Vanity slug — Resolves only on the owner's active custom domain (or everypage.co if no domain is set).

Every form is checked against the host in the pasted url, not just slugs. If that host is a custom domain registered to a different account, the lookup fails — a branded domain can never vouch for a file it does not own.

### Dead links

Dead links of every shape return a uniform 404:

- Expired files
- Burned (revoked) files
- Non-existent identifiers
- Unclaimed anonymous uploads (legacy)
- Revoked link variants
- An identifier on a foreign custom domain

Returning an identical 404 for all dead states prevents third-party consumers from probing whether a link exists or has been claimed.

### Frozen artifact rule

The html field in the response always embeds via the durable /embed/{shortId} URL, never a vanity slug and never a variant identifier. This ensures that the frozen HTML outlives slug renames, domain changes, and variant revocations. Once pasted into a foreign page, the embed remains valid even if the owner changes the link's settings. See embedding for more detail.

### Consumer sandboxing

Some oEmbed consumers (like WordPress) treat EveryPage as an untrusted provider and render the embed in a sandboxed iframe with an opaque origin. This prevents the viewer from booting because requests for /assets and session-based public endpoints fail the same-origin check.

The WordPress plugin resolves this by registering EveryPage as a trusted provider on plugin-installed sites, so embeds render without sandboxing. Without the plugin the iframe is inserted but the viewer does not load — there is no partial rendering, and no configuration on your side changes that. Making plugin-less pastes render is a known outstanding platform change (cross-origin headers on assets and public read endpoints, plus cookieless viewing), not something implemented today. See WordPress integration for setup.

### Format parameter

Only format=json is supported (XML is deliberately not implemented). Omitting the parameter is equivalent to format=json. Any other value returns 501 Not Implemented.

## See also

- API keys — Full-access machine credentials
- Authentication — Session cookies and token types
- Embedding — How embeds work and security considerations
- Link variants — Per-recipient child links
- WordPress integration — Plugin setup and trusted-provider registration

---
URL: https://everypage.co/docs/developers/mcp-server
Title: MCP server for AI assistants | EveryPage Docs
Description: Connect Claude, Cursor or any MCP client to EveryPage so it can share PDFs as tracked links and report who read them.

# MCP server for AI assistants

Connect Claude, Cursor or any MCP client to EveryPage so it can share PDFs as tracked links and report who read them.

The EveryPage MCP server lets an AI assistant use your EveryPage account: upload a PDF and hand back a tracked share link, then answer questions about who read it and how far they got.

It speaks the Model Context Protocol, so it works with any MCP client — Claude Code, the Claude apps, Cursor, VS Code, and others. It is open source (MIT) and published to npm as everypage-mcp; the MCP registry entry is co.everypage/mcp, and the same manifest is served at /.well-known/mcp.json for agents that discover servers by well-known URL.

## Setup

Create an API key in your account settings — it starts with ep_live_ and is shown once — then point your client at the server.

Claude Code

```bash
claude mcp add everypage --env EVERYPAGE_API_KEY=ep_live_... -- npx -y everypage-mcp
```

Everything that reads a JSON config (Claude Desktop, Cursor, VS Code, …)

```json
{
  "mcpServers": {
    "everypage": {
      "command": "npx",
      "args": ["-y", "everypage-mcp"],
      "env": { "EVERYPAGE_API_KEY": "ep_live_..." }
    }
  }
}
```

The server runs locally, launched by your client — there is nothing to host. It needs Node 20 or newer. Because it runs on your machine, it can read a PDF straight off your disk when you ask it to share one.

## Configuration

| Variable | Required | Default | Meaning |
|---|---|---|---|
| EVERYPAGE_API_KEY | yes | — | An API key (ep_live_…), or an OAuth access token (ep_at_…) limited to its granted scopes |
| EVERYPAGE_BASE_URL | no | https://everypage.co | API origin override, for development instances |
| EVERYPAGE_READ_ONLY | no | false | true exposes only the read-only tools — nothing can upload, change or delete |

## Tools

Fifteen tools, grouped by what you would actually ask for.

Documents — everypage_share_pdf (upload from a path or URL and return the share link, embed code and QR URL, applying share settings in the same call), everypage_list_files, everypage_get_file, everypage_update_file_settings, everypage_delete_file, everypage_replace_content (Pro).

Readership — everypage_get_readership (a summary: readers, read time, completion, countries, drop-off page, most re-read page) and everypage_list_events (recent reads, downloads or captured leads, with a polling cursor).

Per-recipient links (Pro) — everypage_create_variants, everypage_list_variants, everypage_update_variant, everypage_delete_variant.

Account and delivery — everypage_list_webhooks, everypage_manage_webhook, everypage_account.

Two prompts ship as slash commands: readership_digest and send_tracked_copies.

## Behaviour worth knowing

Any way of naming a document works. Every tool taking a document accepts a UUID, a short link id, or a share URL pasted from the browser — including /embed/ links and ones with ?via= on the end.

Your key stays local. It lives in your MCP client's config and is sent only to everypage.co. When you ask the server to share a PDF from a third-party URL, that download is made with no EveryPage credentials attached.

Uploads stream and are checked first. A local file is read off disk rather than into memory, and is verified as a PDF and checked against your plan's size cap before anything is sent.

Deleting is reversible by default. everypage_delete_file trashes the document; permanent destruction needs an explicit purge. Irreversible tools are marked with the protocol's destructiveHint, so clients that support confirmation prompts ask first. Set EVERYPAGE_READ_ONLY=true if you want write tools withheld entirely.

Event cursors are per stream. everypage_list_events returns a nextCursor valid only for the same type — the view, download and gate streams have independent id sequences. See Events feed.

## Plan gating

The server works on every plan; what it can do follows the account. Sharing documents and reading readership work on free. Passcodes, view limits, read notifications and page-level statistics need Basic. Per-recipient links, the email-capture gate, content replacement, watermarks and page ranges need Pro. A refusal always names the plan required, so the assistant can tell you rather than retrying.

## Related

- API keys and scopes — creating the key this needs
- Events feed — the cursor semantics behind everypage_list_events
- Developer API — the HTTP API the server calls

---
URL: https://everypage.co/docs/developers/versioning
Title: API versioning and deprecation policy | EveryPage Docs
Description: How the EveryPage API is versioned, what may change inside a version, and how deprecations and sunsets are announced in headers and docs.

# API versioning and deprecation policy

How the EveryPage API is versioned, what may change inside a version, and how deprecations and sunsets are announced in headers and docs.

The EveryPage API is versioned in the URL path. Everything documented in the OpenAPI specification lives under /api/v1/, and that path is the contract: an integration written against v1 keeps working until v1 itself is sunset, which has never happened and is not planned.

## What can change inside v1

Additive changes ship without notice and without a version bump. Treat these as normal:

- New endpoints, new optional request fields, and new query parameters.
- New fields in response objects and webhook payloads. Parse what you need and ignore the rest; never rely on key order or on an object having exactly the keys you saw yesterday.
- New values in open-ended enumerations, such as the code field of an error response or a webhook event kind. Unknown values should fall through to a generic branch.
- New Link relations, new response headers, and tighter validation of input that was already documented as invalid.

Breaking changes do not ship inside v1. A breaking change is one that removes or renames a field, endpoint, or scope; changes a field's type or meaning; narrows what a request accepts; or changes the status code of a documented outcome. Those only arrive in a new version path, alongside v1, never in place of it.

## How deprecation is signalled

When a v1 endpoint, field, or the whole version is scheduled to go away, the same signal appears in three places at once:

1. Response headers on the affected endpoint. A Deprecation header (RFC 9745) carrying the date the deprecation took effect, a Sunset header (RFC 8594) carrying the date the endpoint stops answering, and a Link header with rel="deprecation" pointing at the section of these docs that explains the replacement. For example:

```
Deprecation: @1767225600
Sunset: Wed, 01 Jul 2026 00:00:00 GMT
Link: <https://everypage.co/docs/developers/versioning#deprecations>; rel="deprecation"
```

2. The OpenAPI specification. The operation or property is marked deprecated: true and its description names the replacement and the sunset date.
3. This page. The Deprecations section below lists every active deprecation with its replacement and dates.

The notice period between the Deprecation date and the Sunset date is at least six months. After the sunset date the endpoint answers 410 Gone with an error document whose hint names the replacement. Webhook event kinds follow the same rule: a retiring kind keeps being delivered for the notice period and is listed here.

Agents can therefore rely on two mechanical checks: an endpoint with no Deprecation header is not going anywhere, and an endpoint with one has a Sunset date at least six months out.

## Deprecations

There are currently no active deprecations. Every operation in the OpenAPI specification is supported.

## Next steps

- Authenticating with the API - bearer lanes and error documents
- API keys and scopes - credentials and what each scope allows
- Webhooks - the event kinds this policy also covers

---
URL: https://everypage.co/docs/account/signing-in
Title: Signing up and signing in | EveryPage Docs
Description: Create an account, verify your email, and sign in securely to access your document library and advanced features.

# Signing up and signing in

Create an account, verify your email, and sign in securely to access your document library and advanced features.

You can share a document without an account, but readership data, the file library, and the owner-side sharing controls need one. Sign up with an email address and password, or use Google sign-in where it is available.

## Creating an account

When you sign up, you provide your name, email address, and password (minimum 8 characters). EveryPage then sends a verification email to the address you provided. You must verify your email address by clicking the link in the email before you can sign in. Signup does not sign you in, and an unverified account is rejected at login with "Please verify your email address before logging in" — this is the single most common reason sign-in fails.

Your email address is case-insensitive—EveryPage normalizes it to lowercase, so You@Example.com and you@example.com refer to the same account.

## Verifying your email

After signup, check your email for a message from EveryPage. The verification link is valid for 24 hours. Click it to activate your account, then return to the login screen and sign in with your email and password.

If you did not receive the email, check your spam folder. There is no self-service resend, and signing up again with the same address is refused ("User already exists"), so contact support if the link has expired.

## Session security

When you sign in, EveryPage creates a server-side session. The _session cookie holds only an opaque token — the session data itself lives on the server — and the token is rotated immediately after a successful login to prevent session-fixation attacks. All authenticated requests use this session, so you stay signed in across page reloads and different sections of the app.

Sessions last 24 hours. When one ends you are signed out and returned to the login page.

## Signing in with Google

When Google sign-in is enabled, the login page offers "Sign in with Google" and the sign-up page "Sign up with Google". The code exchange happens server-side, so EveryPage never sees your Google password.

When you sign in with Google, EveryPage:

- Reads your email address and name from Google, and refuses to continue unless Google reports the address as verified
- Signs you into the account already linked to that Google identity, if there is one
- Otherwise links your Google identity to an existing EveryPage account with the same email (safe only because Google verified the address), or creates a new account if there is none

An account created through Google has no usable password. To sign in without Google later, use the forgot-password flow to set one. Signing in with Google skips email verification: Google's verification stands in for it, and the account is active immediately.

Google sign-in is available only when it is configured for the site. When it is not, the button is hidden and the Google endpoints return 404.

## Recovering a forgotten password

If you forget your password, use the "Forgot your password?" link on the login page. Enter your email address, and EveryPage sends a password-reset link valid for 1 hour. Click it, enter a new password, and you will be returned to the login screen. The response is the same whether or not the address is registered, so it never reveals which emails have accounts.

Important: Resetting your password signs out all active sessions on every device. There is no exception for the current device.

## Changing your password

You can change your password from the Change Password section of account settings at any time. It asks for your current password, and the new one must be at least 8 characters. After you update it, EveryPage signs out all your other sessions but keeps you signed in on the device where you made the change — the deliberate difference from a reset, which signs out everything.

## Claiming anonymous uploads

If you uploaded a document anonymously and then signed up or signed in from the same browser session, EveryPage automatically claims that document into your new or existing account. That applies to signup, ordinary login, and Google sign-in alike. The claimed file stops expiring, like any signed-in upload, unless you had set an expiry yourself through the manage token—that one is kept. You can change it afterwards from Share Settings, including to never.

Claiming counts against your plan's active-file limit. If you are already at the limit, the document is not claimed and you are told so; it stays where it is, so freeing a slot and signing in again completes the claim.

When a document is claimed, it appears in your library and you unlock readership tracking and the owner settings. For more details, see Sharing without an account.

## Account security best practices

- Use a unique, strong password you have not used elsewhere.
- Do not share your password with anyone.
- Sign out on shared devices when you are done.
- If you suspect unauthorized access, change your password immediately.

## Related resources

- Account settings
- Billing and plans
- Deleting your account
- Sharing without an account

---
URL: https://everypage.co/docs/account/billing-and-plans
Title: Billing and plans | EveryPage Docs
Description: Manage your EveryPage subscription, upgrade plans, and understand billing through Stripe.

# Billing and plans

Manage your EveryPage subscription, upgrade plans, and understand billing through Stripe.

EveryPage has three plans: free, Basic, and Pro. Pricing is flat per account — there are no seats, teams or per-user charges, so one account is one subscription. Payment, plan changes and invoices all run through Stripe.

## Plan pricing

Free: $0 per month Basic: $9/month, or $90/year — $7.50/mo billed annually, saving $18 a year Pro: $29/month, or $290/year — $24/mo billed annually, saving $58 a year

For a complete feature comparison, see plans and limits.

## Upgrading to a paid plan

To upgrade from free or switch to a paid tier:

1. Go to /pricing and choose monthly or annual billing with the toggle
2. Click Subscribe on the Basic or Pro card (if you are not signed in, this sends you to sign-up first)
3. You'll be redirected to Stripe Checkout to complete payment
4. After a successful payment you're returned to a confirmation page, and your plan updates as soon as Stripe confirms the checkout

If you already have an active subscription, the button reads Manage plan and takes you to your account page, where the billing portal link lives. A second checkout on an account that is already subscribed is refused outright — it would create a second subscription and bill you twice, so plan changes belong in the portal.

## Managing your subscription

All billing management—switching plans, updating payment methods, downloading invoices, and viewing renewal dates—happens in the Stripe billing portal. To access it:

1. Go to /account
2. In the Subscription section, click Manage Subscription
3. You'll be taken to your Stripe customer portal, and returned to /account when you leave it

The portal needs an existing Stripe billing account: on an account that has never subscribed, the button reports that there is no billing account to open.

From there, you can:

- Switch between Basic and Pro plans
- Change your billing period (monthly to annual or vice versa)
- Update your payment method
- Download invoices
- Cancel your subscription
- View your next renewal date and current charges

## Switching plans

You can upgrade or downgrade at any time by opening the billing portal (see above). Your EveryPage tier is re-derived from Stripe when the change is confirmed, so features follow the new plan as soon as the change lands. Charges, proration and dates are handled by Stripe and shown in the portal before you confirm.

## Cancelling your subscription

You can cancel anytime from the Stripe billing portal:

1. Go to /account and click Manage Subscription
2. Choose the cancel option and confirm

Paid features stop when the subscription actually ends — immediately or at the end of the current period, depending on which option you take in the portal. Your account and files remain either way: you drop back to the free plan, and the readership data you have already collected stays in place.

## What happens when you downgrade

When you downgrade to a lower plan, features stop being served but data is preserved. Here's what changes:

Analytics and readership: Measurement itself is not tiered — view sessions, page-level stats and captured emails keep recording on every plan. What changes is what you can see: dropping from Pro to Basic removes reader identities, live presence and CSV export from your reporting, and dropping to free leaves only the summary cards. Nothing is deleted, so upgrading again reveals the history recorded while you were on the lower plan.

Page ranges: Page-range enforcement survives a downgrade on purpose. A link you shared showing pages 4–9 keeps showing pages 4–9 after you drop off Pro — a downgrade must never widen access to a link you have already sent. You just cannot set or change a range until you are back on Pro.

Watermarks: Watermarking works the other way, and this is worth knowing before you downgrade. The overlay is applied only while the document's owner is on Pro, so a downgrade stops it being applied to new views and downloads even though the setting stays stored on the file. Upgrading turns it back on.

Expiry: There is no per-plan expiry cap — every plan can set any window or never-expire — so a downgrade never touches a link's expiry, whether you edit its settings or restore it from the trash.

Comments and receipts: These are served against your current tier, so they stop appearing to readers when you drop below the plan that includes them — comments need Pro, read receipts need Basic or Pro. Everything already collected is retained and reappears when you upgrade.

Email gates: A gate you turned on keeps gating after a downgrade, and keeps capturing addresses; what you lose is the Pro-only reporting that lets you read the captured leads back. As with page ranges, a downgrade does not open a document you had closed.

If you want to restore a feature, you can upgrade back to the plan at any time, and your settings and data pick up where they left off.

## Annual vs. monthly billing

Monthly and annual are separate Stripe prices for the same tier, and both renew automatically until cancelled. Switching between them is a plan change in the billing portal, which shows the new amount and date before you confirm.

## Invoices and receipts

Invoices and payment methods live in the Stripe billing portal, where you can view and download them.

## Questions about billing?

For issues with Stripe, lost receipts, or payment failures, you can:

- Check your Stripe account details and payment methods in the billing portal
- Contact Stripe support directly if you see a charge you don't recognize
- Reach out to EveryPage support if you need help accessing your billing portal

See also: Account settings, Plans and limits

---
URL: https://everypage.co/docs/account/account-settings
Title: Account settings | EveryPage Docs
Description: Manage your profile, subscription, security settings, API access, and integrations from your account dashboard.

# Account settings

Manage your profile, subscription, security settings, API access, and integrations from your account dashboard.

The account page at /account gathers profile, billing, security, integrations and API access into one column of sections. This guide walks them in the order they appear and points to deeper documentation.

## Profile

Change your display name and save it with Save Changes. Your email address is shown but read-only: changing an account email needs a re-verification flow that does not exist yet, so the field carries the note "Contact support to change your account email." See Signing up and signing in for account creation and email verification.

## Subscription

Your current plan is shown as a stamp. Manage Subscription opens your Stripe customer portal, where upgrades, downgrades, payment methods, invoices and cancellation live.

On a free plan the section adds a short upgrade note and a link to pricing. See Billing and plans for plan comparison and pricing.

## Custom domain

Custom domains are a Pro feature; on any other plan this section shows only an upgrade prompt. When verified, a domain serves your share links from your own subdomain—for example, docs.yourcompany.com instead of everypage.co. Links, QR codes, and embeds all use it once it is active.

Enter the subdomain, click Add domain, then create the two DNS records the section prints (a CNAME to our target, and a TXT record for ownership) at your domain provider. Click Verify domain to have EveryPage check them; the section then reports "Waiting for DNS verification", "Verified · certificate provisioning…" or "Verified & active". HTTPS certificates are issued automatically once verified. Full instructions are at Custom domains.

Remove detaches the domain: share links go back to everypage.co immediately and links already handed out on the custom domain stop working. Share links also fall back to everypage.co if you leave Pro, because the domain only serves while the account is on Pro.

## Change Password

Enter your current password and a new one (at least 8 characters) and click Change Password. The update signs out all your other sessions but keeps you signed in here. See Signing up and signing in for how this differs from a password reset.

## Danger Zone

The Delete Account button sits here, mid-page rather than at the bottom. It opens a confirmation dialog, and confirming deletes the account, every document, and all associated data immediately and irreversibly. Read Deleting your account first — particularly the note about cancelling a paid subscription beforehand.

## Zapier and Make early access

Two dismissible banners invite you to request early access to the Zapier and Make integrations. Both fire on document views, downloads and captured leads, and both authenticate with an API key from the section further down. Dismissing one does not dismiss the other, and the choice is stored in your browser, so a different browser or cleared site data shows them again.

## Notion sync

Connect a Notion workspace and every reading session becomes a row in an "EveryPage Reads" database. After connecting, you pick the Notion page the database should live in; the section then lets you choose which events sync (Viewed, Downloaded, and — on Pro — Lead captured), whether all files or up to 20 selected files are tracked, and offers Change location, Send test row, Import recent reads (the last 30 days, up to 250 sessions) and Disconnect.

Rows carry Reader, Pages read and Time spent, plus optional Share link and QR code columns. Below Pro the Reader column shows a pseudonym such as "Reader #214" rather than a name. If Notion access is revoked or the database is deleted, the section says so and offers a reconnect or a resume.

This section is absent entirely when Notion sync is not configured for the site. See Notion integration for setup and troubleshooting.

## API keys

API keys grant programmatic access to your account for integrations and scripts. Each key can be named for easy reference, and the list shows its prefix and when it was last used. Create one by entering a name and clicking Create key. The key itself is revealed once—copy and store it before closing the dialog, because it cannot be retrieved later.

Revoke a key immediately if you believe it has been compromised. Full documentation is at API keys.

## Webhooks

Webhooks let you send data to your own systems when events occur: views, downloads, form submissions, comments, and more. EveryPage includes webhooks on every plan (except gate.completed events, which require Pro at the time the event fires). Webhooks deliver as signed JSON HTTP POSTs or as Slack messages.

Add one with Add webhook: an HTTPS endpoint, the events you want, and JSON or Slack format. A JSON webhook's signing secret is displayed once—save it to verify deliveries. Each webhook lists its format, events and status, and Send test reports the HTTP status and latency of a live delivery. A webhook that keeps failing is disabled automatically and shows "Disabled after repeated failures"; there is no re-enable control, so delete it and create a replacement once the endpoint is fixed. Full details are at Webhooks.

## Contact lists

Contact lists are Pro only; on any other plan the section shows only an upgrade prompt, including lists you created while on Pro. Create a named list with New list, then open it to add members one at a time or Import CSV (email in column 1, optional name in column 2). Lists are used to send bulk tracked invites from the Configure & Share screen. See Contact lists for import format and workflow details.

## Connected apps

Connected apps lists the third-party applications you have authorized through OAuth, with the scopes each one holds. Revoke disconnects one immediately.

## Related resources

- Signing up and signing in
- Billing and plans
- Custom domains
- API keys
- Webhooks
- Notion integration
- Contact lists
- Deleting your account

---
URL: https://everypage.co/docs/account/deleting-your-account
Title: Deleting your account | EveryPage Docs
Description: Understand what happens when you permanently delete your EveryPage account and how to prepare.

# Deleting your account

Understand what happens when you permanently delete your EveryPage account and how to prepare.

Deleting your account is permanent and irreversible. Your entire EveryPage account, all documents you have uploaded, and all readership data are deleted immediately and cannot be recovered. Before you proceed, make sure you have exported any data you want to keep.

## How to delete your account

Open account settings, scroll to the Danger Zone, and click Delete Account. A confirmation dialog appears; confirming starts the deletion straight away. There is no grace period, no cooling-off window, and no undo.

## What gets deleted

When you delete your account, the following are permanently removed:

- Your user account and all its settings
- Every document you uploaded, including files sitting in the trash
- The encrypted files stored on disk, and the encryption keys that decrypt them
- All readership data attached to those documents: view sessions, page-level stats, download records, captured gate responses, comments, receipts, and link variants
- Any custom domain configuration, including its certificate at our edge provider
- API keys, webhooks, folders, contact lists, your Notion connection, and every third-party app you have authorized

You cannot restore any of these after deletion. This differs from document deletion, which is recoverable on Basic and Pro plans — account deletion is final.

## Share links stop working immediately

Every share link you have sent to readers stops working the moment your account is deleted. That includes short-ID links, vanity slugs on a custom domain, per-recipient link variants, embedded viewers on other sites, and QR codes you have already printed. Readers holding any of these lose access instantly, and anyone who has saved or bookmarked your documents will be unable to view them. There is no way to reissue a deleted link.

## Before you delete

### Cancel your subscription

Account deletion does attempt to cancel an active Stripe subscription automatically, as its first step. That attempt is best-effort: if Stripe cannot be reached, the failure is logged and the deletion continues anyway, which leaves a live subscription attached to an account that no longer exists — and no account left to cancel it from.

Because of that, cancel first if you hold a paid plan. Cancel it in the Stripe billing portal from account settings, confirm the subscription is gone, and only then delete the account. See billing and plans for how to reach the portal.

### Export your data

If you want a record of your readership before deleting, export a CSV of your sessions (CSV export is a Pro feature). This is your only opportunity to preserve that data. Download any documents you still need, too — the stored copies go with the account.

### Reclaim or burn links

Consider burning documents you no longer want shared, or retrieving important files and reconfiguring their sharing before deletion. Once your account is gone, there is no way to disable individual share links or retrieve content.

## What is NOT covered

Anything you have already downloaded or saved locally is outside EveryPage's control and will not be affected. Similarly, if you have used captured lead data from your documents outside EveryPage (forwarded to email, exported to a third-party tool, or used elsewhere), deleting your account does not erase that external copy.

## Data security

EveryPage encrypts your files at rest with per-account keys. Deleting your account deletes the stored file data and, with it, the encryption keys those files were written under, so the content is unrecoverable regardless of anything else. See encryption and privacy for how the encryption works.

## Need help?

If you are having second thoughts or want to confirm something before proceeding, contact support. We are happy to help.

---
URL: https://everypage.co/guides
Title: Guides: PDF Tracking, Readership & Integrations | EveryPage
Description: Practical guides on sharing PDFs as secure, trackable links and understanding who reads them - plus setup guides for every EveryPage integration.

# EveryPage guides

Everything on sharing PDFs as secure, trackable links - and understanding who actually reads them. Practical how-tos, honest comparisons, and setup guides for every integration.

## Start here

PDF tracking

See who reads your PDFs page by page - reading time, a read-through funnel, and returning readers, with no stored IPs.

DocSend alternative

The privacy-first, flat-priced alternative to DocSend: page-level analytics without per-seat billing or visitor IP logging.

All features

Readership analytics, four viewer modes, password protection, expiry, QR codes, and the email gate.

Pricing

Free to start; Basic at $9/month flat and Pro at $29/month - no per-user pricing.

PDF to QR code

Turn a PDF into a QR code that opens on any phone - and see how many people scanned it and how far they read.

PDF flipbook

Share a PDF as a page-turning flipbook that opens in the browser - with page-by-page read tracking built in.

Reader comments

Collect feedback on any PDF you share - readers comment without an account, privately to you or publicly for every viewer.

## How-tos & comparisons

- How to see who read your PDF (and how far) Turn a shared PDF into a tracked link and see opens, returning readers, pages, and time - without spyware or stored IPs.
- Send a pitch deck and know if investors read it Share your deck as a link and watch the read-through: which slides held attention and which investors came back.
- Track if a sales proposal PDF was read Stop guessing after you hit send. See when a prospect opened your proposal and how far they got.
- How to track a PDF sent by email A raw attachment can't be tracked - send a hosted link instead and see who opened it, how far, and when.
- How to send a PDF securely Password-protecting the file, email encryption, cloud links, and tracked link sharing - what each method actually protects against, and how to do it.
- GDPR-compliant PDF tracking See who read it without collecting personal data: why IP logging is the risk and how pseudonymous reader IDs avoid it.
- What is a read-through funnel? Why per-page drop-off tells you far more about a document than a single view count.
- Share a PDF without storing reader IP addresses Get returning-reader analytics using pseudonymous IDs - no IP logging, no data-protection liability.
- Data room vs PDF link: what to use and when When a full data room is overkill and a single tracked link does the job better.
- DocSend vs EveryPage vs PandaDoc An honest comparison of three document-tracking tools on price, privacy, and what each is actually for.
- Track if clients read your deliverables Know which sections a client engaged with before the review call - returning reads, per-page time, no stored IPs.
- Embed a PDF on your website and track who reads it Keep the document on your own page and still see read-through, per-page time, and returning readers - no stored IPs.
- What is a document engagement score? Why read-through, time per page, completion, and return visits together beat a single view count.

## Automation recipes

Complete workflows built on Zapier, Make, and n8n - what to connect, which trigger to use, and where each platform still has a gap.

- Automate photo proofing feedback Clients mark keep/reject/maybe on every shot and leave notes - collect the verdicts into Notion, Sheets, or your task list automatically.
- Turn a property shortlist into booked viewings Buyers mark the properties they want to see; the picks become calendar invites and CRM notes without anyone retyping them.
- Send gated downloads to your mailing list Every reader who passes the email gate joins your list, tagged with the document they came for.
- Slack and CRM alerts when a proposal is read Know who read it, how far they got, and how long they spent - posted to the channel and logged against the deal.

## Integrations

Share tracked links from the tools you already use. See the integrations hub for all of them, or jump straight in:

- WordPress plugin Upload and track PDFs from wp-admin, with a dashboard widget and shortcode.
- Zapier Automate PDF sharing across 7,000+ apps with the Upload PDF action.
- Browser extension (Chrome & Edge) Right-click any PDF link to get a tracked EveryPage link.
- Canva app Publish a Canva design straight to a tracked PDF link.
- Google Workspace Tracked links from Slides, Docs, Drive and Gmail, and your readership in Sheets.
- Notion embeds Paste a link, choose Embed, and the tracked viewer renders inside your Notion page - with reads synced to a Notion database.

Looking for more? The EveryPage blog has long-form articles on document sharing and readership beyond these guides.

Ready to see who reads your PDFs?

---
URL: https://everypage.co/guides/see-who-read-your-pdf
Title: How to See Who Read Your PDF (and How Far) | EveryPage
Description: Why you can't track an emailed PDF, the methods ranked by what they tell you, and how to get page-by-page readership on any document you send.

# How to see who read your PDF

By Nick · Updated 4 August 2026

You sent a PDF and heard nothing back. Did they open it? Read it? Stop on page two? Here's why a normal PDF can't tell you - and the ways to actually find out.

## Why you can't track a PDF you emailed

A PDF file is just a document. Once you email it or hand over a file, it opens in whatever app the reader uses, on their device, with no connection back to you. There's nothing to report an "open," let alone how far someone read. Read receipts in email only confirm the message was opened - not the attachment, and not which pages got attention.

This isn't a setting you can flip. Adobe Acrobat, Apple Preview, and every browser's built-in PDF viewer are deliberately designed not to phone home when a document opens. The PDF format technically allows embedded JavaScript, but mainstream readers disable or sandbox it precisely because a script that calls out to a remote server is indistinguishable from malware - and security software flags documents that try. There is no reliable way to make the file itself report back, and any product claiming otherwise is depending on the one reader configuration where the trick still works.

To know what happens inside the document, the PDF has to be opened through something that can measure the reading. That means sharing a link to a hosted viewer rather than sending the raw file.

## The methods, ranked by what they tell you

### 1. Email read receipts - weakest

A read receipt confirms your email was opened. That is all. It says nothing about whether the attachment was opened, which pages were read, or how long anyone spent. Most mail clients now block tracking pixels or ask the recipient before loading them, so even the "opened" signal is unreliable. Use it when you only need to know a message landed. It fails when the real question is "did they read the document?"

It also fails in the other direction: Apple Mail Privacy Protection and Gmail's image proxy pre-fetch tracking pixels on the recipient's behalf, so a pixel can fire when no human ever opened the email. An email tracker can therefore report both false negatives and false positives - and even a true "opened" only ever proves the email was opened, never that the PDF inside it was read. If your workflow lives in email, the fix is to keep the email and swap the attachment for a measured link - here's how to track a PDF you'd normally send as an email attachment.

### 2. A tracking pixel or a "link to a file"

Hosting the PDF somewhere (Drive, Dropbox, your own server) and sharing a link can register that the link was clicked or the file was fetched. That is a real step up: you at least learn the document was opened, and roughly when. But you usually get a single "viewed" event with no depth - not how far they read, not how long they stayed, not whether they came back. Use it when a binary opened/not-opened is enough. It fails when you need to know which pages actually got read.

The gap matters more than it looks. A fetched file tells you the bytes were downloaded, not that anyone read past the cover. Someone who opened your proposal, glanced at page one, and closed the tab produces exactly the same signal as someone who read all thirty pages twice. If you're deciding whether to follow up, those two readers deserve completely different calls.

### 3. A document viewer with page-level analytics - strongest

Sharing through a viewer that measures reading gives you the full picture: which pages were seen, how long each one held attention, where people dropped off, and whether the same reader came back. Because the document opens inside an instrumented viewer, every page turn is a data point. This is the only method that answers "did they actually read it, and how far did they get?" - and the rest of this guide assumes it.

It's also the only method that is structurally reliable, and the reason is where the measurement happens. The viewer serves each page as the reader reaches it, so every page turn is an event the server observes directly - nothing has to execute on the reader's machine, no pixel has to load, no mail client has to cooperate. The first two methods ask the reader's software for a favour; this one simply watches its own viewer do its job. That's why link-based measurement keeps working where receipts and pixels silently fail. See how PDF tracking works in practice for the mechanics end to end.

## How EveryPage does it

EveryPage is built for the third method. Upload a PDF, share the link, and you get a page-by-page readership report: a read-through funnel showing the percentage of readers who reached each page, time spent per page, returning-reader detection, and where each read came from (link, QR, email, or embed).

And it does this without storing a single visitor IP address - readers become stable, pseudonymous identities via a one-way hash, so you get the insight without tracking people. There's a free plan to try it on your own document.

## Who is "who"? Pseudonymous readers, not surveillance

"See who read it" usually doesn't require a name - it requires telling readers apart. EveryPage does that without keeping anything that identifies a person. When a read happens, the visitor's IP address is run through a salted one-way hash - a cryptographic function that always maps the same address to the same output but can't be reversed - and the result becomes a stable pseudonymous identity like Reader #214. The salt is a server-side secret, so the stored value is useless to anyone who obtains it; the raw address is used only to resolve a country in-flight, then discarded.

The practical payoff: your report can say "Reader #214 opened the deck on Tuesday, got to page 9, and came back Thursday to finish it" - a genuinely useful pattern - while the database contains no IP to leak, subpoena, or mishandle. That distinction is what separates readership measurement from reader surveillance, and it's why this approach holds up under the GDPR where IP-logging trackers create liability.

## What the readership data tells you

A view count is a vanity metric; a read-through funnel is a story. Imagine you share a 20-page deck and the funnel comes back: 100% reached page 1, 78% reached page 6, 52% reached page 12, and 24% reached page 20. In one glance you know most people got past the introduction, half made it through the middle, and a quarter finished. The sharp drop between page 6 and page 12 is where you are losing your audience, so that is the section to tighten.

Funnels also surface thresholds you can act on. If readers who pass page 3 finish 80% of the time while half of everyone else bails on the cover, your document doesn't have a length problem - it has a first-three-pages problem, and that's where the rewrite effort should go. Run the same funnel after the edit and you have a before/after measurement instead of a hunch. What a read-through funnel is walks through reading one in detail.

Per-page reading time adds the second dimension. A page with high time-on-page was read; a page everyone flipped past in two seconds was skimmed. Returning-reader signals tell you when someone came back for a second look - often the strongest interest signal you will get. And source attribution shows whether a read came from your direct link, a QR scan, an email, or an embed.

Combine the dimensions and the interpretations get specific. If your pricing page averages 45 seconds while every other page averages 12, price is the sticking point - lead your follow-up call with it. If a proposal's funnel collapses exactly at the terms section, that's the clause to renegotiate, not the design to polish. And a reader who returns three times but never passes the same page is telling you precisely where the internal objection lives.

## Step by step: track a PDF with EveryPage

1. Upload your PDF at everypage.co - no account needed to try it.
2. Copy the share link (or grab the QR code or embed code) and send it the way you normally would.
3. Open your readership report and watch the read-through funnel, per-page time, and returning readers update as people read.
4. Optionally require an email before the document opens, set a password, or schedule the link to expire - each is a control you choose per link, not a default.

## The honest limits

Link-based tracking is the strongest method, not a magic one. Knowing the edges keeps you from over-reading the data.

### Can I see the reader's actual name or email?

Not by default - readers appear as pseudonymous identities like Reader #214. If you need names, turn on the email gate: the reader enters an email before the document opens, knowingly identifying themselves. That's the only way any honest tool gets a name; products that claim to name anonymous visitors are guessing from data you shouldn't want stored anyway.

### What if someone downloads or prints it?

A downloaded or printed copy is a plain PDF again - it stops reporting the moment it leaves the viewer, for the same reason your emailed attachment never reported in the first place. If page-level data matters for a given document, disable downloads on that link so every read goes through the measured viewer.

### What if the link gets forwarded?

Forwarding works in your favour: each new person shows up as a distinct reader with their own funnel, so you can see your deck travelled - five readers when you sent it to one person is a signal in itself. What you can't see is who forwarded it or the chain it travelled through.

### Can two readers ever blur together?

Occasionally. Because identity comes from a one-way hash of the network address, two colleagues reading from the same office network can register as one returning reader, and one person hopping VPN exits can register as several. That's the deliberate cost of never storing IPs - the aggregate funnel and per-page numbers stay accurate either way.

## Related reading

See the full readership feature set, how PDF tracking works in practice, or how EveryPage compares as a DocSend alternative.

Going deeper: what a read-through funnel is, how to send a pitch deck and know if investors read it, and how to track whether a sales proposal was read.

See who reads your next PDF.

---
URL: https://everypage.co/guides/photo-proofing-automation
Title: Automate Photo Proofing Feedback | EveryPage
Description: Send proofs as one tracked PDF, let clients mark keep/reject/maybe and leave notes, then pull the verdicts into Notion, Sheets, or your task list automatically.

# Automate photo proofing feedback

By Nick · Updated 28 August 2026

Send a client their proofs as one tracked document, let them mark each shot keep, reject, or maybe and leave notes on the ones they want changed - then have an automation collect the verdicts the moment they finish, so the edit list writes itself instead of living in a thread of replies.

## What you need

- An EveryPage Pro account - page marks and annotations are Pro features.
- An API key from Account → API keys.
- An account on Zapier, Make, or n8n.

## 1. Turn proofing on

Export the gallery as a PDF, one shot per page, and upload it. On the Configure & Share screen open Proofing and enable Page verdicts - that puts keep / reject / maybe controls under every page. Turn on Annotations too if you want the client to circle a region and say what to change, and Comments if you want free-text feedback per page. A flipbook viewer mode suits a gallery better than the plain page view.

One setting to check if you plan to trigger on comments: leave allow public comments on. It is the owner's override, and with it off every comment is forced private - which is a legitimate way to run proofing, but private comments deliberately never fire a webhook, so the trigger in step 3 would simply never run.

## 2. Send it as an email invite, not a plain link

This step decides whether the automation is any use. Send the proofs with email invites rather than pasting the share link into a message. An invited reviewer is identified by the invite, so their marks follow them from phone to laptop and arrive in your report under their email address. A plain share link identifies the reviewer by a key held in their browser instead: marks survive repeat visits in that browser but not a change of device, and they land under an anonymous label you cannot route on.

## 3. Know when feedback arrives

Two triggers matter here, and the difference between them is the thing that trips people up.

- New Reader Comment (note.created) fires on every public comment, carrying the author, the comment body, and the page number. Private notes stay between the reader and your dashboard and never fire it, and your own comments never fire it either.
- Proofing Updated (proofing.updated) fires once per reviewer, the first time they mark or annotate anything - and it carries no verdicts. A client marking 200 shots fires exactly one event. It is a "they have started" signal, not a record of what they decided.

So do not try to assemble the edit list out of events. Trigger on one of these, then read the verdicts in the next step.

## 4. Pull the verdicts

Add a Get Page Marks step pointed at the document. It returns the whole picture at once: per-page tallies, document totals, and a breakdown per reviewer with the pages they picked, rejected, and were unsure about. On Zapier and Make the picked pages also come back pre-joined as 1, 4, 9, so you can drop them straight into an email or a database field without looping. Get Annotations does the same for the drawn-on regions and their notes.

Because the trigger fires on the reviewer's first mark, they will usually still be working when it lands. Put a delay step in front of the pull - an hour is generous for a gallery - or run the pull on a schedule and let the event just tell you which documents are worth checking.

## 5. Put it where you work

- Create a Notion page per shoot with a row for each picked shot, and a second view for the rejects.
- Append the picks to a Google Sheet the retoucher works from.
- Email yourself a digest: "Alex picked 12 of 40 - pages 1, 4, 9… and left 3 notes."
- Open a task per annotation in Todoist, Asana, or Linear, titled with the page and the note.

## Which platform does what

| Step | Zapier | Make | n8n |
|---|---|---|---|
| Comment trigger | New Reader Comment | Watch Comments | Trigger → note.created |
| Proofing trigger | — | — | Trigger → proofing.updated |
| Read the marks | Get Page Marks | Get page marks | File → Get Page Marks |
| Read annotations | Get Annotations | Get annotations | File → Get Annotations |

Only n8n carries the proofing.updated trigger today. On Zapier and Make, trigger on the first comment instead, or schedule the Get Page Marks step - the verdicts are always there to be read.

## A note on the data

Reviewer identities in both reports are real email addresses whenever the reviewer came in through an invite, so whatever you pipe this into inherits personal data. That is also why both endpoints are owner-only and Pro-only. EveryPage still never stores the reader's IP address - see sharing without storing IPs.

## Questions

### Why does the proofing webhook not tell me which pages were picked?

It fires once per reviewer, the first time they mark or annotate anything, so that a client marking 200 shots does not fire 200 webhooks at your automation. It is a "they have started reviewing" signal. Read the verdicts with the Get Page Marks step, which returns every mark in one call.

### Do I need Pro for this?

Yes, throughout. Page verdicts, annotations and comments are all Pro features, and the endpoints that read the marks and annotations are Pro-only and owner-only. There is no lower-plan version of this workflow.

### My comment trigger never fires. Why?

Almost always because public comments are switched off for the document. That is the owner's override and it forces every comment private, and private comments never fire a webhook by design - they stay between the reader and your dashboard. Your own comments on your own document never fire it either.

### Can I tell which client left which marks?

If you sent the proofs as an email invite, yes: each reviewer is identified by their email address, and their marks follow them across devices. If you sent a plain share link, marks are keyed to the reader's browser and arrive under an anonymous label, so they cannot be attributed to a named client.

### What happens if I downgrade from Pro?

Marking stops being offered to readers and no new marks are recorded, but everything already collected is kept and reappears if you return to Pro. The API endpoints stop serving while you are off Pro.

### Can the client mark pages without an account?

Yes. Readers never need an EveryPage account - they open the link, mark the pages, and leave notes straight in the browser on any device.

## Related

See photo proofing for the feature itself, the page marks documentation for the full reference, or the estate agent version of the same pattern.

Let the edit list write itself.

---
URL: https://everypage.co/guides/estate-agent-viewing-requests
Title: Property Shortlists to Booked Viewings | EveryPage
Description: Send a property shortlist as one tracked document, let buyers mark what they want to view, and turn those picks into calendar invites and CRM notes automatically.

# Turn a property shortlist into booked viewings

By Nick · Updated 28 August 2026

Send each buyer a shortlist as one document, one property per page. They tap through and mark the ones they want to see. An automation reads those picks and turns them into calendar invites and CRM notes - so the shortlist comes back as a booking list instead of a reply saying "numbers 2, 5 and the one with the garden".

## What you need

- An EveryPage Pro account - page marks are a Pro feature.
- An API key from Account → API keys.
- An account on Zapier, Make, or n8n.

## 1. Build the shortlist so one page is one property

The page number is the property reference in everything that follows, so keep it clean: one property per page, in a stable order, and keep a note of which page is which. When the automation reports "picked pages 2, 5, 9" you want that to map to three addresses without ambiguity. Upload it and enable Page verdicts under Proofing on the Configure & Share screen.

## 2. Send it as an email invite

This is the step that makes the whole thing work, and it is worth being precise about why.

Invites name the marker; per-recipient links do not. A reader who arrives through an email invite is identified by their email address, so their picks arrive attributed to them and follow them from phone to laptop. Link variants are excellent for attributing reads to a named recipient and for per-recipient download and page-range rules - but they do not name the person who left a mark. Send a variant link and the picks come back under an anonymous per-browser label, which is no use for booking anything.

So: invites for the shortlist. Use variants alongside them only if you also need to restrict what each buyer can download or which pages they can see.

## 3. Trigger when they start marking

Subscribe to Proofing Updated (proofing.updated). It fires once per buyer, the first time they mark anything - which is exactly the "this buyer is engaging with the shortlist right now" moment. It carries the page they touched and who they are, but not their verdicts, and it will not fire again however many more they mark.

If you would rather not act while they are mid-list, trigger on New Document Read (file.viewed), which fires when a reading session ends, or simply run the next step on a schedule.

## 4. Read the picks

Add a Get Page Marks step for the document. Each viewer row gives you the buyer's email address and the pages they picked, rejected, or were unsure about - on Zapier and Make already joined into a string like 2, 5, 9. The per-page tallies are a useful second signal across your whole buyer list: a property everyone rejects is telling you something about the price.

## 5. Book the viewings

- Map picked pages to addresses with a lookup table (a Google Sheet or an Airtable base keyed on document + page), then create one calendar event per property.
- Send the buyer a booking link with their picks listed back to them, so the confirmation email doubles as a check that you read the list correctly.
- Log the picks against the buyer's CRM record and set a follow-up task for anything marked maybe - that is the column where a nudge actually changes the outcome.
- Notify the listing negotiator for each picked property rather than the whole office.

## Which platform does what

| Step | Zapier | Make | n8n |
|---|---|---|---|
| Proofing trigger | — | — | Trigger → proofing.updated |
| Read trigger | New Document Read | Watch Reads | Trigger → file.viewed |
| Read the picks | Get Page Marks | Get page marks | File → Get Page Marks |
| Per-recipient links | Create Link Variant | Create a link variant | Link Variant → Create |

Only n8n carries the proofing trigger today. On Zapier and Make, use the read trigger or a schedule - the marks are always there to be read.

## Keeping buyer data tidy

Picks arrive attached to real email addresses, so this workflow moves personal data into whatever you connect it to. Two things worth knowing: link variant labels can be erased in place with a GDPR redaction that keeps the anonymised analytics, and EveryPage never stores a reader's IP address in the first place - see GDPR-compliant PDF tracking.

## Questions

### Why not just send everyone a per-recipient link?

Link variants attribute reads to a named recipient and let you vary download permission and page range per person, but they do not name the person who leaves a page mark - those come back under an anonymous per-browser label. Email invites are what tie a set of picks to a named buyer. You can use both together.

### Does the buyer need an account or an app?

No. They open the link in their browser on any device, tap the verdict under each property, and that is it. Their marks are restored whenever they come back, and follow them between devices when they arrived through an invite.

### Can I see which properties are being rejected across all buyers?

Yes - the same call returns per-page tallies across every reviewer alongside the per-buyer breakdown, so you can see at a glance which properties are being passed over by everyone.

### What if a buyer changes their mind?

Marking a page again updates the verdict rather than adding a second one, so the report always reflects their current view. Re-running the read step picks up the change.

### Does this need Pro?

Yes. Page marks, link variants and the endpoint that reads the marks are all Pro features.

## Related

See EveryPage for estate agents, the page marks documentation, or the same pattern applied to photo proofing.

Let buyers tell you what to book.

---
URL: https://everypage.co/guides/email-gate-to-mailing-list
Title: Gated PDF Downloads to Your Mailing List | EveryPage
Description: Gate a lead magnet behind an email form and add every reader to your mailing list automatically - tagged with the document they downloaded.

# Send gated downloads straight to your mailing list

By Nick · Updated 28 August 2026

Put an email gate in front of a lead magnet - a guide, a template pack, a training plan - and every reader who wants it hands you an address first. An automation adds them to your list the moment they do, tagged with which document they came for, so the follow-up can actually be about the thing they downloaded.

## What you need

- An EveryPage Pro account - the email gate is a Pro feature.
- An API key from Account → API keys.
- An account on Zapier, Make, or n8n, and a mailing list that connects to it.

## 1. Gate the document

Upload the PDF and turn on the email gate in its share settings. Readers now see a short form before the document opens. You have two shapes to choose from, and the choice matters later:

- A plain email gate - just an address. Lowest friction, highest completion.
- A capture form - an address plus the fields you define (name, company, role). More to type, more to segment on.

If you only want a particular audience, add a domain allowlist so only addresses at the domains you name get through.

## 2. Trigger on the capture

Subscribe to gate completed. It fires the moment a reader passes the gate - before they have finished reading, let alone left - and carries the document, the timestamp, the address, and any form fields you collected. Both gate shapes fire it.

One quiet exclusion: readers who arrived through an email invite do not fire it. You already know who they are - you invited them - so they are not treated as a fresh capture.

## 3. Add them to the list

Map the address into your mailing tool - Mailchimp, ConvertKit, Beehiiv, Klaviyo, whatever your platform connects to - and set a tag naming the document. That tag is what makes the sequence worth sending: someone who downloaded a pricing template and someone who downloaded a beginner's guide want very different emails next.

Worth adding to the same automation: push the address to your CRM in parallel, and post to Slack when a capture matches a domain you care about.

## 4. Backfill the ones you already have

If the document has been live for a while, you will want the captures from before the automation existed. Here is where the two gate shapes part ways, and it is the single most confusing thing about this workflow:

Capture-form submissions are in the gate responses feed - pull them with the events step (GET /api/v1/gate-responses) and walk the cursor. Plain email-gate captures are not. An address given to a bare email gate is recorded against the reading session rather than as a form response, so it never appears in that feed. Backfill those from the document's readership report instead, whose recent sessions carry the address.

Going forward the webhook covers both, so this only bites on history.

## Which platform does what

| Step | Zapier | Make | n8n |
|---|---|---|---|
| Capture trigger | New Form Fill | Watch Form Fills | Trigger → gate.completed |
| Backfill form captures | — | List events (gate) | Event → Get Many |
| Backfill plain captures | Get Analytics Summary | Get a readership summary | File → Get Readership |

Zapier has no bulk events step, so backfilling form captures there means an HTTP step against the gate responses endpoint - or simply letting the trigger collect from today onward.

## If your plan lapses

Capture keeps working on any plan - EveryPage does not throw away leads because a subscription ended. What is Pro-gated is your access to them: while you are below Pro, gate deliveries are held rather than sent, and the reporting screens and pull APIs stop serving. Go back to Pro and both the history and the deliveries resume.

## Questions

### Does the reader have to complete the gate before they can read anything?

Yes - that is the point of it. The document does not open until the form is submitted, so the address is captured before the content is given away. Readers still need no account and no app.

### Why are my old plain-email captures missing from the events feed?

An address given to a bare email gate is recorded against the reading session rather than as a form response, so it never enters the gate responses feed. Pull those from the document's readership report, whose recent sessions carry the address. Capture-form submissions do appear in the feed.

### Do invited readers get added to my list too?

No. Readers who arrive through an email invite do not fire the capture event, because you already have their address - you sent them the invite. Only fresh gate completions count as captures.

### What happens to captures if I drop below Pro?

Capture continues and nothing is discarded, but delivery and reporting pause: gate events are held rather than sent, and the pull APIs stop serving until you are back on Pro, at which point the history is there waiting.

### Can I limit the gate to certain companies?

Yes. A domain allowlist restricts the gate to addresses at the domains you name, so a document intended for one client's team is not opened by anyone who guesses the link.

## Related

See lead capture for the feature itself, the email gate documentation, or read alerts into your CRM for what to automate once they are reading.

Turn readers into subscribers.

---
URL: https://everypage.co/guides/proposal-read-alerts-crm
Title: Slack and CRM Alerts When a Proposal Is Read | EveryPage
Description: Send proposals as tracked links and get a Slack ping plus a logged CRM activity the moment a prospect reads - naming who, how far they got, and how long they spent.

# Get a Slack ping when a prospect reads your proposal

By Nick · Updated 28 August 2026

Send the proposal as a tracked link instead of an attachment, and the follow-up stops being a guess. When the prospect reads it, the deal owner gets a Slack message saying who, how far, and how long - and the CRM gets an activity logged against the deal without anyone typing it.

## What you need

- Any EveryPage plan for the alert itself. Basic adds the page-by-page depth, Pro adds per-recipient links.
- An API key from Account → API keys.
- An account on Zapier, Make, or n8n.

## 1. Send one link per recipient

Upload the proposal, then mint a link variant for each person you send it to, labelled with their name. Every variant is its own short link off the same document, so the read that comes back is attributed to a named recipient rather than to "someone". Without variants you still get the read - you just cannot tell which of the four people on the thread it was.

Automate the minting too: a new row in your deal tracker, or a stage change in the CRM, creates the variant and hands back the link to send.

## 2. Trigger on the read

Subscribe to document read (file.viewed). One detail shapes every alert you build on it: it fires when a reading session ends, not when the document opens. That is deliberate - it means the event can tell you how far they got and how long they spent, which "they opened it" cannot. The trade-off is that a prospect still reading has not fired it yet.

Your own views never fire it, so previewing your own proposal will not ping the channel.

## 3. Make the alert worth reading

The event carries the document, the recipient label from the variant, the pages viewed, and the time spent. A message built from those beats a bare notification:

Jane at Acme read Acme-proposal.pdf - 9 of 12 pages, 4m 12s. Stopped on the pricing page.

For the "stopped on" line, add a Get Readership step after the trigger and read the funnel, which shows where readers drop off. That is Basic and above; on the free plan you get the summary numbers without the page detail.

## 4. Log it where the deal lives

- Create a CRM activity against the contact, with pages read and duration in the note.
- Nudge the deal stage when the proposal is read end to end - completion is a far better signal than an open.
- Start a follow-up task the same day, so the call lands while it is still fresh.
- Flag a re-read: a second session days later usually means it is being shown to someone else internally.

## Which platform does what

| Step | Zapier | Make | n8n |
|---|---|---|---|
| Read trigger | New Document Read | Watch Reads | Trigger → file.viewed |
| Read-through detail | Get Analytics Summary | Get a readership summary | File → Get Readership |
| Per-recipient links | Create Link Variant | Create a link variant | Link Variant → Create |

All three carry the whole workflow. On Zapier the read trigger comes in both instant and polling flavours - prefer the instant one, since the alert is only useful while the read is news.

## Without any automation at all

If one document is all you need this for, skip the platforms: turn on view notifications and EveryPage emails you when someone reads it, throttled to at most one an hour per document. The automation route is what pays off once alerts need to reach a channel, a CRM, or a colleague.

## Questions

### Does the alert fire the moment they open the proposal?

It fires when their reading session ends, not when the document opens. That is what lets the event carry how far they got and how long they spent - information an open-notification cannot give you. A prospect who is still reading has not fired it yet.

### Will my own previews trigger alerts?

No. The owner's own views never emit the event, so opening your own proposal to check it will not ping the channel.

### How do I know which person on the thread read it?

Send each recipient their own link variant, labelled with their name. The label travels with the read event, so the alert names the person. A single shared link tells you the document was read but not by whom.

### Do I need a paid plan?

The read event and the alert work on any plan. Page-by-page depth - the read-through funnel and per-page time behind the "stopped on" line - needs Basic or higher, and per-recipient link variants need Pro.

### Can I do this without Zapier, Make, or n8n?

For a single document, yes: view notifications email you directly when someone reads it, at most once an hour per document. The automation platforms are worth it when the alert has to reach Slack, a CRM, or a colleague.

## Related

See EveryPage for sales decks, tracking a sales proposal for the manual version, or gated downloads to your mailing list.

Stop guessing after you hit send.

---
URL: https://everypage.co/guides/data-room-vs-pdf-link
Title: Data Room vs PDF Link: What to Use and When | EveryPage
Description: When a full virtual data room is overkill and a tracked PDF link is enough - a practical comparison for founders, advisors, and small teams.

# Data room vs PDF link: what to use and when

By Nick · Updated 25 July 2026

Not every document needs a virtual data room. When you have a folder full of files and a roomful of counterparties, a data room earns its keep. But when you are sending one deck, one report, or one proposal, a full data room is overkill - and a tracked link does the job in seconds. This guide is a practical comparison for founders, advisors, and small teams who want to pick the right tool.

## What a virtual data room is for

A virtual data room (VDR) is a secure online repository built for sharing many documents with many parties at once. Think of a full due-diligence process: dozens or hundreds of files - contracts, financials, cap tables, IP records - organised into folders, each with its own access rules. A VDR exists to manage that complexity.

Its strengths are folder-level structure, granular permissions (who can see, print, or download which folder), watermarking, and a full audit trail across multiple counterparties. That power comes at a price: a full data room often costs hundreds of dollars per month, and the setup - inviting parties, building the folder tree, assigning permissions - is real work. For a large M&A deal that is exactly what you want. For a single document, it is a sledgehammer.

## What a tracked PDF link is for

A tracked PDF link is the opposite end of the spectrum: one document, one shareable link, set up in seconds. You upload a PDF, you get a link, you send it. There are no folders to build and no parties to provision. The link opens the document in a hosted viewer that measures how it is read.

That is where the value sits. Instead of a single "opened" event, you get page-by-page readership - a read-through funnel showing how far people got, time spent on each page, returning-reader detection, and where each read came from. You get the insight a data room's audit trail would give you, scoped to the one document you actually sent, without the per-seat cost or the setup.

## Side by side: when each wins

|  | Tracked PDF link | Virtual data room |
|---|---|---|
| Number of documents | One file per link | Many files in folders |
| Permissions granularity | Per link - email gate, password, expiry | Per folder and per party |
| Deal size and stage | Early stage, single document | Large, multi-party transactions |
| Cost | Flat - $29/month for unlimited PDFs | Often hundreds of dollars per month |
| Setup time | Seconds - upload and share | Folders and party provisioning |
| Privacy | No reader IP stored - pseudonymous IDs | Full per-user audit trail |

## When a tracked link is enough

For most day-to-day sharing, a single tracked link covers everything you need. Reach for it when:

- You are raising early and sending one deck to investors. You want to know who read it and how far they got, not run a folder hierarchy.
- You are sending one report or proposal to a client or partner and want to see whether it landed - which sections held attention and where they dropped off.
- You need a single NDA-gated file. An email gate in front of the document captures who is opening it before they see a page, without standing up a whole room.
- You want page-level analytics without per-seat cost. A tracked link gives you the read-through detail a data room's audit log would, scoped to one document, at a flat price.

## When you genuinely need a data room

A tracked link is the wrong tool when the situation is genuinely about managing many files for many people. Choose a VDR when:

- You are running a large multi-file M&A or due-diligence process, where dozens or hundreds of documents need to live in one organised place.
- You need granular folder permissions - different parties seeing different subsets of files, with print and download controls per folder.
- You have many counterparties in the same process and need to track who accessed what, file by file, across all of them.

If that describes your deal, the cost and setup of a data room are justified. The tool is built for exactly this, and a string of individual links would become unmanageable.

## The cost reality

The clearest difference is price. A full data room often costs hundreds of dollars per month, and many price per user - so the bill grows with every person you add. That makes sense when the room is the backbone of a months-long transaction. It makes far less sense when you are sending one PDF.

EveryPage Pro is $29 per month, flat, for unlimited PDFs - no per-seat charge. You get page-by-page readership, the email-capture gate for NDA-style sharing, file expiry, and AES-256-GCM encrypted storage. See the full readership features or the pricing for the details.

## When to upgrade from a link to a data room

Start with the simpler tool and move up when the signals appear. A tracked link has outgrown its job when:

- You have too many files. A handful of links is fine; juggling fifty separate links is a folder structure waiting to happen.
- You need per-file permissions. The moment different people should see different documents, you have outgrown a single shareable link.
- You have multiple deal parties in one process who all need scoped, audited access. That is the job a data room exists to do.

Until those signals show up, a tracked link keeps you fast and cheap. When they do, a data room earns its cost.

## Related reading

Learn how EveryPage works as a DocSend alternative, or read the guide on how to see who read your PDF.

Share one PDF and see who actually read it.

---
URL: https://everypage.co/guides/share-pdf-without-storing-ip
Title: Share a PDF Without Storing Reader IPs | EveryPage
Description: Most document trackers log visitor IPs - here's how pseudonymous reader IDs give you returning-reader analytics without storing any IP address.

# How to share a PDF without storing reader IP addresses

By Nick · Updated 4 August 2026

You want to know who read your document - who opened it, how far they got, whether the same person came back. Fair enough. But do you really want to keep a log of every reader's IP address to find out? Most document trackers make you do exactly that. It turns out you don't have to.

There is a quiet assumption baked into almost every "track who viewed your document" tool: that recognising a reader and recording their address are the same thing. They are not. You can build a perfectly useful picture of how a document is being read - returning readers, country, pages, time on each page - without ever keeping the one piece of data that turns a reader into a person on a map. This guide walks through why the IP usually gets stored, why that is a problem you inherit the moment you do it, and the cleaner approach EveryPage uses instead.

## Why traditional document trackers log IPs

When a reader opens a shared document, the only thing the server reliably sees is the network connection itself - and the IP address attached to it. So the easy way to tell one visitor apart from another is to write that IP down. It's already there in every request, it's roughly stable for a session, and it doubles as a crude location signal. That's why so many trackers store it: it is the path of least resistance to "the same person came back" and "this view came from this country."

There is also a feature pull. Storing the raw IP feels like it future-proofs your data: maybe one day you will want to cross-reference reads, block a specific visitor, or look up exactly where a view came from. So the address gets kept "just in case." That instinct is understandable, but "just in case" is precisely the kind of open-ended retention that data-protection rules push back against - and most of those hypothetical uses never actually happen.

The problem is that an IP address is not just a row in your database. It is a piece of information about a real person, and once you store it, it is yours to account for.

## The privacy problem with IP-based tracking

Under the GDPR and the UK GDPR, an IP address is generally treated as personal data - information relating to an identifiable individual. The moment you store one, you have taken on the responsibilities that come with handling personal data. In broad terms that means you need a lawful basis for collecting it, you need to be clear about why you hold it and for how long, you are expected not to keep it longer than you need, and you can be asked to produce or delete it if the person makes a request. None of that is exotic - it is just the baseline for anyone holding data about people.

For a freelancer sending a proposal or a founder sharing a deck, that is a lot of obligation to sign up for in exchange for a stat you barely look at. And it compounds: every tool you use that quietly logs reader IPs is another place you now hold personal data, another retention schedule to think about, another data store that could be exposed. The surface area grows without you really choosing it.

There is a principle that runs through good data practice called data minimisation - the idea that you should only collect and keep what you actually need for the job at hand. If the job is "understand how my document is read," you do not need the reader's address to do it. The cleanest way to avoid the liability is therefore the simplest one: don't store the IP in the first place. You cannot leak, mishandle, or be compelled to produce data you never kept. (This guide explains the principles in general terms and is not legal advice.)

## The alternative: pseudonymous reader identities

Here is the trick that makes "no stored IP" compatible with "I can still recognise a returning reader." Instead of saving the IP, you run it through a one-way function together with a secret value - a salt. A one-way function is easy to compute in one direction and effectively impossible to reverse: the same input always produces the same output, but you cannot work backwards from the output to the original input.

So an IP goes in, and what comes out is a fixed, scrambled fingerprint that looks nothing like an address - something the system then labels as a stable identity like Reader #214. Because the same IP always hashes to the same fingerprint, the next time that reader opens the document they map to Reader #214 again. You can see them return. But the actual IP was never written down, and because the function only runs one way - and the salt is secret - you cannot recover it from what was stored. The recognisable identity exists; the address that produced it does not.

The salt is what closes the obvious loophole. Without it, someone who got hold of the stored fingerprints could in theory hash every possible IP address and look for matches, since the range of addresses is small enough to grind through. Mixing in a secret salt before hashing breaks that attack: the fingerprints only make sense in combination with a secret that lives on the server and is never shared. The result is an identity that is stable enough to be useful to you and meaningless to anyone who might come across it.

## What you can know - and what you can't

With pseudonymous identities you still get the things that actually matter for understanding how a document lands. You can see returning readers (Reader #214 came back three times), which country a read came from, which pages were read and how far people got, and how much time was spent on each one. That is enough to tell who is engaged and where attention drops off.

What you cannot know is the part that should make a reader comfortable: the actual IP address, because it was never stored, and the reader's real identity, because a pseudonymous ID is not a name. The only way a name enters the picture is if the reader chooses to give it - by typing an email into an optional gate before the document opens. Absent that, Reader #214 is just Reader #214.

That boundary is deliberate, not a limitation. Most of the time you do not need a name to make a decision. "A returning reader in Germany spent four minutes on the pricing page and came back twice" tells you what you need to know about interest and where attention is landing. If a specific deal genuinely calls for knowing exactly who is on the other end, the email gate gives the reader the choice to identify themselves - which is a very different thing from quietly harvesting an address they never agreed to share.

## How EveryPage implements it

EveryPage is built this way from the ground up. Each reader is identified by a salted one-way hash of their IP, giving the stable Reader #N identity described above - so returning-reader detection works without a single address being saved.

Country attribution is handled the same careful way: the address is resolved to a country in-flight, during the request, and then discarded - the country label is kept, the IP is not. Files themselves are encrypted at rest with AES-256-GCM, and when a share link expires the encrypted file is swept off disk shortly after. The readership measurement is first-party - it happens inside the EveryPage viewer - so there are no third-party tracking scripts riding along on your document. You can read the privacy details for the specifics.

## Why this is better for everyone

For you, the sender, it means less to carry. There is no log of visitor IP addresses sitting in your account waiting to become a liability - nothing to justify a lawful basis for, nothing to hand over, nothing to remember to delete. You get the readership insight and skip the data-handling overhead that usually comes with it.

For the reader, it means being measured without being surveilled. Their reading behaviour helps you improve the document, but their address is never captured and their identity stays their own unless they choose to share it. That is a fairer deal than most trackers offer - and it is exactly why DocSend alternative searches often lead here: DocSend stores IPs, and EveryPage does not.

It is worth saying plainly that you give up almost nothing for this. The metrics that drive real decisions - did they read it, how far did they get, did they come back, where did the read come from - all survive intact. The only thing that disappears is a column of raw addresses that was mostly a liability anyway. Privacy and insight are usually framed as a trade-off; here they point in the same direction.

## Step by step: share a PDF without storing IPs

1. Upload your PDF at everypage.co - no account needed to try it.
2. Copy the share link (or grab the QR code or embed code) and send it however you normally would.
3. Open your readership report to see returning readers, country, per-page reading, and the read-through funnel - all without a stored IP behind any of it.
4. Optionally turn on the email gate (Pro) if you want an actual name attached to a read, set a password, or schedule the link to expire.

## Related reading

Explore the full readership features, learn how to see who read your PDF, or read the privacy details in full.

Get readership without the surveillance.

---
URL: https://everypage.co/guides/what-is-a-read-through-funnel
Title: What Is a Read-Through Funnel? | EveryPage
Description: A read-through funnel shows the percentage of readers who reached each page of your document - here's how to read one and why it beats a view count.

# What is a read-through funnel?

By Nick · Updated 4 August 2026

A read-through funnel is a chart that shows the percentage of readers who reached each page of a document, so you can see exactly where attention drops off. Instead of a single "it was opened" number, you get the whole arc of a read: how many people started, how many made it to the middle, and how many reached the end - and the precise pages where you lost everyone else.

## Why a view count misleads you

A view count tells you a document was opened. That is all it tells you. It treats every open as identical, when in reality two people who both "viewed" your file can have wildly different experiences. One read every page slowly and came back twice. The other opened it, glanced at page one, and closed the tab. The view count records both as a single "1," and you have no way to tell them apart.

That is the trap with a view count: it counts opens, not attention. A document with 200 views where everyone bailed on page two is failing, and a document with 30 views where most people read to the end is succeeding - but the raw number ranks them the wrong way round. A read-through funnel exists to fix exactly this. It replaces one flattering number with the shape of how people actually read.

## A worked example

Imagine you share a 20-page deck and the funnel comes back like this: 100% reached page 1, 78% reached page 6, 52% reached page 12, and 24% reached page 20. Read each number as "what share of readers got at least this far."

- 100% at page 1 - everyone who opened the deck saw the first page. That is the baseline; it is always 100% because reaching page 1 is the same as opening the document.
- 78% at page 6 - just over three-quarters made it through the introduction and into the body. Roughly one in five gave up in the first stretch.
- 52% at page 12 - about half are still with you at the midpoint. Between page 6 and page 12 you lost another quarter of your audience.
- 24% at page 20 - a quarter reached the final page. Whatever lives on your closing pages was seen by one reader in four.

In one glance you know most people cleared the opening, half reached the middle, and a quarter finished. The funnel never goes up as you move deeper into the document, because you cannot reach page 12 without first passing page 6 - it only holds steady or falls. The interesting question is always how fast it falls between any two pages.

## How to read each drop-off

The shape of the line between two pages tells you what is happening, and there are three patterns worth recognising.

### A cliff between two pages = a problem page

When the percentage falls sharply from one page to the next - say from 78% to 52% across a single page - that page is doing something wrong. It might be dense, dull, off-topic, or the natural place a reader decides they have seen enough. A cliff is the clearest signal a funnel gives you: it points at the exact page where your audience leaves.

### A gentle slope = normal attrition

A steady, gradual decline is healthy and expected. Not everyone finishes a long document, and a few readers will peel off at every page no matter how good it is. If the line eases down smoothly with no sudden drops, your content is holding attention about as well as it reasonably can. Do not chase a flat line; it almost never exists.

### A bump back up = re-reading

Occasionally a page shows more reads than the page before it, which looks impossible in a pure funnel. It usually means people are jumping back to re-read something - a pricing table, a key chart, a summary - or navigating non-linearly. A bump is an interest signal: that page is pulling people back to it.

## What to do about it

A funnel is only useful if it changes what you do next. Once you can see the drop-off, the fixes are concrete:

- Fix the page where everyone leaves. If one page is a cliff, rewrite it, split it, or cut it. It is costing you more readers than any other page.
- Move the key slide earlier. If your most important point sits on page 18 but only a quarter get there, it is reaching almost no one. Put it where the audience still is.
- Shorten the document. If the funnel collapses after page 10, a 20-page deck might really be a 10-page deck. Trim to the part people actually read.
- Reorder around the bumps. If a page pulls people back, lead with it - readers are telling you what they care about.

## How it differs from a marketing funnel

If you have seen a sales or web conversion funnel, the read-through funnel will look familiar but it is not the same thing. A marketing funnel measures steps in a process - visited the landing page, clicked sign up, added a card, completed checkout - and each step is a different action a person chooses to take. A read-through funnel measures pages in a single document, and the only action is continuing to read.

Put simply: a conversion funnel is about clicking through stages, a read-through funnel is about reading through pages. One tracks whether someone advances toward a purchase; the other tracks how far someone's attention carries through a piece of content. They share the funnel shape - high at the top, narrowing toward the bottom - but they answer completely different questions.

## How to get a read-through funnel on your own PDF

You cannot get a funnel from a PDF you email as an attachment - once the file leaves your hands there is nothing measuring the reading. The funnel comes from sharing the document through a viewer that records each page turn, then aggregates those page turns into the chart. That is exactly what EveryPage does: upload a PDF, share the link, and it builds the read-through funnel automatically as people read.

Alongside the funnel you get per-page reading time, so you can tell a page that was genuinely read from one that was flipped past in two seconds. And it does this without storing a single reader IP address - visitors become stable, pseudonymous identities via a one-way hash, so you get the insight without tracking people. There is a free plan to try it on your own document, and the funnel lives inside the readership report.

## Step by step: get a read-through funnel

1. Upload your PDF at everypage.co - no account needed to try it.
2. Copy the share link (or grab the QR code or embed code) and send it the way you normally would.
3. Open your readership report and find the read-through funnel - it fills in as people read.
4. Look for the cliffs: the pages where the percentage drops most are the pages to fix first.
5. Cross-check with per-page reading time to separate pages that were read from pages that were skimmed.
6. Edit, reorder, or shorten, re-share, and watch whether the funnel flattens out.

## Related reading

See how PDF tracking works in practice, explore the full readership report, or learn how to see who read your PDF.

See where your readers drop off.

---
URL: https://everypage.co/guides/sales-proposal-pdf-tracking
Title: How to Track If a Sales Proposal PDF Was Read | EveryPage
Description: Track whether a prospect read your proposal, which page they lingered on, and when to follow up - page by page, no IP storage.

# How to track if a sales proposal PDF was read

By Nick · Updated 25 July 2026

You sent the proposal. The reply came back: "Thanks, we're reviewing this internally." Then nothing. A week passes. Did anyone actually open it? Did the decision-maker get past the cover page, or stall on pricing? Without a signal, you're guessing - and guessing badly timed follow-ups is how good deals go cold.

## The problem with emailing a proposal as an attachment

A PDF attachment is a dead end for sales intelligence. Once it leaves your outbox it opens on someone's device, in their reader, with no line back to you. You learn nothing about whether it was read, skimmed, or left unopened in a thread. The deal is moving (or dying) and you're the last to know.

People reach for email read receipts to fill the gap, but they answer the wrong question. A read receipt - if it isn't blocked outright by the recipient's mail client - confirms the email was opened. It says nothing about the attachment. And even where a tracking pixel reports an "open," opened is not read. A prospect who glanced at your subject line and a prospect who spent four minutes on your pricing page look identical to a pixel. In sales, that distinction is the whole game.

## Share the proposal as a tracked link instead

To know what happens inside the document, the proposal has to open through something that can measure the reading. That means sharing a link to a hosted viewer rather than attaching the raw file. Upload the proposal once, send the link in your follow-up email, and the document opens inside an instrumented viewer where every page turn is a data point.

EveryPage is built for exactly this. You get a page-by-page readership report on the proposal you sent: a read-through funnel showing the percentage of readers who reached each page, the time spent on each one, whether the same reader came back, and where the read came from. It's the same approach that powers PDF tracking across the product. There's a free plan - 3 PDFs, up to 20MB each - so you can try it on a live proposal today.

## What page-by-page analytics tell you about buying intent

A view count is a vanity metric; a read-through funnel is a story about your deal. Imagine you send a 20-page proposal and the funnel comes back: 100% reached page 1, 78% reached page 6, 52% reached page 12, and 24% reached page 20. For example, if your pricing sits on page 12, you now know just over half the readers got that far - and a quarter read all the way to the terms on the final page. That last group is your most engaged audience.

Per-page reading time adds the second dimension. A prospect who lingered on the pricing page was weighing the numbers, not skimming. A page everyone flipped past in two seconds was skipped. Those signals tell you what the prospect actually cares about, so your follow-up can speak to it directly instead of repeating the pitch.

### A second returning reader is the forward

Returning-reader detection is one of the strongest signals you'll get. When a distinct second reader opens the same link, the proposal has almost certainly been forwarded internally - your champion is socialising it with the people who sign off. A read that arrives a day later, from a fresh reader, on the pricing and terms pages is a buying committee forming in real time.

Source attribution rounds it out, showing whether a read came from your direct link, a QR code, an email, or an embed - useful when the same proposal goes out through more than one channel.

## Timing the follow-up while it's warm

The hardest part of a follow-up isn't the message - it's the moment. Reach out too early and you're nagging; too late and the deal has cooled. A return visit removes the guesswork. When a prospect comes back to the proposal a few days after the first read, that's intent: they're reconsidering, comparing, or building the internal case. That's the moment to pick up the phone.

The page they returned to tells you what to lead with. Someone who reopens to the pricing page has a budget conversation in mind; someone re-reading the scope wants reassurance on delivery. You arrive in the conversation already knowing what's on their mind, which is the difference between a check-in and a close.

## Fitting it into your sales workflow

None of this requires changing how you sell. Drop the tracked link into your CRM or your outreach sequence in place of the attachment, send it as you normally would, and watch the reads land in your readership report. The link works anywhere a link works.

When you want the signals to drive action automatically, EveryPage has an API with API keys and OAuth 2.0, plus a Zapier app. You can pull readership events into your own tooling, or wire a Zap so a return visit creates a follow-up task, posts to your sales channel, or pings the rep who owns the account. The buying signal arrives where your team already works, while it's still warm.

## Privacy: no IP stored

Tracking a proposal shouldn't mean surveilling the people reading it. EveryPage never stores a visitor's IP address. Each reader becomes a stable, pseudonymous identity via a one-way hash, so you can tell a returning reader from a new one without ever holding anything that identifies the person. Files are encrypted at rest with AES-256-GCM. You get the buying signals; your prospects keep their privacy.

## Step by step: track a sales proposal

1. Upload your proposal at everypage.co - no account needed to try it on a free plan.
2. Copy the share link and send it from your CRM or outreach email in place of the attachment.
3. Open your readership report and watch the read-through funnel, per-page time, returning readers, and source attribution update as the prospect reads.
4. Optionally require an email before the proposal opens, set a password, or schedule the link to expire after the deal closes.
5. Trigger follow-ups automatically by wiring readership events into the API or Zapier - so a return visit becomes a task, alert, or message.

On the free plan you get summary reads; the Basic plan ($9) unlocks the read-through funnel, trends, and per-page stats; the Pro plan ($29) adds pseudonymous reader identities, an email-capture gate, and CSV export for the full picture on a proposal.

## Related reading

See the basics of how to see who read your PDF, the same playbook applied to sending a pitch deck, or how PDF tracking works in practice.

Know when your next proposal gets read.

---
URL: https://everypage.co/guides/pitch-deck-investor-analytics
Title: Send a Pitch Deck & Know If Investors Read It | EveryPage
Description: Know whether investors opened your deck, how far into the financials they got, and whether they came back - all without storing reader IPs.

# How to send a pitch deck and know if investors read it

By Nick · Updated 4 August 2026

You sent the deck to a dozen investors and heard nothing back. Did they open it? Skim it? Stop on the team slide? When the reply is silence, you are left guessing - and guessing is a terrible way to run a raise. Here is how to turn that silence into signal - so you can tell an investor who skimmed the first slide from one who read to the end and is quietly weighing it up.

## Why investors go silent

Silence almost never means "no, and here is why." It usually means one of three things, and they look identical from your side of the inbox. The investor opened the deck, skimmed it in ninety seconds, and moved on. Or they forwarded it internally to a partner or analyst and are waiting to hear back. Or they never opened it at all - it slid down the inbox under twenty other founders' decks.

Each of those needs a completely different follow-up. The skim wants a sharper hook. The internal forward wants patience and an offer to answer questions. The unopened deck just wants a better subject line and a resend. Without knowing which one you are dealing with, every follow-up email is a shot in the dark.

It gets worse the more investors you talk to. A raise is a pipeline, and a pipeline you cannot see is a pipeline you cannot manage. When ten conversations all read as "no reply," you have no way to rank them, no way to decide who deserves a second nudge and who has quietly passed. You end up spending equal energy on the warmest and the coldest leads, because from the outside they are indistinguishable. The whole point of measuring reading is to put those ten conversations back in order.

## Send a link, not an attachment

The moment you attach a deck to an email, it goes dark. The PDF lands on the investor's device and opens in whatever app they use, with no connection back to you. There is nothing to report an open, let alone how far someone read or whether they came back for a second look. An attached deck is a message in a bottle.

A tracked link reports back. When the deck opens inside an instrumented viewer, every page turn becomes a data point: which slides were seen, how long each one held attention, where people dropped off, and whether the same reader returned. This is the same principle behind tracking a sales proposal or simply how to see who read your PDF - you share a link to a hosted viewer instead of the raw file, and the file starts telling you what happens after you hit send.

A link has a second advantage that matters during a raise: the deck stays yours. An attachment is a copy that lives forever on someone else's drive, frozen at the moment you sent it. A link points at a document you still control, so you can fix a typo, swap an outdated number, or expire the link entirely once the conversation has moved on. You are sending access to the current deck, not scattering stale copies across a dozen inboxes.

## What a read-through funnel reveals about interest

A view count is a vanity metric. A read-through funnel is a story about how far your deck carried the reader. Imagine you send a 20-slide deck and the funnel comes back like this: 100% reached page 1, 78% reached page 6, 52% reached page 12, and 24% reached page 20.

In one glance you know the shape of the read. Almost everyone got past the opening, roughly half made it through the middle, and a quarter reached the end. The numbers tell you where attention is leaking. If page 6 is your problem slide and the deck falls from 78% to 52% by page 12, that middle stretch is where you are losing the room, and that is the section to tighten before the next send.

The funnel also reframes a quiet inbox. If 24% of readers reached the last slide, those readers are not ignoring you - they finished the deck and are deciding. That is a very different situation from a deck nobody opened, even though both look like silence from the outside. The same funnel that flags your weak slides also tells you which conversations are still alive, and that second insight is the one that decides where your follow-up energy goes.

## Reading the signals

The funnel tells you how far people got. Per-page reading time tells you what they cared about. Together they let you read investor intent without a single reply.

- Long time on the financials and traction slides is the signal you want. When someone parks on the numbers, they are doing diligence in their head, not skimming. That is real interest.
- A drop at the team slide is a different conversation. It does not mean the team is the problem, but it tells you the reader stopped engaging at the point where you ask them to bet on people, and that is worth addressing directly in the follow-up.
- A returning reader is often the strongest signal you will get. A second visit means the deck earned a place in someone's mind worth revisiting - frequently a sign it is being shared internally or reread before a partner conversation.

Source attribution adds one more layer. Knowing whether a read came from your direct link, a QR code, an email, or an embed tells you which channel is actually putting the deck in front of decision-makers. If most of your meaningful reads come through forwarded links rather than the address you sent it to, that is a clue your deck is travelling past the first contact and into the firm - exactly where you want it.

None of these signals is a verdict on its own. A single skim does not mean rejection, and a long dwell does not guarantee a cheque. The value is in the pattern across all your readers: which slides consistently hold attention, which one consistently loses people, and which readers keep coming back. Read the trend, not any one event.

## Using it to prep the follow-up

The point of all this is not to surveil investors - it is to write a better second email. Once you can see how the deck was read, the follow-up almost writes itself.

### Which slide to lead with

If a reader spent real time on the traction slide, lead the follow-up with the metric that held their attention and offer the data behind it. The slide that earned the most time is the slide your reader found most compelling, so open the next message there rather than restating your generic summary. You are picking up the conversation where they left off, not starting it over.

### Which objection to pre-empt

If the deck dropped off sharply at a particular slide, you already know which objection to pre-empt - address it before they have to ask. A consistent drop at the same slide across several readers is the clearest map you will get of where your story stops being convincing. Rework that slide, and in the follow-up, name the concern it raises and answer it head-on.

### When to reach out

And if a reader came back for a second visit, that is your cue to reach out now, while the deck is still on their mind, rather than waiting a polite week. Timing your follow-up to a returning read is the difference between landing in an inbox while interest is hot and arriving after the moment has passed. You are no longer following up blind; you are following up on evidence.

## Privacy: insight without surveillance

Investors are sensitive about being tracked, and rightly so. EveryPage is built so you get the readership insight without storing a single visitor IP address. Each reader becomes a stable, pseudonymous identity - Reader #1, Reader #2, and so on - derived through a salted, one-way hash. The IP is used in flight and then discarded; it is never written down.

So you can tell that Reader #3 came back twice and lingered on the financials, without ever knowing or storing who Reader #3 is at the network level. The deck itself is held under AES-256-GCM encryption. You learn how your deck is being read; you do not build a file on the people reading it.

If you do want a name attached to a read, that is a choice you make deliberately, not a default that quietly logs everyone. The email-capture gate asks each reader for an address before the deck opens, so the readership you see is volunteered rather than harvested. It is a Pro feature, alongside reader identities and CSV export, and it sits on top of the same privacy model: no IPs stored either way. The distinction matters when you are asking investors to trust you with a far bigger relationship than a single PDF.

## Step by step: track a pitch deck with EveryPage

1. Upload your deck at everypage.co - the free plan covers 3 PDFs up to 20MB, so you can try it on a real deck without an account.
2. Copy the share link (or grab the QR code or embed code) and send it to investors the way you normally would.
3. Open your readership report and watch the read-through funnel, per-page reading time, and returning-reader detection update as people read.
4. Optionally require an email before the deck opens so each read is tied to a name - the email-capture gate is a Pro feature, alongside reader identities and CSV export.

See how investors read your next deck.

---
URL: https://everypage.co/guides/gdpr-pdf-tracking
Title: GDPR-Compliant PDF Tracking (No IP Storage) | EveryPage
Description: Track who reads your PDF and stay GDPR-compliant: why IP logging creates liability and how pseudonymous reader IDs avoid storing personal data.

# GDPR-compliant PDF tracking

By Nick · Updated 4 September 2026

You can know who read your document and stay on the right side of the GDPR - but only if the tracking is built to avoid collecting personal data in the first place. Most document trackers do the opposite: they log every reader's IP address, which the GDPR treats as personal data, and hand you a compliance obligation you never asked for. Here's how to track readership the compliant way.

## Is PDF tracking even allowed under GDPR?

Yes - tracking how a document is read is not banned by the GDPR. What the regulation governs is personal data: information relating to an identifiable person. The question is never "can I see who read it?" but "what personal data am I collecting to do so, and do I have a basis to hold it?" If your tracking records readership without collecting personal data, most of the heavy GDPR machinery simply doesn't apply, because there is no personal data to protect.

## The problem: IP addresses are personal data

Under the GDPR and UK GDPR, an IP address is generally personal data - the Court of Justice of the EU confirmed this for dynamic IPs in Breyer. The moment a document tracker stores a visitor's IP, you (the sender) are processing personal data and inherit the obligations that follow: a lawful basis, a defined retention period, the duty to minimise what you keep, and the ability to honour access and erasure requests.

For a freelancer sending a proposal or a founder sharing a deck, that's a lot of liability in exchange for a stat you barely look at - and it compounds with every tool that quietly logs reader IPs. The most reliable way to comply is the simplest one: don't collect the personal data at all. You cannot mishandle, over-retain, or be compelled to produce data you never stored.

## Data minimisation in practice

Data minimisation - collecting only what you actually need - is one of the GDPR's core principles, and it maps perfectly onto document tracking. The job is "understand how my document is read." You do not need a reader's address to do that. You need to recognise a returning reader, know roughly where reads come from, and see which pages held attention - and all of that can be derived without retaining an identifier that points back to a person.

## How EveryPage tracks readership without storing personal data

EveryPage is built for this. Instead of storing the IP, each reader's address is run through a salted one-way hash the moment a read happens, producing a stable pseudonymous identity (Reader #214). The hash can't be reversed back to the address, and the salt is a server secret, so the stored identity is meaningless to anyone who might come across it - yet it's stable enough to tell you the same reader came back three times. The IP itself is used only to resolve a country in-flight, then discarded. The detailed mechanism is in how to share a PDF without storing reader IP addresses.

On top of that, links expire on a schedule you set and the encrypted file is swept from disk shortly after - so there's no indefinite retention - and readership is measured first-party inside the viewer, with no third-party tracking scripts or cross-site cookies riding along on your document.

## When a reader chooses to identify themselves

Sometimes you do want a name - which investor opened the deck, which client read the contract. EveryPage's optional email gate asks the reader to enter an email before the document opens. That is the reader consciously providing their data, which is a very different basis from quietly harvesting an address they never agreed to share. You collect a name because they chose to give it, you tell them why, and everything else stays pseudonymous.

## Who is the controller - and who is the processor?

GDPR-conscious buyers usually ask this first, so here it is plainly. When you share a document through EveryPage, you are the controller of the readership data collected on your behalf: you decide what to share, who gets the link, whether it expires, and whether readers must identify themselves. EveryPage acts as your processor for that data - we hold it and show it to you, and we don't use it for purposes of our own. (For your account details - your email, your subscription - EveryPage is a controller in the ordinary way any service is.)

What makes the split unusually light here is how little sits inside it. For an ungated link, the readership processed on your behalf is a salted hash, page numbers, reading time, and a country - pseudonymised by design before anything is written down. Personal data really enters the picture at the email gate, where a reader types an address they know you will see. That address is yours to answer for as controller: collect it because you need it, and say why.

On paperwork, honestly: our processing commitments live in the terms and privacy policy; EveryPage doesn't currently publish a separate standalone DPA for countersigning. If your organisation's procurement requires one, talk to us. Either way, remember what a DPA actually governs - the personal data a processor holds for you - and that the design here keeps that set unusually small.

## Where your data lives: residency and sub-processors

EveryPage is built and operated from the United Kingdom, so processing sits under the UK GDPR - a regime the EU has formally recognised as adequate, meaning personal data can flow from the EU to a UK-operated service without additional transfer safeguards. The service itself runs on a deliberately small stack of servers we administer directly, not a sprawl of managed cloud products each holding a copy of your data.

Fewer moving parts also means a short sub-processor list, kept current in the privacy policy: Stripe handles subscription billing, a transactional-email provider sends verification and notification emails, and a geolocation service resolves a reader's country in transit - the address is used for that lookup and then discarded, never stored. Traffic to everypage.co passes through Cloudflare's network on its way to our servers. Even our own site analytics follow the same posture: a self-hosted, cookieless analytics instance measured first-party, so reading this page doesn't ship your visit to an analytics company either.

## Breach notification - and what a breach could even expose

Under the GDPR and UK GDPR, a processor must tell the controller about a personal-data breach without undue delay, and a controller must assess whether to notify the regulator within 72 hours. Those duties apply to EveryPage like anyone else: if an incident ever touched data we process for you, we would tell you promptly so you could meet your own clock.

The more useful question is what a breach here could actually expose. Documents are encrypted at rest with AES-256-GCM, each user's files under their own key, and readership rows contain pseudonymous hashes, page numbers, timings, and countries. A copied database would not contain a single reader IP address, because none was ever stored - you cannot leak what you don't hold. The email addresses collected by gates you enabled are the main personal data at stake, and that is exactly the set you knowingly chose to collect.

One thing we won't do is dress this up in acronyms. EveryPage is a small UK operation, not an enterprise compliance programme, and doesn't currently hold certifications such as SOC 2 or ISO 27001. What we can tell you precisely - and what this page tries to do - is what is stored, how it is protected, and what isn't there at all. For breach exposure, that last part is the one that matters.

## Retention and deletion, on your terms

Storage limitation - not keeping data longer than the job needs - is the GDPR principle retention policies answer to, and EveryPage turns it into a control rather than a policy document. You decide how long a document stays live: set an expiry and the link stops serving the moment it passes, with the encrypted file swept from disk shortly after; or keep a document up indefinitely on any plan, because plenty of documents are meant to stay published. Retention matches the document's job, and you set it.

Deletion is equally direct: remove a document whenever you like, and deleting your account removes the account and its files with it. Pseudonymity pays off on the rights side too. For an ungated read there is no stored identifier that maps back to a person, so there is nothing to dig out of a log when someone asks what you hold on them - the scope of a subject-access request shrinks to the email addresses you deliberately collected through a gate.

## A practical compliance checklist

1. Use a tracker that doesn't store reader IP addresses (or other raw identifiers).
2. Know your role: for reader data collected on your behalf, you are the controller and your tracking tool is your processor.
3. Set links to expire so readership data isn't retained indefinitely.
4. Only ask readers for an email (or other personal data) when you genuinely need it - and tell them why.
5. Keep your privacy policy honest about what is and isn't collected.
6. Prefer first-party measurement over embedded third-party trackers and cookies.

This guide explains the principles in general terms and is not legal advice; check your own obligations for your situation.

## Related reading

See how to share a PDF without storing reader IP addresses, the full readership features, or why DocSend-alternative searches lead here (DocSend stores IPs; EveryPage doesn't).

Readership insight, without the liability.

---
URL: https://everypage.co/guides/track-pdf-email-attachment
Title: How to Track a PDF Sent by Email | EveryPage
Description: You can't track a raw PDF email attachment - send a tracked link instead and see who opened it, how far they read, and when. No IP storage.

# How to track a PDF sent by email

By Nick · Updated 4 August 2026

You emailed a proposal, a quote, or a deck as a PDF attachment - and now you're staring at your inbox wondering if anyone opened it. The honest answer is that a raw email attachment can't really be tracked. But there's a simple change that gives you exactly what you want: who opened it, how far they read, and when.

## Can you track a PDF attachment in an email?

Not meaningfully. Once a PDF leaves as an attachment, it's a copy sitting on the recipient's device, opened by whatever PDF app they use - there's no connection back to you. The closest thing is an email open pixel, and that only tells you the email was previewed, not whether the attachment was opened, and it breaks the moment images are blocked or the mail is forwarded. For the actual document, an attachment goes dark the instant you hit send.

## The fix: send a tracked link instead of an attachment

The trick is to stop attaching the file and start sharing a hosted link to it. The recipient clicks the link and reads the document in their browser - which means there's a viewer in the middle that can measure the read. You send a link exactly the way you'd send an attachment; they don't need an account or anything installed; and you get a readership report instead of silence.

As a bonus, a link sidesteps the things that make PDF attachments annoying: no bouncing on attachment size limits, no "this message was quarantined," and you can update or expire the document after sending.

## What you can see once it's a link

- Whether they opened it - and when, in real time.
- How far they read - the read-through funnel shows the percentage who reached each page.
- Time on each page - the difference between read and skimmed.
- Returning reads - when the same person comes back, a strong interest signal.
- A view notification - an email to you the moment it's opened, so you can time the follow-up.

## Step by step

1. Upload your PDF at everypage.co - no account needed to try it.
2. Copy the share link (or use share-by-email to send it with a note).
3. Paste the link into your email instead of attaching the file.
4. Watch the readership report - who opened it, which pages, how long - and turn on a view notification if you want a ping on first open.

## Without spying on the reader

Tracking a link doesn't have to mean surveilling the person who opens it. EveryPage measures readership without storing the reader's IP address - each reader is a stable pseudonymous ID, not a logged address - so you get the engagement signal without holding personal data. More on that in how to share a PDF without storing reader IP addresses.

## Related reading

See the basics of how to see who read your PDF, the same playbook for a sales proposal, or how PDF tracking works.

Send a link, not an attachment.

---
URL: https://everypage.co/guides/consultant-pdf-tracking
Title: Track If Clients Read Your Deliverables | EveryPage
Description: Send reports and decks as tracked links and see which sections clients read before the review call - returning reads, per-page time, no stored IPs.

# Track whether clients read your deliverables

By Nick · Updated 4 August 2026

You send a report, an audit, or a strategy deck - the work the engagement was for - and then hear nothing until the review call, where it becomes clear who actually read it and who is skimming the summary live. Tracking your deliverables turns that blind spot into a quiet signal you can act on before the call, not during it.

## Why deliverable tracking is different from sales tracking

A sales proposal is read once and either wins or doesn't. A consulting deliverable is reference material: it gets opened, set aside, returned to, and shared with stakeholders who weren't on your calls. The useful signal isn't just "did they open it" - it's which sections the client and their team actually engaged with, and whether the document kept circulating after you sent it.

## What to watch on a deliverable

- Pre-call confirmation. Before a readout, a quick check of whether the client opened the document tells you whether to walk through it or assume they've read it.
- Which sections landed. The read-through funnel and per-page time show whether they read the methodology or jumped to recommendations - so you lead the call where their attention already is.
- Internal circulation. Returning reads and new readers suggest the deliverable is being passed around the client's org - the moment to offer a follow-on or a stakeholder session.
- Appendix engagement. If nobody reaches the appendix where the detailed evidence lives, that's a structure problem worth fixing in the next deliverable.

## Do it without surveilling the client

Consulting runs on trust, and logging a client's IP addresses is a bad look (and a data-protection liability). EveryPage measures readership without storing any IP address - readers are pseudonymous IDs, not logged people - so you get the engagement signal while keeping the relationship clean. If a specific stakeholder's name matters, the optional email gate lets them identify themselves rather than you harvesting it. More in sharing a PDF without storing reader IPs.

## Step by step

1. Upload the deliverable at everypage.co and send the tracked link instead of an attachment.
2. Set an expiry that matches the engagement, and a password if the content is sensitive.
3. Turn on a view notification so you know the moment the client opens it.
4. Check the readership report before the review call and steer the conversation accordingly.

## Related reading

See the basics of how to see who read your PDF, the same idea for a sales proposal, or a pitch deck.

Know if your work was read.

---
URL: https://everypage.co/guides/embed-pdf-tracking-analytics
Title: Embed a PDF on Your Website & Track Who Reads It | EveryPage
Description: Put a PDF on your web page with a tracked viewer: see how far visitors read, which pages held them, and who returned - with no stored IP addresses.

# Embed a PDF on your website and see who reads it

By Nick · Updated 25 July 2026

Dropping a PDF onto a web page is easy. Knowing whether anyone actually read it once it is there is the hard part - a plain embedded PDF is a black box. With a tracked embed you keep the document on your own page and see how far visitors read, which pages held them, and who came back.

## Why a normal embedded PDF tells you nothing

The usual ways to put a PDF on a site - a download link, a Google Drive preview, or a raw <iframe> to the file - all stop at "the file loaded." You cannot tell a three-second glance from a careful read, you cannot see which section lost people, and a download link hands the file over entirely, after which the visitor is invisible. For a whitepaper, a product spec, or a report that is meant to do a job, that is the most important part left unmeasured.

## How a tracked embed works

EveryPage gives every uploaded PDF an embeddable viewer at its own /embed/ URL. You paste a small iframe onto your page and the document renders inline, styled to sit in your layout. Because the viewer is the thing rendering the pages, it records the same readership signals you would get from a shared link - page by page - without the visitor leaving your site or downloading anything.

## What you can see

- Read-through, not just opens. The read-through funnel shows the share of visitors who reached each page, so a long document's drop-off is visible.
- Time per page. Every page turn is timed, so you can tell a skim from a genuine read and see which section earned the most attention.
- Returning readers. Someone coming back to the embedded document is a strong interest signal - useful for a pricing sheet or a spec a buyer keeps revisiting.
- Aggregate, across every embed. Because the viewer reports centrally, the same file embedded on several pages still rolls up into one readership report.

## Without surveilling your visitors

A tracked embed should not mean tracking people. EveryPage measures readership without storing any IP address - each visitor is a pseudonymous, salted hash, so you get returning-reader detection and per-page engagement without holding personal data or needing a cookie banner for it. That matters more, not less, when the document lives on a public page. More on the approach in sharing a PDF without storing reader IPs.

## Step by step

1. Upload your PDF at everypage.co.
2. Open the file's sharing options and copy the embed snippet (the /embed/ iframe).
3. Paste it into your page, post, or CMS block where you want the document to appear.
4. Watch the readership report fill in as visitors read - no extra setup on your site.

## Related reading

See the fundamentals in how to see who read your PDF, or how the same tracking works for a sales proposal sent as a link rather than an embed.

Embed a PDF and watch it get read.

---
URL: https://everypage.co/guides/document-engagement-score
Title: What Is a Document Engagement Score? | EveryPage
Description: A document engagement score combines read-through, time per page, completion, and return visits into one honest measure of whether a document landed - no stored IPs.

# What is a document engagement score?

By Nick · Updated 25 July 2026

A document engagement score is a single read on how much a reader actually engaged with a document, combining several signals - how far they read, how long they spent, and whether they came back - into something more honest than a view count. It answers the question a raw "opened" can't: did this land?

## Why a view count lies

"12 views" feels like information, but it flattens a careful cover-to-cover read and an accidental two-second open into the same number. It says nothing about where attention went or where it fell off. Two documents with identical view counts can have completely different fates - one read in full by the right person, the other abandoned on page one - and a view count can't tell them apart. An engagement score exists to recover that lost detail.

## The signals that make it up

- Read-through depth. How far into the document the reader got. The read-through funnel turns this into a per-page picture, so you see exactly where interest drops.
- Time on page. Dwell time per page separates a skim from a read. A long page with three seconds on it was scrolled past; the same page with ninety seconds was studied.
- Completion. Reaching the final page - the ask, the pricing, the recommendation - is often the signal that matters most.
- Return visits. A reader who comes back, or forwards the document so a new reader opens it, is showing more intent than any single session reveals.

## Reading the signals together

No single number is the whole story, and that is the point - engagement is a shape, not a scalar. High completion with low dwell time means the document was easy to skim but maybe too thin; deep dwell that stops halfway means a strong opening that lost the thread; repeat visits to one specific page point straight at what the reader cares about. The value is in combining them: a proposal read to the last page, slowly, then reopened the next morning is a buying signal a view count would have hidden.

## Measuring it without tracking people

Engagement scoring sounds invasive, but it doesn't have to identify anyone. EveryPage records every one of these signals without storing an IP address - each reader is a pseudonymous, salted hash, which is enough for stable returning-reader detection and per-page timing without holding personal data. You learn how the document performed, not who the people are. See sharing a PDF without storing reader IPs for how that works.

## Putting it to work

Use the engagement picture to decide your next move: follow up with the investor who reread your deck, rework the section of a sales proposal where everyone drops off, or lead a client call with the section they actually studied. The score is only useful if it changes what you do next - so read it, then act on it.

See how your documents actually perform.

---
URL: https://everypage.co/guides/docsend-vs-everypage-vs-pandadoc
Title: DocSend vs EveryPage vs PandaDoc Compared | EveryPage
Description: How three document-tracking tools compare on page analytics, privacy, pricing model, and e-signature - and which fits which workflow.

# DocSend vs EveryPage vs PandaDoc: document tracking compared

By Nick · Updated 4 August 2026

These three tools all touch documents, but they are built for three different jobs. One is for private page-by-page readership on a single PDF, one is for data rooms inside the Dropbox world, and one is for proposals and e-signature. Picking the wrong one means paying for features you will never open. Here is how they line up - and how to choose.

|  | EveryPage | DocSend | PandaDoc |
|---|---|---|---|
| Primary job | Private page-level readership on a single PDF | Document sharing & data rooms | Proposals, contracts & e-signature |
| Page-by-page analytics | Yes - per page, read-through funnel | Page-level analytics | Document open & completion tracking |
| Stores visitor IPs | No - pseudonymous reader IDs only | Yes - full visitor tracking | Yes - visitor tracking |
| E-signature | No | Limited | Yes - core feature |
| Virtual data room | No | Yes | No |
| Free plan | Yes - 3 PDFs, full core readership | Limited free tier | Limited free e-sign tier |
| Pricing model | Flat per account - $9/month | Per user - $15/user/month (Personal); $65/user/month (Standard) | Per user - typically higher |

DocSend details per docsend.com; PandaDoc positioning per pandadoc.com, June 2026. Check current pricing on each vendor's site.

## EveryPage is for private, page-level readership

EveryPage does one thing: you upload a single PDF, share the link, and see who actually read it - page by page. You get a read-through funnel showing the percentage of readers who reached each page, per-page reading time, returning-reader detection, and where each read came from. It is the tool for a proposal, a report, or a pitch deck when the only question that matters is "did they read it, and how far did they get?"

Two things set it apart. Pricing is flat: $9/month on Basic, not per seat, so the bill does not climb with your team. And it never stores a visitor IP - each reader is reduced to a salted one-way hash, so you get stable returning-reader detection without holding personal data. There is a free plan to try it on your own document first.

## DocSend is for data rooms and the Dropbox world

DocSend, now part of Dropbox, is built for teams that share documents at scale and need a virtual data room: folder-level permissions, multi-file deal spaces, and document analytics inside the Dropbox ecosystem with enterprise SSO. It bills per user - $15/user/month on Personal and $65/user/month on Standard - and, like most analytics tools, records visitor IP addresses as part of its tracking. If your workflow is fundraising, M&A, or any process where you hand a counterparty a folder of files behind one secure space, DocSend is the natural fit.

## PandaDoc is for proposals and e-signature

PandaDoc is a different category again. It is a document automation platform built around proposals, quotes, contracts, and legally binding e-signature, with a template library, approval workflows, and CRM integrations. The point is not just to see who opened a document - it is to get a deal drafted, sent, signed, and back in one place. It uses per-user pricing that is typically higher than the others here, and pricing changes often, so check pandadoc.com for the current numbers. If you need a signature on the way out the door, PandaDoc is the one of the three that delivers it.

## The pricing math for a three-person team

Pricing model matters more than headline price once you have more than one person sharing documents. EveryPage is flat per account: a three-person team pays $9/month total on Basic, because billing is not tied to seats. Per-user tools multiply by headcount instead. DocSend's Personal plan at $15/user/month works out to $45/month for three people, and the Standard plan at $65/user/month reaches $195/month for the same three.

PandaDoc is also per user and typically priced higher than DocSend's entry tier, so a three-seat bill there will land above the EveryPage figure as well - check pandadoc.com for the exact rate. The pattern is the same in every case: flat pricing stays put as you add people, while per-seat pricing climbs before your usage does.

## Privacy: only one avoids storing IPs

If you would rather not log your readers' IP addresses - because of GDPR, a security policy, or a principle - this is the clearest line between the three. DocSend and PandaDoc both record visitor IPs as part of their tracking. EveryPage never stores one: each reader becomes a salted one-way hash, country is resolved in-flight and the address is discarded immediately. You still get stable returning-reader detection, but there is no personal data sitting in a log for you to explain in a data-processing review. For EU and UK teams, that is one less thing to account for.

## The verdict: which fits which workflow

An honest comparison points in three directions, because these are three different tools:

- Need e-signature, proposals, or contract workflows? Choose PandaDoc. Neither of the others is built to get a document signed.
- Need a virtual data room, or you already live in Dropbox? Choose DocSend. Folder permissions and multi-file deal spaces are its home turf.
- Need cheap, private, page-level readership on a single PDF? Choose EveryPage. Flat $9/month, no IP storage, and a read-through funnel that tells you how far people actually read.

They overlap on the surface - all three can tell you a document was opened - but the right pick comes down to the job around that signal. See the full readership features, how PDF tracking works, or read the deeper DocSend alternative breakdown.

See who reads your next PDF.

---
URL: https://everypage.co/guides/wordpress-pdf-plugin
Title: Track PDFs in WordPress: the EveryPage Plugin | EveryPage
Description: Install the EveryPage WordPress plugin, connect with an API key, and share trackable PDF links with readership analytics - right from wp-admin.

# Track PDFs in WordPress

By Nick · Updated 4 September 2026

The EveryPage plugin turns the PDFs on your WordPress site into tracked documents: embed them in posts with the EveryPage Document block - flipbook, swipe, and magazine modes included - share them straight from the Media Library, and see who read them, all without leaving wp-admin. Readership depth and link controls follow your EveryPage plan. See the WordPress plugin overview for the full feature catalogue.

## What you need

- A WordPress site (6.6 or newer) where you can install plugins.
- A free EveryPage account.
- An EveryPage API key - create one under Account → API keys (it starts with ep_live_). Treat it like a password.

## Install the plugin

1. In wp-admin, go to Plugins → Add New and search for EveryPage.
2. Click Install Now, then Activate.
3. Prefer to install by hand? The listing is at wordpress.org/plugins/everypage - download the zip and upload it under Plugins → Add New → Upload Plugin.

## Connect your account

1. Go to EveryPage → Settings in the wp-admin sidebar.
2. Paste your API key and save. The plugin runs a connection test so you know it's linked.

The key is stored in your site's options table and is only ever sent to everypage.co over HTTPS. You can revoke it anytime from your EveryPage account.

## Embed a tracked PDF in a post

1. In the editor, add the EveryPage Document block and pick a document - or upload one right from the block.
2. Choose how it renders: the inline viewer in Standard, Flipbook, Swipe, or Magazine mode, or a tracked button or text link.
3. Style the viewer in the block sidebar - the appearance options include picking up your theme's colours, so the embed looks native to your site.
4. Using the classic editor or a page builder? The shortcode [everypage uuid="..."] places the same tracked viewer anywhere shortcodes go.

## Share from the Media Library

1. In the Media Library, use the Share via EveryPage row action on any PDF (or select several and use the bulk action). A modal hands back the tracked link, QR code, and embed snippet.
2. Old posts linking straight to media-library PDFs? The replace links in content tool finds those raw links and swaps them for tracked ones - run the dry run first to preview every change.
3. Each file has a settings drawer in wp-admin covering everything your plan includes: viewer customisation, expiry rules, the download toggle, and protection toggles - with passwords and view notifications on Basic, and the email gate and vanity slugs on Pro.

## Read the readership

1. Your files are listed with view counts and expiry; open the full per-file readership report - page-by-page read-through and reading time - with one click.
2. The Recent reads dashboard widget shows the latest activity - file, reader country, pages read, and when.

## What data is sent

When you upload a PDF, the file is sent to your EveryPage account to create the share link. When you view files or analytics, the plugin makes authenticated requests with your API key. Nothing is sent until you take one of those actions, and the plugin contacts no other service. See the privacy details for specifics.

## Questions

### Is the EveryPage WordPress plugin free?

The plugin is free to install. Readership depth and password protection follow your EveryPage plan - expiry, including never-expire, is on every plan - and the free plan covers core readership on up to 3 PDFs.

### Where are my PDFs stored - in WordPress or on EveryPage?

On your EveryPage account, encrypted at rest - not in your WordPress media library or on your host. The plugin uploads the file to EveryPage over HTTPS and stores only the resulting share link.

### Does the plugin slow down my site?

No. It only calls EveryPage from wp-admin when you upload or view a file; nothing runs on your public front-end except the optional [everypage] shortcode where you place it.

### Can I track a PDF that is already in my media library?

Yes. Use the "Share via EveryPage" row action (or bulk action) on the file: the plugin uploads it to your EveryPage account and hands back a tracked link, QR code, and embed snippet. The replace-links tool can then swap raw media-library links across your posts for the tracked versions, with a dry run first.

## Related

See the WordPress plugin overview, browse all EveryPage integrations, or learn how to see who read your PDF.

Track your first PDF in minutes.

---
URL: https://everypage.co/guides/zapier-pdf-automation
Title: Automate PDF Sharing with Zapier | EveryPage
Description: Connect EveryPage to Zapier with an API key: turn any file into a trackable PDF link, and fire Zaps when documents are read or leads captured.

# Automate PDF sharing with Zapier

By Nick · Updated 28 August 2026

Connect EveryPage to the 7,000+ apps on Zapier - in both directions. Whenever a PDF lands somewhere - a new file in Google Drive, an email attachment, a form upload - have Zapier send it to EveryPage and hand back a secure, trackable link you can route anywhere. And when your readers act - opening a document, completing the email gate, downloading a copy - EveryPage triggers fire a Zap the moment it happens. See the Zapier integration overview for the full trigger and action catalogue.

## What you need

- A Zapier account.
- A free EveryPage account.
- An EveryPage API key from Account → API keys.

## Connect EveryPage

1. In the Zap editor, add EveryPage as an action app.
2. When prompted to connect an account, paste your EveryPage API key. Zapier verifies it and remembers the connection for future Zaps.

## Actions: from any app to a tracked link

The core action is Upload PDF & get tracking link. Map your trigger's file to it (most file apps expose the PDF directly) and optionally set the filename and protections. The action uploads the PDF to your EveryPage account and returns the share URL, QR code, embed code, and file ID, which you can use in any later step. Further actions update a document's settings (including its expiry rules), find a file by name, mint per-recipient link variants (Pro), replace the content behind a live link (Pro), pull an analytics summary, or delete a file.

## Triggers: know the moment it gets read

Triggers run the other way: reader activity in EveryPage starts the Zap. Most deliver instantly - EveryPage pushes the event to Zapier the moment it happens, rather than waiting for a polling cycle.

- New Document Read - a reader opened your document, with pages viewed and reading time. Available as polling or instant.
- New Form Fill / Email Gate Capture (Pro) - a lead completed your email gate or capture form; the fields arrive ready to map into your CRM.
- New Download - a reader saved a copy.
- Link Expired / Self-Destructed - a link reached the expiry date or view budget you set for it.
- New Reader Comment and Receipt Confirmed - feedback and proof of delivery, pushed as they happen.

The lead-capture pairing is the one to know: put an email gate in front of a document, and the New Form Fill trigger posts each captured lead straight into HubSpot, Salesforce, or any CRM on Zapier - while the lead is still reading.

## Example Zaps

- New form fill on a gated whitepaper → create a HubSpot contact with the captured fields.
- New document read → Slack DM to the deal owner naming the document and how far they got.
- New PDF in a Google Drive folder → upload to EveryPage → email the tracked link with Gmail.
- New row in Google Sheets → create a link variant labelled with that recipient.
- Deal marked Closed-Lost in the CRM → update file settings to expire the proposal link.
- New download → append a row to a spreadsheet.

## What data is sent

Actions send the PDF you map to them to your EveryPage account over HTTPS, authenticated with your API key. Triggers deliver the reader events you subscribed to - document, timestamp, and the readership fields your plan reports - to your Zapier account. Nothing else is shared. See the privacy details.

## Questions

### What can I automate with EveryPage and Zapier?

Any workflow that produces a PDF - or reacts to one being read. Upload documents from Drive, Gmail, or a form and route the tracked link anywhere; and fire Zaps from reader activity: a document read, a lead captured through the email gate, a download, a comment, a confirmed receipt, or a link reaching the expiry rule you set.

### Is there a trigger for when a PDF is read?

Yes. The New Document Read trigger fires when a reader opens your document, with pages viewed and reading time - available as a scheduled polling trigger or as an instant trigger that pushes the event the moment it happens. Downloads, form fills (Pro), comments, receipts, and link-expiry events have instant triggers too.

### Which Zapier plan do I need?

The triggers and the Upload PDF action work on any Zapier plan, including the free tier. Multi-step Zaps that chain steps across apps require a paid Zapier plan.

### How does EveryPage authenticate in Zapier?

You paste your EveryPage API key (Account -> API keys, starts with ep_live_) when you connect the EveryPage app in Zapier. The integration attaches it only to requests whose host is everypage.co, over HTTPS - when a Zap step fetches your PDF from somewhere else, that download carries no credentials. You can revoke a key anytime from Account -> API keys.

## Related

See the full Zapier integration overview (every trigger, action, and plan detail), browse all EveryPage integrations, or see the developer API the Zapier app is built on.

Put PDF sharing on autopilot.

---
URL: https://everypage.co/guides/browser-extension
Title: EveryPage Browser Extension for Chrome & Edge | EveryPage
Description: Turn any PDF into a tracked EveryPage link with a right-click or the toolbar popup. Install the extension, paste your API key, and share from anywhere.

# The EveryPage browser extension

By Nick · Updated 28 August 2026

Turn any PDF into a tracked EveryPage link without opening the dashboard. Right-click a PDF link on any page, or use the toolbar popup to upload one, and get a secure share link back in a couple of clicks. Works in Chrome and Edge.

## What you need

- Google Chrome or Microsoft Edge.
- A free EveryPage account.
- An EveryPage API key from Account → API keys.

## Install

1. Install from the Chrome Web Store (Chrome) or the Microsoft Edge Add-ons store.
2. Click Add to Chrome (or Get on Edge), then pin the EveryPage icon to your toolbar.

## Connect your account

1. Click the EveryPage toolbar icon and open Options.
2. Paste your API key and save. It's stored locally in the extension and sent only to everypage.co.

## Share a PDF

- Right-click a PDF link on any page and choose Share via EveryPage - the extension uploads it and copies the tracked link.
- Or open the toolbar popup and upload a PDF directly from your computer.

Uploads run through the extension's background worker, so the link comes back without a page reload.

## What data is sent

The extension only contacts everypage.co, and only when you ask it to share a PDF. It sends the PDF and your API key over HTTPS - nothing else, and no browsing data. Full details are in the extension privacy policy.

## Questions

### Which browsers does the extension support?

Chrome and Edge (and other Chromium-based browsers that use the Chrome Web Store). It is built on Manifest V3.

### Does the extension read my browsing history?

No. It acts only on a PDF link you right-click or a file you choose in the popup, and it talks only to everypage.co using your API key. It does not watch the pages you visit.

### Is the extension free?

Yes, the extension is free. Readership depth follows your EveryPage plan, and the free plan covers core readership.

### Do I need an EveryPage account?

Yes - a free account and an API key (Account -> API keys). You paste the key into the extension options once to connect it.

## Related

Browse all EveryPage integrations, or learn how to see who read your PDF.

Share PDFs from anywhere you browse.

---
URL: https://everypage.co/guides/canva-pdf-tracking
Title: Publish a Canva Design as a Tracked PDF Link | EveryPage
Description: Use the EveryPage app for Canva to publish your design as a secure, trackable PDF link - see who opened it, which pages they read, and for how long.

# Publish a Canva design as a tracked link

By Nick · Updated 28 August 2026

The EveryPage app for Canva publishes the design you're working on straight to your EveryPage account as a secure, trackable PDF link. Share it like any other link and see who opened it, which pages they read, and for how long.

## What you need

- A Canva account.
- A free EveryPage account (you connect it once, no API key to copy).

## Connect EveryPage in Canva

1. Open a design in Canva and add the EveryPage app (also reachable from the Share menu as a publish destination).
2. Click Connect EveryPage account and sign in. Canva handles the secure sign-in - there's no key to paste.

## Publish and track

1. Choose your link options: viewer mode (standard, flipbook, swipe, magazine), how long the link lasts, whether downloads are allowed, and an optional password.
2. Click Publish. Canva exports your design to PDF and EveryPage returns a tracked share link.
3. Open the readership report in EveryPage to see who read it, page by page.

## What data is sent

When you publish, Canva exports the open design and EveryPage uploads that PDF to your account over HTTPS. Sign-in uses OAuth 2.0 - EveryPage never sees your Canva password, and the app stores nothing beyond what's needed to create the link. Full details are in the Canva app privacy policy.

## Questions

### How do I share a Canva design as a tracked PDF?

Publish it through the EveryPage app inside Canva. It exports your design to PDF, uploads it to your EveryPage account, and hands back a trackable share link - no manual download-and-upload step.

### Which Canva designs work?

Any design Canva can export as a PDF - presentations, docs, proposals, one-pagers. Multi-page designs keep their pages, so you get per-page read-through on the result.

### Does EveryPage get access to my Canva account?

No. The app works on the single design you choose to publish; it does not browse your Canva projects. You link your EveryPage account, and Canva sends only that exported PDF.

### What can I see after I share it?

The same readership as any EveryPage link: who opened it, how far they read, time per page, and returning readers - all without storing visitor IP addresses.

## Related

Browse all EveryPage integrations, or see how it works for a pitch deck.

Know if your design got read.

---
URL: https://everypage.co/guides/google-slides-docs-tracking
Title: Track Google Slides & Docs with EveryPage | EveryPage
Description: Use the EveryPage Google Workspace add-on to export a Slides deck or Doc to a secure, trackable PDF link and see who read it - without leaving Google.

# Tracked links inside Google Workspace

By Nick · Updated 28 August 2026

The EveryPage add-on for Google Workspace turns the deck, document or PDF you have open or selected into a secure, trackable link without leaving Google - from Slides, Docs and Drive - drops your links into Gmail drafts, and imports your readership into a Google Sheet. Send the link and see who read it, how far they got, and for how long.

## What you need

- A Google account. The add-on works in Gmail, Drive, Sheets, Slides and Docs.
- A free EveryPage account (connected once, no API key to copy).

## Install the add-on

1. Get EveryPage from the Google Workspace Marketplace and install it.
2. Open any presentation in Google Slides (or a document in Docs). EveryPage appears in the side panel on the right.

## Connect and share

1. Click the EveryPage icon in the side panel and click Connect EveryPage. Sign-in is OAuth - there's no key to paste.
2. Click Create tracked link and allow access to this one file when Google asks.
3. Choose your options - viewer mode, expiry, downloads, password, copy protection, watermark, email gate - exactly what your plan includes, then create. You get the link, a QR code and an embed snippet.
4. Open your readership report in EveryPage to see who read it, page by page.

## Update a link you've already sent

Edited the deck after sharing it? Reopen the panel: it leads with the link you already created and a one-line readership summary. Update this link replaces the document behind the same URL, so the link in your recipient's inbox, the QR code on your handout and the readership history all survive. Link settings edits password, expiry and the rest in place.

## Gmail: send a link, not an attachment

Compose a message, then open EveryPage from the compose toolbar and pick one of your links. It lands at the cursor as a named link - a 20 KB email instead of a 20 MB attachment, with a readership report behind it. The add-on cannot read your email: it writes into the draft and nothing else.

## Drive: any PDF, one click

Select a PDF in Google Drive - a scanned contract, an exported deck, a file a client sent - and open EveryPage in the side panel. Create tracked link, allow access to that one file, and it's live. Google Docs and Slides selected in Drive work the same way.

## Sheets: your readers in a spreadsheet

Open a spreadsheet, grant EveryPage access to it, choose a file (or all of them) and which events to bring in, and click Import read events. Each import adds the new reads - who, when, which pages, how long - to an "EveryPage Reads" tab you can pivot, filter and join to your CRM export. Readers are pseudonymous and no IP addresses are ever stored.

## What data is sent

When you create a link, the add-on sends that one file - as a PDF - to your EveryPage account over HTTPS. Sign-in uses OAuth 2.0, so EveryPage never sees your Google password. Access is granted one file at a time, the add-on requests no broad Drive access, and it cannot read your email. Read events imported into a spreadsheet are your own readership data, written only into the sheet you chose. See the add-on privacy policy.

## Questions

### Which Google apps does it work in?

Slides and Docs (create a link from the open file), Drive (create a link from any selected PDF or Google file), Gmail (insert a link into the draft you are composing), and Sheets (import your readership events into a spreadsheet).

### Can the add-on read my email?

No. In Gmail it can only insert a link into the draft you are composing. It does not read the draft, its recipients, or any message, and requests no mailbox scope.

### Can I update a link after I have sent it?

Yes. Reopen the panel on the same file and click Update this link. The document behind the URL is replaced; the URL, QR code, settings and readership history stay.

### Does EveryPage access my whole Google Drive?

No. The add-on works on the document you have open and choose to share; it does not browse or read the rest of your Drive.

### Is the add-on free?

Yes, the add-on is free. Readership depth follows your EveryPage plan, and the free plan covers core readership.

### What about PowerPoint or Office files?

This add-on is for Google Workspace. For other files you can upload directly at everypage.co or use the browser extension; broader Office support is on the roadmap.

## Related

Browse all EveryPage integrations, or read how to send a pitch deck and know if investors read it.

Send a deck, know if it landed.

---
URL: https://everypage.co/guides/how-to-send-a-pdf-securely
Title: How to Send a PDF Securely: Methods Compared | EveryPage
Description: Password-protect the file, encrypt the email, share a restricted cloud link, or send a tracked link - what each method actually protects against, and how to do it.

# How to send a PDF securely

By Nick · Updated 4 August 2026

"Send this securely" covers four different jobs: password-protecting the file itself, encrypting it in transit, controlling what happens after it arrives, and knowing whether it was actually opened. No single method does all four. This guide walks through each option - built-in PDF passwords, email, cloud storage links, and tracked link sharing - with honest tradeoffs and the steps for the tools you already have.

## What does "securely" actually mean for a PDF?

Before picking a tool, it helps to name the risk you actually care about. Most people sending a contract, proposal, or report are worried about one or more of these four things:

- Interception: someone reading the document on its way to the recipient.
- The wrong recipient: a mistyped address, a forwarded email, a link shared onwards.
- Loss of control after delivery: the copy that lives forever in someone's downloads folder, long after the deal changed.
- Not knowing: you cannot tell whether the document arrived, was opened, or was read past page two.

Different methods defend against different subsets of this list. A password-protected file defends against interception and the wrong recipient, but not against loss of control. An email attachment defends against almost nothing on its own. A hosted link is the only approach that addresses the last two, because the document stays somewhere you can still reach it. It is also worth being honest about what nothing prevents: a recipient who can read a document can always photograph the screen. Real-world PDF security is about controlling distribution and keeping evidence, not about making reading physically impossible.

## Should you password-protect the PDF file itself?

Every serious PDF tool can encrypt the file with a password, so this is the approach most people try first. Done with a modern tool, it uses real AES encryption: without the password, the file is unreadable no matter where the copy ends up.

Here is how in the common tools:

- Adobe Acrobat: All tools → Protect a PDF → Protect with password → choose viewing password, save.
- macOS Preview: File → Export → tick Encrypt, set a password. (Recent macOS versions use strong encryption; very old exports used weaker ciphers.)
- Microsoft Word: when exporting to PDF, choose Options → Encrypt the document with a password.
- LibreOffice: File → Export as PDF → Security tab → set open password.

The tradeoffs are real, though. You now have a second secret to deliver, and it must travel by a different channel than the file - a password in the same email defeats the point; text it or say it on a call instead. The protection is also static: once someone has the file and the password, they have it forever, and you cannot revoke, expire, or update the document. Old tools that encrypt with the legacy RC4 cipher (rather than AES-256) offer far weaker protection than the padlock icon suggests. And there is recipient friction - a mistyped password on a phone is often where "secure" delivery quietly fails.

## Is an email attachment ever the secure option?

Email is where most PDFs travel, so it is worth being clear-eyed about what it does and does not protect. Between major providers, email is encrypted in transit (TLS) - interception is not the main risk. The problems are everything else: a copy now exists on your mail server, the recipient's mail server, and every device that syncs either mailbox. You cannot un-send it, you cannot expire it, forwarding is one click, and you get no signal about whether it was even opened. Attachments also hit size limits around 20-25 MB.

The mainstream providers offer partial fixes:

- Gmail confidential mode: compose → toggle confidential mode → set an expiry and optional SMS passcode. The recipient cannot forward, copy, or download - but it works by replacing the attachment with a link to Google's servers, screenshots remain trivially possible, and there is no read analytics.
- Outlook / Microsoft 365 encryption: Options → Encrypt (or "Do Not Forward"). Solid inside organisations that both use Microsoft 365; clunky for external recipients, who may need a one-time passcode flow.

A sensible rule: an attachment is fine when the document is not sensitive, the recipient is certain, and you do not care what happens next. For anything else, combine email with one of the other methods - either attach an encrypted file, or (usually better) email a link instead of the file. If knowing whether it was read matters to you, see our companion guide on tracking a PDF sent by email.

## When is a cloud storage link (Drive, Dropbox) enough?

Sharing from Google Drive, Dropbox, or OneDrive fixes email's worst problem: the file stays in one place you control. Restrict access to specific email addresses (in Drive: Share → add people, and turn link access off; in Dropbox: Share → specific people), and you can revoke access or replace the file later. That is genuinely more secure than an attachment.

The limits show up at the edges. "Anyone with the link" mode - which is what people actually use, because per-address permissions force recipients to sign in with the matching account - is only as secure as the least careful person the link reaches. Download blocking is patchy across apps and platforms. And visibility is thin: Dropbox shows basic view events on some plans, Drive tells you almost nothing. For a personal document shared with someone you trust, a restricted cloud link is enough. For a business document where you need certainty, it usually is not.

## What is tracked link sharing - and when is it the better tool?

The fourth approach is a category built for exactly this job: document-sharing services such as EveryPage, DocSend, or Papermark. You upload the PDF once and send a link. The document never leaves the server - readers view it in the browser - so control survives delivery: you can require a password (entered on the page, not baked into a file), gate the document behind an email address, watermark every page with the viewer's identity, block downloads, expire the link on a schedule or after a number of views, and replace or kill the file behind the link at any time.

The same architecture is what makes the fourth risk - not knowing - solvable. Because reading happens on the page rather than in a downloaded copy, the link can report back: who opened the document, how far they got, how long they spent on each page, whether they came back. That turns "sent securely" into "sent securely, and read on Tuesday, twice, with four minutes on the pricing page." How that works under the hood is covered on our PDF tracking page.

The tradeoffs, honestly stated: the document lives with a third party, so the provider's own security posture matters (encryption at rest, what they log about your readers - EveryPage, for instance, stores no reader IP addresses and encrypts files with AES-256-GCM). Readers need to be online. And nothing client-side can truly prevent a determined person photographing a screen - watermarking exists to make that traceable rather than impossible.

## Which method should you choose?

Match the tool to the risk, not the other way around. Two habits do more for document security than any product choice: never send a password in the same channel as the file it unlocks, and prefer a link you can still control over a copy you can't. With that in mind:

- One-off file to a trusted person, no follow-up needed: password-protect the PDF (AES), send the password by a second channel.
- Internal documents inside a Microsoft/Google organisation: your suite's built-in encryption and permissions are the low-friction choice.
- Casual sharing where revocation would be nice: a cloud storage link restricted to named people.
- Proposals, decks, contracts, reports - anything where control after delivery or knowing it was read matters: a tracked link with a password or email gate, expiry, and watermarking as the stakes demand.

The methods also combine. Many senders email a tracked link (the email is just the envelope; the document and its rules live on the server), or keep a password-protected copy for archival while sharing the working version as a link. What rarely makes sense is the default most people fall back to: a naked attachment with none of the above, sent and hoped for.

## How do you send a PDF securely with EveryPage?

1. Upload your PDF at everypage.co - it is encrypted with AES-256-GCM before it touches disk, and no account is needed to try it.
2. On the configure step, set the rules the document calls for: a password, an expiry date or view budget, downloads on or off, an email gate or per-viewer watermark for the sensitive cases.
3. Send the link (or QR code) however you normally would - the secrets stay on the server, not in the URL.
4. Watch the readership report: who opened it, how far they read, who came back. If something leaks or changes, expire the link and the document dies with it.

The full protection stack - passwords, screenshot deterrence, expiry, watermarking, encrypted storage - is laid out on the secure PDF sharing page.

## Related reading

See how secure PDF sharing works in EveryPage, what PDF tracking reports on every link, how to track a PDF sent by email, or why EveryPage never stores reader IP addresses.

Send it securely - and know it was read.

---
URL: https://everypage.co/guides/notion-embed
Title: Embed a Tracked PDF in Notion | EveryPage
Description: Paste an EveryPage link into Notion, choose Embed, and the tracked viewer renders in-page - plus how to sync every read into a Notion database.

# Embed a tracked PDF in Notion

By Nick · Updated 28 August 2026

Paste an EveryPage link into any Notion page and choose Embed: the tracked, branded viewer - flipbook, swipe, or standard - renders right inside the page, and every read is attributed and tracked. No Notion setup, no plugin, works on every plan. Connect your workspace afterwards and each read session also lands as a row in a Notion database. See the Notion integration overview for the full picture.

## What you need

- A document shared with EveryPage - a free account is enough.
- Edit access to the Notion page you want the document on.
- Nothing else. Embeds need no API key, no OAuth, and no Notion configuration.

## Step 1: copy the embed link

Open your document's share sheet and use Copy embed link for Notion - it copies the durable short-ID embed URL, the form built for iframes. The plain share link works too; the embed link just skips the viewer chrome that makes sense on a full tab but not inside a portal page.

## Step 2: paste, then choose Embed - not Bookmark

1. Paste the link into the Notion page where you want the document.
2. Notion asks what to do with it. Choose Embed. (Bookmark makes a flat preview card that sends readers off to another tab - the one option to avoid.)
3. The tracked viewer renders in-page, in whichever viewer mode the document is set to.

## Sizing tips

- Drag the embed's handles to resize it - taller suits flipbooks, and the viewer adapts to whatever width the block gets.
- For documents that deserve the room, put the embed in a full-width section rather than a narrow column - page-turn spreads read much better wide.
- Inside a narrow column the viewer collapses to single-page display on its own; nothing to configure.

## What tracking you get

Everything a direct link gets, attributed to the embed channel so portal reads are distinguishable from link opens: read sessions with pages read and time spent, the read-through funnel, returning readers, countries, and per-page stats on your plan's readership dashboard - with no reader IP addresses stored.

## Optional: sync reads into a Notion database

The second half of the integration turns Notion into your CRM. Go to Account settings, choose Connect Notion, authorize your workspace, and pick a parent page - EveryPage creates an "EveryPage Reads" database there and writes one row per reading session, moments after each reader closes the document: document, reader, pages read, minutes, read-through %, returning, source, country, and a session link. A 30-day backfill import covers reads from before you connected. The integration page documents every column and the plan gating (reader names and lead rows need the Pro email gate).

## Troubleshooting

- You got a Bookmark card. Delete the block, paste the link again, and pick Embed this time. Pasting the /embed link from the share sheet makes the Embed option the natural choice.
- The embed says the document can't open here. Password-protected and email-gated documents refuse to render inside an embed on purpose - an iframe on someone else's page is no place for a password. The embed shows an "Open document" link to the direct share page, where the gate works normally. To render in-page, remove the password and rely on watermarks and expiry instead.
- Notion's mobile app looks different. The mobile app renders embeds in a smaller, sometimes lazily-loaded frame - the viewer works, but readers may need a tap to start it and get the single-page layout. The web and desktop apps show the full experience.
- The page is public. Public Notion page means public embed: anyone who can see the page can read the document, and those views count toward your plan limits like any other read.

## Questions

### How do I embed a PDF in Notion with tracking?

Share the PDF with EveryPage, copy the embed link from the share sheet, paste it into your Notion page, and choose Embed - not Bookmark - when Notion asks. The tracked viewer renders in-page and every read session is recorded: pages read, time spent, read-through, and returning readers, with no reader IP addresses stored.

### Do my readers need an account or an app?

No. Readers just see the document inside the Notion page they already have. There is nothing to install on either side - Notion's built-in Embed block does the rendering, and the tracking is part of the EveryPage viewer.

### Why does my embed show a Bookmark card instead of the viewer?

Bookmark was picked when the link was pasted - it is the flat preview card option in the same menu as Embed. Delete the block, paste the link again, and choose Embed. Using the /embed link from the share sheet's "Copy embed link for Notion" button makes this the natural choice.

### Can Notion reads sync into a Notion database?

Yes - connect your workspace from Account settings and EveryPage creates an "EveryPage Reads" database under a page you pick, then writes one row per reading session moments after it ends, with pages read, minutes, read-through %, source, country, and a session link. Reader names and captured lead rows require the Pro email gate; other plans see stable pseudonyms like "Reader #214".

## Related

See the full Notion integration overview (the Reads database columns, personas, and plan details), the general guide to embedding a tracked PDF on any website, or browse all EveryPage integrations. EveryPage is also listed in Notion's own integration gallery.

Give your portal real analytics.

---
URL: https://everypage.co/developers
Title: Developer API - Upload & Track PDFs | EveryPage
Description: The EveryPage API: upload and import PDFs, configure the viewer, replace content behind a live link, readership reports, and signed webhooks.

Developer API

# EveryPage API

Upload PDFs and get trackable share links programmatically — the same engine behind our integrations. Authenticate with an API key from your account settings.

Prefer a machine-readable spec? Grab the OpenAPI 3.0 definition as JSON or YAML.

## Authentication

Pass your key as a bearer token. Keys are scoped to your account and respect your plan's upload limits.

```
Authorization: Bearer ep_live_xxxxxxxx
```

Every endpoint is guarded by a scope. Personal API keys (ep_live_…) hold every scope, including ones we add later; OAuth access tokens (ep_at_…) are narrowed to what the user granted.

- files:read — list files, file details, QR codes, list link variants.
- files:write — upload, import, settings, content replacement, delete, create/update/delete link variants.
- readership:read — the events feed, gate responses, per-file readership reports, and proofing feedback (page marks and annotations, Pro).
- webhooks:manage — create, list, test, and delete webhooks.
- profile — your account and plan (GET /api/v1/user).

## Upload a PDF

POST /api/v1/files — multipart form, field file. Returns the file's UUID and its short ID; the share link is https://everypage.co/<shortId> (the UUID form works too).

```
curl -X POST https://everypage.co/api/v1/files \
  -H "Authorization: Bearer ep_live_xxxxxxxx" \
  -F "file=@proposal.pdf"

# {"uuid":"550e8400-…","shortId":"Ab3xY9kQ2mZ7","message":"PDF uploaded successfully"}
```

POST /api/v1/files/import — JSON body {"url", "filename"}. Creates a file by server-side download instead of an upload. The URL must be plain HTTPS on our import allowlist (design-tool export URLs, e.g. Canva exports — not arbitrary hosts), PDF only, capped at your plan's size limit. The response may include an advisory palette of hex swatches extracted from the document.

```
curl -X POST https://everypage.co/api/v1/files/import \
  -H "Authorization: Bearer ep_live_xxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://export.canva.com/…/design.pdf", "filename": "brochure.pdf"}'

# {"uuid":"550e8400-…","shortId":"Ab3xY9kQ2mZ7","shareUrl":"https://everypage.co/Ab3xY9kQ2mZ7"}
```

## Configure a file

PUT /api/v1/files/<uuid>/settings — JSON body. Set the viewer mode, a password, the download permission, the expiry, and everything below. Omitted fields keep their current value.

```
curl -X PUT https://everypage.co/api/v1/files/<uuid>/settings \
  -H "Authorization: Bearer ep_live_xxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{
    "viewerMode": "flipbook",
    "password": "hunter2",
    "allowDownload": false,
    "neverExpire": true,
    "viewLimit": 25,
    "pageRange": {"from": 1, "to": 10},
    "viewerSettings": {
      "background": {"type": "gradient", "gradient": "dusk"},
      "brand": {"accentColor": "#e63b2e"}
    }
  }'
```

- viewerMode: standard, flipbook, swipe, or magazine.
- password: non-empty to protect (Basic+), "" to clear; allowDownload: false to disable downloads. showExpiry: false to hide the live "Expires in" countdown from readers (default true; the public metadata then omits deleteAt).
- requireEmail: gate viewing behind an email (Pro). notifyOnView: email you when someone opens it (Basic+).
- Expiry: "deleteAt": "<ISO 8601>" for a fixed expiry, or "neverExpire": true for a permanent link (the server then stores no expiry at all). Signed-in accounts are uncapped on every plan. Manage-token callers on an anonymous file are capped at 7 days and cannot set neverExpire. Omit both to keep the current expiry.
- viewLimit: self-destruct after this many views (Basic+); 0 clears the limit. A burned link keeps its row and readership; only the bytes are destroyed — see content replacement below for the un-burn path.
- pageRange: {"from": 1, "to": 10} limits non-owner viewers to that page window, trimmed server-side (Pro to set; files up to 100MB). {"from": 0, "to": 0} clears it on any plan. Enforcement deliberately survives a downgrade; owners always get the full document.
- gateFields: a lead-capture form definition shown instead of the plain email prompt (Pro; null or [] clears on any plan; a non-empty form switches requireEmail on). gateDomains: restrict the email gate to listed domains (Pro).
- askReceipt: ask viewers to confirm receipt (Basic+). commentsEnabled (+ commentsAllowPublic, notifyOnComment): reader feedback notes (Pro). marksEnabled / annotationsEnabled: proofing (Pro).
- watermark: stamp viewer pages (Pro). Watermarked downloads are limited to files up to 100MB.
- slug: a custom link name on your custom domain (Pro) — lowercase letters, digits, and hyphens; "" to clear. Returns 409 if another of your files already uses it.
- Writes to an already-dead link — expired, or burned by its view limit — answer 410. Extend the expiry before it lapses, not after. The public GET /api/files/{id}/metadata answers a dead link with 410 and a JSON body (reason, why, endedAt, and originalName unless the document was password- or email-gated); every other endpoint answers with plain text.

### Viewer appearance (viewerSettings)

viewerSettings is a JSON object of appearance and behavior blocks. Any deviation from the defaults requires Basic+; the fields marked Pro require Pro. Unknown fields are dropped, out-of-range numbers are clamped, and the gates are re-checked when pages are served — a downgraded plan's Pro styling stops rendering for viewers immediately.

- background: type solid (+ color #RRGGBB), gradient (preset: dusk sand slate forest blush mono), or image (+ assetId, fit cover|contain, blur 0–20, dim 0–80).
- logo: assetId, position tl|tr|bl|br, size s|m|l|xl, linkUrl, hideBadge. Asset IDs come from the file's uploaded assets.
- page: shadow 0–3, rounded 0–3, edges, coverAlone.
- flip: speedMs 200–1200 (default 450), sound, rtl, layout adaptive|single|double.
- swipe: autoAdvance with intervalMs 3000–30000 (default 6000).
- protect: contextMenu, print, select (Basic+); blurOnLeave (Pro). Soft deterrents, not DRM.
- ga4Id: your Google Analytics 4 measurement ID, G-XXXXXXXXXX (Pro).
- brand: accentColor #RRGGBB, toolbarTheme light|dark|auto, badgePosition tl|tr|bl|br (Pro).
- cta: a call-to-action button — label (1–40 chars) and an https url required, style solid|outline, color, position tl|tr|bl|br|bar (Pro).
- watermarkStyle: opacity 0.05–0.5 (default 0.12), density sparse|normal|dense (Pro; the watermark setting above turns the watermark itself on).

## Replace content (dynamic links)

POST /api/v1/files/<uuid>/content — multipart, field file (Pro). Swaps the PDF behind a share link in place: the UUID, short ID, slug, QR code, settings, and all readership history survive — only the bytes change. Each replacement increments contentVersion, and superseded versions appear as revisions on the file detail.

```
curl -X POST https://everypage.co/api/v1/files/<uuid>/content \
  -H "Authorization: Bearer ep_live_xxxxxxxx" \
  -F "file=@proposal-v2.pdf"

# {"uuid":"550e8400-…","contentVersion":2,"originalName":"proposal-v2.pdf",
#  "size":88123,"anchorsCleared":true,"clearedHotspots":2,"clearedNotes":0,
#  "message":"Content replaced"}
```

- Page-anchored hotspots and notes are cleared by default (the new pages don't line up with the old ones); pass ?clearAnchors=false to keep them. Document-level notes always survive.
- Fires a content.replaced webhook event carrying the new contentVersion.
- Burned files (view limit reached) ARE replaceable — content replacement is the un-burn path, and the link comes back to life. Expired links answer 410.

## Link variants (per-recipient links)

Mint child links off one file — one per recipient — each with its own short ID and URL (Pro; up to 200 per file). Viewers arriving through a variant are attributed to it in readership and in file.viewed / file.downloaded webhook payloads.

- GET /api/v1/files/<uuid>/variants — list (revoked and redacted included)
- POST /api/v1/files/<uuid>/variants — create
- PUT /api/v1/files/<uuid>/variants/<variantUuid> — update label/overrides, revoke/un-revoke
- DELETE /api/v1/files/<uuid>/variants/<variantUuid> — delete; add ?redact=1 to GDPR-redact instead

```
curl -X POST https://everypage.co/api/v1/files/<uuid>/variants \
  -H "Authorization: Bearer ep_live_xxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{"label": "Jane at Acme", "overrides": {"allowDownload": false}}'

# 201 {"uuid":"7c9e6679-…","shortId":"Xy7Qm2aB9kZ3",
#      "url":"https://everypage.co/Xy7Qm2aB9kZ3","label":"Jane at Acme",
#      "overrides":{"allowDownload":false},"revoked":false,"createdAt":"…"}
```

- label (up to 200 chars) is the recipient tag — the only personal field on a variant.
- overrides refine the file's settings for this variant's viewers: allowDownload and pageRange ({"from":0,"to":0} serves the full document even when the file has a range). On update, overrides REPLACES the stored set as a whole object — never a per-key merge — so send every override you want to keep; {} clears them all.
- Revoking ("revoked": true) makes the variant's link answer 404 to viewers, reversibly, without revealing that a canonical link exists.
- ?redact=1 erases the label for good — from the variant, analytics, and stored webhook payloads — while the link and its analytics keep working. That's the compliance path for GDPR erasure requests; a redacted label can never be set again (409).
- Passwords and viewing gates are per-file, not per-variant: a viewer who passed the gate through one link has passed it for all of the file's links.

## Other endpoints

- GET /api/v1/files — list your files
- GET /api/v1/files/<uuid> — file details (includes the replacement revisions history)
- GET /api/v1/files/<uuid>/qr-code — QR code (PNG) for the share link
- DELETE /api/v1/files/<uuid> — delete a file
- GET /api/v1/user — your account + plan

A file object (returned by list and detail) looks like:

```
{
  "uuid": "550e8400-…",
  "shortId": "Ab3xY9kQ2mZ7",           // short share link; absent on older files
  "slug": "2026-pricing",              // custom link name; absent unless set
  "originalName": "proposal.pdf",
  "size": 91234,
  "mimeType": "application/pdf",
  "createdAt": "2026-06-15T14:00:00Z",
  "deleteAt": "2026-06-16T14:00:00Z",   // absent if it never expires
  "viewCount": 12,
  "viewerMode": "flipbook",
  "protected": true,
  "allowDownload": false,
  "requireEmail": false,
  "notifyOnView": true,
  "contentVersion": 1                   // increments on content replacement
}
```

## Readership report

GET /api/v1/files/<uuid>/readership — the same aggregates the readership dashboard shows (scope readership:read). The response is shaped by your plan: a tier field (free, basic, pro) says which sections are present; sections above your tier are omitted entirely.

- Every plan: summary — total views, sessions, unique visitors, unique countries, average read time, downloads — plus the file object.
- Basic adds: median read time, completion rate, and re-read share in the summary, plus viewsOverTime, the read-through funnel, and referrers / browsers / sources / viewerModes / peakTimes / devices / countries breakdowns.
- Pro adds: live activeReaders, new-vs-returning session counts, recent sessions with reader identities and captured emails, hotspotTaps, CTA clicks (ctaTaps), the per-variant breakdown, and contacts captured by the lead-form gate.
- When a page range is active the response carries effectivePages — the shared window's size — so funnels over partial documents read honestly.

## Read events (for automations)

GET /api/v1/events serves three polling streams selected by ?type= — view (the default: finished read sessions), download (explicit saves), and gate (completed lead-form gates; Pro). The basis for "new read" automations like the Zapier trigger.

```
curl "https://everypage.co/api/v1/events?type=view&since=0" \
  -H "Authorization: Bearer ep_live_xxxxxxxx"

# [{"id":42,"fileUuid":"550e8400-…","fileName":"deck.pdf",
#   "readAt":"2026-06-15T14:00:00Z","country":"United Kingdom",
#   "pagesViewed":7,"timeMs":48000,"type":"view"}]
```

- Each event has a stable id. Cursors are per-stream: every type has its own id sequence, so a since value from one stream is meaningless in another — never mix them.
- Without a cursor (since=0) you get the newest events first — a peek window. With since=<id> results ascend from the cursor, so polling with the highest id you've seen walks the stream forward without gaps or duplicates.
- ?limit= up to 100 (default 50). ?file= filters to one file (UUID or short ID; unknown or foreign identifiers return [], never an error).
- The download stream includes your own downloads — unlike the file.downloaded webhook, which only fires for non-owners.
- gate events carry the submitted form in fields. GET /api/v1/gate-responses is a resource-path alias of ?type=gate — same rows, cursor, and Pro gate.

## Webhooks

Prefer push over polling? Register an HTTPS endpoint and we POST events to it as they happen. Webhooks are available on every plan — only gate.completed deliveries additionally require Pro at event time, because their payload carries captured lead data. Up to 25 webhooks per account; your own actions on your own files never fire them.

- GET /api/v1/webhooks — list (never includes secrets)
- POST /api/v1/webhooks — create
- DELETE /api/v1/webhooks/<uuid> — delete
- POST /api/v1/webhooks/<uuid>/test — synchronous test delivery (10/min per token)

```
curl -X POST https://everypage.co/api/v1/webhooks \
  -H "Authorization: Bearer ep_live_xxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://example.com/hooks/everypage",
       "events": ["file.viewed", "gate.completed"]}'

# 201 {"webhook":{"uuid":"…","url":"…","events":["file.viewed","gate.completed"],
#      "format":"json","active":true,"createdAt":"…"},
#      "secret":"whsec_9f2c…"}     <- shown exactly once; store it now
```

- format: json (default, signed) or slack (Slack Block Kit for incoming webhooks — unsigned; Slack authenticates by URL).
- fileUuid (optional, UUID or short ID of a file you own) scopes delivery to that one file; omit it for account-wide delivery.

### Event kinds

- file.viewed — a non-owner read session ended. Extras: pagesViewed, timeMs.
- file.downloaded — an explicit save-to-disk by a non-owner. No extras.
- gate.completed — a viewer passed the email/lead-form gate. Extras: source, email, fields (Pro delivery).
- note.created — a viewer left a public feedback note. Extras: author, body, pageNumber (when page-anchored).
- receipt.confirmed — a fresh "mark as received". Extra: name.
- file.burned — the view limit destroyed the file's bytes. No extras.
- content.replaced — the document behind the link was swapped. Extra: contentVersion.
- invite.viewed — an email invitee opened the document for the first time. Extras: email, name.
- proofing.updated — a viewer's first page mark or annotation on a document. Extras: kind, pageNumber, viewer.

Every json delivery is an envelope whose data always carries fileUuid and fileName plus the kind's extras. Sessions and downloads that arrived through a link variant additionally carry variantUuid and variantLabel:

```
POST <your url>
Content-Type: application/json
X-Everypage-Signature: t=1750000000,v1=5257a869e7…

{
  "event": "file.viewed",
  "timestamp": "2026-06-15T14:03:22Z",
  "data": {
    "fileUuid": "550e8400-…",
    "fileName": "deck.pdf",
    "pagesViewed": 7,
    "timeMs": 48000
  }
}
```

### Verifying signatures

The X-Everypage-Signature header is t=<unix time>,v1=<hex> where v1 is HMAC-SHA256 over the string <t>.<raw body>. The HMAC key is the FULL secret string exactly as shown at creation — the whsec_ prefix is part of the key, not a wrapper to strip. Verify against the raw request bytes (before any JSON parsing), and reject stale timestamps (we suggest ±5 minutes) to prevent replays.

```
const crypto = require('crypto')

// secret is the full "whsec_…" string; rawBody is the unparsed request body
function verifyEverypage(secret, rawBody, header) {
  const parts = Object.fromEntries(header.split(',').map((p) => p.split('=')))
  const expected = crypto.createHmac('sha256', secret)
    .update(parts.t + '.' + rawBody).digest('hex')
  return parts.v1.length === expected.length &&
    crypto.timingSafeEqual(Buffer.from(parts.v1, 'hex'), Buffer.from(expected, 'hex')) &&
    Math.abs(Date.now() / 1000 - Number(parts.t)) < 300
}
```

- Delivery: any 2xx from your endpoint counts as delivered; the request times out after 10 seconds. Failures retry up to 5 attempts with 1 minute / 10 minutes / 1 hour backoff.
- After 20 consecutive exhausted deliveries the webhook is switched off automatically and you get one email. Re-create it (or use /test) once your endpoint is healthy.
- Deliveries carry no delivery ID and retries send the same body, so dedupe best-effort on (event, timestamp, data) if double-processing matters to you.
- The signing secret is shown once, at creation, and is never retrievable again — delete and re-create the webhook if you lose it.

## OAuth 2.0 (for apps)

Building an app that acts for other users? Use OAuth 2.0 (Authorization Code + PKCE) instead of asking them for an API key. Register your app with us to get a client_id (and a secret for server-side apps).

- Send users to GET /oauth/authorize with response_type=code, client_id, redirect_uri, scope, state, and a PKCE code_challenge (S256).
- After they approve, we redirect back with ?code=. Exchange it at POST /oauth/token (with code_verifier) for an access + refresh token.
- Call /api/v1 with Authorization: Bearer <access token>. Refresh with the refresh_token grant (tokens rotate); revoke at POST /oauth/revoke.
- Scopes: files:read, files:write, readership:read, webhooks:manage, profile (see the scope table above). Users manage authorized apps under their account.

## QR codes & embedding

- GET /api/v1/files/<uuid>/qr-code — a PNG QR code for the share link (scope files:read). The encoded link is durable — the short ID or UUID, never the renameable slug — and carries ?via=qr so scans show up in the readership source breakdown.
- GET /api/files/<uuid>/qr-code — the same PNG, public and unauthenticated (rate-limited to 60 requests/minute per IP), for embedding a QR without exposing a token.
- GET /oembed?url=<share link> — public oEmbed provider endpoint: turns any pasted share link (UUID, short ID, or slug form) into an embeddable rich object.

## Client libraries & examples

- everypage-node — the official TypeScript/JavaScript client.
- everypage-mcp — an MCP server, so Claude, Cursor and other AI assistants can share documents and report readership. Setup.
- webhook-examples — working signature verification in Node, Python, PHP, and Go.

## Versioning, deprecation policy and rate limits

Every endpoint lives under /api/v1; changes inside a version are additive only, and anything scheduled to go away carries Deprecation and Sunset headers with at least six months' notice — see the versioning and deprecation policy. Requests are limited to 120 per minute per token; every response carries RateLimit and RateLimit-Policy headers, and a 429 adds Retry-After. Getting started needs no sales call: the free plan has no card, API keys are self-serve in account settings, and there is no separate sandbox — use a free account and delete the test file afterwards.

## Errors

Errors come back as an RFC 9457 problem document (application/problem+json): the HTTP status, a stable code such as plan_required or insufficient_scope, a human-readable detail, and a hint. Branch on the status or the code, never on the text. 401 and 403 responses carry a WWW-Authenticate: Bearer challenge; 429 carries Retry-After.

- 400 — bad request (e.g. the file isn't a PDF, or a malformed body)
- 401 — missing, malformed, invalid, or revoked API key
- 403 — not allowed: you don't own the file, or the setting is above your plan (e.g. password on Free)
- 404 — no such file (or not owned by you)
- 409 — conflict: the slug is already used by another of your files, or a redacted variant's label was re-set
- 410 — the link is dead: expired, or burned by its view limit (settings writes; content replacement 410s only on expiry — burned links replace fine)
- 413 — the file is larger than your plan allows
- 429 — rate limit exceeded (120 requests per minute per key; webhook tests 10 per minute)
- 502 — an import's export source couldn't be fetched or returned an error

## Notes

- PDF first: Word (.docx) and PowerPoint (.pptx/.ppt) uploads are converted to PDF where conversion is enabled; everything else is rejected. Max file size follows your plan (20MB free, 200MB Basic, 2GB Pro).
- Rate limit: 120 requests per minute per key (per token, not per IP — integrations may share an egress IP).
- Revoke a key anytime from account settings — it stops working immediately.
- Readership analytics on API-uploaded files work exactly as they do in the app.
- Webhooks work on every plan; the plan only gates gate.completed deliveries.

---
URL: https://everypage.co/extension-privacy
Title: Browser Extension Privacy Policy | EveryPage
Description: Privacy policy for the EveryPage browser extension: it stores only your API key locally and uploads only the PDFs you choose to share.

Browser extension

# Extension Privacy Policy.

Last updated: August 2026

The EveryPage browser extension helps you upload PDFs to your EveryPage account and create trackable share links. This policy explains what it handles. It covers the extension specifically; the main service is covered by our Terms & Privacy.

## What the extension stores

- Your API key. Saved in your browser's local extension storage and sent only to everypage.co as a bearer token to authenticate your requests. It is never sent anywhere else.
- The last share link you created, stored locally for convenience.

The extension does not collect browsing history, analytics, or any personal information beyond the above.

## What is sent off your device

Only the PDFs you choose to share - either a file you pick in the popup or a PDF link you right-click - are uploaded to your EveryPage account over HTTPS. Nothing else leaves your device.

## Host access

The extension's standing access is limited to everypage.co. When you right-click a PDF link to share it, the extension asks for one-time access to that site only, so it can download that single file for upload. It does not request or use access to other sites for any other purpose.

## How uploaded files are handled

Uploaded PDFs are stored and served by EveryPage under your account and your plan's settings (encryption at rest, expiry, password, and so on). See the main Terms & Privacy for details.

## Data sharing

We do not sell your data or share it with third parties. The extension talks only to the EveryPage API.

## Removing your data

- Remove the stored API key by clearing it in the extension's options, or uninstalling the extension.
- Revoke the key anytime at your account → API keys.
- Delete uploaded files from the extension's "My files" tab or in the app.

## Contact

Questions? Email support@everypage.co.

---
URL: https://everypage.co/workspace-privacy
Title: Google Workspace Add-on Privacy Policy | EveryPage
Description: Privacy policy for the EveryPage Google Workspace add-on: it accesses only the document you open it on and requests no broad Drive access.

Google Workspace add-on

# Workspace Add-on Privacy Policy.

Last updated: August 2026

The EveryPage add-on for Gmail, Google Drive, Google Sheets, Google Slides and Google Docs turns the file you open or select into a secure, trackable share link, inserts your links into Gmail drafts, and imports your own readership events into a spreadsheet - without leaving Google. This policy explains exactly what the add-on accesses and sends. The main service is covered by our Terms & Privacy.

## What the add-on accesses

- Only the file you open it on. The add-on uses the drive.file scope, which grants per-file access to the single document you are working in, the file you select in Drive, or the spreadsheet you import into - granted on demand, one file at a time. It cannot see or browse the rest of your Google Drive.
- A connection to your EveryPage account. You connect once via EveryPage's OAuth sign-in; the add-on holds a token to create files in your account on your behalf.

## What is sent off Google

Only the PDF export of the document you choose to share is sent, over HTTPS, to everypage.co so it can be stored in your EveryPage account and given a trackable link. The add-on does not send your document anywhere else, and does not transmit any other Drive content.

## Scopes the add-on requests

- drive.file - to read the open document so it can be exported as a PDF.
- script.external_request - to upload that PDF to the EveryPage API.
- script.locale - to display the add-on in your locale.
- gmail.addons.execute - to run the add-on inside Gmail.
- gmail.addons.current.action.compose - to insert a link into the email you are composing. The add-on cannot read your email: it does not read the draft, its recipients, or any message.
- drive.addons.metadata.readonly - to show the name and type of the file you select in Google Drive. Reading its contents still requires the per-file access above.

The add-on requests no broad Drive access, reads no document other than the one you run it on, and cannot read your email. Read events imported into a spreadsheet are your own readership data from your EveryPage account, written only into the spreadsheet you grant access to.

## How uploaded files are handled

Uploaded PDFs are stored and served by EveryPage under your account and your plan's settings (AES-256-GCM encryption at rest, expiry, password protection, and so on), and readership is measured without ever storing a visitor's IP address. See the main Terms & Privacy for details.

## Data sharing

We do not sell your data or share it with third parties. The add-on communicates only with Google (to export the open file) and the EveryPage API (to upload it). EveryPage's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

## Removing your data

- Disconnect the add-on from within its panel, or uninstall it from Google Workspace.
- Revoke EveryPage's access anytime at your account, and Google access at your Google account permissions.
- Delete uploaded files from your EveryPage account at any time.

## Contact

Questions? Email support@everypage.co.

---
URL: https://everypage.co/canva-privacy
Title: Canva App Privacy Policy | EveryPage
Description: Privacy policy for the EveryPage app for Canva: it receives only the PDF you publish plus a pseudonymous Canva user id and design id that power republishing, and readers of your links are measured without ever storing their IP address.

Canva app

# Canva App Privacy Policy.

Last updated: August 2026

The EveryPage app for Canva publishes the design you are working on as a secure, trackable PDF link - with or without an EveryPage account. This policy explains what the app sends us, what we keep, and why. It covers the Canva app specifically; the main service is covered by our Terms & Privacy.

## What the app sends us

- The PDF export of the design you publish. When you publish, Canva exports the open design and we download that PDF over HTTPS so it can be stored (encrypted at rest) and served at your link. We receive nothing else from your Canva account - the app cannot browse your other designs.
- Proof of a real Canva session. Each publish carries a short-lived token that we verify against Canva's published signing keys, purely to confirm the request comes from a genuine Canva session. This is our anti-abuse check - without it, anyone could push files into EveryPage anonymously.
- A design identifier. Canva also provides a signed token naming the design being published, which we verify the same way.

## What we keep, and why

- Your Canva user id. An opaque identifier taken from the verified token - not your name, email, or anything else from your Canva profile. It enforces the per-user cap and rate limit on anonymous uploads, so a single Canva account cannot mass-produce files, and together with the design id it is how a republish finds the link it should update.
- The id of the design you published. Stored with the file so that publishing the same design again updates your existing link in place - same URL, same QR code - instead of minting a new link every time.

Neither identifier is used for marketing or shared with third parties. They exist only for the two mechanics above.

## Publishing without an account

You can publish without an EveryPage account. The file is stored anonymously - it belongs to nobody until you claim it into an account via the claim link the app shows you. Claiming keeps the same share link; the document stops expiring unless you set an expiry yourself, and you unlock the owner features (readership, settings, your library). Designs published into a connected EveryPage account are ordinary uploads, handled under your account and plan settings.

## Reader privacy on your links

People who open your link are measured without storing their IP address - ever. The address is turned into a pseudonymous reader id with a salted one-way hash and then discarded; it is also used in-flight to resolve a country for your readership report, then dropped. Reports show pseudonymous readers, never addresses.

## Retention and deletion

- Anonymous links are kept for 365 days from publishing. Republishing a live design restarts that clock (unless you set an expiry yourself), so a link in active use stays alive.
- When a link expires, the file and its record are deleted automatically. Claimed files follow your account settings instead - you choose the expiry and can delete them anytime.
- To remove an anonymous link early, claim it into a free account and delete it there, set a shorter expiry in the app when publishing, or email support@everypage.co and we will remove it.

## Data sharing

We do not sell your data or share it with third parties. The app communicates only with Canva (to export the design you publish) and the EveryPage API (to store it and hand back your link).

## Contact

Questions? Email support@everypage.co.