Read the analytics in the order decisions happen

The analytics page is most useful when you read it in order. Start with link opens, readers and sessions. Then move to full reads, CTA clicks and downloads. After that, use page reach, time on page, version changes and A/B variant comparison to decide what to change in the document.

Start with the top metrics

Link opens

Use link opens to measure reach. This tells you how many times the public link was opened in the selected range.

Use it for:

• send volume
• channel reach
• top-of-funnel comparison between campaigns

Do not use it alone to judge the document itself. A weak opening page can still get many opens.

Readers

Readers are sessions with meaningful activity such as 10 seconds or more, a page view, a CTA click or a download. This is the first quality filter after raw traffic.

Use it when you need to tell the difference between "someone touched the link" and "someone actually reviewed the document".

Sessions

Sessions are unique viewing sessions. This is the base for bounce rate and exit before end.

When sessions and link opens are close, most people opened the link once. When opens are much higher than sessions, the same audience may be returning or refreshing.

Full reads

Full reads are sessions that reached the last page. This is the cleanest completion signal for proposals, onboarding guides and long review docs.

It does not mean agreement. It means the document carried the session to the end.

CTA clicks and downloads

CTA clicks show how often the next-step action was used. Downloads show how often people wanted a local copy.

CTA clicks are usually stronger than downloads when the document is supposed to drive one clear next action. Downloads are still useful, but they often mean "take this into another workflow" rather than "I am ready now".

Good CTA use cases:

• sales deck with a call booking link
• proposal with an approval or reply step
• onboarding guide with a setup page or workspace step

If the document is mainly for review, forwarding or offline reading, downloads can matter more than CTA clicks. Do not force every document into a button-driven workflow.

Avg time per reader and avg time per page

Use these to add context, not as the first decision signal.

• average time per reader helps you see depth per session
• average time per page helps you see whether one section was skimmed or actually read

Longer time is not always better. Fast understanding can be a good outcome.

Page views

Page views are total viewed pages, not unique sessions. More page views can mean strong interest, rereading or confusion, so read this together with page reach and time on page.

Bounce rate and exit before end

Bounce rate shows sessions with little activity. Exit before end shows sessions that ended before the last page.

Use bounce rate to judge the opening. Use exit before end to find where a longer document stopped carrying people forward.

Then read the lower sections

The lower half of the analytics page answers the "why here?" question.

Trends

The trend line shows whether attention came from one send, stayed steady over time or changed after a new version went live.

Version changes in this range

The orange version markers matter when you replace one variant or publish a new file in the same slot. They tell you where the data changed, so you do not compare pre-update and post-update behavior as if it were one unchanged document.

A/B variant comparison

Use the variant comparison chart to see whether one active variant consistently pulled more sessions than the others. Then confirm the decision with readers, full reads and CTA clicks. A single spike is not enough on its own.

This is also where slot-based A/B testing stays readable. One public link stays the same while the analytics still shows which active file did better.

Page reach and time on page

Page reach shows how many sessions reached each page at least once. Time on page shows whether people spent real attention there.

That combination is usually the fastest way to find the first real breakpoint:

• strong early reach and weak mid-document reach means the structure loses people
• strong reach and high time on one page usually means decision point or friction point
• weak reach before pricing or proof means readers never even got to the section you care about

Source, location and platform

Use these after you understand document behavior itself.

Good uses:

• compare newsletter traffic with LinkedIn traffic
• check whether mobile readers drop earlier than desktop readers
• see whether one partner source brings stronger completion

Bad use:

• blaming the channel before you check the page where readers stopped

That matches the broader usability point from recognition over recall: the flow should make the next step obvious in context instead of forcing the reader to reconstruct it later.

How to read A/B tests and version updates

When A/B testing is active, read the result in this order:

1. Check which variant got enough sessions to be worth comparing.
2. Compare readers and full reads, not just opens.
3. Check CTA clicks or downloads only after the document earned attention.
4. Use page reach to find where one variant starts losing people.
5. If you replace one weak variant, use the version marker to separate old and new data.

This is why one slot and one public link matter. The workflow stays stable while the comparison stays honest.

If you have not started that flow yet, use the A/B setup guide first.

Three practical use cases

Sales deck

For a sales deck, compare:

