> 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/what-would-you-like-to-learn-about/creator-program/recruit-creators/creator-content-check/add-creators-to-your-creator-content-check.md).

# Add Creators to Your Creator Content Check

Once you've [created a Creator Content Check policy](/brand/what-would-you-like-to-learn-about/creator-program/recruit-creators/creator-content-check/create-a-creator-content-check-policy.md), add creators from your social listener results to it to check their content against your standards. Ensure you've [created a social listener](/brand/what-would-you-like-to-learn-about/platform-features/find-partners-and-creators/social-listening/create-a-social-listener.md) then follow the steps below.

{% hint style="warning" %}
This feature is currently in closed beta and is not available to all brands.
{% endhint %}

1. From the left navigation bar, select ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2FLGBlwxuVWsrxNsjYUMjf%2Fdiscover-v2%20\(1\).svg?alt=media\&token=8a0e56eb-ff89-4046-8e72-ad2b503f8bf9) **\[Discover] →** [**Social Listening**](https://app.impact.com/secure/advertiser/discover/protect/fr/social-listening.ihtml).
2. Hover over a social listener and select **View Results**.
3. Select ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-12f7eaf63a57fcdca99505d28faa7518ee8f2e24%2F9edba0c2b540227e929a0d03bb91fcdff3738d652b0b14d839e37b5f47572b3d.svg?alt=media) **\[Grid]** to display the creators in a grid format.
4. Use the [search bar or filters](/brand/what-would-you-like-to-learn-about/platform-features/find-partners-and-creators/social-listening/view-social-listening-results-and-dashboard.md) to find specific creators' content.
5. Hover over the caption of the content and select ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2FNVJihd9nYKCiCEg5tI6i%2F2a92939e8e78dd7e0c0416b1a250d5ef1d7ab0dec966fb5ed320ca62acfc06c5.svg?alt=media\&token=7cab8ce5-a26b-4057-a822-0746130d9117) **\[More] → Add to Creator Content Check**.

<div data-with-frame="true"><figure><img src="https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2FykQRzljLYT6DVxrcVBKt%2Fcreator%20content%20checks.png?alt=media&amp;token=f46572dc-a026-499e-afb5-3965737e189e" alt="" width="148"><figcaption></figcaption></figure></div>

6. In the *Add to Creator Content Check* modal, select a policy from the ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-c2cb550b55c51ea1eeff0acbd6f437a03b621a2c%2F60d033ae8a04c14498d5229c3c0160ac05feea7f605dbd770741793c900469f0.svg?alt=media) **\[Drop-down menu]**.
   * If you haven't created a policy yet, you can select **Creator Content Check** from the modal which will direct you to the *Creator Content Check* screen. [Create a Creator Content Check policy](/brand/what-would-you-like-to-learn-about/creator-program/recruit-creators/creator-content-check/create-a-creator-content-check-policy.md), then add your creator.
   * If you've already added this creator to the selected policy, you can view the results by selecting **Creator Content Check** from the modal.
7. Select **Add**.
   * Once added, view the results. Refer to [View Your Creator Content Check Results](/brand/what-would-you-like-to-learn-about/creator-program/recruit-creators/creator-content-check/view-your-creator-content-check-results.md).
   * Results can take up to 4 hours to return.

{% hint style="success" %}
**Note**: A creator can be added to more than one policy. To check the same creator against different standards — for example, a general vetting policy and a stricter campaign policy — repeat these steps and select a different policy each time.
{% endhint %}

<div data-with-frame="true"><figure><img src="https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2F2rckbJOHtS30ScIcis4q%2FScreenshot%202026-08-19%20at%2014.04.11.png?alt=media&amp;token=cadd30c9-eb38-4e08-912f-c493e5e540d7" alt="" width="563"><figcaption></figcaption></figure></div>

## What happens next

Once a creator is added, their check runs against your policy's criteria.

* Creators show as *Pending* while a check is running.
* When a check finishes, the creator's content check label changes to *Safe* or *Unsafe*.
* Creators on a policy that hasn't been run yet show as *Not checked*.

You don't need to stay on the page while checks run.


---

# 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/what-would-you-like-to-learn-about/creator-program/recruit-creators/creator-content-check/add-creators-to-your-creator-content-check.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.
