# 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.

#### **How does website visitor identification work?**

Reo.Dev’s Website Visitor Identification leverages a sophisticated **browser fingerprinting technique** and a **network of trusted third-party data providers** to de-anonymize website visitors.

Here’s how this unfolds:

* **High-Quality Developer Data**: Reo.Dev partners with reputable data providers to access a reliable database of developer profiles. This ensures that you’re identifying the most accurate, relevant people with higher confidence, without relying on outdated or generic data.
* **Browser Fingerprinting**: As visitors explore your site—whether they're reviewing documentation, checking out features, or engaging with specific content— we use browser fingerprinting (a technology widely adopted by sales intent tools - 6sense, Warmly, Vector, etc.) - to collect unique identifiers from their interaction. These data points are then matched against the trusted the developer data from our data-providers in real-time. If there’s a match, the developer is immediately identified, and you get to see exactly who is behind the visit.
* **Compliance & Security**: We prioritize privacy and security by ensuring:
  * We automatically exclude EU + UK - based visitors to ensure GDPR compliance
  * No personal contact information is exposed without proper consent
  * Visitors maintain control over their data through opt-out mechanisms

### **Configuring Website Visitor Identification on Reo.Dev**

Here’s a step-by-step breakdown on how you can control whether you want to enable or disable website visitor identification.

1. Website Visitor Identification is disabled by default for all customers.
2. Enabling/Disabling website visitor identification is accessible only to users with ‘ADMIN’ role on Reo.Dev

**Step 1:** Go to Settings > Integrations

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2FkkDjYvCxAtRn66KP9cGU%2Fimage.png?alt=media&#x26;token=a18c447f-6e7b-49f8-82a9-25de9eb93fe4" alt=""><figcaption></figcaption></figure>

**Step 2:** Next, click on configure under the '**Website Visitor Identification'** card

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2F2V0R9k8ibNmP0zZcrfJD%2Fimage.png?alt=media&#x26;token=205e53a0-8eaa-48a4-9b41-3bd881611199" alt=""><figcaption></figcaption></figure>

**Step 3:** Here you will see 2 options:

1. **Enable Identification** **(Recommended)**: Enabling this means you can view/access website and doc visitors even though they haven’t yet filled out any first party forms.

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2FUaoX1XQkwjiCYApEFvMd%2Fimage.png?alt=media&#x26;token=8375188f-2e02-4f73-8230-b8fbdc412c1d" alt=""><figcaption></figcaption></figure>

*Note: Any visitors from the EU/UK region are automatically excluded in compliance with GDPR. .*

Once you’ve enabled identification - you can view the identified developer profiles in the following sections on Reo.Dev:

1. Developer Section
2. Buyer Section
3. Account → Active Developers
4. Account —> Activity Timeline
5. Account → Prospects → Buyers
6. Account → Prospects → Developers

This gives sales and marketing teams immediate visibility into high-value anonymous traffic.

2. **Disable Identification:** At anytime you can choose to disable website visitor identification by clicking on the ‘disable identification’ option. This ensures that you only see website/doc visitors who have filled out your 1st party forms.

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2FKMniQHwBTSp6n4Czv3WA%2Fimage.png?alt=media&#x26;token=9c0eb63f-8a62-4b5c-95de-7bb333568982" alt=""><figcaption></figcaption></figure>

Once you disable this:

* All existing identified contacts (who have not filled out any forms) are removed from your interface.&#x20;

**Note:** In case you re-enable this feature you will be able to see these previously identified contacts again.

* Contact limits used by identified visitors are credited back to your account
* The feature can be re-enabled at any time through the same settings section
