> 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/start-here/how-melody-works.md).

# how melody works

Melody connects campaign owners and publishers without asking either side to manage every individual placement.

## The campaign path

1. A campaign owner creates a Melody campaign in the Boom•Clap Workstation.
2. The owner supplies a destination, campaign subject, creative, targeting preferences, cycle length, and budget.
3. The campaign is reviewed when required.
4. Approved campaigns enter the eligible campaign pool.
5. Melody evaluates which Spins are compatible with each campaign.

## The publisher path

1. An eligible CanNoli publisher creates a Spin.
2. The publisher describes the Spin's preliminary context and can add public context sources over time.
3. Melody assembles a changing composition of compatible campaign slots.
4. The publisher attaches the Spin to a Melody Noli or installs an approved CanNoli CDN kit on a website.
5. Visitors encounter a brief intermission when an eligible link interaction occurs.

## Delivery and reporting

For each eligible intermission, Melody selects from the active Spin composition while considering campaign health, geography, prior delivery, and balance. The selected campaign may use a native media experience or campaign cover.

Validated activity is reported back to both sides:

* Campaign owners see impressions, clicks, engagement sessions, spend, Spin activity, origins, and UTC daily rollups.
* Publishers see Spin metrics, estimated earnings, and account-level earnings balances.

Spins are not static playlists. Campaigns can enter, leave, pause, expire, or be vetoed, and context can evolve. Melody periodically refreshes the composition to keep it useful rather than stale.

## Who controls what?

Campaign owners control campaign budget, targeting preferences, whether to require branded publishers, and whether an active campaign is paused or dropped.

Publishers control their Spin context, where the Spin is installed, selected donation inventory, and limited campaign vetoes. Melody controls final slot selection and composition balancing.

Next: [Sign Up and Access](broken://pages/5fc9aba93de93a2fcfbccdbb47d91d19f4b3f181)


---

# 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/start-here/how-melody-works.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.