> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/ja/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/segments/manage-your-partner-segments.md).

# パートナーセグメントを管理する

この記事では、あなたの [パートナーセグメント](/brand/ja/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/segments/create-a-partner-segment.md).

1. 左側のナビゲーションバーで、 ![](/files/7ddd72d8e69e7055d9408cf4847c5c54abf9f71d) **\[Engage]** → **パートナー** → **自動化** → **セグメント**.
2. を選択 **ステータス** で絞り込む *アーカイブ済み* または *アクティブ* セグメント。
3. を選択します ![](/files/187769f9262d59ed36ce79b3988030fed7098825) **\[列]** 画面右側で、テーブルの列を追加または削除します。

   | 列     | 説明                        |
   | ----- | ------------------------- |
   | 名前    | セグメントの名前。                 |
   | 作成日   | セグメントが作成された日付。            |
   | 最終更新者 | セグメントに変更を加えた最後のアカウントユーザー。 |
4. 変更を加えたいセグメントにカーソルを合わせて、 **編集**.
5. 必要に応じて、セグメントにカーソルを合わせて、 ![](/files/967afd940eacbf83a7772ab9ff5584bc129c9568) **\[More]** 次を選択します：
   * セグメントのパートナーをプレビュー
   * 複製
   * アーカイブ


---

# 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://help.impact.com/brand/ja/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/segments/manage-your-partner-segments.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.