We’ve delivered new metrics in the Ad Quality UI, API support for day parting, improvements to outbound requests, and more since our last newsletter. This spring has been a busy one for us over here at SpringServe, and we’re excited to share what we’ve been working on with you.
Core Improvements
Tier Competition Allows all Magnite Tiers to Compete with SpringServe Tiers, including Programmatic Guaranteed
SpringServe has improved how we’re handling tier prioritization with Magnite Streaming in this beta release. This work enables all Magnite tiers to compete with SpringServe tiers and represents the continued evolution of SpringServe and Magnite as we continue to bring workflows together in one place for a more seamless experience. This feature is not yet generally available, but connect with your account manager if you’re interested in learning more.
Tile Deduping Logic has been Updated to Include Creative Code
The deduping logic for tiles has now been updated to include creative code. This update means the logic for Tiles now also dedupes on Supply Partner ID, Creative ID, and Creative Code.
IP Address and Device IDs No Longer Obfuscated in Outbound Requests
SpringServe has updated their obfuscation rules for when the DNT and LMT flag is present. When DNT or LMT are true, it means the user is opting out of having their data added to audience based segments. SpringServe will continue to disable cookie tracking, user synching, and users will not get added to any audience based segments. As of March 20th, SpringServe will no longer obfuscate the IP address and Device IDs in outbound requests. This decision was made strategically with the advice of Magnite’s Privacy experts.
For more information visit the Privacy Targeting page of our wiki here: https://springserve.atlassian.net/wiki/spaces/SSD/pages/3547005272/Privacy+Targeting or feel free to reach out to your dedicated TAM.
Ad Quality UI
New metrics in Ad Quality UI create more transparency into performance
Wins, impressions, and error metrics have been incorporated into the Ad Quality UI and are now available under the Ad Q tab. These new metrics offer an at-a-glance view for the last 24-hour time period of VAST Hashes and their associated win and impression metrics along with the quantity of error occurrences for easier troubleshooting.
Status for Audited Creative Targeting now Available as Bulk Action in the Ad Quality UI
The ability to change the audit status as a bulk action for audited creative targeting is now available on the scanned creative index table. Talk to your account manager if you are interested in audited creative targeting.
Usability Improvements
API Support Now Available for Day Parting
For campaigns, creatives, demand, and supply tags, API support now exists for day_parting.
Segment Index Tables now show object counts
This improvement allows users to see the objects that are targeting a particular first-party or partner segment. Note the total count is displayed on the index table while the itemized objects are displayed on their respective tabs (for example, supply and demand tag) of the segment.
Dropdown now remains open in reporting when applying filters
This improvement in the “Reporting” tab enables a better user experience when filtering by multiple objects.
Italicize campaigns that are inactive in the campaign dropdown
Within the demand tag section of the platform, campaign flight dates that have passed will be italicized and alert text will display, letting users know when a tag will not serve because the campaign end date is in the past.
Read and Write Support for Day Parting in Demand Tags and Campaigns
Read and Write API support has been added for “note” and “day_parting_user_timezone” on demand tags and “day_parting_user_timezone” on campaigns.
Reporting Improvements
Run Reach and Frequency Reports on Creative
Reach and Frequency reports now include Creative as an available dimension for selection. For clients who use line item class demand tags for creative rotation, this improvement is especially useful. Note that the Creative dimension is the SpringServe creative object, not hashed creative from the Ad Quality UI. This means that reports will return a line where the creative ID is 0 or null because it’s not a demand class of line item, creative asset, or house ad.
View Scheduled reports as an Analytics User
Analytics users can now view scheduled reports of admin and ad ops users in the account.
Comments are closed.