> For the complete documentation index, see [llms.txt](https://gitbook.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.com/docs/publish/adaptive-content/enabling-adaptive-content/url.md).

# URL

Pass visitor data into your docs through URL query parameters

{% hint style="info" %}
Head to our guides to find a [full walk-through](https://gitbook.com/docs/guides/docs-personalization-and-authentication/how-to-personalize-your-gitbook-site-using-url-parameters-and-adaptive-content) on setting up adaptive content with cookies.
{% endhint %}

You can pass visitor data to your docs through URL query parameters. Below is an overview of the method:

<table data-full-width="false"><thead><tr><th width="325.45703125">Method</th><th width="266.6015625">Use-cases</th><th width="206.58984375">Ease of setup</th><th width="202">Security</th><th>Format</th></tr></thead><tbody><tr><td>Query parameters <code>visitor.&#x3C;prop>=</code></td><td>Feature flags, roles</td><td>Easy to use</td><td><span data-gb-custom-inline data-tag="emoji" data-code="274c">❌</span> Visitor can override the properties</td><td>JSON</td></tr></tbody></table>

### Query parameters

To pass data to GitBook through URL parameters, you’ll need to pass the data in the URL in the format `visitor.<prop>`.

For example:

```url
https://docs.acme.org/?visitor.language=fr
```

This will allow you to use these claims in the [condition editor](/docs/publish/adaptive-content/adapting-your-content.md#working-with-the-condition-editor) under the unsigned object:

```javascript
visitor.claims.unsigned.language === "fr"
```

{% hint style="warning" %}
Data passed through query parameters must be defined in your visitor schema through an [unsigned](/docs/publish/adaptive-content/enabling-adaptive-content.md#set-an-unsigned-claim) object. Additionally, query parameters can be easily changed by the visitor and are best suited for non-sensitive information.
{% endhint %}

### Video tutorial

{% embed url="<https://www.youtube.com/embed/hCd2_AAHU_I?si=jm2VOThMVh7NdJm>\_" %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://gitbook.com/docs/publish/adaptive-content/enabling-adaptive-content/url.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.