# Basic Website Visitor Identification

#### **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="/files/bzvLf40xi80q5UYQbwwP" alt=""><figcaption></figcaption></figure>

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

<figure><img src="/files/9N0OgqEK8d3RfQqUzNMy" 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="/files/KxfAKCYqldwH817XhpN0" 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="/files/TRY1bAhLfkuu3iSDYofG" 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


---

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