> 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/reporting.md). # reporting The campaign profile combines cumulative performance, budget delivery, daily reporting, and Spin presence. ## Core metrics ### Impressions Validated Melody intermissions associated with the campaign. ### Clicks Validated visits from the intermission to the campaign destination. The profile also calculates click-through rate from valid clicks and impressions. ### Engagements Validated engagement sessions, commonly involving meaningful interaction with supported native media. ### Spins The profile shows active Spins relative to total Spins featuring the campaign. A campaign may remain associated with a Spin even when that Spin or slot is not currently active. ### Spend and budget left Spend reflects validated events multiplied by the campaign's CPI, CPC, and CPE rates. Budget left is the campaign budget minus recorded spend. ## Daily performance The daily chart uses UTC rollups. It appears after daily performance data has been processed. Recent activity may appear in cumulative totals before the next daily bar is available. ## Featured in Spins The **Featured in Spins** section summarizes publisher origins and available Spin references. Origins help answer where the campaign is circulating without exposing private matching data. ## Reporting delays Delivery events are validated before they are accepted. Reporting can therefore lag raw browser activity. Daily totals also depend on the next UTC rollup. Do not treat a short reporting delay as evidence that the campaign has stopped. First check campaign status, remaining budget, active Spins, and the latest report time. ## What clients do not see Detailed internal Melody match records are administrative. Client reporting focuses on delivered performance, Spin activity, origins, rates, and budget rather than the full candidate-matching pool. --- # 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/reporting.md?ask=&goal= ``` `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.