# Website Visitor Identification with Verified Email

> Identify verified viewers of shared proposals, reports, and demos while keeping anonymous website traffic private.

## Website Visitor Identification for Shared Client Work

**Website visitor identification** may sound like revealing every site visitor, but Verified Email does not. It helps you **identify website visitors** who choose to open a deliberately shared link and verify an email address they control. Public, anonymous traffic stays anonymous.

**TL;DR:** Verified email access lets shared-link viewers identify themselves while public traffic stays anonymous, a narrower, more useful promise for client work. Use proposal tracking and document tracking to share a presentation, report, file bundle, or demo; receive an open notification; and see what an authorized viewer did next. It explains:

- What Verified Email confirms, and what it cannot prove
- When aggregate analytics are enough
- How paid, permission-gated viewer activity supports better follow-up

If you are asking *who viewed my website*, first distinguish the website and audience. A public homepage and a private proposal link are different problems.

## What Website Visitor Identification Really Means

Two ideas hide inside **website visitor identification**. Aggregate measurement covers visits, viewed paths, referrers, countries, and likely bot traffic. Attributed activity ties a known email address to a protected link's page views, clicks, or downloads.

Ordinary analytics may recognize a browser or session, but cannot reliably name the person using it. Cookies store state to connect requests from the same browser, but privacy controls can block them, and cross-site tracking carries real privacy costs, as [MDN explains](https://developer.mozilla.org/en-US/docs/Web/Privacy/Guides/Third-party_cookies).

| Question | Honest answer |
|---|---|
| Can aggregate analytics identify website visitors by name? | No. They report traffic patterns, not a person's identity. |
| Can Verified Email support website visitor identification? | Yes, after a visitor submits and verifies an email to open a deliberately shared link. |
| Does verification prove a legal identity or job title? | No. It proves control of the inbox at that moment. |
| Can Revdoku tell who viewed my website if the page was public and ungated? | It can show aggregate activity, but it does not deanonymize the people behind that traffic. |

That boundary matters. **Website visitor identification** requires a clear access exchange, not a hidden guess.

## How Verified Email Access Helps Identify Website Visitors

Verified Email adds a short access step before shared work. It does not identify visitors after they arrive anonymously.

It asks recipients to identify themselves before access. Screens vary by publication settings, but the logic is simple.

1. **You publish the work.** Drag a PDF, presentation, demo, or folder into a Revdoku bucket, creating a live link with built-in viewing.

2. **You choose an email gate.** Gate the shared link with Verified Email when attribution matters. This mode uses an emailed one-time code and no shared site password.

3. **The recipient verifies access.** The visitor submits and verifies an email, connecting the protected session to an inbox they control.

4. **Revdoku records permitted activity.** You can receive an open notification and, when plan, settings, and workspace permissions allow, attribute viewed pages, clicks, and downloads to the verified address.

![Revdoku Require Email access settings with verified-email viewer options](/assets/website-visitor-identification/app-verified-email-access.webp)

5. **You follow up with context.** Follow up because the client opened the proposal or downloaded the pricing file, not because a tracking pixel fired.

As of March 2024, Litmus reported Apple Mail Privacy Protection affected **55% of opens**, making many email opens unreliable engagement signals. [Link activity after access is a more direct signal](https://www.litmus.com/blog/measure-email-marketing-success), though it still does not tell you what a viewer thought.

## Visitor Analytics and Permission-Gated Viewer Activity

Good **website visitor identification** separates audience-level **visitor analytics** from activity tied to a verified viewer. Revdoku offers aggregate publication analytics; detailed per-viewer activity is paid and visible only when access mode, plan, and workspace permissions allow.

| Data level | What it can show | What it means |
|---|---|---|
| Aggregate analytics | Hits, visitors, popular paths, referrers, countries, and likely bot activity | How the publication performs as a whole |
| Protected-link event | An authorized link was opened and an owner alert was triggered | Someone completed the required access flow |
| Verified viewer activity | Verified email, pages viewed, clicks, and downloads, when available | Activity attributed to that verified session |
| Lead or form submission | Email plus information the visitor chose to submit | A direct request, question, or expression of interest |

The [Revdoku analytics API](https://revdoku.com/api/) also documents ranges of 7, 30, and 90 days for aggregate reporting. Those **client link analytics** show which proposal pages get traffic and whether a demo is revisited.

They answer *who viewed my website* only when a protected viewer completes Verified Email and the owner can access viewer-level data. Revdoku attributes allowed activity to an OTP-verified address, not a secret profile derived from an anonymous IP address.

## Choose the Right Verified Email Access Mode for Website Visitor Identification

Identification adds friction, so I would not gate a public brochure merely because the setting exists. Use the lightest access mode that fits the work and the relationship.

| Access mode | Best for | Can it identify website visitors? | Tradeoff |
|---|---|---|---|
| Public | Portfolios, public samples, open resources | No; use aggregate analytics | Lowest friction, broadest access |
| Password | Client previews, shared drafts, small groups | Usually not by person; several people may share one password | Better privacy, weak attribution |
| Verified Email | Proposals, decks, reports, and demos where follow-up matters | Yes, by verified email for permitted activity | A short access step |

An email gate is lighter than a full account, while forced registration is costly. In a 2022 study of 4,384 U.S. adults, **24%** of online shoppers said they had abandoned a cart because they were forced to create an account. The context was ecommerce, not client documents, but the lesson travels: [do not turn a simple view into a signup project](https://baymard.com/blog/make-guest-checkout-prominent).

Use Verified Email when visitors can understand why you ask. Without a clear reason, identification is the wrong goal.

## Set Up Website Visitor Identification in Revdoku

You need no code. Set up **website visitor identification** in the dashboard, then share it in a few steps.

1. **Create or open a bucket.** Keep each deliverable or client project in one bucket. Add a PDF, slide deck, HTML demo, or folder, then review the generated navigation and viewers.

2. **Publish a stable link.** Name the publication clearly. Its URL remains stable when you replace a file or publish a revision, preventing recipients from comparing old links.

3. **Select Verified Email access.** Add a password if the material needs a shared secret. Explain the gate plainly: “Verify your work email to open the proposal and let us know who has access.”

4. **Set owner access.** Choose which workspace members can see aggregate analytics, captured leads, and paid viewer-level activity; file-editing contractors may not need visitor records.

5. **Test the recipient experience.** Test the link in a private browser window by verifying access, viewing several pages, clicking a link, and downloading a safe test file. Confirm the expected notification and records.

6. **Share with named recipients.** Send the link through your usual channel, then update the bucket after feedback instead of sending a new URL.

Default to manual uploads. Use APIs, the CLI, or AI agents when repeated publishing becomes tedious.

## Five Website Visitor Identification Examples for Proposal Tracking

These illustrative examples use numbers to clarify the workflow. Each owner wants to **identify website visitors** to an intentionally shared link, not uncover people on a public site.

- **Freelance proposal:** A designer sends one **proposal tracking** link to a sponsor and procurement contact, who verify separately. The sponsor views the approach pages and procurement downloads the fee schedule, letting the designer tailor each reply without asking whether the file arrived.

- **Agency presentation:** An agency sends six client stakeholders a 30-slide campaign deck; four verify and open it, three reach the media plan, and one downloads the budget PDF. The team schedules its review around pages that drew attention.

- **Founder demo:** A founder sends a demo to 12 prospects; after forwarding within one company, seven verified addresses replace one vague “company visit.” Two viewers click pricing, a useful **website visitor identification** signal that does not prove buying authority.

- **Consulting report:** A consultant uses **document tracking** to publish a 40-page report and spreadsheets; finance downloads the model and operations reads the setup pages. The consultant sends role-specific notes while updating the report at the same URL.

- **AI-built dashboard:** An agent refreshes a static dashboard each morning through the API; stakeholders verify by email, and an authorized owner reviews activity. Automation updates files without widening access or bypassing permissions.

Built-in feedback and contact forms can turn any of these links into a conversation without a separate backend.

## Website Visitor Identification Privacy and Accuracy Practices That Build Trust

Because **website visitor identification** uses personal data, its design requires restraint. Pew Research Center found **81%** of U.S. adults concerned about companies' use of collected data, while **73%** felt they had little or no control over it. [Clear notice is practical, not decorative](https://www.pewresearch.org/internet/2023/10/18/views-of-data-privacy-risks-personal-data-and-digital-privacy-laws/).

| Practice | What to do | Why it matters |
|---|---|---|
| Explain the gate | Say that email is required for access and activity may be visible to the sender | Visitors can make an informed choice |
| Collect less | Ask for an email, not unrelated personal details | Less stored data means less risk |
| Limit access | Give viewer analytics only to people who need them | Paid access alone is not a permission policy |
| Set retention rules | Remove visitor data when the business purpose ends | Old data creates risk without helping the client |
| Interpret carefully | Treat a view, click, or download as interest, not agreement | Analytics show behavior, not intent |

The FTC's business guidance gives **five principles**: take stock, scale down, lock data, dispose of it safely, and plan ahead. Its advice to [keep only information you need](https://www.ftc.gov/business-guidance/resources/protecting-personal-information-guide-business) fits this use case well.

Check the rules governing your visitors. The UK ICO, for example, says non-essential analytics cookies may require consent and organizations should disclose personal-data collection. Your notice, lawful basis, and retention practice remain your responsibility.

## Website Visitor Identification Limits

Searches for *who viewed my website* often expect more certainty than the web provides. These answers ground **website visitor identification**.

Sometimes the honest answer to *who viewed my website* is “we do not know.” For a deliberately shared protected link, Verified Email gives a limited answer: the verified address tied to the permitted session.

## Final Thoughts

**Website visitor identification** works best with a modest promise and clear business use. Revdoku can **identify website visitors** to proposals, decks, reports, demos, and file bundles by verifying email before access. It cannot or does not claim to reveal anonymous public-site visitors.

Remember:

- Use aggregate analytics when you need patterns, not names
- Use Verified Email when attributed follow-up is worth a short gate
- Restrict paid per-viewer activity to authorized people and explain the collection

Start with one client deliverable: add its files to a bucket, choose a gate, test the link, and share it. Update the same URL as the work changes. The result is current client work, clearer follow-up, and **website visitor identification** that respects the boundary between attribution and surveillance.

Start publishing for free

Connect this AI to Revdoku so it can store files, create, update, and publish websites for me. Read and follow https://revdoku.com/prompt.md. A Revdoku account is required. If I do not have one, send me https://app.revdoku.com/users/sign_up?utm_source=revdoku.com&utm_medium=ai-chat&utm_campaign=connect_ai_first and wait until I confirm signup is complete. For ChatGPT, Claude, or another cloud AI, connect https://app.revdoku.com/mcp and complete Revdoku OAuth. For a local agent, use Revdoku's browser device sign-in and complete the connection in Revdoku. Never ask me for a password or API key in chat, or for a verification code. When Revdoku tools are connected, verify the connection, tell me you’re ready, and ask what I want to publish.

Copy Prompt

or

Create Free Account

## Frequently asked questions

### Can I identify website visitors who never entered an email?

No. You can study aggregate traffic, but Revdoku does not deanonymize anonymous visitors.

### Does a verified email prove the person's legal identity?

No. It confirms control of an inbox. NIST treats identity proofing as a separate, higher-assurance process in its [Digital Identity Guidelines](https://www.nist.gov/identity-access-management/projects/nist-special-publication-800-63-digital-identity-guidelines).

### What if someone forwards the link?

Each new viewer should complete the access gate. Shared devices and inbox access still limit certainty.

### Does a page view mean the proposal was read?

No. It means the page loaded in an attributed session. A download also does not prove the file was read.

### Can everyone on my team see per-viewer activity?

They should not. Viewer-level activity requires a paid capability and proper workspace permissions.

### What if I only need total traffic?

Use aggregate analytics. There is no need to identify website visitors when a trend answers the business question.

### Can I add a reply path?

Yes. Add a Revdoku feedback or contact form to collect a question, approval note, or lead without building a backend.

### Can I update the deliverable?

Yes. Replace or revise files in the bucket and republish to the same stable link.

### When should I use Verified Email instead of public access?

Use Verified Email when knowing which recipient accessed a proposal, report, deck, or demo will improve follow-up or accountability. Keep general marketing materials and public resources open when aggregate traffic data is sufficient.

### What does verifying an email actually confirm?

It confirms that the viewer controlled the submitted inbox during the access process. It does not verify the viewer’s legal identity, job title, purchasing authority, or intent.

### What happens if a recipient forwards the protected link?

Each new viewer should be required to complete the configured access flow. Their activity may then be attributed to the email they verify, although shared inboxes and devices can still limit certainty.

### How should I interpret page views, clicks, and downloads?

Treat these events as signs of activity, not proof that someone carefully read, understood, or approved the material. Use them to make follow-up more relevant, then ask the recipient directly about decisions or concerns.

### Can I update a shared deliverable without sending a new link?

Yes. Replace or revise files in the existing bucket and republish them at the same stable URL. This helps recipients use the current version and avoids fragmenting activity across multiple links.

### How can I test the viewer experience before sharing?

Open the link in a private browser window, complete email verification, and test representative actions such as viewing pages, clicking links, and downloading a safe file. Then confirm that the expected notification and permitted activity records appear for the appropriate workspace members.

### Who should have access to viewer-level activity?

Limit access to team members who need the information for client service, sales, or account management. Review workspace permissions and retention practices regularly, and remove viewer data when its business purpose has ended.

---

[View the canonical page](https://revdoku.com/website-visitor-identification/) · [Browse llms.txt](https://revdoku.com/llms.txt)