> 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/connect-an-external-business-or-data-system.md). # Connect an external business or data system Connect an approved demand, finance, reporting, or data system with a clear authority boundary and a testable contract. Use an integration connector when the Podigee Ad Server must exchange data with another business or data system. A connector records what the system does, who controls each side of the exchange, which media and standards it supports, and how Podigee can test and stop the connection. This procedure creates a governed connector. It does not make the connector live. A connector must pass the required checks and activation steps before a Campaign, report, or delivery request can use it. ## Before you start * You have permission to configure integrations in the workspace. * You have the provider name, endpoint, supported operation, and business owner. * You know whether data moves into Podigee, out of Podigee, or in both directions. * You know the supported media, markets, and standards. * You have a credential reference in an approved secret store when the system requires one. * You have the provider's current contract or certification information. Do not put a username, password, token, or private key in an endpoint URL. Use an approved credential reference instead. ![The One Podigee Add flight form shows the delivery destination and the choice between Podigee delivery and a connected demand provider.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-5fc4e4d261a5d8c83f52f4569ec7dfeb55c32a06%2Fdoc-monetization-034-add-flight.jpg?alt=media) *Choose a connected provider only when its connection has passed the required checks.* ## Create the connector 1. Open **Monetization > Integrations**. 2. Select **Add integration** or open **Revenue jobs > Integration certification > Configure a connector**. 3. Select the workspace in **Where this applies**. 4. Select the integration type, such as ad demand, finance, reporting, or data exchange. 5. Enter the provider name. 6. Enter the secure endpoint without embedded credentials. 7. Select the authority direction: inbound, outbound, or bidirectional. 8. Select the supported capability, media, and standards from the available lists. 9. Select the allowed markets. 10. Set the request quota, response timeout, retry profile, and no-response behavior. 11. Select the external ID strategy that matches the provider contract. 12. Select the conformance check that will verify the connector. 13. Add the credential reference when the integration needs one. 14. Add a reason and submit the connector. Podigee uses controlled values for capabilities, standards, markets, limits, and identifier handling. Do not type a value that looks similar to an existing option. If the required value is missing, ask a workspace administrator to add or approve it. ## Understand the first state After submission, the connector is normally **Proposed** or **Configured**. This means that the connection details are saved. It does not mean that the endpoint answered a test or that the provider accepted the connection. Use the integration state guide to distinguish configuration, local conformance, provider certification, and activation: [Understand integration states and capability levels](/documentation/grow-and-monetize/monetization/understand-integration-states-and-capability-levels.md) ## Test the connector 1. Open the connector from **Monetization > Integrations**. 2. Confirm the exact endpoint, capability, standards, markets, and limits. 3. Select the conformance or verification action. 4. Review the request and response result. 5. Confirm that the media, tracking, identity, privacy, and error behavior match the provider contract. 6. Save the test evidence. A passing check applies to the selected connector version and capability. It does not certify a different endpoint, media type, standard, or provider operation. ## Activate the connector 1. Open the connector state and review the current evidence. 2. Confirm that the required provider or validator evidence is current. 3. Select the activation action. 4. Choose the exact environment and effective time. 5. Confirm the activation. 6. Check the active state in **Monetization > Integrations**. Use the connector in a Flight, Marketplace deal, report, or delivery surface only after the selected capability is active. A platform such as Spotify can still control final playback or ad insertion after the Podigee connector is active. ## Monitor and repair the connection Open **Monetization > Operations** to review timeouts, rejected responses, no-bid results, failed exports, and other connection events. Use the exact connector version and operation reference when you investigate a problem. If an external record is out of sync: 1. Open the connector's repair action. 2. Select the current connector version. 3. Select the affected external record. 4. Choose retry, reconcile, or supersede only when the displayed evidence supports that action. 5. Submit the repair with a reason. 6. Confirm the new result in **Operations**. Do not edit an external identifier in an old record to make two systems look equal. Keep the old result and create a new version or a declared repair operation. ## Stop or replace a connector Suspend the connector when it must stop receiving new traffic but its history is still needed. Create a new version when the endpoint, credential reference, standard, or capability changes. Keep the previous version so that earlier decisions and reports remain explainable. ## If the connector is blocked * **Endpoint is unsafe:** use HTTPS without embedded credentials. * **Capability is missing:** choose a supported capability or ask for a governed addition. * **Credential is missing:** add a reference from the approved secret process. * **Provider contract is stale:** update the connector with the current version and run the checks again. * **Test fails:** read the response and media evidence before changing a limit or retry rule. * **Activation is unavailable:** complete the required validator or provider certification first. ## Expected result The external system has a named, versioned connector with a clear data authority, controlled capabilities, safe endpoint handling, test evidence, and a defined activation state. Operators can use the connector in a booking, delivery, or report without hiding the provider boundary. --- # 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/connect-an-external-business-or-data-system.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.