> For the complete documentation index, see [llms.txt](https://docs.claimr.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.claimr.io/data-analytics/ugc-analytics.md).

# UGC analytics

## What is the UGC analytics?

The UGC (User-Generated Content) analytics section gives you a full overview of all video and media submissions shared by users as part of your UGC tasks. It helps you evaluate the quality and relevance of these submissions and make data-informed decisions about user engagement and rewards.

**Use UGC analytics to:**

* Review user submissions: Open the images or links your users submitted.
* Track post performance: See metrics like views, shares, and comments — available for tracking tasks only.
* Manage content: Approve valid submissions or reject the ones that don’t meet your requirements.
* Rate content quality: Assign a score to each submission (internal use only).
* Monitor participation: Access submission timestamps, user IDs, and file or link references.

To learn more about how to create a UGC task, visit [UGC tasks](/tasks/ugc-tasks.md).

## How your users see UGC tasks

<figure><img src="/files/TRQuIENNAgtOKaKymowq" alt="" width="370"><figcaption><p>UGC task example</p></figcaption></figure>

1. Your user selects a UGC task in your campaign.
2. They upload an image or submit a link, depending on the task type.
3. The task is marked as completed.
4. Their submission appears in your UGC analytics section, where you can see and manage it.

## Accessing the UGC section

1. Log in to your claimr account.
2. Select your campaign.
3. Click the Analytics tab in the campaign menu.
4. Choose UGC from the analytics submenu.

### UGC dashboard

The UGC dashboard displays all user-submitted content in a visual grid. Each submission appears as a card that includes key information and actions. You can manage and evaluate incoming UGC here.

<mark style="color:yellow;">Need a nice SS</mark>

<figure><img src="/files/7AMPiGRAYX1BaBaqJwgF" alt=""><figcaption></figcaption></figure>

Use the dashboard to:

* View submissions: See thumbnails and link previews depending on the task type.
* Sort or filter entries: Filter by task type, status, or other parameters.
* Approve or reject: Click the ✓ or ✕ icon to change the submission status.
* Score content: Assign an internal quality rating to any UGC item.
* Bulk action Select multiple cards and perform approval/rejection actions for all selected entries.

### UGC's submission card&#x20;

<mark style="color:yellow;">Need a nice SS</mark>

<figure><img src="/files/RKRuOMqoDq39YIWNIfOi" alt="" width="312"><figcaption></figcaption></figure>

* Preview – A thumbnail for images or a visible link for URLs.
* User information – The user’s display name and ID (with copy option).
* Submission type – Image or link, depending on task settings.
* Performance metrics – Plays, shares, and comments (for tracking tasks only).
* Date – When the submission was received.
* Status – You can approve (✓) or reject (✕) any submission. By default, submissions are approved as soon as the task is completed, but you can manually override this.
* Score – An optional field where you can rate content. It lets you rate your users’ content based on creativity, relevance, or any other criteria you choose. It does not influence task completion or point allocation.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.claimr.io/data-analytics/ugc-analytics.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.