US privacy, pod and VAST only improvements, report filters, and more.
Alerts
California Consumer Privacy Act (CCPA)
With the California Consumer Privacy Act (CCPA) coming into effect on January 1, 2020, we have released the us_privacy parameter and its corresponding macro {{US_PRIVACY}}. This macro identifies users from California who have opted out of the sale of their data. Publishers are responsible for passing the appropriate value on all incoming data from California in the format defined by the IAB. For more information about the value of the {{US_PRIVACY}} macro visit the IAB’s documentation.
The us_privacy parameter is included by default in the export tab of a supply tag. This information will also be passed to Header Bidding and PC demand sources.
Ads.txt and App-ads.txt
If you are connected to bidders via Programmatic Connect, update the ads.txt (desktop and mobile web) and app-ads.txt (in-app and ctv) files for you and your partners to include the following lines:
- springserve.com, [Your Account ID], DIRECT, a24eb641fc82e93d
- districtm.io, 101856, DIRECT,
3fd707be9c4527c3 - undertone.com, 3817, DIRECT
- synacor.com, 82101, DIRECT, e108f11b2cdf7d5b
- openx.com, 540634634, DIRECT, 6a698e2ec38604c6
- beachfront.com, 4969, RESELLER, e2541279e8e2ca4d
- advertising.com, 26282, RESELLER
- pubmatic.com, 157310, RESELLER, 5d62403b186f2ace
- rhythmone.com, 2968119028, RESELLER, a670c89d4a324e47
- spotxchange.com, 239904, RESELLER, 7842df1d2fe2db34
- spotx.tv, 239904, RESELLER, 7842df1d2fe2db34
- contextweb.com, 561910, RESELLER, 89ff185a4c4e857c
- openx.com, 540226160, RESELLER, 6a698e2ec38604c6
- appnexus.com, 1908, RESELLER, f5ab79cb980f11d1
- google.com, pub-9685734445476814, RESELLER, f08c47fec0942fa0
- appnexus.com, 2234, RESELLER
- advertising.com, 19623, RESELLER
- EMXDGT.com, 1251, RESELLER, 1e1d41537f7cad7f
- appnexus.com, 1356, RESELLER, f5ab79cb980f11d1
Make sure to replace [YOUR ACCOUNT ID] with the number in the lower right hand corner of the screen. For example, CrushTownUSA’s Account ID is 17.
For any and all questions and requests, please reach out to you account manager, who can connect these partners and ensure your domains and apps are whitelisted.
IP Lists
SpringServe no longer supports IP ranges in IP list targeting.
Core Improvements
Programmatic Connect in Ad Pods
We continue to improve pod functionality in SpringServe. As such, we now allow ad pods to request ads for multiple slots in a single request to a PC bidder. With this update, PC bidders will be able to respond with multiple bids in a single response, increasing potential for fill in ad pods.
UI/UX Improvements
DC Supply Tag Duplication
You can now duplicate a DC supply tag as a managed supply tag. By selecting To Supply Tag from the Duplicate Connected Supply button menu, you can create a managed supply tag that has the same settings, targeting, and demand stack as the DC supply tag.
VAST Only Supply Tag Opportunities
We now record an opportunity on VAST Only supply tags when they return a non-empty VAST response. Since this metric is now meaningful for SSB tags, we display this data in quickstats summaries and in all supply index tables.
Pod Tag Indicator
In the index tables throughout the platform, pod supply tags are now denoted by three horizontal dots in the badge preceding the tag name. This update makes it easier to visually separate your pod from non-pod tags when scanning index tables.
Realtime Debugger
When debugging supply tags in your SpringServe account, you can analyze the incoming requests. The entries shown on the table on the Incoming Requests tab now contain hyperlinks eliminating the need to copy and paste a URL into your browser.
Reporting Improvements
New Metrics
Additional metrics in reporting include Pod Opt Outs and Duplicate Impressions.
As noted above, Opportunities for VAST only supply tags will now be non-zero, as we record this event when a supply tag with a response type of VAST only returns a non-empty VAST response.
Pod Settings
A supply tag report will now return data for both pod and non-pod tags in your account. Previously, the report would only include pod tags when you included Pod Tag as a dimension. If you are running both pod and non-pod tags in your SpringServe account, you can filter by Pod Setting to return data for Custom or Dynamic pods. To see only data for your non-pod tags, filter by Pod Settings Include None.
Likewise, you can display a column for Pod Setting in your report by including the Pod Setting dimension.
Saved Report Filters
Filter Download Reports by Status, Origin, and User (Creator). Default origin is Ad Hoc. Status options are Pending, Processing, Completed, and Failed.
Scheduled Report filters include Frequency, Permissions, and User (Creator).
Bug Fixes
Various bug fixes and performance improvements
Comments are closed.