> For the complete documentation index, see [llms.txt](https://docs.publicit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.publicit.com/advertiser/reporting-and-analytics/campaign-metrics.md). # Campaign metrics Track the performance of every campaign and every space from the reporting section of your dashboard. *** ## Where to find your data Open any campaign from the **Campaigns** tab and navigate to the **Performance** tab within the campaign detail page. You'll see metrics broken down by space and by date range. *** ## Key metrics explained ### Impressions The number of times your ad was displayed across all contracted spaces during the selected period. For digital placements, this is measured at the impression level. For offline formats (outdoor, TV, radio, print), impressions are estimated based on the audience data provided by the publisher. *** ### Clicks For digital placements only — the number of times users clicked your ad. Clicks are recorded by the publisher's platform and reported to Publicit. *** ### CTR — Click-through rate ``` CTR = (Clicks ÷ Impressions) × 100 ``` Expressed as a percentage. A higher CTR means your creative is resonating with the audience of that placement. Average CTR varies significantly by format and context. *** ### Budget spent The total amount charged across your campaign, compared against your total budget. Shown as both a figure and a percentage of budget consumed. *** ### Daily budget pacing How your daily spend tracks against your daily budget cap. If spend is consistently near your daily limit, you may want to increase the daily budget to avoid under-delivery on days with high demand. *** ### Space performance breakdown Each space in your campaign has its own performance row. This lets you compare which placements are driving the most value and inform future media planning decisions. | Column | Description | | ----------- | ----------------------------------- | | Space name | The specific placement | | Format | Digital, exterior, TV, radio, etc. | | Impressions | Audience reached through this space | | Clicks | Clicks generated (digital only) | | CTR | Click-through rate (digital only) | | Spend | Amount charged for this space | *** ## Campaign summary tab The **Summary** tab in each campaign shows: * Campaign objective and category * Start and end dates * Segmentation settings (targeting applied) * Current status * List of all contracted spaces with their status *** ## Budget & Spaces tab Shows the budget allocation across spaces — how much of your total budget is committed to each placement, and how much has been spent to date. *** ## Configuration tab View and manage campaign settings — targeting parameters, dates, and campaign details. Editable while the campaign is in Draft or Paused status. --- # 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://docs.publicit.com/advertiser/reporting-and-analytics/campaign-metrics.md?ask=&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.