In our latest release, we discuss additions to Header Bidding, account level defaults, supply tag VAST version, and new macros for GDPR compliance.
Core Improvements
Header Bidding
We continue to increase the robustness of our Header Bidding demand. With the addition of bRealTime and district m, SpringServe now offers nine platform partners for Header Bidding demand tags.
Optional Parameters are available for several platform partners; Rubicon’s inventory and visitor optional parameters and OpenX’s customParams have been recently added. To add optional parameters, click the +New Optional Parameter button and a dropdown list of parameters will appear. Passing this information may improve the performance of your Header Bidding tags.
Additionally, our API now fully supports Header Bidding optional parameters, so you can do all your Header Bidding demand management in the API. Please see our documentation for further details on our API.
Account Defaults
You now have the ability to set defaults for new supply and demand objects in your account settings. On the Default Settings tab, you will find Optimization Defaults, Supply Defaults, and Demand Defaults:
Supply Defaults will apply to any new supply tag that is created going forward; set your preferences for Pre-Bid IVT Filtering and Post-Imp IVT Detection.
Demand Defaults show options for IVT filtering and detection. These settings will apply to any new demand tag that is created going forward. Options for Buy Flagged Supply and Default Tiers apply to new demand partners. When Buying Flagged Supply is disabled, requests will not be passed to the demand if they are coming from a flagged supply tag. The Default Tier can be set for managed and DC demand partners; select from First Look (1L) and tiers 1 through 5. Note that if the Default Tier is 1L, non-Header Bidding demand tags will be added to DC waterfalls at tier 1.
Feature Additions
Supply Tag VAST Version
SpringServe supports VAST version 3.0, 2.0. Supply tags exported from SpringServe are VAST version 3.0. However, certain supply partners may require a VAST 2.0 tag. We have therefore added the ability to change the VAST version of a supply tag in SpringServe. In the Advanced section of the supply tag Settings tab, select the desired VAST version.
Note that it is not necessary to reexport the supply tag if its VAST version changes.
UI/UX Improvements
Quickstats Table Updates
Quickstats show summary data for your SpringServe supply and demand so you can get an idea of what may need attention. We have added range compare on the requests column so you can spot changes in traffic volume. On supply tag tables, you can now find the environment column in the full view.
Demand Updates
Direct Connect App List Sharing
With Direct Connect, SpringServe is able to see targeting along the entire call chain and therefore will not pass a request to a DC demand tag if it would not meet your demand partner’s targeting. Sharing targeting information can be helpful in these situations so the DC demand can be effectively aligned to the appropriate supply. We now allow app name and bundle list sharing directly in the UI for Direct Connect. When applying app targeting to a DC supply tag, enable Share App Name/Bundle Lists and your DC supply partner will be able to download the list by clicking the download icon that appears in the Connected Targeting section of the corresponding DC demand tag.
Campaign Updates
Third party fees can now be set on campaigns. In the Fees section of the Settings tab of a campaign, define a campaign fee.
This feature can be useful when working with demand partners that work via deal IDs. In reporting, Third Party Fees will account for both partner and campaign fees, if applicable.
KPI targeting on campaigns allow you to only send requests to demand in a campaign if the inventory has historically met specified KPIs. You now have the option to use Moat Bot Rate as a KPI. Use this KPI to ensure your Moat Bot Rate stays below a threshold.
Reporting Improvements
We have expanded the number of supported time zones in reporting. Run reports in your preferred time zone in the reporting UI. Time zones are listed by city or region in order from offset from UTC.
Alerts
SpringServe and GDPR
In response to the European Unions General data protection regulations SpringServe has created two new macros for clients who serve European traffic:
- gdpr={{GDPR}}: a boolean value (1=True, 0=False) which flags the user as part of the EU
- consent={{CONSENT}}: the consent string from various consent management platforms. We support all formats.
For more information on the data we collect and your rights as an individual please visit our privacy policy.
SpringServe in ads.txt
SpringServe fully supports the IAB’s ads.txt initiative and its goal of increasing industry-wide transparency between buyers and sellers. With increasing adoption of the ads.txt initiative by a number of buying and selling platforms, we encourage all SpringServe clients to implement ads.txt on their domains and any domains with whom they work.
We have included instructions about how to add SpringServe to an ads.txt file below:
Owned and Operated Domains
springserve.com, {{ACCOUNT_ID}}, DIRECT, a24eb641fc82e93d
Resellers
springserve.com, {{ACCOUNT_ID}}, RESELLER, a24eb641fc82e93d
Replace {{ACCOUNT_ID}} with your SpringServe Account ID; this ID can be found in the lower right hand corner of the browser when you are logged into your SpringServe account. In the example below, CrushTown USA has Account ID 17.
Bug Fixes
Various bug fixes and performance improvements
Comments are closed.