• readers on the opening pages
• page reach on proof and pricing
• CTA clicks after the pricing section

If one opening gets more readers and stronger CTA clicks, keep it. If it gets more opens but weaker readers, the send worked better than the deck. If CTA clicks stay weak even with strong reads, the deck may be doing its job while the next step is still too vague.

Proposal review

For proposals, page reach around proof, rollout and pricing usually matters more than raw traffic.

If readers reach pricing fast and then exit before the end, the proposal may be asking for evaluation before it built enough confidence. If one variant keeps stronger reach through rollout and still gets CTA clicks, that is usually the better structure. In this flow, CTA clicks help confirm that the proposal did not only get read, but also moved the buyer to a concrete next step.

Onboarding guide

For onboarding, watch full reads, page reach on the first setup steps and time on page around dense explanation sections.

That fits older NNGroup reading research: people often scan long content, so structure has to carry them quickly to the action pages.

If the short guide gets more full reads but weak reach on setup pages, it may be too compressed. If the long guide loses people before setup starts, the opening path likely needs to tighten. If readers reach the setup section but do not use the CTA, the guide may explain the task but still fail to make the next action feel immediate.

What to do next

Use the first upload guide if you still need the basic publish flow. Use the A/B guide if the next job is comparing variants, keeping one slot password or replacing one weak file without changing the public link.

When A/B testing is the right next step

Upload two to five PDFs into one slot, keep one slot title and let sessions split evenly across the active variants. If the document is protected, the password belongs to the slot, not to each file.

Start the test in four steps

1. Open one slot and upload two to five PDFs.
2. Keep one slot title for the public link.
3. Set one password rule for the active set if the link is protected.
4. Publish the slot and send one public link.

After that, AnDocs assigns new sessions randomly and evenly across the active variants.

The best use cases are document decisions that can change reading behavior inside one stable link:

• test two sales deck openings
• compare proposal structure or pricing order
• compare a shorter onboarding version with a more detailed one

How the slot works

One A/B slot in AnDocs has a few hard rules:

• up to five active variants
• equal random split only
• one slot title for the public link
• one password state for the active set
• each active variant counts as its own document in the plan

This is intentionally simpler than ad-style weighting. The point is to compare document decisions without creating several public links or hidden access states.

That also means the slot can keep the rest of the workflow stable while you compare the document itself: same public link, same password rule and the same CTA or download path for readers.

How to keep the access flow safe

If the slot uses a password, every active variant has to fit that same rule. Otherwise the same link can become inconsistent for readers, which is exactly what should not happen in a secure review flow.

Use one slot password when:

• one audience gets one shared link
• the file may be replaced later
• A/B testing is active

If different audiences truly need different passwords, that should usually be a different slot.

How version replacement should work

When one variant loses, replace that file inside the same slot instead of creating a brand new public link. That keeps the history cleaner and the workflow easier to follow.

Treat replacement as a real version change:

1. keep the slot
2. keep the link
3. replace only the weak variant
4. compare the new version against the remaining active set

That replacement shows up later in analytics as a version change marker, so the before and after periods stay readable.

Check the reader flow before sending traffic

Open the preview once before a real send. You want to confirm the slot title, page order and viewer behavior before the test starts collecting live sessions.

What to do next

After the test starts, use the analytics overview to compare readers, full reads, page reach and variant changes before you replace anything else.

Start with one clean document flow

Start with one real PDF, one stable slot title and one clear next step. Publish the slot, open the public viewer yourself and only then send the link.

What to set before you publish

The first setup should stay simple:

1. upload one PDF
2. set the slot title people should recognize later
3. add a short description only if it helps the reader
4. add a CTA only if the next action is already obvious
5. turn on a password only if the file is actually sensitive

The slot title matters more than the raw file name because the slot is the thing you will keep sharing, updating and reviewing later.

A CTA helps most when the document already has one clear next step:

• sales deck: book a call
• proposal: approve scope or reply
• onboarding guide: open the setup page

If the real next step is still discussion, review or internal forwarding, leave the CTA off and let reads, reach and downloads carry the signal first.

If this is the first time you are setting up a link, do not start with A/B. Start with one clear document and one clear follow-up action.

How the public link should look before the first send

Before you send the link to anyone else, check the public viewer once yourself. The opening page needs to feel clear fast. That still matches what we know from Lindgaard's first-impression research: weak early framing hurts the rest of the review.

