How to Export Document Analytics
Export engagement data and preserve the link, date range, file version, and metric definitions needed to interpret it.

On this page (8 sections)▼
To export document analytics usefully, select the correct reporting scope, download the available records, and preserve the definitions needed to interpret them. A CSV without its link, date range, and version context can be misleading.
Decide whether the recipient needs detailed visitor records or a concise activity summary before handing over the export.
1. Define the report's purpose

An outreach review, client delivery record, and internal content analysis need different data. Write down the question the export should answer.
| Reporting need | Appropriate starting scope |
|---|---|
| One proposal's activity | The relevant link and document |
| Several campaigns | Clearly separated link groups |
| Content revision comparison | Identified file versions and dates |
| General team summary | Account-wide report with definitions |
Avoid starting with every available personal detail. If a colleague needs totals only, an aggregated report may be sufficient.
2. Check export availability and fields
SendNow's visitor help documents an Export CSV control for visible visitor rows and identifies Pro or Business eligibility. SendNow: Visitor records and export Verify the current account and the report you are using.
An NDA certificate export is a different artifact from a visitor CSV. Do not substitute one for the other just because both have an Export button.
Before downloading, record the active filters and displayed scope. If the interface lacks a requested date filter, do not pretend the export already matches that range. Apply a transparent downstream selection where appropriate.
3. Save the original export before editing

Keep an untouched source copy and make a separate working file for analysis. Use a clear filename identifying the document or report and export date.
Open the working copy and inspect:
- Column names and types.
- Timestamps and timezone assumptions.
- Blank or anonymous identity fields.
- Link and document identifiers.
- Whether filters affected the exported rows.
Do not assume a spreadsheet application's automatic formatting preserved every field. Check long identifiers, dates, and text values before sorting or joining records.
4. Create a small data dictionary

Describe each field you actually received. This example is a suggested reporting dictionary, not a claimed export schema.
| Field concept | Record alongside it |
|---|---|
| Viewer identity | Captured, verified or anonymous meaning |
| Visit time | Timezone and event definition |
| Document or link | Stable identifier and display title |
| Viewing duration | Whether it is per-session or aggregated |
| Completion | Provider's measurement rule |
| Download action | What event is counted |
If a field is not in the export, do not silently invent it. You can add editorial context in a separate column if it is clearly labeled.
5. Reconcile with the dashboard

Compare the working report with the same dashboard scope. A mismatch does not automatically mean either source is wrong. Check filters, versions, timezones, refresh timing, and whether one measure is an aggregate while another is row-level.
Do not count exported rows and label the result 'unique people' without the provider's identity rule. Repeat sessions and anonymous technical identifiers can complicate that interpretation.
Document any exclusions, including your own test visits. Keep the original file unchanged so the analysis can be reviewed.
6. Share a report someone can interpret
Include a short report note:
This export covers the proposal link shown above for the stated period. Viewing activity is not proof of reading or approval. The working summary excludes the explicitly identified test session; the original export is retained separately.
Remove personal details that are unnecessary for the recipient's task and use an appropriate access policy for the report itself. Do not place a row-level visitor export in a public document collection.
For a revision comparison, state whether old and new content occupy the same page positions.
Frequently asked questions
Which plan supports SendNow visitor CSV export?
The current visitor help identifies Pro and Business. Check the linked documentation and current account before promising export availability.
Are exported rows the same as unique visitors?
Not necessarily. Rows may represent visits or another event unit. Use the provider's definition before aggregating them.
Can I share the full export with a client?
Decide which information the client actually needs and which sharing permissions apply. A useful summary may avoid exposing unrelated visitor details.
Before you share
A useful export preserves meaning as well as numbers. Keep the original, define the fields, reconcile the scope, and hand over only the information the task requires.
Related articles
Sources and editorial disclosure
Primary documentation reviewed October 11, 2026. Product settings and entitlements can change; use the linked help for current details.
VDR Directory is published by the SendNow team. SendNow is included where relevant to the task. This guide is based on public documentation and editorial recommendations, not a claim that a signed-in product demonstration was performed. Stock photos illustrate the topic; they do not show the described product interface or prove feature behavior. Examples and verification checklists are illustrative unless explicitly stated otherwise.
Related Guides & Research
Recommended next reading for deal teams and transaction leaders.
How to Create a Document Microsite
Build an organized document page with clear file labels, navigation, and a useful next step.
Are Your Document Views Real?
Investigate automated opens and repeated sessions before using view counts for follow-up.
How to Identify Document Viewers
Choose between anonymous links, email gates, and verified access without overstating what identifies a reader.