> For the complete documentation index, see [llms.txt](https://being-and-time.gitbook.io/boom-clap-melody-field-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://being-and-time.gitbook.io/boom-clap-melody-field-guide/campaign-owners/submit-a-campaign.md).

# submit a campaign

Create campaigns from the Boom•Clap Workstation.

### Before you begin

Confirm that:

* your client account is level 2 or higher;
* your Melody Credit balance is at least as large as the planned budget;
* your campaign destination is publicly available;
* your subject image and campaign cover use stable HTTPS URLs;
* you understand whether the campaign needs manual review.
* fully aware of and agree to the latest [pricing](https://cancancan.cc/boomclap/pricing) structure.

### Complete the campaign form

<figure><img src="/files/rqRwoqRcFnfSbCkqI3qX" alt=""><figcaption><p>Melody Campaign Form</p></figcaption></figure>

#### Classification

Choose a main category and add useful labels separated by semicolons. These signals help contextual matching. Prefer concrete labels such as `local music`, `album launch`, or `independent fashion` over broad promotional language.

#### Campaign name and URL

Use a recognizable campaign name and the final destination URL. Remove unnecessary tracking parameters before submitting.

Melody checks the URL for native support. Compatible YouTube, SoundCloud, and Instagram post or reel links can use native presentation. Other destinations require a campaign cover.

#### Placement preference

Enable **Branded Publishers Only** when you want circulation limited to publisher-hosted Spins rendered directly on approved websites. Leave it disabled to participate in the broader contextual Spin environment.

#### Cycle, budget, and geography

* One campaign cycle lasts 14 days.
* The form currently supports one to four cycles.
* The minimum campaign budget shown in the Workstation is $5.
* Choose **Global** or **North America**.
* Select a US state when state-level vicinity is relevant; otherwise leave it unset.

Your budget cannot exceed your current Melody Credit balance.

#### Description and images

The optional description gives Melody additional contextual information. Write for matching rather than advertising: identify what the campaign is, who it is for, and what environments fit.

Add the campaign image and cover according to [Creative and Cover Requirements](broken://pages/5cd7806dad7d230095e61f3d7f004478f964bc4c).

### Submit

Review the information carefully before selecting **Submit**. Campaign owners cannot freely rewrite live campaign content after approval. Material changes require administrative review.

After submission, the Workstation opens the campaign profile. Level 2 campaigns normally show **In Review**. Eligible higher-level campaigns may become active immediately.

Next: [Review and Approval](/boom-clap-melody-field-guide/campaign-owners/review-and-approval.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 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://being-and-time.gitbook.io/boom-clap-melody-field-guide/campaign-owners/submit-a-campaign.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.