# Website Visitor Identification

#### **What is Website Visitor Identification?**

A significant % of website traffic are digital "ghosts". They’re visiting key pages, documentations - but not filling up any forms. But that doesn’t rule out the fact that they might be potential leads you don’t know about. That’s where Website Visitor Identification comes in - turning anonymous website visitors into de-anonymized developers.

While traditional analytics tell you *what* happened (page views, session duration, bounce rates), website visitor identification reveals *who's* behind those interactions. It's the difference between knowing "someone from San Francisco spent 12 minutes on our pricing page" and discovering "Sarah Chen, Senior Engineering Manager at a Series B fintech startup, explored your API documentation and pricing—twice this week."

So instead of seeing traffic only identified by source, you gain visibility into the actual identified developers browsing your website/documentations.

#### **Why is Website De-anonymization a key part of your GTM engine?**

From a passive source to an active lead generation and prioritzation engine -Website Visitor Identification changes the game by de-anonymizing website visitors while they're in-market, not after they're deep into their evaluation and maybe already chosen a competitor.

* **Capture hidden pipeline** - When you’re able to identify website visitors - you’re no longer waiting for leads to come to you. You’re pro-actively engaging developers that might be potential prospects.
* **Perfectly timed, contextual outreach** - Because you get the full context on which pages the prospect visited - your sales teams can reference this into their outreach instead of shooting out generic/cold emails.
* **Find high-intent prospects before your competitors do** - By identifying website visitors early on in their evaluation process, you get first-mover advantage in building relationships with prospects competitors can't even see.

Every developer who checks out your documentation, every decision-maker who downloads your whitepaper, every prospect who's clearly in research mode but hasn't filled out any first-party forms yet —they're all visible now.

There are 2 types of website visitor identification you can set up on Reo.Dev: <br>

1. [Basic Website Visitor Identification ](https://docs.reo.dev/integrations/input-sources/website-visitor-insights/website-visitor-identification/basic-website-visitor-identification)
2. [Enhanced Website Visitor Identification ](https://docs.reo.dev/integrations/input-sources/website-visitor-insights/website-visitor-identification/enhanced-website-visitor-identification)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.reo.dev/integrations/input-sources/website-visitor-insights/website-visitor-identification.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.