> For the complete documentation index, see [llms.txt](https://gimi.gitbook.io/gimi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gimi.gitbook.io/gimi/for-brands/contest-campaigns.md).

# Contest campaigns

Run a GIMI contest campaign with a deadline, ranked or category prizes, and winners paid when you release results.

A contest campaign has a **deadline and winners**. Creators compete for ranked places, category prizes, or finalist rewards.

A contest can be:

* **Distribution-style** — creating and sharing on socials
* **Sourcing-style** — file upload only

Setup is similar to other campaigns, but you pay **prizes**, not an ongoing approval / performance / Spotlight mix.

## Why run a contest?

Use a contest when you want:

* Competition and a clear end date
* To reward selected winners rather than every qualifying contribution
* First, second, and third-place prizes
* Different creative categories
* A set of finalists

Contests can generate strong participation, but they need meaningful prizes and clear judging criteria.

## How do I set a contest deadline?

1. Create a contest campaign.
2. Open timing settings and activate the deadline.
3. Select the closing date and time, including time zone.
4. Save, and show the deadline clearly in the brief.

Creators should know when submissions close, whether late entries are accepted, when winners will be announced, and how they will be selected.

Avoid changing the deadline after launch unless necessary.

## What prize structures can I use?

### Ranked prizes

Reward by position: first, second, third, and so on.

1. Open **Contest Rewards**.
2. Select **Ranking**.
3. Add each position and reward amount.
4. Review the total prize pool and save.

Use ranked prizes when submissions can be judged against one overall standard.

### Category prizes

Reward different kinds of excellence, for example Best Overall, Best AI Animation, Funniest Submission, Best Product Story, Best 3D Design, Most Original Concept, or Best Social Performance.

1. Open **Contest Rewards** and select **Categories**.
2. Add the category name, a short explanation, the reward amount, and how many prizes are available.
3. Repeat and save.

Keep category descriptions specific enough that creators know what judges want.

### Finalists

Choose a number of finalists and a fixed amount each, for example 50 people × $20. Every selected finalist receives the same reward.

## Do I still approve contest submissions?

Yes. Review entries as they arrive.

Approval confirms the content meets the brief, is eligible for judging, follows the rules, is safe, and includes mandatory requirements.

**Approving a contest entry does not mean the creator has won.** It means the submission can be judged.

## How do I select contest winners?

After the contest closes:

1. Open the completed contest.
2. Review approved submissions.
3. Select the trophy or winner control on the submission you want to reward.
4. Choose the ranking, category, or finalist position.
5. Repeat for all winners, review the list, and confirm amounts.
6. Publish or **release** the winners.

A Winners section may appear on the campaign page once you start selecting.

Before release, check that every prize is assigned correctly, none is assigned twice, each submission is eligible, names and amounts are right, and internal judging is complete.

{% hint style="success" %}
Once results are released, configured rewards are distributed automatically. Winners are paid when you release them — not at the moment you approve an entry.
{% endhint %}


---

# 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://gimi.gitbook.io/gimi/for-brands/contest-campaigns.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.