Review three things:

• the slot title is correct
• the first page is the right first impression
• the CTA or download action matches the job of the document

That makes the simple single-file flow useful for more than one job:

• share a sales deck and push readers to book the next call
• send a proposal and measure whether people move to the approval step
• publish an onboarding PDF and send people to the setup page only after they actually read it

What happens after publish

Once the slot is live, one link becomes the center of the workflow. From there you can:

• send the public link
• return to the same slot to replace the file later
• open the app preview if you want to inspect the reader flow
• review analytics after real sessions arrive

That is also when the workflow splits:

• if one file is enough, stay with the same slot and review metrics
• if you need to compare openings or structure, move to the same-slot A/B flow

Where this stops being a single-document workflow

If you already know you need to compare two openings, two proposal structures or two onboarding versions, do not create separate links too early. Move straight to the A/B guide so the variants stay under one slot.

What to do next

After the first real send, go to the analytics and metrics guide and review readers, full reads and page reach before you change the file.

Begin with what the recipient must do

"Do we need a client portal?" is often asked too early. Start with the handoff instead.

If the recipient needs to read one finished proposal and choose a meeting time, a portal may add more setup than value. If they need to upload evidence, comment on several files, approve versions and return over many months, one PDF link will be too narrow.

The two approaches overlap around access and presentation, but they solve different sizes of work. AnDocs is designed for a controlled PDF handoff. A client portal is a shared operating space.

What a controlled PDF link does well

A controlled link keeps one finished file at a stable public address. The sender can present a clean title, manage availability and review signals such as opens, page reach, full reads, time by page, downloads and clicks on the next-step action.

That is useful for:

• A proposal followed by a scope call.
• A post-demo deck followed by a technical review.
• A campaign report followed by a renewal discussion.
• An onboarding guide followed by a kickoff.

The recipient does not need an account merely to read the document. The sender does not need to build a folder structure for a one-file exchange. The cost of that simplicity is scope: the link is not a project room, approval system or long-term client record.

What a portal earns by being heavier

A client portal becomes useful when the work continues inside the shared space. It can hold several file types, tasks, comments, approvals, uploads and a history that both organisations revisit.

That extra structure is justified when removing it would push coordination back into email. For example, a compliance engagement may require the client to upload documents, answer requests and track which items are accepted. A PDF can explain the process, but it cannot run it.

Portals also create operational work. Somebody must configure access, maintain folders, remove old members and teach clients where to act. For a long engagement this may be reasonable. For a single proposal it can delay the moment the client actually reads the material.

Compare the real requirements

Do not choose from the feature count alone. Write down the next three actions the recipient must take. If two of them happen outside the PDF, the workflow may already need a portal.

Security depends on the operating model

Neither label guarantees that a document is handled safely.

With a controlled link, decide how long it remains available, who owns it and what happens when a newer version replaces the file. Test the public viewer outside the team's session. Do not put credentials or material requiring specialised controls into a lightweight public handoff.

With a portal, review account provisioning, role boundaries, guest removal and the visibility of old projects. A login screen is not a complete access policy. The larger system may offer more controls, but it also creates more permissions to maintain.

The right comparison is not "link versus login." It is whether the chosen process matches the document's sensitivity, lifetime and required collaboration.

A small decision test

Use a controlled PDF link when all of these are true:

1. The document is finished.
2. The recipient primarily needs to read it.
3. There is one clear next action.
4. Collaboration can continue in the existing channel.
5. The link can be retired when the handoff ends.

Choose a portal when the recipient must upload, comment, approve, manage several artefacts or revisit a shared history.

There is also a reasonable middle path. An agency may use a portal for the long-running client relationship and a controlled document link for a specific proposal or executive report. The tools do not have to replace each other.

The smallest workflow that fully supports the handoff is usually the better one. A simple link should not be stretched into a workspace, and a portal should not be introduced merely to make one PDF look more formal.

An onboarding guide has one job

A guide is not successful because it contains every policy, screenshot and edge case. It is successful when a new customer or teammate can complete the first meaningful task without asking where to begin.

That makes the handoff as important as the writing. A 40-page PDF attached to a welcome email may be thorough, but the reader can still miss the setup page, open an old version or finish without knowing what happens next.

