> For the complete documentation index, see [llms.txt](https://docs.dinmo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dinmo.io/integrations/destination-platforms/yahoo-dsp/export-audiences.md). # Export audiences Configure add-only audience exports to Yahoo DSP. DinMo adds mapped identifiers from a segment to an advertiser-level Yahoo DSP custom audience. You can select an existing audience or let the first nonempty sync create one. ## Before you begin * Have a Yahoo DSP account with access to the target advertiser and Traffic API client ID and secret. See [Yahoo's access guide](https://help.yahooinc.com/dsp-api/docs/setup-access-guide). * Create a DinMo segment with email addresses, Apple IDFAs, Google advertising IDs, or IP addresses. One activation uses one identifier type. ## Connect Yahoo DSP In DinMo, create a destination for **Yahoo DSP** and choose **Export audiences**. Enter the Traffic API client ID and client secret. DinMo checks that these credentials can access Yahoo advertisers. ## Configure the activation 1. Select the **Yahoo advertiser** that owns the audience. 2. Choose the **audience identifier type**: email, Apple IDFA, Google advertising ID, or IP address. 3. To add to an audience already in that advertiser, choose it under **Existing audience** or enter its Yahoo audience ID. Leave this field empty to create an audience from the first nonempty batch. DinMo uses the activation name with a stable DinMo sync identifier in Yahoo to find the same audience on later runs. 4. Map **Audience identifier** to the corresponding segment field, then choose a schedule and activate. The identifier field may contain one value or an array of values per row. DinMo skips empty values and duplicates within each request. Raw email and IP values are normalized and SHA-256 hashed before upload; already hashed SHA-256 values are sent as supplied. Device IDs are sent without hashing. Use the matching identifier type for the audience you select. ## Sync behavior Yahoo DSP accepts audience membership updates asynchronously. A successful DinMo sync means Yahoo accepted the uploaded identifiers; the audience may take time to become usable for targeting. See [Yahoo's Custom Audiences API](https://help.yahooinc.com/dsp-api/docs/custom-audiences). This activation is **add-only**. New segment members are added, but members who leave the segment are not removed from Yahoo. A full sync adds all current identifiers again; it does not replace or clear the Yahoo audience. An empty segment does not create an audience or change existing membership. Yahoo does not support deleting a custom audience through this API. If the initial audience creation fails after Yahoo has accepted it, inspect Yahoo DSP for an audience with the activation name and stable DinMo identifier before retrying. Select its audience ID in DinMo if needed to avoid creating a duplicate. For an existing audience, DinMo checks advertiser ownership before upload; Yahoo's read response does not expose the original identifier subtype, so select a compatible type. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.dinmo.io/integrations/destination-platforms/yahoo-dsp/export-audiences.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.