> 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/documentation/ja-gitbook-documentation/publish/adaptive-content/enabling-adaptive-content/url.md).
# URL
URL のクエリパラメータを通じて、訪問者データをドキュメントに渡します
{% hint style="info" %}
ガイドを見て、 [詳細な手順](https://gitbook.com/docs/guides/docs-personalization-and-authentication/how-to-personalize-your-gitbook-site-using-url-parameters-and-adaptive-content) Cookieを使ったアダプティブコンテンツの設定方法について。
{% endhint %}
URL クエリパラメータを通じて、訪問者データをドキュメントに渡すことができます。以下はその方法の概要です:
| 方法 | ユースケース | 設定のしやすさ | セキュリティ | 形式 |
|---|
クエリパラメータ visitor.<prop>= | 機能フラグ、ロール | 使いやすい | ❌ 訪問者がプロパティを上書きできます | JSON |
### クエリパラメータ
URL パラメータを通じて GitBook にデータを渡すには、次の形式で URL にデータを渡す必要があります `visitor.`.
例えば：
```url
https://docs.acme.org/?visitor.language=fr
```
これにより、これらのクレームを次の場所で使用できるようになります [条件エディタ](/docs/documentation/ja-gitbook-documentation/publish/adaptive-content/adapting-your-content.md#working-with-the-condition-editor) 署名なしオブジェクトの下で：
```javascript
visitor.claims.unsigned.language === "fr"
```
{% hint style="warning" %}
クエリパラメータを通じて渡されるデータは、訪問者スキーマ内で次の方法により定義する必要があります [署名なし](/docs/documentation/ja-gitbook-documentation/publish/adaptive-content/enabling-adaptive-content.md#set-an-unsigned-claim) オブジェクト。また、クエリパラメータは訪問者によって簡単に変更できるため、機密性のない情報に最適です。
{% endhint %}
### 動画チュートリアル
{% embed url="\_" %}
---
# 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/documentation/ja-gitbook-documentation/publish/adaptive-content/enabling-adaptive-content/url.md?ask=&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.