Use a PDF when the material is stable, should look the same for every reader and does not require collaborative editing. Keep changing instructions in maintained documentation instead of repeatedly exporting a file that becomes stale.

Give the reader a route through the document

The first page should say who the guide is for, what they will complete and how long the first pass should take. Put prerequisites before the setup steps, not in an appendix. If the guide serves several roles, provide a short route for each role rather than asking everyone to read every page.

A practical structure is:

1. What will be ready at the end.
2. What the reader needs before starting.
3. The first setup task.
4. A check that proves the task worked.
5. Common blockers and where to get help.
6. One next action.

The final action should be specific. "Continue onboarding" is vague. "Book the configuration review" or "Open the workspace and add the first document" gives the reader a testable next move.

Test the public handoff

Before sending, open the shared link in a private browser window on both a phone and a laptop. Check the title, first page, internal links, download behaviour and final action. This is also the moment to catch an internal filename or an instruction that depends on the sender's signed-in session.

AnDocs can place the finished PDF behind one controlled viewer and record signals such as opens, page reach, full reads, time by page, downloads and next-step clicks. These signals help the sender see whether the guide reached its critical steps. They do not prove that the reader understood or completed them.

Suppose readers repeatedly reach account setup but stop before the verification page. The useful response is to inspect that transition: perhaps a prerequisite is missing or the verification instruction is unclear. It would be a mistake to label those readers disengaged based only on the page sequence.

Review the guide against real questions

After the first few sends, collect the questions that arrive in support or during kickoff. Map each question to the page that should have answered it.

If the answer exists but people miss it, improve the route, heading or surrounding example. If it does not exist, add it to the maintained source and publish a new version. If the question belongs to a changing product state, link to current documentation instead of expanding the PDF.

Keep the guide honest about limits. A static PDF is a poor home for frequently changing interface details, account-specific data or a large troubleshooting catalogue. The more often those sections change, the more likely the public file will drift from the product.

Use one version and retire it deliberately

Choose one owner for the public guide. Record when it was reviewed and what event should trigger the next review. When a new version is ready, replace or retire the old public handoff rather than sending another attachment into the same email thread.

Before the next send, check:

• The guide matches the current product flow.
• The public title is clear and the internal filename is hidden.
• Prerequisites appear before setup.
• Every critical step has a visible success check.
• There is one next action.
• Old links have an explicit retirement decision.

The best onboarding guide is not the longest. It is the version a reader can follow, verify and leave at the right next step. Document analytics can show where the path was taken or abandoned. The team still has to learn why.

The short answer

Choose AnDocs when the job is to publish a PDF, keep one stable link, see how it was read and give the reader one clear next step. Choose DocSend when document sharing is already part of a wider sales or deal process that needs several files, eSignatures, team administration or a data room.

This is not a winner-takes-all comparison. The products overlap on tracked document sharing, but they solve different amounts of the surrounding workflow. The useful question is which parts you will use on the next live send.

What AnDocs covers today

AnDocs is PDF-only. A document slot can hold up to five active PDF variants, and new viewing sessions are split evenly between them while the public link stays the same. The sender can review opens, pages viewed, time by page, completion, CTA clicks and downloads for each variant.

The same slot also controls expiry, PDF password protection, download availability and where the action button appears. These are link and document controls, not identity verification or digital-rights management. Reading time is useful follow-up context; it does not prove intent, approval or who sat in front of the screen.

What DocSend adds around the document

DocSend supports a broader set of files and workflows. Its official pricing page lists multi-file sharing, video and rich-media analytics, file requests, branded viewers, eSignatures and Spaces. Higher plans add visitor email authentication, allow and block lists, dynamic watermarking, NDAs, granular permissions, audit logs and data-room analytics.

Those capabilities matter when several people manage content, a recipient must sign inside the same product or a deal needs a persistent room. They are not automatically useful for a proposal that still lives in one PDF.

Compare the pricing unit, not only the monthly total

AnDocs includes one active public document. Additional capacity costs EUR 1.47 before tax for each block of ten active public documents per 30 days. Every active A/B variant counts as an active public document, so a three-variant test uses three documents of capacity.

