Running Reports

The Ad Hoc Reporting page will automatically load the settings for your default reporting template. In a new SpringServe account, the default report template is the SpringServe Supply Report, which is for today in your account time zone, broken out by supply tag. For more information regarding report templates, including how to change your default and create new templates, see Saved Reports.

In the Time Parameters section, you can switch the template, select the Date Range, Interval, and Time Zone for your report.

Dimensions

In the Dimensions section, select the dimensions for your report. All dimensions are also available as Filters.

The available dimensions / filters for creating reports are the following:

* available for PC-enabled accounts

† available for Ad Pod-enabled accounts

Click the button next to the Run Report button to download your report. To schedule your report, click the calendar button. To share your report using a link, click the share button.

If you run a very large report, SpringServe will prompt you to name your report and continue to the Downloads tab, where you will be able to download your report once it has completed. The first 2500 rows of your report will be visible in the UI if you select Preview rather than continue to the download report page. You can download this report preview, but keep in mind that it is incomplete.

See the Reporting Glossary page for a description of metrics shown in your reports.

For tips on how to best utilize Create Reports, please see our Best Practices page. 

Back to top

Flexible Filters

Flexible filters allows SpringServe to offer robust reporting without overcrowding the UI. You can filter by inclusion or exclusion. Several filters are shown by default, and clicking a Quick Add button reveals the specified filter.

To add a filter not included in quick add filters, there are two options:

• Click the +New Filter button and select the desired filter from the dropdown.
• Change an existing filter dropdown to your desired filter.

Tag filters offer two options: Select and Enter List. When Select is highlighted, search for individual tags. When Enter List is highlighted, paste a comma-separated list of tag ids.

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:

• Numbers: Requests, Blocked (Total), Opps, Imps
• Calculations: Request Fill %
• Response Metrics: Errors, Errors %, Timeouts
• Financials: Revenue, Media Cost, Profit (Net), Margin (Net), RPM, CPM, PPM (Net)

If you add demand tags to the dimension, or filter by a specific demand tag, the metrics will update.

The default metrics for a demand report are as follows:

• Numbers: Ad Requests, Opps, Imps
• Calculations: Request Fill %
• Response Metrics: Errors, Errors %, Timeouts
• Financial: Revenue, Media Cost, Profit (Net), Margin (Net), RPM, CPM, PPM (Net), Score

Back to top

Conditional Reporting

Set conditions on your report to return only those lines which meet those conditions. For example, you can run a report for only supply tags with fill rate over 1%.

Use the Quick Add buttons to select a metric or click the +New Condition button and a dropdown will appear. Select your desired metric from the dropdown and set the condition.

Data Availability & Data Retention

IVT Metrics

Metrics for IVT and viewability metrics are not compiled realtime, but rather provided to SpringServe by our data partners. Therefore, these metrics have a delay, resulting in initial zeros before SpringServe receives the data:

• HUMAN: 72 hour delay for pre-bid. Post-imp data is available through your HUMAN 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.

Historical daily domain and app data is available for the last 100 days. If you foresee the need for historical data, we recommend running a scheduled report for your records, as the data is destroyed after 100 days and there is no method of retrieval.

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

Note that in domain and app reports, you may see "unclassified". At the end of each hour, domains/apps which have fewer than 15 total requests and no impressions in the last hour are compiled into "unclassified". In this way SpringServe is able to deal with long-tailed data. If you notice that you are seeing a lot of unclassified domains/apps on a supply tag, talk to your supply partner about the quality of domains/apps that they are sending to you. 

For more information about unclassified domains and apps, go to our FAQ page.

Overlimit

Since there are so many app names and bundles out there, SpringServe has set a threshold limit for the number of unique App Names and App Bundles per supply source. If you see "Overlimit" in your reports it means that the threshold has been exceeded. 

Thresholds are:

Content,  Device, Geo and Key Value Reports

The data retention period for any content params, geographical data, device user agent data eg. brand, browser, operating system and all key values is 100 days. If you foresee the need for historical data, we recommend running a scheduled report for your records, as the data is destroyed after 100 days and there is no method of retrieval.