> 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/govern-a-metric-definition.md).

# Govern a metric definition

Publish a reviewed metric definition and keep every later report tied to the correct version.

The Podigee Audio Video Ad Server gives each measurement one stable meaning. A metric definition records the unit, aggregation, qualification, attribution, privacy, time zone, and effective period used by reports, analytics, and financial evidence. Publish a new version when the meaning changes. Do not edit a published version in place.

## Before you start

You need metric governance permission. Your workspace must contain a current unpublished metric definition. The definition must have a reviewed exact version and a valid effective period. If your workspace requires a second reviewer, a completed governance review must be available. A workspace that permits solo confirmation can use its own confirmation instead.

## Understand what is being published

Before you publish, confirm these parts of the definition:

* **Name and reporting key:** how operators find the metric.
* **Unit:** for example, qualified audio impressions or qualified video starts.
* **Aggregation:** how individual events become a report value.
* **Qualification:** which delivery and validity rules must pass.
* **Attribution:** which Campaign, Flight, Creative, Inventory package, show, and destination get credit.
* **Privacy and invalid traffic:** which values are grouped, hidden, or removed from commercial totals.
* **Time zone and dimensions:** how periods and report rows are formed.
* **Effective period:** when this exact definition becomes authoritative.

The definition version is immutable after publication. A report keeps the definition version that it used, so a later successor does not rewrite older results.

## Publish the reviewed definition

1. Open **Monetization > Workflows**.
2. Open **Governed reports**.
3. Select **Publish a measurement definition**.
4. Choose the current unpublished definition that your team reviewed.
5. Check the effective time.
6. Choose the completed governance review when your workspace requires another reviewer.
7. Use the solo confirmation only when the workspace policy permits it.
8. Review the exact definition and supporting evidence.
9. Select **Publish measurement**.

![The current One Podigee report form shows a saved report scope and metric choices before the metric definition is used.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-a5f134f5e9c76966a2d3bbe1d02863ba0b9b3b3a%2Fdoc-monetization-072-create-scoped-report.png?alt=media)

*Use the report context to check which metric definition downstream consumers use.*

Podigee binds the exact definition version and its evidence to the command. The action does not change a report that already ran. It changes which definition new reports can use after the effective time.

## Understand review and solo operation

The workspace review policy controls the final confirmation:

* **Required independent review:** choose the completed review from a different authorized person.
* **Optional review:** publish after checking the definition yourself, or use a review when your team wants one.
* **Solo confirmation:** confirm the exact definition yourself when the workspace allows it.

If the required review is missing, do not copy a digest or bypass the policy. Complete the review or ask a workspace administrator to change the policy before you publish.

## Replace an existing definition safely

1. Create or update an unpublished successor with the new meaning.
2. Keep the original published version unchanged.
3. Review the successor and its affected reports.
4. Check the new unit, qualification, attribution, privacy, time zone, and effective time.
5. Publish the successor through **Publish a measurement definition**.
6. Update report specifications that should use the successor.
7. Keep older reports and evidence on their original definition version.

Do not replace a definition only to make two existing numbers match. Open a reconciliation case when the source values disagree. The report and evidence record must explain the real difference.

## If the action is blocked

| Message or situation                | What to do                                                                                                       |
| ----------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
| No definition appears               | Check that an unpublished current version exists in this workspace.                                              |
| The definition is not eligible      | Check its effective period and lifecycle state.                                                                  |
| Review evidence is missing          | Complete the required governance review or use the permitted solo confirmation.                                  |
| The exact version changed           | Return to the current candidate and review it again. Do not reuse an old reference.                              |
| The effective time is invalid       | Choose a valid time supported by the workspace policy.                                                           |
| A report still uses the old meaning | Open the report detail and check its bound metric definition version. Existing runs keep their original version. |

## Expected result

The reviewed metric version is published once, with its exact definition, evidence, actor, and effective time recorded. New reports use the authoritative version. Older reports, evidence, and settlements remain reproducible because their original metric definition is preserved.


---

# 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/govern-a-metric-definition.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.