On 14 July 2026, DocSend's US monthly prices showed Personal at USD 10 per user, Standard at USD 45 per user, Advanced at USD 150 with three users, and Advanced Data Rooms at USD 180 with three users. Annual and regional prices can differ, so verify the current amount on the official page before buying.

The models answer different questions: AnDocs charges for live document capacity; DocSend packages users and workflow breadth. A low document count favors the first model. A team using eSignatures, shared folders and Spaces may get more from the second even at a higher monthly price.

A practical way to decide

• Start with AnDocs if the next send is a PDF, one owner manages it, page-level reading context and CTA clicks are enough, and you want to compare up to five variants on one link.
• Start with DocSend if the next process needs multiple file types, eSignatures, shared team content, authenticated visitors, a data room or stronger administrative controls.
• Do not choose either product from an analytics screenshot alone. Run one real document through the full path: upload, access, reading, follow-up and expiry.

If the focused path matches your work, review the AnDocs capacity model before publishing the next PDF.

The short answer

AnDocs is the narrower choice when a small number of live PDFs carries the workflow and you want page-level analytics, CTA clicks and built-in variant testing under one link. Papermark is a document platform: it supports single-document sharing too, but its paid plans extend into branding, more file types, team use and data rooms.

The overlap is real, so price alone is not enough. Decide whether you are improving one document or building a reusable document space.

Where AnDocs is deliberately narrow

AnDocs accepts PDF files and lets one stable public link serve up to five active variants. New sessions are distributed evenly, and the analytics separate those variants so the sender can compare reading and action signals without maintaining several campaign links.

Expiry, PDF password protection, download rules and a configurable action button live on the same document set. One account owner manages the workflow today. There are no team workspaces, custom domains, folders or data rooms, and AnDocs should not be bought on the assumption that those features already exist.

Where Papermark becomes a broader platform

Papermark's product overview covers both single documents and secure data rooms. Its current plans add folders, custom branding, more file types, custom domains, team members, visitor verification, allow and block lists, screenshot protection, dynamic watermarking, agreements and granular room permissions at different tiers.

Papermark is also open source and offers a self-hosted route. That can matter to teams that want to inspect the code or run their own deployment. It also introduces operating decisions that do not exist in a hosted, focused PDF tool.

Pricing reflects those different scopes

AnDocs includes one active public document, then charges EUR 1.47 before tax per block of ten active public documents for 30 days. Active variants count individually. Pausing or removing public access reduces the active count rather than leaving an unused workspace tier in place.

On 14 July 2026, Papermark's official pricing showed Free with 50 documents and 50 links, Pro at EUR 24 per month, Business at EUR 59 per month on annual billing, and Data Rooms at EUR 99 per month on annual billing. Monthly billing was higher for Business and Data Rooms. Plan limits and prices can change, so verify the current table before deciding.

AnDocs will usually cost less for a few active PDFs. Papermark can be the better value when folders, branding, many documents, team seats or room controls replace other tools in the stack.

Check the next six months, not an imagined future

• Use AnDocs if you have one owner, PDF-only material, a small active set and a real need to compare variants or track a document CTA.
• Use Papermark if you need branded document infrastructure, several file types, team access, custom domains, open-source deployment or data rooms.
• Treat page time as context in either product. It can show where attention accumulated, but it cannot explain why a reader paused or whether a deal will progress.

List the documents that will stay live for the next six months and mark which ones truly need a room, team access or stronger controls. If most rows still describe one PDF and one follow-up, check the AnDocs active-document cost against that list.

The short answer

Use AnDocs when you need a controlled PDF link, page-level reading context, CTA and download tracking, and optional variant testing. Use Digify when the document is sensitive enough to require named recipients, granular permissions, dynamic watermarking, Screen Shield, access terms or a governed data room.

AnDocs is not a low-cost replacement for those security controls. It solves a lighter sharing and follow-up job. The decision should begin with the consequence of an unauthorized view or copy, not with the number of features on a pricing page.

What AnDocs protects and what it does not

AnDocs can set a public-link expiry, protect the PDF with a password, disable the download button and revoke public access. It can also keep up to five active variants under one link and report opens, pages viewed, reading time, completion, CTA clicks and downloads by variant.

These controls reduce casual access and keep the sender in control of the live link. They do not bind access to a named person, stop every copy, prevent a photograph of the screen or add a viewer-specific watermark. A disabled download button is not DRM, and a password can be forwarded with the link.

