> For the complete documentation index, see [llms.txt](https://docs.relevant-digital.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.relevant-digital.com/changelog/readme/2023.05.md). # 2023.05 ## Welcome to the Relevant Yield Feature and Information Letter! Welcome, dear user of Relevant Yield, to a nice big chunk of improvements and functions for your Relevant Yield product. 1. API Insight forecast report 2. Improved time zone handling for HB Analytics and Prebid-server 3. Custom dimension support for Prebid Mobile (Apps) 4. New/Improved API Insight connections The release will drop today and during the rest of the week. ### **1. API Insight forecast report** The API Insight forecast report is a new report, alarms and dashboard option that will bring you some core forecasting data from your ad server (only GAM supported in this first version), into Relevant Yield. The forecast report looks forward in time, as opposed to backwards like the normal reports do and it is intended to give you a nice overview of the sell-out rates in your current ad server. The data provided can be used 3 months forward on a day to day basis. [![API Insight forecast report](/files/8214e05ec1fb4bf1c1c50703853cadae4c85e377)](broken://pages/149d7f89027ec557974e2fd94af31641b50a501c) Please notice that the new forecast report is intended for getting an overview, and not as a basis for your sales team to do dedicated forecast analysis for specific campaign bookings. The ad server will usually have more detailed data and update more frequently, so it is most likely better to do that in the ad server directly. For a generic holistic understanding, the new report is great though! You can [**read more about the new function here**](broken://pages/149d7f89027ec557974e2fd94af31641b50a501c), and how it can be activated in your setup. #### **What’s in it for you?** A great way to get a day to day understanding on your current sell-out level; so it is a nice dashboard to have when you log in. This information can be used to launch initiatives like adjusting your prebid floorprices, focusing more on deals or direct sales, both on a site by site level, but also on a more holistic level in your organisation. The alarms can of course also be used to flag if your sell-out rates fall below specific levels, and a good alarm setup could be: “Ping me if the Sell-through %rate falls below X% for the next 30 days per site.” If you have very fluctuating sell-through rates on your websites, it might be good to create multiple alarms; having different thresholds on different websites: ![Screenshot 2023-05-09 at 12.05.23](/files/0e9e4bf553d6cedeb5dec76d5c8acb1624892e07) Please notice that programmatic non-guaranteed deals and OpenRTB are not taken into consideration! So this is more for a focus on direct campaigns and guaranteed deals, things that actually reserve impressions in your ad server system. ### **2. Improved time zone handling for HB Analytics and Prebid-server** We have added the option to select your own timezone output in your dashboards and reports for the HB Analytics module. Default has always been UTC, but you can now select the time zone you prefer to have viewable for each individual dashboard or report. Just scroll through the options, or use the free text search to find the time zone you prefer - easy peasy!: ![Screenshot 2023-05-09 at 12.34.36](/files/0462f93bfa62400dfcfb74b4f3061064d95ae587) #### **What's in it for you?** The time zone option lets you set different time zones on your dashboards and reports, which makes it easier to understand what is happening in real-time. It also makes it easier to compare data from other systems that might work with other time zones; and finally it allows international teams, working in different time zones, to process the same data in their current time zone individually. ### **3. Custom dimension support for Prebid Mobile (Apps)** You can now build (or get help building) custom dimensions for your Prebid Mobile (Apps) integrations. This means that if there is something that is very important for you to log in relation to the auction, we can now add that as a new dimension in HB Analytics. You can read more about [**how these should be implemented here**](broken://pages/8567b993dded2d546154f8c8560ab5e046b496a7). #### **What's in it for you?** Each publisher is different, and by extending the custom dimension to Prebid Server and Prebid Mobile, we can now make sure that we can catch things that are important for each publisher. This could be things like, logged in user (yes or no), consented (yes or no) or whatever you would like to forward to us so that we can log in relation to the Prebid auction. If you are interested in this, we recommend that you reach out to your customer success representative, and they can help you with the integration. ### **4. New/Improved API Insight and HB Manager connections** ![Connections](/files/bc7a5b3e4e3961ccadef66dc43c7dc26d395113d) We have updated/added support for: * Smartstream TV * R2B2 Adapter * Seeding Alliance --- # 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.relevant-digital.com/changelog/readme/2023.05.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.