> For the complete documentation index, see [llms.txt](https://docs.podigee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podigee.com/documentation/grow-and-monetize/monetization/welcome-to-monetization.md). # Welcome to Podigee Ad Server See how Podigee Ad Server connects podcast supply, Campaigns, delivery results, and revenue. The Podigee Audio Video Ad Server connects advertising work with the podcasts that you manage in Podigee. Use the Podigee Ad Server to prepare supply, plan Campaigns, deliver audio and video ads, and review the business result. The visible product area is called **Monetization**. It is part of the same Podigee application as your podcast and episode work. ## The complete workflow An advertising order moves through six connected stages: 1. **Prepare supply.** Define the podcast content, ad breaks, formats, markets, and delivery methods that you can sell. 2. **Plan the Campaign.** Record the buyer, dates, price, delivery goals, targeting, and inventory. Check the forecast before you reserve capacity. 3. **Prepare the ad.** Upload and preview each audio or video creative. Confirm that each creative can serve in its intended placement and destination. 4. **Check and publish.** Resolve missing work. Complete any review that your workspace requires. Publish only the exact Campaign setup that is ready to serve. 5. **Deliver and adjust.** The Podigee Ad Server selects an eligible ad for each delivery request. Watch delivery pace and correct a Campaign when it is ahead of or behind its goal. 6. **Measure and settle.** Review qualified delivery, revenue, differences, and reports. Keep the evidence that explains what ran and how the value was calculated. ![A booked audio and video Campaign with its commercial details and a complete launch checklist.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-e81de6f7c9b11ee2780874614dacc87cf9f1f9e8%2Fdoc-monetization-002-campaign-workflow-live.jpg?alt=media) *A Campaign brings its commercial terms, inventory, creative coverage, and launch checks together.* ## The main work objects You do not have to build the workflow from technical records. Start with these business objects: * A **commercial account** identifies the advertiser, agency, or other buyer. * A **Campaign** holds the shared commercial purpose, order, and schedule. * A **Flight** defines one delivery goal. It connects a date range, media type, price, targeting, inventory, and ad source. * An **inventory package** defines the podcast supply that the operator can sell. * A **creative** is the audio or video ad that can serve for a Flight. * A **report** explains delivery and value for the selected business scope. A Campaign can contain multiple Flights. This lets you manage one buyer agreement while you keep different audio goals, video goals, prices, and measurement units separate. ## Readiness protects the launch The Campaign page gives you one launch checklist. It checks the commercial decision, inventory and capacity, and creative or demand coverage. If your workspace does not require a separate reviewer, an authorized solo operator can complete the work without waiting for another person. The checklist does not replace your judgment. It shows what is ready and what needs attention before publication. ## Delivery connects to business results After a Campaign starts, its page shows delivery, pace, remaining work, and qualified revenue. Audio and video goals stay separate because their delivery and measurement rules can differ. ![A live Campaign with planned Flights, qualified delivery, earned revenue, and the latest delivery evidence.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-0b92a085b24029780f1b709ce383a1472dfc7a5d%2Fdoc-monetization-002-delivery-revenue-live.jpg?alt=media) *Use the live Campaign view to compare delivery with the plan and see the qualified revenue.* Some destinations let Podigee control media delivery. Other destinations control the final playback or reporting step. The Podigee Ad Server keeps these boundaries visible and does not combine results that use different measurement rules. ## One application with two contexts Use the **Podcast** context to manage shows, episodes, media, and distribution. Use the **Monetization** context to manage advertising work. Switch between them without changing your account or opening a separate application. Your access controls which Monetization areas you can use. A small operation can keep the workflow simple. A larger team can add review, collaboration, Marketplace demand, integrations, and advanced evidence work. ## Next step [Open Monetization](/documentation/grow-and-monetize/monetization/open-monetization.md) and review the Control Room. It shows the current work and the next useful action for your workspace. --- # 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://docs.podigee.com/documentation/grow-and-monetize/monetization/welcome-to-monetization.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.