> 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/improve-yield-and-prepare-renewals.md).

# Improve yield and prepare renewals

Test a revenue improvement, apply it safely, and prepare a non-binding renewal proposal.

Use **Revenue jobs** when you need to improve the value of available inventory or prepare the next commercial proposal. A yield improvement is a reviewable change. It does not change live delivery when you prepare it. A renewal proposal is a non-binding draft. It does not book a Campaign or sign an agreement.

## Before you start

Select the correct Monetization workspace. You need permission to read Campaign and delivery evidence. You need yield planning permission to prepare a revenue improvement. You need the relevant approval or finance permission to apply the improvement or create a renewal draft.

Check that the current Campaign commitments, revenue rules, and performance evidence are correct. The selected evidence is copied into the proposal so another operator can review the same facts.

## Model a revenue improvement

1. Open **Monetization > Revenue jobs > Revenue optimization and renewals**.
2. Select **Model a revenue improvement**.
3. In **Where this applies**, select the workspace or inventory item that you want to improve.
4. Open **Current revenue rules** and **Performance evidence**. Confirm that they describe the current delivery and revenue state.
5. Set the **Minimum CPM**, **Demand priority**, and **Demand response time** that you want to test.
6. Enter the **Expected additional publisher revenue** for the period covered by the evidence.
7. Choose the **Campaign displacement risk**. Use the highest risk that could occur if the rule is applied.
8. Explain why the change should improve revenue. Add an improvement hypothesis when it helps the reviewer understand the expected result.
9. Enter a reason, select **I reviewed these details and authorize this action**, and select **Prepare proposal**.

![The current One Podigee Orbit screen for modelling a revenue improvement shows the workspace scope, revenue rules, evidence, CPM, demand priority, response time, and displacement risk.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-6dad1549147350e1e46fbf81fff6c5a61251436c%2Fdoc-monetization-074-yield-proposal.png?alt=media)

*Describe the business change before you prepare the proposal.*

The proposal records the rules, evidence, expected gain, and displacement risk. **Live delivery stays unchanged** while the proposal waits for review.

## Review the prepared improvement

Open the activity record shown after you prepare the proposal. Check these values:

* the revenue rules that the proposal uses;
* the expected publisher revenue gain;
* the Campaign displacement risk;
* the delivery effect.

The record must say that there is no change to live delivery. If the rules or evidence are wrong, return to the workflow and prepare a new proposal. Do not apply a proposal that uses the wrong workspace, Campaign commitments, or evidence package.

![The current One Podigee Orbit activity record shows a prepared revenue improvement with a 1,250 EUR expected gain and no change to live delivery.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-5c0f996adf3f1ad40d3c1b54aa82c8e2e60d5e66%2Fdoc-monetization-074-yield-prepared.png?alt=media)

*Review the expected gain and delivery effect before you apply a change.*

## Apply the tested improvement

1. Open **Revenue jobs > Revenue optimization and renewals > Apply a revenue improvement**.
2. Select the workspace and the prepared improvement that the team reviewed.
3. Choose when the new rules should become active.
4. Select **Confirm this improvement yourself** only when the workspace allows one person to complete the review. Otherwise, use the assigned approval workflow.
5. Enter the reason and select **I reviewed these details and authorize this action**.
6. Select **Apply improvement**.

![The current One Podigee Orbit activity record shows an applied revenue improvement, its start time, and the message that new revenue rules are scheduled.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-349fc84c99578d20a97753f5f7d892fcd7f94e7d%2Fdoc-monetization-074-yield-applied.png?alt=media)

*An applied improvement schedules new rules and records the time of the change.*

The result must show **Revenue improvement applied** and **New revenue rules scheduled**. Existing Campaign commitments remain part of the recorded decision. Use the activity record when you need to explain who applied the change, which evidence was used, or when it became active.

## Prepare a renewal proposal

1. Open **Revenue jobs > Revenue optimization and renewals > Prepare a renewal proposal**.
2. Select the workspace, the signed order to renew, and the performance evidence that supports the renewal.
3. Enter a renewal reference that your sales and ad operations teams can recognize.
4. Choose the currency. Enter the proposed budget, delivery goal, and commercial rate when they are part of the next agreement.
5. Set the proposed start and end dates. Add a purchase order reference, buyer contact, and commercial notes when they are available.
6. Enter the reason, select **I reviewed these details and authorize this action**, and select **Create renewal draft**.

![The current One Podigee Orbit renewal workflow shows the selected workspace, source order, and the confirmation notice before the proposed commercial terms are entered.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-977a365841ef8a7408124aa6664afd5fb4022d10%2Fdoc-monetization-074-renewal-proposal-top.png?alt=media)

*Start with the completed order and its performance evidence.*

The renewal draft keeps the source order and performance evidence attached. It is ready for review, but it is not booked. Capacity and delivery remain unchanged until the renewal is agreed and booked.

![The current One Podigee Orbit activity record shows a prepared renewal draft with a 36,000 EUR budget and a non-binding status.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-36a5c299496577d36861cae9b47b0f17819c996a%2Fdoc-monetization-074-renewal-prepared.png?alt=media)

*Use the activity record to share the proposed terms without presenting them as a booked deal.*

## Review the renewal draft

Check the source order, proposed budget, proposed period, currency, delivery goal, commercial rate, and attached performance evidence. Confirm that the status is **Non-binding draft**.

If the proposal needs a different budget, date, or rate, prepare a new draft. Do not edit a booked Campaign to represent a renewal discussion. The renewal workflow keeps planning separate from live delivery.

## Example: improve yield and prepare a renewal

1. Use the latest qualified delivery and revenue report as the evidence package.
2. Model a higher minimum CPM and record the expected publisher revenue gain.
3. Review the displacement risk and apply the improvement only after the rules and evidence are correct.
4. Wait for the next delivery evidence to confirm the result.
5. Use the completed order and updated evidence to prepare a non-binding renewal draft.
6. Send the draft to the responsible sales or finance person for agreement and booking.

## Expected result

You can test a yield change without changing live delivery, apply a reviewed change with an audit record, and prepare a renewal proposal from verified Campaign evidence. Operators can see the expected money result, the delivery guardrails, and the difference between a scheduled rule change and a non-binding commercial draft.


---

# 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/improve-yield-and-prepare-renewals.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.