Reach & Frequency reports, geo targeting improvements, and more header bidding optional parameters.
Core Improvements
Reach & Frequency Reporting
You can now run Reach and Frequency reports in the SpringServe UI. These reports give you visibility into the number of unique users and how often they have seen impressions.
New Metrics
- Unique Users: total unique user ids
- Unique IPs: total unique IP addresses
- Unique Devices: total unique Device IDs
- User Reach: average number of impressions per unique user ID = Impressions / Unique Users
- IP Reach: average number of impressions per unique IP address = Impressions / Unique IPs
- Device Reach: average number of impressions per unique device ID = Impressions / Unique Devices
The Reach and Frequency Report templates preselect Impressions, Unique Metrics, User Reach, Revenue, and RPM. You select the desired time interval for the Reach Report.
Cadence Dimension
Frequency reports include an additional “Cadence” dimension, which consists a set of pre-defined intervals:
- Days 1-2
- Days 3-4
- Days 5-7
- Days 8-15
- Days 16-30
- Days 31-60
- Days 61 – 90
- Days 91 – 180
- Days 191 – 365
The date range selected defines available cadence values. In the case where you run a report for the last 30 days, cadences of Day 31 – 60 and beyond will not be included. Note that the cadence indicates the number of days before the last date in the date range; i.e. Days 1 – 2 displays the total number of impressions and uniques for today and yesterday.
Report Performance
Due to the high level of granularity of this data, these reports are available for the last 365 days and can only be run in UTC. Reach and Frequency reports take longer to run than other reports due to the high volume of data and therefore you will be directed to the Download Reports page when running them. Including any additional filters or dimensions on this report is likely to increase the amount of time required to run.
For more details on Reach and Frequency Reports, please see our wiki. If you are interested in adding this reporting feature to your SpringServe account, please reach out to your account manager.
Geo Targeting Additions
SpringServe now supports regional targeting for all countries. Previously, State and Province targeting was only available for the US, Canada, India, and Australia. Notably, this change allows you to target the home nations of Great Britain: England, Scotland, Wales, and Northern Ireland.
In the UI, we have updated the label from State/Province to Region.
We have expanded City targeting to include additional cities across the globe.
Note that when you apply geo targeting you can do so by specifying individual values on a tag, or you can create geo lists from the Targeting page to use across multiple objects in SpringServe.
Feature Additions
LiveRamp Integration
For publishers who are integrated with LiveRamp’s Sidecar, you can pass the envelope ID in the eids={{LIVERAMP_EIDS}} param/macro combination on your supply tags. SpringServe will pass this value to Magnite, Xandr, and Index exchange SSPs via the eids parameter, which will be used for cross-device targeting.
UI/UX Improvements
Header Bidding
HB floor on Supply Tags
You can now set a universal RPM floor rate for header bidding demand on supply tags. When setting the RPM floor rate for a supply tag, check “Apply to HB” to set the floor on all header bidding demand behind the supply tag.
Optional Parameters
SpringServe has expanded optional parameters for a number of adapters:
- All adapters: buyer_uid override
- Xandr: traffic_source_code, imp_tag_id override, and user.id Override
Segments
You can now view pixel segment items in the API.
Alerts
From 8:30 PM – 10:30 PM EDT on April 13th, 2022 we will be performing database maintenance and data will be delayed. There will be no effect on ad serving. We apologize for the inconvenience and thank you for your understanding.
Performance Improvements
When supply tags, demand tags, and campaigns are inactive and have not been updated for 6 months, we will remove existing supply-demand associations. This change allows the UI to run faster.
Comments are closed.