Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

On the main Supply page, there are tabs for Tags, Partners, and GroupsLabels. In the Tags tab, you'll see a table with your supply tags and performance metrics for the time period specified. The default view shows all active tags of all types in all groups for all partners for today. Select your desired view from the dropdown lists.

Image Removed

Toggling from Lite to Full will show additional metrics in the table, including waterfall size, targeting, and number of changes made to the tag. See the Reporting glossary for a definition of metrics.

Tags

From the main Tags tab, Click on "+ Supply to Supply" to create a new supply tag. You can find similar buttons in the Partners and Groups tabs to create new Supply Partners or Supply GroupsLabels.

Settings

On the Settings tab for a supply tag, set the name, partner, payment terms, and environment. Demand Tag Options allow you to enable the supply tag for open market demand and set detected targeting on domain and player size. Pre-bid and post-imp IVT filtering and quality detection can be set in the IVT Options section. Labels and Notes can be added in the More Info section. Expand the Advanced section if you want to set the VPAIDResponse Type, type, demand side editsType, Demand Side Edits, VAST versionVersion, custom timeoutCustom Timeout, or declare keysKeys.

Image Removed

If you are working with a direct publisher, you may want to implement a custom timeout setting. If you do not set a custom timeout, SpringServe will not close the VPAID unit until an impression is filled or it has gone through all levels in the waterfall.

To override the type of domain targeting or player size targeting used by your demand tags, select your preference in Demand Tag Options section. Both targeting settings are defaulted to declared. 

Pre-Bid IVT blocking can be enabled in the IVT Options section. You have the ability to select which components to use for your pre-bid filtering. By default, both SpringServe and WhiteOps are active when Pre-Bid IVT Filtering is enabled. A la carte pre-bid options give you more control over the inventory that is filtered to your demand.

Back to top

Environment / VPAID Controls

Basic Info

Set the name, status, partner, payment terms, and environment. Options for payment terms are CPM , Rev-Share, and Dynamic.

Environment is a label within SpringServe and does not result in automatic targeting based on user agent or device ID. 

On your managed supply tags, you must specify the environment where the tag will run: Desktop, Mobile Web, In-App, or Connected TV. Selecting the environment will specify the VPAID response type of the tag. For Desktop tags, both the JS and Flash VPAID will return. For Mobile Webdesktop, mobile web, and in-app tags, JS VPAID will return, and flash demand is not allowed. ; CTV tags are VAST Only. You  You have the ability to override these settings; expand the Advanced section and the VPAID Enabled Response Type field will be revealed.

...

Note that

...

the

...

SpringServe VAST Only supply tags return no VPAID .We give you options for controlling the VPAID response to a supply tag so you can choose what works best for your inventory. Setting everything to VPAID both may improve performance on much of your supply, but lower fill rates on a subset of tags. Knowing your supply well will allow you to use the available tools effectively.Note that the VPAID for your connected supply depends on the settings on the managed supply tag that is selling to your DirectConnection.

Back to top

JS VPAID - allow Flash

Flash inventory can also serve through our JS VPAID, which is returned when JS VPAID is selected. Certain publishers may be sensitive to Flash demand; if you would like to disable the ability to play Flash demand via your JS VPAID, simply uncheck the box next to "Allow flash demand". Tags for inventory from HTML5 players must use our JS VPAID, which you can enable by selecting JS or Both.

Image Removed

You also have the option to return both Flash and JS VPAID in the same VAST response. When this option is selected, SpringServe returns both Flash and JS VPAIDs and the player must decide which one to use based on compatibility.

Back to top

IVT Settings

New supply tags use the account settings for defaults for pre-bid and post-imp. To use Pre-Bid IVT Blocking, set it to enabled in the IVT Options section. Post-Imp IVT Detection analysis is conducted after the impression occurs to determine if it is IVT. You will be able to run reports to determine domains against which to optimize. Note that Post-Imp IVT data has a delay of 8 hours.

When you enable Pre-Bid IVT Blocking, the request is analyzed when it comes into the adserver. If it is deemed to be IVT, then the request will be blocked and an empty VAST response will be returned. Pre-Bid IVT blocking is good to use if your Demand Partners are especially sensitive to receiving IVT traffic. 

You have the ability to select which components to use for your pre-bid filtering. By default, both SpringServe and WhiteOps are active when Pre-Bid IVT Filtering is enabled. A la carte pre-bid options give you more control over the inventory that is filtered to your demand.

You can specify which vendors to use for both pre-bid blocking and post-impression detection. When post-imp is enabled, impressions will be analyzed by your selected vendor(s) at the sampling rate specified.

Forensiq is the only partner that does IVT detection for inApp and CTV inventory.

Back to top

Keys

Demand Tag Options

