> ## Documentation Index > Fetch the complete documentation index at: https://docs.apostra.com/llms.txt > Use this file to discover all available pages before exploring further. # Map source inputs and owners > Record where avails, products, CRM context, creative formats, properties, execution, and reporting come from ## When and where these worksheets are used Complete these worksheets during **source input setup** — the step where you connect an inventory source that draws data from multiple independent systems (avails from one place, bookings from another, reporting from a third). Start from [Prepare inventory source inputs](/v2/setup/publisher-onboarding-starter-kit), which is where the five questions these worksheets record are asked. They are **supporting evidence**: this worksheet is not a production import schema or a request to design a software module. You share it with Apostra for review rather than uploading it to a parser, and Apostra reviews the map with you before any custom path is activated. You do not need to send all four at once. Fill them in as you confirm each one. Use one row per input; split a row only if the authority or key mapping changes for a subset. Skip these worksheets if all your inventory passes through unchanged to an external sales agent and Apostra will not operate a separate capability for it. *** ## Inputs A **source boundary** is one body of inventory whose capacity, bookings, and history must stay coherent — `Sample Publisher CTV` in the example below. It is defined by capacity and booking authority, not by vendor, credential, transport, or filename. One source boundary usually draws the **inputs** below from different systems, on different schedules, with different owners. Name the source boundary on every row — the same input can appear under more than one boundary, and worksheets often arrive separately — then use one row per input. | Input | What it covers | | ------------------------------------------ | ----------------------------------------------------------------------------------------------------------------- | | **Inventory identity** | The stable IDs for the placements, capacity pools, or inventory scopes you sell | | **Property coverage and authorization** | The domains, apps, or channels the inventory runs on, and the evidence that you are authorized to sell them | | **Availability** | How much capacity is sellable, for which period, and whether the number is gross or net | | **Source price or floor** | The CPM or floor price attached to that capacity | | **Product catalog and descriptions** | The buyer-facing packages, their names and descriptions, and which inventory backs each one | | **Upstream bookings, if needed** | Capacity already sold elsewhere, used to turn gross capacity into net | | **CRM and buyer-account context, if used** | Sanitized account and opportunity context for buyer-specific merchandising — never inventory or booking authority | | **Creative formats and requirements** | Which creative each product accepts: dimensions or duration, asset rules, approvals, and lead times | | **Trafficking and execution** | How a booking becomes a campaign, order, or line item in your ad server | | **Status, update, cancellation** | How live state, changes, and cancellations come back | | **Reporting and reconciliation** | How delivered impressions and spend return, join to the booked line, and get corrected | *** ## Worksheets Complete section 1 first — sections 2, 3, and 4 each follow the same rows. ### 1. Map the input and its authority Identify who or what supplies each input and what it is trusted to define. | Column | What to fill in | | ------------------------------- | ---------------------------------------------------------------------------------------------------------------- | | **Source boundary** | The body of inventory this row covers — e.g. `Sample Publisher CTV` | | **Input and covered scope** | Which input you're documenting, from the list above, and the inventory scope it covers | | **Provider, system, or person** | Who or what produces this data: an API, a named export file, a team member, or a combination | | **Authority and covered scope** | What this source is the trusted owner of, and which inventory it covers | | **Grain and stable keys** | The smallest unit of data and the ID field that stays consistent across updates — e.g. `placement_id`, `availId` | Copy this block and save it as `.csv` to open it in Excel or Google Sheets: ```csv theme={null} Source boundary,Input and covered scope,Provider / system / or person,Authority and covered scope,Grain and stable keys ,Inventory identity,,, ,Property coverage and authorization,,, ,Availability,,, ,Source price or floor,,, ,Product catalog and descriptions,,, ,"Upstream bookings, if needed",,, ,"CRM and buyer-account context, if used",,, ,Creative formats and requirements,,, ,Trafficking and execution,,, ,Status / update / cancellation,,, ,Reporting and reconciliation,,, ``` ### 2. Assign owners and close open questions Record who is responsible for each input and what still needs to be resolved. | Column | What to fill in | | ------------------------------------ | ----------------------------------------------------------------- | | **Source boundary** | The same source boundary from section 1 | | **Input and covered scope** | The same input from section 1 | | **Method and current handling** | How the data arrives today — choose one value from the list below | | **Customer and Apostra owners** | Your responsible contact and Apostra team that handles this input | | **Open question or evidence needed** | What is still unclear or unresolved before this input can go live | **Values for "Method and current handling":** * **Production parser or integration** — name the exact current contract. * **Manual pilot step** — name the person, work item, expected response, and durable evidence. * **Supporting evidence** — reviewed material that is not ingested. * **Gap** — no acceptable production or manual path; state whether advisory, capability-blocking, or pilot-blocking. Copy this block and save it as `.csv` to open it in Excel or Google Sheets: ```csv theme={null} Source boundary,Input and covered scope,Method and current handling,Customer and Apostra owners,Open question or evidence needed ,Inventory identity,,, ,Property coverage and authorization,,, ,Availability,,, ,Source price or floor,,, ,Product catalog and descriptions,,, ,"Upstream bookings, if needed",,, ,"CRM and buyer-account context, if used",,, ,Creative formats and requirements,,, ,Trafficking and execution,,, ,Status / update / cancellation,,, ,Reporting and reconciliation,,, ``` ### 3. Record timing and failure effects Document how often each input arrives and what happens if it doesn't. | Column | What to fill in | | ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Source boundary** | The same source boundary from section 1 | | **Input and covered scope** | The same input from section 1 | | **Snapshot, patch, delta, event, or human** | How updates arrive: a full replacement, a partial update, a real-time event, or a manual step | | **Cadence or trigger and timezone** | How often it arrives or what triggers it — include timezone, e.g. "nightly 02:00 UTC" or "on every booking" | | **Grace or freshness limit** | How late or stale this input may be before the consequence you record in worksheet 4 applies. It is a tolerance, not a promise that a previous value keeps being used — events, human steps, and reviewed evidence may have no reusable last-good payload, and some paths must fail closed | Copy this block and save it as `.csv` to open it in Excel or Google Sheets: ```csv theme={null} Source boundary,Input and covered scope,Snapshot / patch / delta / event / or human,Cadence or trigger and timezone,Grace or freshness limit ,Inventory identity,,, ,Property coverage and authorization,,, ,Availability,,, ,Source price or floor,,, ,Product catalog and descriptions,,, ,"Upstream bookings, if needed",,, ,"CRM and buyer-account context, if used",,, ,Creative formats and requirements,,, ,Trafficking and execution,,, ,Status / update / cancellation,,, ,Reporting and reconciliation,,, ``` ### 4. Agree recovery and escalation Define what breaks when an input fails and who fixes it. | Column | What to fill in | | ------------------------------------------- | ------------------------------------------------------------------------ | | **Source boundary** | The same source boundary from section 1 | | **Input and covered scope** | The same input from section 1 | | **Stale, missing, or failed consequence** | What stops working or pauses if this data doesn't arrive on time | | **Correction, replay, or retry** | How to fix it — resend the file, replay the event, correct and re-upload | | **Owner, backup, fallback, and escalation** | Who handles recovery and who to escalate to if they're unavailable | Copy this block and save it as `.csv` to open it in Excel or Google Sheets: ```csv theme={null} Source boundary,Input and covered scope,Stale / missing / or failed consequence,Correction / replay / or retry,Owner / backup / fallback / and escalation ,Inventory identity,,, ,Property coverage and authorization,,, ,Availability,,, ,Source price or floor,,, ,Product catalog and descriptions,,, ,"Upstream bookings, if needed",,, ,"CRM and buyer-account context, if used",,, ,Creative formats and requirements,,, ,Trafficking and execution,,, ,Status / update / cancellation,,, ,Reporting and reconciliation,,, ``` *** ## Completed fictional example | Source boundary | Input or operation | Provider/system or person | Authority and scope | Grain and stable keys | Semantics | Method | Cadence/trigger | Grace/freshness | Stale consequence | Customer owner | Apostra owner | Correction and escalation | Current handling | | -------------------- | ----------------------------------- | --------------------------------------------------- | ------------------------------------------------------------------------------- | ------------------------------------------------------ | --------------------------------- | --------------------------------------------- | ----------------------------------- | -------------------- | -------------------------------------------------------- | -------------------- | ------------------------- | ------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- | | Sample Publisher CTV | Inventory identity | Fictional ad server | CTV placements and capacity pools; no AdCP Collection is asserted | placement id, capacity pool id | Full snapshot | Managed connection plus reviewed declarations | Nightly and on material change, UTC | 36 hours | New discovery is withheld for unresolved identity | Inventory Operations | Source Operations | Repair the mapping; escalate unknown authority to both owners | Supporting evidence in this pack; reconcile through current owner surfaces | | Sample Publisher CTV | Property coverage and authorization | Property Roster and publisher authorization | CTV inventory under sample-publisher.synthetic.invalid | publisher domain, property selector, placement id | Full snapshot | Reviewed declarations | On material change | 36 hours | Affected inventory cannot be presented as authorized | Inventory Operations | Source Operations | Correct the roster or authorization evidence and re-review coverage | Supporting evidence in this pack | | Sample Publisher CTV | Availability | Publisher planning export | Net sellable impressions for each static-v1 compatibility grouping and quarter | legacy collectionId field, availId, startTime, endTime | Patch/upsert | CSV upload | Monthly by 17:00 Eastern | One business day | New reservations pause for stale affected rows | Inventory Planning | Source Operations | Correct the row and preview the full intended patch again | Production compatibility parser: static-avails-feed:v1; not the target Inventory Feed schema | | Sample Publisher CTV | Source price | Publisher planning export | Source CPM for the same availId and period | availId, currency, effective period | Patch/upsert | Same CSV row | Monthly with availability | Same as availability | Affected row remains unpriced | Revenue Operations | Source Operations | Submit a corrected row; do not invent a CPM | Production parser: static-avails-feed:v1 optional CPM | | Sample Publisher CTV | Product catalog and descriptions | Fictional product catalog, Media Kit, and rate card | Buyer-facing CTV packages backed by declared inventory scopes | product id, component inventory scope, availId | Correctable snapshot | Reviewed merchandising evidence | Monthly and on material change | One business day | Affected product is withheld from new proposals | Product Marketing | Merchandising Operations | Correct the product-to-inventory mapping or unsupported description | Supporting evidence applied through product and merchandising owner surfaces | | Sample Publisher CTV | Upstream booking | Fictional campaign system | Existing booked impressions used only for gross-to-net evidence | availId, upstream order/line item, updatedAt | Snapshot | CSV evidence | Daily while flight is open | 12 hours | Gross capacity cannot be treated as current net | Ad Operations | Source Operations | Correct the booking evidence and re-run capacity review | Supporting evidence; no generalized importer | | Sample Publisher CTV | CRM and buyer-account context | Fictional CRM export | Sanitized account and opportunity context for buyer-specific merchandising only | crm account id, opportunity id, buyer account mapping | Correctable snapshot | Reviewed CSV evidence | Weekly | Two business days | Generic merchandising continues without CRM context | Sales Operations | Merchandising Operations | Quarantine unknown buyer joins and correct the sanitized export | Supporting evidence; not inventory or booking authority | | Sample Publisher CTV | Creative formats and requirements | Creative review team and format matrix | CTV VAST duration, aspect ratio, asset, approval, and lead-time rules | format\_option\_id | Full snapshot plus human decision | Reviewed specifications | On policy change | One business day | Affected products cannot claim creative readiness | Creative Operations | Campaign Operations | Correct the canonical format mapping or requirement | Supporting evidence applied through format and policy owner surfaces | | Sample Publisher CTV | Trafficking and status | Fictional ad server | Campaign/order/line-item creation and live status | media buy, package, upstream lineItemId | Event plus human decision | Work item | Per booking and change | One business day | Buyer success cannot be claimed | Ad Operations | Campaign Operations | Record failure evidence, correct, and retry or release | Manual pilot step | | Sample Publisher CTV | Reporting | Fictional delivery export | Final delivered impressions and spend for the booked line | reportingJoinKey, mediaBuyId, availId, period | Correctable snapshot | CSV evidence | Weekly Tuesday 12:00 Eastern | Four hours | Reporting is visibly stale; discovery remains unaffected | Reporting Operations | Reconciliation Operations | Quarantine unknown joins and send a corrected export | Supporting evidence; no generalized importer | The fictional rows demonstrate one source boundary with several providers and human owners. They do not claim that these systems, schedules, or service levels exist for a real publisher.