> 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：キャンペーンの成果を表示する

キャンペーンを立ち上げて運用するためのすべての手順を完了したら、次のレポートでさまざまなパフォーマンス指標を確認できます。

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

こちらを参照してください [クリエイター レポートの概要](/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.