Demand Tag Options allow you to enable the supply tag for open market demand and set detected targeting on domain and player size. If the supply tag is enabled for Open Market demand, it can be sold to bidders through Programmatic Connect. Granular control of bidders is available on the Demand tab.

Domain and Player Size Targeting can be set to declared or detected for VPAID supply. Detection of domain and size is done using the VPAID. If declared targeting is being used, the waterfall is built based on demand tag targeting and the declared domain and size. These values are based on what has been passed through the macros on the request to the supply tag. If the request meets targeting for a demand tag, it may be included in the waterfall; if it does not, the demand tag is excluded from the waterfall.

In the case of detected domain and size targeting, we do a first build of the waterfall based on declared parameters. Once the VPAID has initialized and the domain and size have been detected, we check for a mismatch. If the declared value does not match the detected value, the waterfall is rebuilt based on the detected values.

Advanced Supply Tag Settings

Response Type allows you to select JS VPAID or VAST Only. Note that JS VPAID responses are generally not supported for CTV environment.

If you own the player, then set the Type to Syndicated. For syndicated supply, you have the option to Track player costs based on player loads and not impressions. A player pixel will appear on the Export Tag tab if you use this option.

Demand Side Edits allow the supply to be associated to demand from the demand side.

SpringServe can return either VAST 2.0 or VAST 3.0; make your selection in the VAST Version setting. 

If you are working with a direct publisher, you may want to implement a custom Timeout Setting. If you do not set a custom timeout, SpringServe will not close the VPAID unit until an impression is filled or it has gone through all levels in the waterfall.

To report Key-Value on data, you must declare the Key(s) on the Supply Tag level. In the Settings tab of a Supply Tag, select the Keys keys that you would like to report on in the Advanced section.

Image Removed

You are limited to 5 keys per supply tag for reporting. Note that you must include the key(s) in the tag that you export to your supply partner if you want to report on key-value data. In addition to reporting, you will also want to declare keys if any demand is using custom key-value targeting. Declare those keys in the Keys field and they will be included in the export tag so they get passed to the demand stack. 

The key and a placeholder will automatically be added in the Export Tag tab. For the targeting above, you would export the following tag:

...

When running reports, select Key-Values as a Dimension. You can also filter by Key. 

IVT Options

IVT settings on new supply will use the Default Settings of your account. You can override these defaults for pre-bid IVT filtering and post-imp detection in the IVT Options section.


To use Pre-Bid IVT Blocking, set it to enabled in the IVT Options section. Post-Imp IVT Detection analysis is conducted after the impression occurs to determine if it is IVT. When post-imp is enabled, impressions will be analyzed by your selected vendor(s) at the sampling rate specified. You will be able to run reports to determine domains against which to optimize. Note that Post-Imp IVT data has a delay of 8 hours.

When you enable Pre-Bid IVT Blocking, the request is analyzed when it comes into the adserver. If it is deemed to be IVT, then the request will be blocked and an empty VAST response will be returned. Pre-Bid IVT blocking is good to use if your Demand Partners are especially sensitive to receiving IVT traffic. 

Back to top

Demand

...

In the Demand Tags tab, associate your demand and set up your waterfall. Existing supply tags also display summaries of performance. You can look at these quickstats summaries as a table or a graph. Read more about Graph Views

Add Demand Tags

Click the Image Removed"+Demand" button to attach align Demand Tag(s) to your Supply Tag; you can either copy from existing demand or select tags manually. If you choose the later, a modal will pop up, and you can select which demand to associate with your supply.

When you are choosing your demand, the modals automatically filter for rates that will not result in loss to you. For example, if you are aligning demand to a supply tag with a rate of $6, the demand tag modal will automatically filter for demand tags with rates $6 and above. 

Image Removed

You can change the rate by which to filter , and any tag that has a rate that will result in a negative margin will be highlighted in red. 

Image Removed

Note that the default view for the demand tag modal is for active tags. If you expect to see some demand tags that aren't theredo not appear, select any Any status or inactive Inactive from the dropdown.

Make sure to attach the right kind of demand to your supply tag. For desktop, attach Flash, and for mobile, attach JS VPAID or VAST Only. Note that a JS VPAID supply tag will work with both JS VPAID and VAST Only demand. 

Set up your Waterfall

Once you have added your demand tags, you can arrange them in either a tiered or flat waterfall (example of tiered below). For a tiered waterfall, within the waterfall. Within each tier SpringServe will call the tags in priority order. If a tag at priority 1 first, and if it demand tag does not fill, it will move down the tier. If SpringServe goes through an entire tier's waterfall with no fill, it begins the waterfall of the next tier. 

If a demand tag is aligned to a supply tag with a CPM above its RPM, it will be highlighted in red (see tag DemandPartner6 $5). This feature provides a visual warning that a supply-demand relationship will result in a negative margin to you.

