> 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/reconstruct-and-export-audit-evidence.md). # Reconstruct and export audit evidence Reconstruct an exact change history and export a protected audit package for an approved purpose. Podigee Audio Video Ad Server lets an authorized operator trace a change from the actor and request to the saved version, event, review, and result. After the first mention, this article uses Podigee Ad Server for the product name. The trace is read-only. A separate export job creates a signed, redacted package when support, compliance, or an investigation needs a file. Use this task when someone asks who changed an item, which version was used, why a decision was made, or what evidence supports a delivery or security result. Do not use an audit export as a replacement for a customer report. Use the smallest scope and purpose that answers the question. ## Before you start * You have permission to inspect audit evidence in the selected workspace. * You know the object, incident, Campaign, Creative, delivery result, or time period to review. * You know the purpose: customer evidence, compliance review, commercial dispute, or internal investigation. * You know who may receive an exported package. * You know the required redaction level and package expiry. Do not put raw identities, credentials, access tokens, or event payloads into a note or export request. The audit views use protected and redacted evidence. ## Reconstruct the audit trail 1. Open **Monetization > Revenue jobs**. 2. Select **Security, privacy, and audit**. 3. Select **Reconstruct the audit trail**. 4. Select the exact scope and object to inspect. 5. Set the **As of** time to a past time that covers the question. 6. Enter the approved purpose. 7. Select **Run observation**. The result is read-only. It connects the saved subject version to its ordered events, command, acting principal, request correlation, and event digest. It does not publish, replay, change delivery, reserve inventory, or affect billing. ## Read the trace Check the result in this order: 1. **Subject and version:** confirm the object and revision that the question concerns. 2. **Actor:** confirm the principal that performed the action. 3. **Command and event:** identify the action and the event that recorded it. 4. **Time and correlation:** follow the event time and correlation references. 5. **Digest:** compare the saved version and event digests when another operator needs exact proof. 6. **Review:** check the approval or review evidence that applied to the action. 7. **Outcome:** connect the change to the delivery, report, financial, or security result. ![The current One Podigee decision details page shows a recorded delivery result, its content context, and investigation controls.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-5fdd893cc5587dc1823701c9ed3690c5bd6de434%2Fdoc-monetization-073-decision-detail.png?alt=media) *A recorded result explains what happened without changing delivery or billing.* Use the short references in normal work. Copy the complete value only when support, compliance, or another controlled process needs exact evidence. ## Prepare a protected audit package 1. Open **Export an audit package** from **Security, privacy, and audit**. 2. Select the **Activity period**: last 7 days, last 30 days, last 90 days, or all available activity. 3. Select the **Reason for export**. 4. Select **Information protection**. 5. Set **Download expires** when the recipient needs a time-limited package. 6. Review the scope, event count, recipient, purpose, and redaction profile. 7. Select **Start**. The activity period selects evidence automatically. The package contains only exact events with current subjects in the selected workspace. If no auditable activity is available, narrow or change the period only when the purpose supports it. ![The current One Podigee decision evidence view connects the Campaign and Creative to the podcast, episode, ad break, privacy mode, value, and exact delivery references.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-a6a46bc4f1c8230e01ac95b529b06c49a9b3d5f9%2Fdoc-monetization-064-decision-evidence.png?alt=media) *Use the evidence references to connect the business result to the recorded delivery event.* ## Verify and deliver the package 1. Wait for **Protected audit package ready**. 2. Check the purpose, scope, evidence count, redaction profile, expiry, and signature result. 3. Confirm that raw event payloads, raw identities, and credentials are excluded. 4. Select **Download package**. 5. Use the approved secure channel and recipient. 6. Keep the completion receipt with the request or investigation. The package is signed and bound to the exact event digests. If an event changed or is missing, the operation stops. Do not send a partial package as if it were complete. ## If the trace or export is incomplete * **The object has no current approvable version:** keep the question open and ask the object owner to resolve the version boundary. * **An event is missing or changed:** stop the export and report the evidence difference. * **The period is too broad:** use a narrower period that still answers the approved question. * **The recipient is not authorized:** do not download the package. Update the recipient through the controlled process. * **The redaction level is too open:** stop and select the minimum approved information. * **The package expiry has passed:** create a new package with a current expiry. * **The trace shows an unexpected actor or action:** keep the evidence unchanged and open the appropriate operational or security issue. ## Expected result The audit question has a read-only, version-bound trace. When a file is needed, the workspace has one signed, redacted package with a clear purpose, scope, evidence count, expiry, recipient, and completion receipt. The audit work does not change delivery, inventory, reporting, or billing. ## Next useful tasks Use [Explain an ad decision or no-fill result](/documentation/grow-and-monetize/monetization/explain-an-ad-decision-or-no-fill-result.md) for a listener or Campaign question about one ad decision. Use [Create an evidence package](/documentation/grow-and-monetize/monetization/create-an-evidence-package.md) for a broader business or financial evidence request. --- # 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/reconstruct-and-export-audit-evidence.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.