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

# Create your first campaign

Before you start, set the project's currency in **Settings** and decide what a participant must do to qualify. You need a Project Manager or administrator account.

## Tutorial 03

**Create a Campaign and Test a Booking**

Build a campaign, link its calendars, and follow a test participant from booking into the reward portal.

{% embed url="<https://assets.cdn.filesafe.space/mYdk8zjDWRfpvpBKfwxH/media/6ac440855be7b18197950cf4.mp4#t=4>" %}

[Open Tutorial 03 video in a new tab](https://assets.cdn.filesafe.space/mYdk8zjDWRfpvpBKfwxH/media/6ac440855be7b18197950cf4.mp4).

**Chapters**

1. Set campaign basics, rewards and call stages.
2. Add branding, preparation videos and an introduction-video task.
3. Save the campaign, link calendars and apply redirects.
4. Make a test booking and check the participant portal and Claim URL.
5. Review the submitted introduction video.
6. Explore identity requirements, advertising tracking and translations.

Tracking and translations are additional configuration topics. They are not prerequisites for your first booking test. The tracking segment shows settings, not verified conversion delivery.

[All video tutorials](/showreward-docs/getting-started/video-tutorials.md) · [Next: Tutorial 04](/showreward-docs/daily-operations/validations.md#tutorial-04)

## Set up the campaign

1. Open **Campaigns** and select **New campaign**.
2. In **Basics**, enter **Name**. Add **Description** and **Funnel** if useful. Choose a **Status**: **Active**, **Paused** or **Archived**.
3. In **Reward**, enter **Amount** in the project's currency. **Sale value** is the revenue attributed to a call marked sold; it is separate from the participant's reward.
4. In **Calls**, define at least one named call type, such as Discovery or Demo. Set its **Minimum duration (min)** and keep the types you use active.
5. Set **Max. reschedules**. Exceeding this limit opens a risk signal. A value of 1 represents one reschedule, meaning two call bookings; exceeding it raises a risk signal.
6. In **Verification and payout**, decide whether to enable **Requires identity verification**. If enabled, choose **Automatic (recommended)** or **Manual (fallback)** under **Identity verification**.
7. In **Portal copy**, choose **Source content language** and write the **Thank-you message**, **Claim page message** and **Terms and conditions** that participants should see.
8. Review **Portal preview** and **Maximum cost per lead who attends**, then select **Save**.

Minimum call duration is used to flag short calls for review. It should match your campaign rules. A campaign reward remains unique per lead and campaign, even when the campaign has several call types.

The cost preview adds the base reward and enabled task bonuses. ShowReward usage fees are separate. Administrator accounts also have advanced controls such as **Requires payout details** and an identity workflow override.

## Link your booking calendars

For a new campaign, calendar linking is a second step after the initial save:

1. Connect GoHighLevel under **Settings → Calendar integrations**.
2. Return to **Campaigns** and choose **Edit campaign** on your saved campaign.
3. In **Calls → GoHighLevel calendars**, select the calendar for each active call type.
4. Review **Redirect to reward after booking**. When enabled, ShowReward configures that calendar's GoHighLevel confirmation page.
5. Select **Save and apply in GoHighLevel**, or the campaign's **Save** button to save the campaign and apply pending calendar changes.
6. Check the success message and test a booking.

**Unapplied changes** means the calendar configuration has not yet been applied. If a message says the campaign was saved but calendars could not be applied, return to **Calls** and resolve the calendar error.

## Edit or organize existing campaigns

Use the pencil action, **Edit campaign**, to change a campaign. The campaign list also provides **Pause**, **Activate** for paused campaigns, and **Archive**. Review settings before changing the status of a campaign that participants are already using.

## Related guides

[Add branding and pre-call tasks](/showreward-docs/campaigns/portal-and-tasks.md) · [Link calendars](/showreward-docs/gohighlevel/calendar-links.md) · [Configure advertising tracking](/showreward-docs/campaigns/tracking.md)


---

# 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://showreward.gitbook.io/showreward-docs/campaigns.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.