> 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/creator-program/introduction-welcome-to-creator/step-6-view-your-campaigns-performance.md).

# ステップ6：キャンペーンの成果を表示する

キャンペーンを開始するためのすべての手順を完了すると、次のレポートでさまざまなパフォーマンス指標を確認できます。

* [コンテンツとキャンペーンの概要レポート](https://help.impact.com/brand/ja/what-would-you-like-to-learn-about/creator-program/creator-reports/content-and-campaign-overview-report.md)

指標の集計方法の内訳については、 [クリエイターレポートの概要](https://help.impact.com/brand/ja/what-would-you-like-to-learn-about/creator-program/creator-reports/creator-reports-overview.md) をご覧ください。

## キャンペーンのパフォーマンスを確認する際のベストプラクティス <a href="#section-idm235017160746596" id="section-idm235017160746596"></a>

* パフォーマンスを分析する際は、どの階層のクリエイターが最も成果を上げたか、どの種類のコンテンツやプラットフォームが最も効果的だったか、どのコンテンツテーマが最も高いエンゲージメントを得たかを検討しましょう。
* まず、メッセージ、ソーシャルプラットフォーム、コンテンツ形式など、1つの変数を一度に分析します。次に、クリエイターのセグメント別にパフォーマンスを分析し、成果を実際に左右する要因を明らかにします。こうした知見を活用して、何が最も効果的かを特定し、データに基づいて精度を高めながら今後のキャンペーンを改善しましょう。


---

# 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/creator-program/introduction-welcome-to-creator/step-6-view-your-campaigns-performance.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.
