> 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/seller-program/amazon-seller-program/introduction-welcome-to-impact.com/step-3-partner-engagement.md).
# ステップ3：パートナーとの連携
## アプローチを計画する
粘り強く、価値重視の一連の [アプローチメール](/brand/ja/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/email-workflows/create-and-manage-email-workflows.md)。簡潔にまとめ、より高い報酬率、長いCookie有効期間、成果ボーナスなど、プログラムに参加するメリットに焦点を当てましょう。
サインオンボーナスや一時的な報酬率の引き上げで条件を魅力的にし、初期導入を促しましょう。 [予定された条件](/brand/ja/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/set-limited-time-payouts-with-scheduled-terms.md) または [プロダクトブースト](/brand/ja/what-would-you-like-to-learn-about/beta-product-boost/product-boost-campaign-management/create-a-product-boost-campaign.md) これを実現するのに役立ちます。
## 関連ニュースを共有する
プロモーション、製品／機能のリリース、会社からのお知らせなどについて、パートナーに常に情報共有しておくことが重要です。impact.comの [ニュースレター](/brand/ja/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/newsletters/introduction-to-newsletters.md) 機能は、パートナーのエンゲージメントと生産性を高めながら、これを行う最も簡単な方法です。
## パートナーを教育する
あなたの [*リソース*](https://app.impact.com/secure/advertiser/engage/ads/manage-resources-flow.ihtml) 共有するためのページ [研修資料や教育用アセット](/brand/ja/what-would-you-like-to-learn-about/platform-features/ads/requests-from-partners/create-a-resource-to-share-with-partners.md) パートナーがあなたのAmazon商品を効果的に販売し、売上を生み出すのに役立ちます。あなたの *リソース* 初回のウェルカムメッセージや、予定しているニュースレター内のページ。
パートナーがあなたの製品をどのようにプロモーションし、何を理解できるよう、関連するヘルプドキュメントをぜひ共有してください。 [ベストプラクティス](https://help.impact.com/partner/what-would-you-like-to-learn-about/seller-partnerships/amazon-seller-partnerships/best-practices-for-seller-partners) が、彼らに最も大きな成功をもたらします。
---
# 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/seller-program/amazon-seller-program/introduction-welcome-to-impact.com/step-3-partner-engagement.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.