> 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/campaign-workflow-and-best-practices.md).

# Campaign workflow and best practices

Follow GIMI campaign workflow and best practices from launch through moderation, creator retention, and post-campaign review.

## Recommended campaign workflow

### Before launch

1. Complete your organization profile.
2. Choose the correct campaign type: [sourcing](/gimi/for-brands/sourcing-campaigns.md), [distribution](/gimi/for-brands/distribution-campaigns.md), or [contest](/gimi/for-brands/contest-campaigns.md).
3. Write a clear brief with only essential mandatory requirements.
4. Upload working references.
5. Set realistic creator rewards or prizes, plus submission and payout limits.
6. Confirm content usage rights.
7. Review the campaign as a creator.
8. Make sure your moderation team is ready, then fund and publish.

### During the campaign

1. Review submissions regularly.
2. Approve qualifying content promptly and give clear decline reasons.
3. Check suspicious-content signals.
4. Spotlight exceptional work and shortlist content for later use.
5. Monitor budget and analytics.
6. Identify strong creators and invite high performers into your network.

### After the campaign

1. Complete all moderation.
2. Select contest winners where relevant and release outstanding rewards.
3. Review unused funds and organise approved content.
4. Review analytics, identify top creators, and add Creative Partners.
5. Create private follow-up opportunities and record improvements for the next campaign.

## Campaign best practices

**Keep briefs focused.** Creators should understand the main task immediately. Do not combine several unrelated creative tasks into one campaign.

**Reward effort fairly.** More complex content should offer higher earning potential. A simple social image and a polished 60-second video should not necessarily have the same approval reward.

**Moderate consistently.** Decisions should match the written brief. Do not approve content that ignores the rules while declining similar work from another creator.

**Respond quickly.** Long moderation delays reduce participation and damage trust. Set internal review times before launching. Daily moderation is recommended for active campaigns; high-volume campaigns may need several sessions per day.

**Balance quality and performance.** Views alone do not always indicate strong content. Use approval, Clean Engagement, and Spotlight rewards to recognise quality.

**Protect creators from unclear expectations.** Do not add new mandatory requirements after creators have started. When a major change is unavoidable, communicate it clearly.

**Build relationships beyond one campaign.** Invite strong creators back. Use tags, Creative Partner status, and private campaigns to create a lasting network.

{% hint style="success" %}
Keep submissions private unless visibility is part of the concept. On sourcing, use approval and Spotlight only. On distribution, combine approval, performance, and Spotlight. Always set a deadline on contests.
{% 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/campaign-workflow-and-best-practices.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.