> For the complete documentation index, see [llms.txt](https://docs.wicle.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wicle.io/organization-project/project-setting/tag.md).

# プロジェクトの計測タグ設定

プロジェクトの計測タグ画面で確認・設定できる項目と、タグの設置、自動計測イベント・対象ドメイン・URLの設定手順への参照先を案内します。

サイドメニューの`プロジェクト / 組織設定`で対象の組織・プロジェクトを選択し、`プロジェクト設定`の`計測タグ`を開きます。

タグの確認・設置に加え、自動計測イベント、計測対象ドメイン、イベントごとの対象URLなどを設定できます。設定変更には組織のOwner権限が必要です。

具体的な設置・設定手順は、初期設定の[計測タグの設置・設定](/initial-setting/tag.md)をご覧ください。


---

# 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://docs.wicle.io/organization-project/project-setting/tag.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.