5. タスクにカーソルを合わせて、次を選択します **タスクの詳細を表示**.
6. 右側のスライドアウトで、次を選択します **成果物。**
* 検出された日付を確認できます。
7. 次を確認できます *クリエイター* コンテンツの、 *期限日*、 *一致したハッシュタグ* と、識別されたコンテンツです。ソーシャルプラットフォームのアイコンを選択すると、そのプラットフォーム上でコンテンツも確認できます。
* 同じハッシュタグで複数の成果物が投稿されている場合、それらもここに表示され、確認できます。
8. 成果物として送信したいコンテンツを選択し、次を選択します **投稿を承認**.
* 正しい投稿が自動検出されない場合は、次を選択します  **\[もっと見る]** → **投稿をさらに読み込む** と、さらに投稿を表示するか、次を選択します  **\[もっと見る]** → **成果物を手動で送信します。**
{% endtab %}
{% endtabs %}
---
# 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/creator-campaigns-for-brands/submit-campaign-tasks-on-behalf-of-your-hired-creators.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.
%20copy.png?alt=media&token=404e7225-62aa-491b-8497-f698119f4d1d)