> 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/performance-program/recruiting-partners/extended-search/extended-search-overview.md).

# パートナー向け拡張検索の解説

Extended Searchは、impact.comマーケットプレイス内およびimpact.comネットワーク外を検索することで、パートナーの発掘を自動化します。この検索機能は、主要な検索エンジンでキーワード検索を頻繁に行い、関連性の高い新しいパートナーを定期的に見つけて表示します。Extended Searchは、impact.comの [Prospects機能](/brand/ja/what-would-you-like-to-learn-about/performance-program/recruiting-partners/prospective-partners/track-partner-recruitment-efforts-overview.md) パートナーを見込み開拓ワークフローに追加することで。

#### メリット

* 収益成長を加速します。
* impact.comネットワーク内のパートナーを超えてリーチし、パートナーポートフォリオを多様化します。
* パートナー発掘を自動化して時間を節約します。
* 発掘の取り組みを一元化されたプラットフォームに集約します。

#### 仕組み

Extended Searchは強力なパートナー開拓ツールです。最大限に活用するための簡単なヒントをご紹介します。

1. 理想的なターゲット候補のプロフィールを検討し、一覧化します。
2. ターゲット候補がコンテンツ内で使用しそうなキーワードを特定します。
3. キーワードで検索を設定します。
   * 手順については、 [新しいExtended Searchを作成](/brand/ja/what-would-you-like-to-learn-about/performance-program/recruiting-partners/extended-search/create-a-new-extended-search.md).
4. 結果を確認し、興味のあるパートナーをProspectsに追加します。
   * 手順については、 [Extended Searchの結果を表示・フィルタリング](/brand/ja/what-would-you-like-to-learn-about/performance-program/recruiting-partners/extended-search/view-and-filter-extended-search-results.md).
5. Extended Searchとその結果を毎週見直します。
   * 手順については、 [Extended Searchを一時停止または削除](/brand/ja/what-would-you-like-to-learn-about/performance-program/recruiting-partners/extended-search/pause-or-delete-an-extended-search.md).

当社の [Extended Searchのベストプラクティス](/brand/ja/what-would-you-like-to-learn-about/performance-program/recruiting-partners/extended-search/extended-search-best-practices.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://help.impact.com/brand/ja/what-would-you-like-to-learn-about/performance-program/recruiting-partners/extended-search/extended-search-overview.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.