| Table of Contents |
|---|
...
The available dimensions / filters for creating reports are the following:
| Demand | Supply | Inventory | Content | Partner segments |
|---|---|---|---|---|
| Bid Bucket | Pod Setting | Advertiser Domain | Content Name | Partner Segment Code |
| Bidder Account * | Ad Pod Tag † | App Bundle | Content Episode | Partner Segment Vendor |
| Buying Demand Tag | Response Type | App Name | Content Genre | |
| Campaign | Router | Browser Type | Content ID | |
Campaign Code | Selling Supply Tag | Country | Content Season | |
| Creative | Slot Number | Declared Domain | Content Series | |
| Creative Code | Slot Order | Declared Player Size | Content Title | |
| Deal ID * | Supply Account Managers | Detected Domain | Language | |
| Demand Account Managers | Supply CPM | Detected Player Size | Livestream | |
| Demand Class | Supply Class | Device | Network Name | |
| Demand Code | Supply Environment | Device Brand | Production Quality | |
| Demand Environment | Supply Format | Key | Rating | |
| Demand Format | Supply Partner | Key-Values | ||
| Demand Partner | Supply Tag | Operating System | ||
| Demand Partner Code | Supply Tag Label | |||
| Demand RPM | Supply Type | |||
| Demand Tag | Marketplace Type | |||
| Demand Tag Label | ||||
| VAST Error Code |
* available for PC-enabled accounts
...
Domain and app filters also offer the option to use a list. When Manual is highlighted, enter a comma-separated list. When List is highlighted, you can search your targeting lists and filter by all domains/apps on that list. Checking the Exact Match box searches for the exact domain/app; if it is unchecked, partial match is executed.
Selectable Metrics
You will find the metrics section below the Filters section on the Create Reports page. Metrics are divided into 6 categories: Numbers, Calculations, IVT Metrics, Quality Metrics, Response Metrics, and Financials. By default, this section is collapsed and the pre-selected metrics are defined by the template selected.
Metrics update when you add dimensions or filters. For example, the SpringServe Supply Report template has the following metrics:
...
- WhiteOps: 72 hour delay for pre-bid. Post-imp data is available through your WhiteOps login.
- Forensiq: 12-18 hours
- IAS: 12-18 hours. Note that SpringServe aggregates IAS log level data; it is not MRC accredited and may vary slightly from IAS's MRC accredited data
- Moat: 6 hours
- Protected: 2 hours
Domain & App Reports
Declared domain information is passed through the url={{ENCODED_URL}} macro. Note that {{URL}} and {{DOMAIN}} macros can also be implemented, but we recommend using the encoded url. The App Name and App Bundle information comes in through the app_bundle={{APP_BUNDLE}} and app_name={{APP_NAME}} macros respectively. If these macros are not filled, we will report unknown.
You can run a report by declared domain, detected domain, app name, and/or app bundle in SpringServe. To run a reports for periods other than today and yesterday, switch to UTC timezone.
...
Hourly data is available for the last 48 hours. Reporting by country and domain/app is supported for select countries (US, Canada, Mexico, Argentina, Brazil, Australia, Taiwan, India, and European countries), with the remainder grouped by continent. This geographical data is available for the last 48 hours.
The information passed through on the domain/url macro is the Declared Domain. SpringServe also has domain detection, which occurs when the VPAID initializes. The domain that is detected at this point is the Detected Domain. Note that because domain detection occurs upon VPAID initialization, Detected Domains are only available when there is an opportunity; an opportunity is defined as a VPAID initialization. It is impossible to know what the detected domain is if there hasn't been an opportunity, and therefore, requests are not shown when running a detected domain report.
Unclassified Domains and Apps
...