How to Identify Document Viewers
Choose between anonymous links, email gates, and verified access without overstating what identifies a reader.
On this page (8 sections)▼
To identify document viewers, choose an access method that captures the account used to open the document. Anonymous links, entered email, verified email, and recipient-specific URLs provide different levels of attribution.
Decide how much identity you actually need, test the chosen method, and describe its limits honestly. An IP address or a link label is not the same as a verified person.
1. Compare the identity methods
Start with what the platform can observe.
| Method | What it associates with activity | Important limitation |
|---|---|---|
| Anonymous link | A session or technical identifier | No reliable person name |
| Entered email | The address someone typed | May not establish control of the inbox |
| Verified email | Access to an email account | Does not prove the physical reader |
| Recipient-specific URL | The link assigned to a recipient | Forwarding can complicate attribution |
| Allowed-recipient gate | Permitted account access | Shared accounts remain a limitation |
These describe identity concepts, not identical implementations across every platform. Check how your selected service handles each method.
2. Separate identity from permission
Knowing an address and restricting access are different outcomes. A gate may capture an email from anyone, while an allowed-recipient list can reject accounts outside your selected group.
SendNow's specified-user documentation describes exact allowed addresses and an inbox code before entry. SendNow: Specified-user access Use the current help to check entitlement and configuration.
Do not assume a generic 'require email' label means every service verifies the address. Ask what happens after entry and whether another person's address can be submitted without proof of inbox access.
3. Test with addresses you control
Create a harmless sample link and an intended permitted identity. Open it in a fresh session and complete the access process. Check how the resulting visitor is labeled.
If the purpose is restriction, try another address you control that is not permitted. Expect rejection according to the chosen policy. Do not use an unrelated person's email for testing.
Record:
- The exact link settings.
- Whether a code or sign-in was required.
- The account recorded in analytics.
- What happened with a non-permitted account.
- Whether reopening changed the record.
This is a recommended verification process, not an already executed test.
4. Check what forwarding changes
A personalized link can be forwarded. Unless the service adds an identity requirement, later activity may remain associated with the original link rather than a newly verified viewer.
Test permitted forwarding with accounts you control when attribution matters. Ask whether the second account is recorded distinctly, blocked, or attributed to the original URL.
Avoid using location or device details to fill in missing identity. They may provide context but do not establish someone's name, employer, or authority. A shared device and shared mailbox also weaken person-level conclusions.
5. Report the account, not an imagined individual
Use careful labels in your working notes:
| Observed evidence | Appropriate wording |
|---|---|
| Verified account entry | This email account accessed the link |
| Anonymous activity | An unidentified visit was recorded |
| Activity on a personalized URL | Activity occurred through this assigned link |
| Allowed-account access | A permitted account completed the gate |
Do not translate those records into 'the CEO read every page.' That adds assumptions the system did not observe.
SendNow's visitor documentation explains how captured identity appears in its visitor records. SendNow: Visitor records and export Review the exact row rather than guessing from totals.
Collect only what the task needs
Identity requirements should serve the sharing purpose. A confidential report may need named access; a public brochure may not. Explain the access step before the recipient opens the link.
Keep viewer records within the appropriate team and share summaries rather than unnecessary personal details. If a colleague only needs overall activity, do not automatically hand over a full row-level export.
Use the person's actual reply to establish intent, approval, or the next action. Identity and engagement data provide supporting context.
Frequently asked questions
Is an entered email always verified?
No. Confirm whether the service uses an inbox code, authenticated sign-in, or another verification step. A text field alone is not verification.
Can a forwarded link misattribute a view?
It can, depending on the link and identity model. Test forwarding behavior before treating personalized URLs as proof of a particular reader.
Does verified email prove who was physically reading?
No. It establishes an account access condition, not the identity of every person looking at the screen.
Before you share
Choose the identity requirement deliberately, test its behavior, and preserve its meaning in your reports. Accurate attribution is more useful than a confident guess.
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 Export Document Analytics
Export engagement data and preserve the link, date range, file version, and metric definitions needed to interpret it.