What Digify adds for confidential material

Digify describes itself as a secure document-sharing and virtual data-room platform. Its official product guide lists named-recipient access, print and download restrictions, expiry, revocation, dynamic watermarks with viewer details, Screen Shield and page analytics for individual files.

For data rooms, Digify adds guest groups, file- and folder-level permissions, activity logs, exports and multiple roles. Its permissions guide distinguishes view, print, PDF download, original download, edit and no-access rights. Those distinctions matter in diligence, legal review, board materials and controlled intellectual-property sharing.

No browser product can make a viewed document impossible to reproduce. Digify raises the barrier and adds accountability; AnDocs offers a smaller set of controls for lower-risk material.

Choose from the risk, then check the price

AnDocs includes one active public document and charges EUR 1.47 before tax per block of ten additional active public documents for 30 days. Each active A/B variant counts separately.

Digify packages document security and data-room capabilities in subscription plans. Its pricing and packaging can change, and regional offers may differ, so check the official pricing page for the current amount after you define the controls you need. Comparing a light PDF workflow with a governed data room only by monthly price hides the main difference.

A security threshold for the decision

• AnDocs can fit proposals, onboarding PDFs and client documents where a password, expiry, download rule and revocable link are proportionate controls.
• Digify is the safer shortlist when a leak would create legal, financial or material competitive harm, or when access must be attributed and audited by recipient.
• If policy requires watermarking, screen protection, terms of access, granular roles or an exportable activity log, AnDocs does not meet that requirement today.
• In either product, document analytics are evidence of interaction, not proof of identity, understanding or consent.

Write down the minimum controls your policy or client requires before you open either product. If link-level controls are enough, review the AnDocs capacity model. If they are not, keep Digify or another governed document-security product on the shortlist.

Treat the handoff as three separate things

An agency proposal is ready at 2:17 p.m. The account lead wants it in the client's inbox today, the strategist expects comments by Friday and finance may revise one line before approval. Sending the file is easy. Keeping the handoff understandable after it leaves the agency is the real job.

There are three parts to that job:

1. The PDF contains the finished proposal, report or review.
2. The message explains why it is being sent, who should review it and by when.
3. The access layer controls the link, records basic reading activity and gives the sender a way to replace or restrict the document.

AnDocs handles the third part for one finished PDF. It does not turn the document into a collaborative workspace, collect line-by-line approvals or organize an account's entire file history.

An annotated client message

The handoff email does not need to describe the tracking technology. It needs to remove ambiguity.

Hi Maya — the campaign review is ready. Pages 6–9 contain the channel decisions; the appendix holds the supporting numbers. Please review it by Friday at noon. Use the button in the document to choose a 20-minute review slot. If the budget table changes before then, this same link will show the corrected PDF.

Each sentence has a job. The first names the document. The second directs attention without asking the client to hunt. The third creates a review window. The fourth offers one next step. The last explains the benefit of a controlled link in ordinary language.

A password may be appropriate for sensitive work, but it should travel through a different channel. An expiry date makes sense when the review period is genuinely limited. Neither setting rescues a PDF that contains information the recipient should not have received in the first place.

What the agency can learn after sending

Suppose the document was opened, the reader reached the channel decisions and the scheduling button was not used. The agency knows that the relevant pages were reached. It does not know that the client rejected the recommendation.

That distinction should change the follow-up. A useful message might ask whether the team wants to discuss the channel split or needs the supporting numbers in another format. A generic "just checking in" wastes the context; a claim about what the client thought invents context that the log cannot provide.

Opens, full reads, page time and button clicks are prompts for a better conversation. Page time can be distorted by an idle browser tab. A forwarded link may be used by more than one person. These are reading signals, not an approval record.

Choose the lighter tool only when the work is light

A controlled PDF link fits a proposal, monthly report, renewal summary, onboarding pack or creative presentation that is already finished and leads to one clear response. It also lets the agency replace the file behind the link when a corrected version is needed, instead of starting another email thread with another attachment.

Use a client portal or project workspace when the client needs a durable file library, several reviewers must comment, approvals have stages or source files change continuously. If the engagement requires those capabilities, avoiding a portal is not simplicity; it is missing workflow.

