> 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/retire-an-integration.md). # Retire an integration Stop an integration, remove its service access, and retain the evidence that explains the retirement. Use the Podigee Audio Video Ad Server to retire a connection when its delivery or data work is complete. After the first mention, this article uses Podigee Ad Server for the product name. Retirement is a controlled sequence, not a delete action. Stop new traffic, confirm that no active Campaign or report depends on the connection, remove service access, and retain the integration history for support, privacy, and finance work. ![The current One Podigee Operations control room shows active delivery assurance work, incidents, delayed evidence, and the next action.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-6db53133b0902c0ebe2d348da5710f6f8cfe7c7b%2Fdoc-monetization-067-operations.png?alt=media) *Start from one incident and its displayed next action.* ## Before you start * You have workspace administrator or integration-owner permission. * The integration is no longer required for new delivery, reports, events, or automation. * You know the replacement integration or the final fallback. * You know the retention and settlement period that still applies. * You have a service-access owner who can revoke credentials. Do not retire a connection while an active Campaign, Marketplace deal, open report run, settlement, or privacy request still depends on it. ## 1. Stop new activity 1. Open **Monetization > Operations**. 2. Open the integration record. 3. Review active Campaigns, delivery surfaces, report schedules, webhooks, and service access. 4. Use [Suspend an integration](/documentation/grow-and-monetize/monetization/suspend-an-integration.md) for the affected capabilities. 5. Confirm the declared fallback or the clean no-fill behavior. 6. Check a new request and the latest event evidence. Keep the integration suspended while you complete the retirement checks. Do not start a new activation to replace the connection until the replacement has passed its own checks. ## 2. Finish dependent work 1. Move active Campaigns and reports to the replacement delivery or data surface. 2. Confirm that no Marketplace deal or publisher commitment points to the old connection. 3. Wait for open report retries, event acknowledgements, and settlement evidence to complete. 4. Resolve or document every open integration issue. 5. Export the required audit and support evidence. Use the relevant provider or platform guide when the old system owns insertion or reporting. Keep the old connection in history so you can explain earlier delivery. ## 3. Remove service access 1. Open each service access record for the retired integration. 2. Confirm the owner, allowed actions, scope, and expiry. 3. Revoke the credential through the approved access process. 4. Confirm the revocation receipt. 5. Keep the service identity and revocation evidence in the integration record. Revocation stops access. It does not delete the integration history or the records that it created. ![The people list with Maya Chen shown as revoked and a Restore access action.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-27c54a1028210328e519e080546da5106d5d1db3%2Fdoc-monetization-016-revoked-access.png?alt=media) *Revocation stops the access. It does not delete the person's earlier work or the business records.* ## 4. Record the retirement 1. Add the retirement reason and effective time to the integration record. 2. Record the replacement or the final disabled state. 3. Link the last active version, suspension receipt, revocation receipt, and evidence package. 4. Mark the integration as retired when the workspace provides that lifecycle action. 5. Keep the record under the configured retention and settlement rules. If the workspace does not show a separate **Retire** action, keep the connection suspended, record the completed retirement checks, and ask the workspace administrator to apply the lifecycle state. Do not delete the record as a substitute for retirement. ## If retirement is blocked * **Active traffic remains:** move the Campaign or keep the integration suspended. * **A report or event is still open:** wait for the receipt or record the documented exception. * **A credential cannot be revoked:** keep the integration suspended and escalate the access issue. * **A settlement is open:** preserve the integration and delivery evidence until the period closes. * **A replacement is not ready:** use the configured fallback and do not activate the replacement. ## Expected result No new traffic uses the retired integration. Dependent Campaigns, reports, events, and settlements have a documented replacement or safe final state. Service access is revoked, and the complete integration history remains available for audit and recovery. --- # 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/retire-an-integration.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.