Over the last several weeks we have released a number of UI improvements to help you keep track of performance as well as back end improvements to decrease latency in the platform.
Now in addition to setting daily impression and request caps for your demand tags, you can set lifetime impression caps and implement even daily pacing. Find Budgeting in the Targeting tab of a Demand Tag.
If your daily request or impression budgets are small relative to the volume the demand tag receives, use even daily pacing. It is possible for a demand tag to get flooded with requests in the first minute of the day and for the daily budgets to be exceeded if it is receiving high volume. Using daily pacing will mitigate this risk because it breaks your daily budget into even smaller budgets to spend every 15 minutes.
Lifetime caps can be placed on a demand tag. If you set a lifetime impression cap and flight dates, but no daily cap, selecting even pacing will evenly pace the requests each day throughout the flight dates. Note that you cannot use lifetime impression budgets with even pacing if you do not set flight dates.
SpringServe has added a size macro that allows for size targeting for tags that are implemented in SpotX. Unlike other servers, SpotX does not declare the dimensions of the player but rather S, M, or L according to the size of the player. Add the size macro when exporting your SpringServe tags for implementation in SpotX.
The declared size will be parsed so requests coming into SpringServe will not register as unknown sizes. Now you do not have to allow unknown player sizes in your targeting. Note that the dimensions passed to your demand tags do not necessarily represent the actual size of the player but are dimensions that represent sizes as SpotX defines them.
We have created a new pipeline for getting data from the UI to the adserver. This new route is faster and simpler, and thus more reliable. Changes made in the UI are now in the adserver’s memory 30 seconds after they are made. Previously, it would take two minutes for changes to register. This change cuts down on latency platform-wide.
Supply Tag Response Time
In the past the response time of a supply tag was not evident. Now you can see Response Time: the average number of seconds required for a supply tag to fill. This metric should not be confused with the VPAID window, which is the average number of seconds before the supply tag timed out without filling.
Response Time is shown when you run a report with the dimension Supply Tag. This figure is also shown with its distribution graph in the Quickstats section on the waterfall tab of a Supply Tag.
You can use the response time distribution to make decisions about setting a supply tag time out, if necessary. You can also use the metric to help you determine if you need to reoptimize your demand tag waterfall.
The dashboard shows performance for your top 10 Supply and Demand partners. These tables now show the total figures as well as the top 10, and other. We have consolidated the Impressions and Change column into a single column and added columns for Revenue and Fill Rate. The number shown in parentheses is the change from yesterday at the same time.
For example, if you load the dashboard at 11:00am, you will see the number of impressions that were monetized between midnight and 11:00 am today, and the percent change is the comparison to the number of impressions monetized between midnight and 11:00am yesterday. Note that the dashboard reports figures in Eastern time only.
This type of range compare is now shown throughout the platform: on the Supply and Demand pages and on the Supply Tags tab for a Demand Tag and the Demand Tags tab for a Supply Tag. This figure based on the time frame that you have selected in your drop down menu.
Quickstats & Waterfall Page Additions
Supply Quickstats now include overall supply, financials, and quality stats. You will also find a Refresh button on the waterfall page. Clicking this button will refresh the Quickstats and performance metrics in the waterfall. .
In the waterfall you can now see the Ad % when you toggle to the full view.
This metric is very useful in troubleshooting, as you can quickly see how often your demand tag is returning a non-empty VAST response. If this rate is low, you should talk to your demand partners about what is required to get a non-empty VAST response. Normally this issue arises when there is a targeting misalignment and you are sending inventory to your demand partners that they are blocking. It can also be the case that they require macros that you are not populating.
We have improved the filtering in the modals for adding Supply or Demand Tags. Not only can you search by name, but you can include a maximum rate when adding supply tags to demand or a minimum rate when adding demand to supply. This addition will prevent you from accidentally aligning supply and demand that do not make your margin.
Comments are closed.