Feeling Like Fall with SpringServe

SpringServe allows you to select the optimization metric that best fits your particular use case.

When using the revenue per second optimization metric, we prioritize your demand based on their RPM divided by the duration of the ad. Employing this optimization strategy allows for selection of the demand that will give you the highest revenue per second, which means that you can serve more ads and generate more revenue in a single broadcast call.

We recommend using this metric for your pod supply tags.

You can now set macro overrides on both supply and demand tags in SpringServe. When you set a macro override on a tag, SpringServe will populate the macro with your specified value or a mapped value.

In the Advanced section of the settings tab, clicking +Macro Override will reveal your options.

Due to inconsistencies between systems, you may want to override app information using the app name, app bundle, or app store url macros. The value inputted below the selected macro will be passed to your demand partner in place of the original macro’s value. SpringServe will also pass the value when the macro is not replaced.

You can also replace your custom keys with macro overrides. These keys are created on the Targeting page. When you select Custom Key, a dropdown of your SpringServe keys will appear. If the key is free, enter the override value. If the key is predefined, the SpringServe will retrieve the override value based on the key.

For example, the Genre map key has the following mapping:

When the macro has the value “ca”, SpringServe will replace it with the value ‘Comedy’ in the request we pass to the demand partner.

Custom VAST extensions allow you to append a VAST extension to the VAST response. In the Advanced section of a demand tag you can click the +Custom VAST Extension button to set the name and value of the extension.

For demand that runs on VAST only supply, any extensions added to the demand tag will be displayed in the vast response for the ad(s) that the demand tag returns.

Note that this feature is not available for DC demand tags.

You can now apply competitive exclusions targeting using advertiser domain lists on demand tags of all environments. Previously, this targeting could only be set on CTV demand tags.

For frequency caps that use a global frequency cap pixel, we now include that pixel in the VAST response. This update results in the pixel fire both from SpringServe calls and external pings. Additionally, you can now see how many of your SpringServe objects are using a pixel in the index table.

We continue to add adapters to our header bidding product, including TappX, InMobi, Telaria and Smart Ad Server. Header bidding demand tags now support over 30 platforms.

We have added more flexibility for house ad management; you can now manage house ads from demand side. As for other demand classes, you can add supply manually or copy from another demand tag’s supply associations. When adding a house ad to supply from the demand side, the ratio will be set at 1. Navigating to the demand of a supply tag from the house ads supply tab is now easier; simply click the number in the Demand column of full view of the table.

You can now access an overview of the creatives for a demand partner in the Creatives tab of the partner. To navigate from the main demand partners page, click the number in the Creatives column.

Here, you will see an index table with the creative id, name, and the number of demand tags to which it is associated, and a reporting link.In the full view of this table, you can also find additional metadata and the number of transcoded assets. Creatives can be deleted if they are not associated to any demand tags.

Supply tags that make calls to server side HB demand tags now display an Outgoing SSHB tab in the Realtime Debugger. From this page, you will see SSHB URLs links, which show the full bid request information in JSON.

When you create a budget in the UI, even pacing will be selected by default for non-lifetime periods. Budgets created using the API will default to ASAP pacing unless otherwise specified.

While you cannot define pod settings on a DC supply tag, underlying demand may return a pod through a DC supply tag. We now display pod metrics for both managed and DC supply in reporting.