> For the complete documentation index, see [llms.txt](https://docs.vagon.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vagon.io/streams/configurations/visitor-data-collection.md).

# Visitor Data Collection

<figure><img src="https://lh4.googleusercontent.com/rm3vbznYoeH7iAgJoZupl88WhdLKZH_GMDLoJIn5zQykpim8iaSWBilmyFiGQAFISDyczumTRm9Fhxd04ompgP3xGHwqfUybZbw2SCnJSsjfZf-tCqy1yIq3dRp6TgQKzAJrLkNf6fDjM5IqlbR_hl4" alt=""><figcaption><p>Stream Configurations - Visitors</p></figcaption></figure>

## Collect Visitor Data

<div align="left"><figure><img src="/files/BMXS9T8M4mcG1BU5K7nn" alt="" width="48"><figcaption></figcaption></figure></div>

When the **Collect Visitor Data** is enabled, your visitors will be asked to share their email addresses before joining the Stream.

You will be able to collect visitor data and track connected user data from the Stats > Visitor tab inside your Streams Dashboard.

![](/files/CwxhTlpJZMmBB8tb6p7x)

### Visitor Data Collection via URL Parameters

In addition to the Visitor Data Collection page, you can collect user information by sending user email addresses via URL Parameters.

After your Streams URL, you just need to add `visitor_email` parameter and send the user email as the parameter value at the end of your URL. You can find the sample URL below.

`https://streams.vagon.io/streams/<STREAM_ID>?visitor_email=streams@vagon.io`

{% hint style="info" %}
If you are using both URL Parameters and Visitor Data inside your URL, be sure that you separated them via `&` sign to prevent issues.
{% endhint %}

## Connections Stats

<div align="left"><figure><img src="/files/BMXS9T8M4mcG1BU5K7nn" alt="" width="48"><figcaption></figcaption></figure></div>

When you enable **Connection Stats**, you will be able to monitor your visitor device and connection performance information on your Stats page.

**Visitor Stats** are also available through our Streams API which gives you the option to embed your streaming data to your own dashboard or system.

<figure><img src="/files/byX0OKnZiMqGtz8Ii7le" alt=""><figcaption><p>Vagon Streams Stats Page</p></figcaption></figure>

## Password Protection

<div align="left"><figure><img src="/files/Q6jum2ktNg3RYlu3t7K9" alt="" width="96"><figcaption></figcaption></figure></div>

When you enable **Password Protection** for your Streams, your users will be asked for a password to join your Stream, and visitors without the password will not be able to connect to your experience.

<figure><img src="/files/DHQjuSKodmhKflSoHl78" alt=""><figcaption></figcaption></figure>

## Visitor Authentication (SSO)

When you enable **Visitor Authentication (SSO)**, visitors must sign in with your identity provider — **Microsoft Entra**, **Auth0**, or **Google** — before they can connect to your Stream. This limits access to authenticated visitors only.

Visitor Authentication is an **Enterprise** feature available on individual Streams. For the full setup and per-provider integration steps, see the dedicated guide.

{% content-ref url="/pages/ZLISCWZgzuAFGhxGouvr" %}
[Visitor Authentication](/streams/custom-flows/visitor-authentication.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.vagon.io/streams/configurations/visitor-data-collection.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