Image Removed

Demand

On managed tags and DC tags without auto-opti enabled, demand tags have a lock icon to the right of their priority. Clicking this icon will lock the tag in place (see tag DemandPartner12 $6.5). Optimization can be enabled on the supply tag and any locked demand tag will remain at its current priority and tier. This feature allows for easier A/B testing – lock in two demand tags at the same priority to distribute requests evenly and see which tag performs better. Note that you cannot change the priority of a locked tag, so click the icon to unlock it before changing its priority.

You can have more than one demand tag at the same priority and tier. Tags at the same priority will be called in a round robin fashion, meaning that they will be called with an equal probability (provided the demand tags have the same targeting). Putting tags at the same priority and tier will allow you to do an A/B test and see how different tags perform at the same tier in the waterfall. New demand tags are assigned priority 1 by within their partner's default tier. You may have an idea of what's going to perform best and if so, arrange your waterfall based on this knowledge. If you do not know what will perform best, you can leave all tags at the same priority and you can rearrange your waterfall after your tag sees some volume.

If a demand tag is aligned to a supply tag with a CPM above its RPM, it will be highlighted in red. This feature provides a visual warning that a supply-demand relationship will result in a negative margin to you.

Back to top

Waterfall Best Practices

Waterfalls should have between 3 and 10 priority levels with no more than 3 tags at the same priority, and no more than 15 25 demand tags per supply tag. Following these recommendations will allow you to have a clear picture of how your demand is performing and let you optimize effectively. Remember that unless you set a custom timeout on your supply tag, SpringServe will move all the way down the waterfall until an impression is filled. If your waterfall is longer than 10 priority levels, you could run into latency issues.

Note that SpringServe has a policy to automatically remove old demand tags from waterfalls. If a demand tag has been on a waterfall for at least 90 60 days and has zero requests in the last 90 60 days, it will be removed from the waterfall. This removal increases UI speed on the waterfall page and help automate the clean up of old tags in your account. 

Back to top

Optimization

You can optimize your waterfall manually or automatically. Manual optimization entails you setting the waterfall priorities yourself. SpringServe also offers auto optimization, which is enabled by default on your supply tags. To disable it or to change the parameters, go to the Optimization tab. Default parameters are as follows: Request Fill over the last 60 minutes:

Image Removed

Optimization runs every 20 minutes and will calculate the Optimization Metric selected based on the Lookback Minutes specified. The algorithm will reprioritize your demand tags based on their performance during the lookback window.

When you are setting up your tag, think about the volume that you are expecting to see. If you have all your tags on priority 1, the requests will be split among them. You may need to increase your lookback minutes in order for auto-optimization to take effect. There are no minimum or maximum values for optimization parameters.

Read more about optimization here.

Back to top

Targeting

Note that in reporting, "Blocked (Targeting)" requests are a result of your supply tag targeting and you will not be charged based on these unusable requests to SpringServe.

...

  • Domain: This option is available for all Desktop and Mobile Web environment types. A dropdown will display all domain lists available that could be associated as a white list or black list. For instructions on how to create domain lists see here: Domain Lists
  • App Name and App Bundle: These options are available for all In-App and CTV environment types. Selecting the the App Name list  list type enforces that inventory matches the App Name in the list before being considered eligible. A dropdown will display all App Name and Bundle lists available that could be associated as a white list or Black list.  App Name + Bundle ID enforces that inventory matches the App Name and the App Bundle ID combination in the list before being considered eligible.  'App Name + Bundle ID' Lists are more restrictive than App Name Lists or Bundle ID Lists on their own which only look at their respective fields.  
    For instructions on how to create app name and bundle lists see here:  App Name Lists

...

  • Country: Select countries to either include or exclude from the dropdown values list.
  • Player Size: Player size targeting allows you to select the criteria for targeting by checking the player size you want.

         Image Removed

  • SpringServe defines player sizes by width in pixels as follows:
    • x-small: < 250 pixels
    • small: 250-349 pixels
    • medium: 350 - 500 pixels
    • large: 501 - 799 pixels
    • x-large: ≥ 800 pixels
  • Player Aspect Ratio: Here you could target from a list of aspect ratios, which is calculated as the ratio between width and height: width / height. Tall skinny players have a smaller aspect ratio value and short wide players have a larger aspect ratio.
  • DMA Targeting
  • Device Type: Device Targeting allows you to select specific device types to target.
    • Computer
    • Mobile
    • Connected TV
    • Table
    • Other
  • Operating System (OS)
    • Android
    • iOS
    • Linux
    • Windows
    • Mac OS X
    • Chrome OS
    • Fire OS
    • Xbox OS
    • Tizen (Samsung)
    • Roku OS
    • Other        
  • Browser: Select which browsers are allowed. Browser is based on user agent.
    • Chrome
    • Edge
    • firefox
    • Safari
    • IE
    • Chromium
    • Chrome Mobile
    • WebView
    • Android
    • Samsung Browser
    • Facebook on Android
    • Facebook on iOS
    • Mobile Safari
    • Roku App
  • Country: Select as many countries as you need to either include or exclude from the dropdown values list.

      Image Removed

