In our latest release, we discuss exciting additions on SpringServe, including the Realtime Debugger and Reporting Templates. We also discuss targeting and reporting additions and various UI/UX improvements.
We are proud to announce the release of our Realtime (RT) Debugger in the SpringServe UI. The RT Debugger is a valuable tool that allows you to see the behavior of your tags in real time and diagnose issues that need to be addressed. There are several ways to navigate to the RT debugger:
- click the wrench icon in the actions column on the index page
- click the wrench icon in the actions column in the supply tab of a demand tag or the demand tab of a supply tag
- click the wrench icon in the header of an object
- navigate to Troubleshooting from the Settings menu
In the RT Debugger, you can search your SpringServe objects and see corresponding metadata, performance data, and traffic data (secure vs. non-secure, environment, player size, country, user agent, and domain/apps).
Performance data is displayed in the Events container. Here, you will see a sunburst chart which shows events in a hierarchy. This chart can give you an idea of updates that need to be made to targeting or demand stacks. For demand objects, VAST error codes are also shown in the sunburst chart.
Selecting Performance in the pillbox will display a time series of requests, impressions, and fill rate. Selecting Table will display a subset of the sunburst data in table format.
Information about your traffic includes graphs showing security protocol of requests, environment, country, user agents, domains and/or app name and bundles, and player sizes.
The player sizes container will show ratio of declared sizes as default. You can also see histograms of width and height, as well as a scatter plot showing the aspect ratio of the player. If there are opportunities, detected data is also available.
The User Agent container displays the ratio of Device Type as default. You can also see donut graphs for Device Makes, Operating Systems, and Browsers by selecting from the dropdown.
The Inventory container will show the top 25 domains that are requesting your tag. For in-app and ctv tags, this graph will display app names. If you are debugging multi-environment object such as a partner, you can use the drop down to look at domains, app names, and app bundles. If there are opportunities, detected data is also available.
For more details about the Realtime Debugger, please see our wiki
Users can now create custom report templates and set the default report for the reporting UI. Your templates can be accessed and edited on the Templates tab of the Saved Reports page.
There are two ways to create a report template:
- On the Templates tab of the Saved Reports page, click the + Report Template button.
- On the Create Reports page, select your settings, metrics, filters, and dimensions and click the disk icon to the right of the Run Report button.
Performing either of these actions will take you to a New Report Template page. Update the name and description fields and scroll to the bottom of the page to save the template.
Once you have created your templates, you can select the default template that will load when you go to the Create Reports page. There are two ways to set the default template:
- On the Templates tab of the Saved Reports page, click the star in the last column of the index
- Under the user icon menu, select Edit Profile. Change your default report template in the Settings section of the third column.
For additional details on reporting templates, please see our wiki.
Additional Targeting Options
Device ID an IP Targeting
You now have the ability to target based on Device ID and IP address. List management can be accessed via the Targeting menu.
As with Domain and App lists, you items can be added manually or by uploading a CSV. IP targeting allows both specific IP addresses and ranges. Assign IP and Device ID lists to Supply and Demand on the targeting tab of your SpringServe objects. You can also set account-wide IP or Device ID targeting on the Basic Settings page.
In addition to Device ID lists, you can now require that the device id macro is present for your CTV and in-app demand tags. Your demand partners may require that the device ID be passed to them.
When you select Enabled for Device ID Required in the User Agent Targeting section, only requests which have the DEVICE_ID macro properly implemented will be eligible for that demand tag.
DMA targeting is now available on supply tags in addition to demand tags.
Additional Event Pixels
You can now append event pixels to demand partners and campaigns, as well as on the account level. Event Pixels that are added to a demand partner or campaign will be fired on all demand tags associated to the partner or campaign. Set these pixels on the settings tab of the partner or campaign.
Account event pixels can be set on the Default Settings tab of the Basic Settings page in the third column. These pixels will be fired on all demand tags in your SpringServe account.
Fees are now displayed only in the full view of demand partner and campaign indices. Format of fee has also been updated to be more readable.
The search bar on the changelog tab now searches the user and the summary columns of the changelog table.
Reporting & API Improvements
Reporting on Tag Lists
When using the Reporting UI, you may want to filter by a list of tag ids. Now, rather than selecting each tag in the search box, you can paste a comma-separated list of IDs into the supply and demand tags filters. Toggle to Enter List in order to use this functionality.
Additional Dimensions and Filters
Supply Class has been added to reporting. Possible values for supply class are Managed and DC. Demand Environment is also now available as a filter and a dimension. Reporting Demand Environment reflects the current setting on a demand tag and does not reflect historical changes.
Supply Partner targeting can now be set in the API. You also now have the ability to create Creative Assets in the API. To create a creative asset demand tag, first you will need to upload your creative and then associate the creative to a new demand tag. For further details about the API, please see our wiki.
Various bug fixes and performance improvements.