For a first trial, choose one repeated handoff—monthly reports are a good example—and use the same review message for three cycles. Check whether the link reduced version confusion and whether the reading signals changed the next conversation. If neither happened, adding more tracked documents will not create value.

The point of secure document sharing for agencies is not to make a PDF look like a portal. It is to give one finished document a controlled, explainable path from the agency to the next client decision.

The screenshots use demonstration data

The analytics screens below come from the AnDocs demonstration document. The numbers are fixtures used to show the interface. They are not a customer case study and they do not support a claim about conversion rates.

That distinction is a useful place to begin. Sales deck analytics records events inside a document viewer. It can show that a link opened, a page was reached or a button was clicked. It cannot show who made a buying decision, why someone paused or whether a second session came from the same person.

The overview separates link opens, readers and sessions because they answer different questions. An open is an access event. A reader is the privacy-preserving visitor grouping used by the report. A session is a period of activity. None of those labels is a verified human identity.

Read the labels before reading the story

The screen contains enough numbers to tempt a sales team into a neat narrative. Resist that for a minute.

• Link opens counts opens of the public document link.
• Readers groups activity for reporting without claiming a known recipient identity.
• Sessions separates periods of reading activity.
• Full reads reports sessions that reached the document's completion condition.
• CTA clicks counts clicks on the configured next-step button.
• Downloads counts use of the download action when downloads are enabled.
• Average time per reader and average time per page summarize recorded active time. An idle tab can still distort time-based interpretation.

These fields describe viewer activity. They do not measure understanding, approval or purchase intent. A full read can come from a careful buyer, a colleague checking the file or the sender testing the public link. A short session can mean low interest, a familiar topic or a page that answered the question quickly.

Use filters and source data to narrow the event set when that distinction matters. Do not convert a filtered set into certainty that the product does not provide.

Page reach is more useful than a single engagement score

The page report shows where sessions reached and how recorded time is distributed. It is often more useful than a combined score because the salesperson can compare the pattern with the actual structure of the deck.

Consider a 14-page proposal with implementation on pages 6-8, pricing on page 11 and security on pages 12-14. If the report shows that page 11 was reached but page 12 was not, two facts are available: the session reached pricing and did not continue to security. "The buyer only cares about price" is not a fact. Neither is "security is not a concern."

The deck itself supplies the context. If page reach falls sharply before a dense implementation diagram, review the diagram. If several sessions reach the CTA page but the button gets no clicks, check whether the action is clear and whether it asks for too much. Those are changes the sender can test without pretending to know the reader's thoughts.

For the mechanics of the report, the separate document metrics guide explains each view and filter.

Let the evidence shape the follow-up quietly

Avoid telling a prospect that you watched a specific page. It can feel intrusive and it overstates what the report knows. Use the activity as private preparation.

For the illustrative page pattern above, a restrained follow-up could read:

I have pulled the rollout assumptions and pricing options into a short recap. If the team is comparing the two launch paths, I can walk through the trade-off on Thursday. I can also send the security notes separately if that review is happening later.

The message makes the likely next decision easier without claiming that the analytics revealed intent. If the session stopped on the cover, sending another attachment would probably add noise. A better reply would ask whether the project is still timely and explain in one sentence why the deck matters.

CTA clicks deserve the same restraint. A click proves that the viewer used the button. It does not prove that the meeting happened, the form was completed or the opportunity moved stage. Check the destination system before updating the sales record.

Test the document, not the person

Choose one post-demo deck that already leads to a clear next step. Keep the page order, headings and CTA stable for several sends. If every proposal has a different structure, the page patterns describe different documents and cannot be compared cleanly.

Before sharing, open the PDF on a phone and a laptop. Give implementation, pricing and security sections headings that make sense without narration. Remove internal filenames from the public view. Keep one next-step action. Then review the report shortly before the planned follow-up instead of watching it as a live notification feed.

When the next call happens, compare the report with what the prospect actually says. Trust the conversation when the two disagree. The mismatch is not a failed dashboard; it is evidence of the dashboard's limit.

AnDocs fits a finished PDF that needs a controlled link, basic access settings and page-level reading context. It is not a deal room, a collaborative editor or a system for verified recipient identity. Sales deck analytics is useful when it helps someone fix a confusing page, write a shorter follow-up or ask a better question. It should not be used to score a person's intent.