> 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/configure-creative-tracking-and-external-identifiers.md). # Configure Creative tracking and external identifiers Add a UniversalAdID for connected demand and understand where destination tracking and click settings belong. The Podigee Audio Video Ad Server can store a UniversalAdID with an exact Creative version. This identifier helps connected demand providers recognize the same ad across systems. Click targets and tracking URLs are destination settings. They are not free-text fields on the generic Creative record. ## When you need a UniversalAdID UniversalAdID is optional for Podigee-owned delivery. Add it when a connected demand provider or commercial agreement requires an industry identifier. Ask the advertiser, agency, or media provider for these two values: * The UniversalAdID. * The registry that issued the identifier. Podigee currently accepts these governed registries: | Registry | Select in Podigee | | --------- | ----------------- | | Ad-ID | **Ad-ID** | | Clearcast | **Clearcast** | Do not invent an identifier or select a registry that did not issue it. ## Add the identifier during upload 1. Open **Monetization**. 2. Select **Creatives**. 3. Select **Upload master**. 4. Enter the Creative and rights details. 5. Enter the UniversalAdID exactly as the issuer supplied it. 6. Select the UniversalAdID registry. 7. Complete the master upload. ![The current One Podigee Upload creative master window shows the UniversalAdID and UniversalAdID registry fields together with the other Creative details.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-3b2547b9e8314a4479e3a31bae96545c96a6a733%2Fdoc-monetization-043-upload-master.jpg?alt=media) *Enter the identifier and its issuing registry as one pair.* Podigee requires both values or neither value. The identifier can contain no more than 256 characters. ## Correct an identifier The identifier belongs to the exact Creative version. Do not silently change the identity of an approved or delivered version. If the identifier or registry is wrong: 1. Confirm the correct values with the issuer. 2. Upload the authorized media as a new Creative version. 3. Add the correct identifier and registry. 4. Complete media preparation and review. 5. Assign the corrected version when it is eligible. The earlier version stays connected to its earlier decisions and delivery evidence. ## Understand connected-demand readiness A connected demand line can require UniversalAdID. Podigee blocks assignment when the exact Creative version does not contain both the identifier and registry. This check prevents an external system from receiving an unidentified Creative. It does not prove that the external provider accepted the identifier. Check the provider readiness state after submission. ## Configure click targets The current generic Creative upload does not contain a click-target field. Add click data in the destination workflow that owns the clickable experience. For example, Spotify direct sales can use a Spotify clickable-ad configuration. After Spotify has an existing clickable ad, the current contract does not allow silent removal or replacement. Make a deliberate destination change when the buyer supplies different click data. For RSS audio without a clickable surface, do not add a click target only to imitate a video or app placement. ## Configure tracking URLs The current generic Creative upload does not accept arbitrary tracking URLs. This protects the system from ungoverned third-party requests and keeps destination rules in the correct adapter. Spotify direct sales supports no more than five tracking URLs for one advertisement. Each URL must use HTTPS. Other connected providers can have different rules. Use the provider workflow and its validation. Do not put tracking URLs into Creative names, notes, or UniversalAdID fields. ## External references from provider systems Keep provider-specific advertisement, campaign, or asset references in the provider connection or delivery plan. UniversalAdID identifies the Creative across systems. It does not replace the provider's own operation reference. This separation makes it possible to explain these facts later: * Which Podigee Creative version was used. * Which UniversalAdID represented it. * Which provider operation submitted it. * Which destination accepted or rejected it. * Which delivery and measurement evidence came back. ## Security rules for tracking Use these rules for every destination: * Use HTTPS when a destination permits tracking URLs. * Use only buyer-approved or provider-approved addresses. * Do not include credentials in a URL. * Do not add listener names, email addresses, or raw personal identifiers. * Do not bypass destination validation with redirects or encoded URLs. * Remove or replace unsafe tracking through the owning destination workflow. Tracking permission does not override privacy, consent, or publisher rules. ## Solve common problems | Problem | Cause | Safe action | | ---------------------------------------------- | --------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ | | Podigee rejects the UniversalAdID fields | One value is missing, the identifier is too long, or the registry is not recognized. | Enter both valid values or leave both empty. | | External-demand assignment is blocked | The exact Creative version has no UniversalAdID pair. | Upload a version with the issuer-provided identifier and registry. | | The provider rejects the identifier | The value is unknown, incorrect, or not enabled for that provider. | Confirm it with the issuer and provider. Use a corrected version. | | There is no click-target field on the Creative | Click behavior belongs to the destination, not the generic media record. | Open the owning destination workflow. | | A Spotify tracking URL is rejected | The URL is not HTTPS or more than five URLs were supplied. | Use no more than five valid HTTPS URLs. | | A Spotify clickable ad cannot be replaced | The existing clickable-ad configuration is immutable in the current operation contract. | Prepare a deliberate destination update instead of overwriting it. | | A provider reference is missing | The provider operation did not create or return it. | Check the connection operation and retry only when the error is safe to retry. | ## Expected result The exact Creative version contains a valid UniversalAdID pair when connected demand requires it. Click targets, tracking URLs, and provider references stay in the destination workflow that owns them. Next, assign and rotate Creatives. --- # 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/configure-creative-tracking-and-external-identifiers.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.