> 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/concepts-and-reference/object-and-relationship-map.md). # Object and relationship map See how the customer-facing Monetization records connect from buyer plan to delivery evidence and finance. The Monetization records form one chain from a commercial promise to a delivered and measured ad. Each record has one purpose. A later record does not replace the source record that explains how it was created. ![The current One Podigee Flightboard shows Campaign Flights with dates, media, destination, goal, and delivery state.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-5f01c9462cb55a5dceb4afd96d49778e4635de24%2Fdoc-monetization-065-flightboard.png?alt=media) *The Flightboard connects Campaign planning to delivery work.* ## The complete customer flow ```mermaid flowchart LR account[Commercial account] --> brand[Brand] brand --> campaign[Campaign] campaign --> flight[Flight] flight --> forecast[Forecast] forecast --> reservation[Reservation] flight --> assignment[Creative assignment] creative[Creative family] --> version[Creative version] version --> rendition[Prepared rendition] version --> rights[Rights and review] assignment --> flight show[Show and episode] --> breaks[Ad breaks] breaks --> inventory[Inventory package] inventory --> flight flight --> setup[Prepared Campaign setup] setup --> delivery[Delivery version] delivery --> decision[Ad decision] decision --> evidence[Delivery evidence] evidence --> report[Report and analytics] evidence --> settlement[Settlement period] settlement --> invoice[Buyer invoice] settlement --> payout[Publisher payout] provider[Connected provider] --> flight provider --> decision ``` ## Commercial planning records | Record | Owns | Connects to | | ---------------------- | -------------------------------------------------------------------------- | ------------------------------------------------------------------ | | **Commercial account** | Buyer organization and commercial relationship. | Brands, contacts, and Campaigns. | | **Brand** | Brand identity used for buyer and suitability decisions. | Commercial account, Campaigns, and Creative families. | | **Campaign** | The buyer promise, schedule, rules, and commercial plan. | Flights, approvals, Creative assignments, and delivery setup. | | **Flight** | One measurable segment of a Campaign by media, destination, time, or goal. | Inventory, reservations, Creatives, demand, and delivery evidence. | | **Forecast** | A scenario estimate for supply, fill, quantity, cost, and revenue. | A Flight and its current supply assumptions. | | **Reservation** | A confirmed capacity commitment for a Flight version. | A Flight, Inventory package, and reservation evidence. | A Forecast is an estimate. A Reservation is a capacity commitment. Neither is delivery evidence. ## Supply and content records | Record | Owns | Connects to | | ---------------------- | ---------------------------------------------------------------------------------------- | ---------------------------------------------------------------- | | **Show** | The podcast identity and its delivery configuration. | Episodes, RSS, HLS, and destination connections. | | **Episode** | One published audio or video content item. | Media versions, chapters, ad breaks, and delivery presentations. | | **Ad break** | A governed position and slot rule in an episode or presentation. | Inventory, Flights, decisions, and fallback. | | **Inventory package** | The supply that can be sold, including media, markets, delivery, measurement, and dates. | Shows, episodes, ad breaks, Flights, and forecasts. | | **Creative family** | A durable identity for related ad assets. | Brand, Campaign assignments, and Creative versions. | | **Creative version** | One exact master, rights, review state, and prepared media set. | Renditions, coverage decisions, and Flight assignments. | | **Prepared rendition** | One checked audio or video file for a delivery use. | Creative version, destination, and Playback Plan. | An episode is content. An ad break is an opportunity. Inventory defines what can be sold. A Creative is what can play in that opportunity. ## Delivery records | Record | Owns | Connects to | | --------------------------- | ----------------------------------------------------------------------- | ------------------------------------------------------------------- | | **Prepared Campaign setup** | One exact, checked combination of Campaign inputs. | Launch readiness, approvals, and publication. | | **Delivery version** | The verified setup that controls new eligible requests. | RSS, HLS, connected destinations, and recovery controls. | | **Playback Plan** | One exact result for an HLS presentation and its media requests. | Episode, break, selected ads, timeline, and measurement. | | **Ad decision** | The result for one request and its break slots. | Campaign, Flight, Creative, episode, delivery method, and fallback. | | **Fallback** | The safe result when paid delivery is not eligible or cannot be proven. | Decision, playback, and measurement. | | **Connected provider** | A certified external demand or destination capability. | Flight, decision, provider receipt, and platform evidence. | The Delivery version controls new requests. An already assigned Playback Plan remains bound to its own presentation boundary. ## Evidence and finance records | Record | Owns | Connects to | | ----------------------- | -------------------------------------------------------- | ----------------------------------------------------------------------- | | **Audience analytics** | Listener or viewer activity under the analytics rules. | Episode, request, and reporting period. | | **Delivery evidence** | Proof that a selected ad met its measurement rule. | Ad decision, Creative, Campaign, and qualified value. | | **Qualified delivery** | Delivery evidence that can support a commercial amount. | Reports, Settlement periods, invoices, and statements. | | **Report** | A governed view of metrics for a scope and period. | Audience, delivery, finance, and destination delivery. | | **Reconciliation case** | A frozen comparison of two trusted records. | Reports, delivery evidence, provider receipts, and finance corrections. | | **Settlement period** | One controlled finance period for a seller and month. | Qualified delivery, invoices, statements, and payouts. | | **Buyer invoice** | The receivable document for approved delivery lines. | Settlement period, buyer, tax, currency, and accounting receipt. | | **Publisher statement** | The publisher's earnings and deductions. | Settlement period, delivery evidence, and payout. | | **Payout** | The controlled payment record for a publisher statement. | Beneficiary, amount, currency, review, and payment receipt. | An Ad decision is not automatically qualified delivery. Qualified delivery is not automatically an invoice or payout. Each step needs its own evidence and state. ## Versions and relationships When a connected record changes, Podigee creates or requires a new version where the change could affect delivery, review, measurement, or money. The new version points to its predecessors and keeps the earlier evidence readable. Examples: * a new Campaign date can require a new Forecast, Reservation, Creative coverage, approval, and Prepared Campaign setup; * a new episode media version can require new ad breaks and delivery preparation; * a changed Creative right can remove coverage from a Flight without deleting the Creative family; * a new finance rule can affect a later Settlement period without changing a closed period; * a new provider capability can replace a Flight binding without rewriting earlier decisions. ## What does not connect directly Some records intentionally stay separate: * A Forecast does not create an Ad decision. * A provider bid does not create qualified delivery. * A report does not change a Campaign or finance record. * An approval for one version does not approve a later version. * A playback retry does not create a second decision for the same presentation. * A closed Settlement period does not receive a silent edit. These boundaries help operators explain what happened and prevent one UI action from changing an unrelated business record. ## Find the right starting record | Your question | Start with | | ---------------------------------------- | -------------------------------------------------- | | What did we promise the buyer? | Campaign and Flight. | | What supply can we sell? | Inventory package and Forecast. | | Which ad can play? | Creative version, coverage, and Flight assignment. | | What did the listener or viewer receive? | Ad decision and Playback Plan. | | Did it qualify commercially? | Delivery evidence and qualification. | | Why is the report or invoice different? | Reconciliation case and source records. | | What must be paid? | Settlement period, statement, and payout. | ## Expected result You can move from a buyer promise to its supply, Creative, delivery, evidence, report, invoice, or payout without treating one record as a substitute for another. The map keeps customer-facing relationships clear while versions preserve the history behind every decision. --- # 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/concepts-and-reference/object-and-relationship-map.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.