> 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/create-an-evidence-package.md).

# Create an evidence package

Issue a signed evidence package that keeps completed report results, metric definitions, reporting periods, and integrity proof together for an authorized recipient.

Use an evidence package in the Podigee Audio Video Ad Server when a recipient must verify a report, not only read its numbers. The package keeps the completed result, reporting period, data cutoff, report definition, metric versions, and signed integrity manifest together in a downloadable ZIP.

Use an evidence package for a buyer, publisher, finance reviewer, auditor, support case, or dispute. Use **Download** or **Share securely** instead when the recipient only needs to read the result.

## Before you start

Create and run the report first. The run must be complete and its result must be available. Confirm the report scope, period, time zone, privacy class, currency, and metrics before you issue the package. You need report read permission and report share permission.

The package is built from the exact completed run. It does not recalculate the report, change the report definition, or create a new ad decision. If a report definition or metric definition changes later, the package still refers to the versions used by the completed run.

## Open the evidence package form

1. Open **Monetization > Evidence & Money**.
2. Open the saved report.
3. Open **Report history**.
4. Find the completed run.
5. Select **Create evidence package**.

The form opens in a confirmation dialog. It shows the reporting period and the result file type and row count before you choose the package purpose and availability period.

![The current One Podigee Evidence & Money page shows the report history entry point for saved reports, scheduled delivery, and evidence access.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-ab157f76d1c3f5f7be3a2d369de4c2995b42dd3b%2Fdoc-monetization-072-reports-overview.png?alt=media)

*Open the completed report run from Evidence & Money before you create its evidence package.*

## Choose the package settings

1. Choose a **Package purpose**:
   * **Client delivery** for a customer or buyer;
   * **Finance review** for a finance or settlement check; or
   * **Audit record** for an audit or formal record.
2. Choose **Available for**: 7 days, 30 days, 90 days, or 1 year.
3. Read the proof notice and confirm that the report and its proof must stay together.
4. Select **Create package**.

The package purpose selects the evidence profile. The availability period controls how long the package can be downloaded. The package remains listed after expiry, but the download is no longer available.

## What the package contains

The downloaded ZIP contains:

* `manifest.json`, with the package schema version, package identifier, evidence profile, recipient scope, requester, expiry, and the report and metric references;
* one report file for each included completed run;
* the report file format and row count;
* the reporting interval and data-as-of time;
* the exact report specification version and its digest;
* each metric definition version, metric key, unit, evidence profile, revision, and digest; and
* the package digest and signature information used to check integrity.

The manifest is deterministic for the package contents. The package signature and digest protect against a changed report, changed metric definition, or changed file after issue.

## Help a recipient verify the package

Give the recipient the ZIP and the context for its use. The recipient should:

1. Open `manifest.json`.
2. Check the package purpose, recipient scope, expiry, and report period.
3. Check the report file name, format, row count, and artifact digest.
4. Check the report specification version and digest.
5. Check every metric definition version, unit, revision, and digest.
6. Recalculate the package digest from the manifest.
7. Verify the package signature with the trusted Podigee verification process.
8. Compare the manifest with the report file before using the result in a financial, client, or audit decision.

Do not treat a ZIP as proof only because it has the expected file name. A package is trustworthy when the manifest, file digests, exact versions, and signature all agree.

## Download an issued package

1. Return to the report detail page.
2. Open **Evidence packages**.
3. Find the package by purpose and creation time.
4. Check **Available until**.
5. Select **Download package** while it is available.

The list keeps expired packages visible for history, but shows them as no longer available. If the download fails an integrity check, do not distribute the file. Create a new package from the completed run or contact the workspace administrator.

## Troubleshoot evidence packages

| Situation                                      | What to check                                                                                              |
| ---------------------------------------------- | ---------------------------------------------------------------------------------------------------------- |
| **Create evidence package** is not available   | Confirm that the run is completed and that you have report share permission.                               |
| The package form does not open                 | Confirm that the report run belongs to the saved report and is still available.                            |
| The package request is rejected                | Check that every report run is complete and that its metric definitions still match the report definition. |
| The package is listed but cannot be downloaded | Check **Available until**. If it is still valid, do not distribute a file that fails integrity checks.     |
| A recipient needs only the numbers             | Use **Download** or **Share securely** instead of creating a package.                                      |
| A recipient questions a result                 | Compare the manifest's period, data-as-of time, metric versions, report digest, and artifact digest.       |

## Expected result

You have an issued evidence package that binds one or more completed report results to the exact definitions and metric versions used to produce them. The recipient can inspect the manifest and verify the package before using it for client delivery, finance, audit, support, or dispute work.


---

# 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/create-an-evidence-package.md?ask=<question>&goal=<endgoal>
```

`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.