When you select Whitelist or Blacklist for Domain and Country targeting, boxes will appear. When you click in these boxes, dropdown lists will appear. You can target as many domain lists as you like for a tag. Select Custom Player Size, OS, and Device Targeting and a list of options for each will appear; check the boxes next to the options you want to target. 

Note that in reporting, "Blocked (Targeting)" requests are a result of your supply tag targeting and you will not be charged based on these unusable requests to SpringServe.

  • Supply Capping: impression and request supply caps are supported for various periods. Select ASAP, Even, or Front-Loaded pacing.
  • Frequency Capping: impression and request frequency caps are supported for various periods.

Back to top

Optimization

You can optimize your waterfall manually or automatically. Manual optimization entails you setting the waterfall priorities yourself. SpringServe also offers auto optimization, which is enabled by default on your supply tags. To disable it or to change the parameters, go to the Optimization tab. Default parameters are as follows: Request Fill over the last 60 minutes:

For requests to your supply tags, SpringServe will calculate the Optimization Metric selected based on the Lookback Minutes specified. The algorithm will reprioritize your demand tags based on their performance during the lookback window.

Read more about optimization here.

Back to top

Export Tag

After you have clicked "Save and Exit" or "Apply" for your Supply supply tag, the Export Tag tab will appear. 

...

Click the buttons for the macros you would like to be passed and they will automatically fill in with the appropriate keys and macros and the export tag can be exported to your supply partner or the player.

Back to top

Partners

On the Supply Partners tab, you will see a table of your supply partners along with columns showing targeting, the number of associated tags, and performance metrics. Toggling to the Full view will reveal all targeting, budget bar, the number of users, the account managers, and additional performance metrics.  In the top right corner click the Click "+ Supply Partner" to add a new partner. 

Supply Tags

Existing supply partners have a Supply Tags tab. Here, you can see a summary of performance for all supply tags that belong to the supply partner. You can look at these quickstats summaries as a table or a graph. Read more about Graph Views

All tags are shown in the table on this tab, and metrics will update when you change the time range. New supply tags can also be created for this supply partner from this tab.

Settings

When adding a Supply Partner to your account, enter in the name and choose an available user as the Account Manager(s). If available, choose supply tags to associate to the partner by selecting them in the table. Use the search bar to filter the available tags. 

...

SpringServe supply tag optimization occurs every twenty minutes and reprioritizes the waterfall depending on the Optimization parameters. If you would like to use SpringServe your account default optimization metrics, no actions need to be taken. 

There is not a one size fits all set of parameters for optimization. Based on your supply, you may want to use a different optimization metric.  On the Settings tab of a supply partner, you can now You can set custom partner Optimization parameters by toggling to Custom in the Optimization Defaults section for the partner.

Note that any changes made to Optimization Defaults on both the account and partner level will apply to newly created supply tags and connected supply; no changes will be made to existing supply tags. If you would like to make a bulk update to existing tags, use bulk actions.

Back to top

Targeting

Select targeting options are available on the supply partner level. If targeting is in place on the supply partner, a request must pass targeting on both the partner level and the tag level.

Back to top

Labels

You can now assign multiple labels to each supply. Example use cases include labels for desktop, outstream, direct, testing, etc.

You can assign a tag to a label from both the label side and the tag side. When you go to the main supply page, you will see the labels tab at the far rightOn the Supply Labels tab, you can create a new label by clicking "+Supply Label"Creating a new label or selecting an existing label, will bring you to theits Settings tab, where you can edit the name of your label. On the Supply Tags tab, you will see tags that are already associated to a label appear in the table on this tab. You can add tags to the label by clicking "+Supply" and a modal will appear.

From the tag side, you can assign labels in the settings tab. Clicking in the Labels box shows your available labels.

...

Reporting is available for labels both as a dimension and a filter. When running a report for a tag that has multiple labels, you will see one line per label; the metrics for both lines will be the same. Note that reporting currently results in inflated totals; i.e., if you have two labels on a tag, the total will be inflated by a factor of two.

Graph Views

The Graph view of quickstats summaries show a visual representation of performance, financial, and quality metrics for your SpringServe objects. In each section, sunburst graph is displayed for given metrics. Sunburst graphs give you a hierarchical view of data. Read more about Graph Views

Back to top