Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 33 Next »

 

General

What is the Default Supply Tag Type in SpringServe?

When you make a Supply tag, the default type is VPAID both (JS and Flash). Make sure you attach the right type of demand to your Supply tag.

Back to top

Which Version of VAST do SpringServe Tags Accommodate?

SpringServe will work with demand tags that return both VAST 2.0 and 3.0. 

Supply Tags default to VAST 3.0; the version can be set in the Advanced section of the settings tab.

Back to top

How does SpringServe call demand tags? 

SpringServe uses a traditional waterfall to call your demand tags. SpringServe will call a tag at priority 1 first, and if it does not fill, it will move to the next tag down the waterfall. You can have more than one demand tag at the same priority. 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 will allow you to do an A/B test and see how different tags perform at the same tier in the waterfall. 

Back to top

How does SpringServe define player Size?

You can see how we define player size in the targeting tab of a supply or demand tag.

  • X-Small: <250 pixels in width
  • Small: 250-350 pixels in width
  • Medium: 350-500 pixels in width
  • Large: 501-799 pixels in width
  • X-Large: ≥800 pixels in width

Does SpringServe offer Two Factor Authentication (2FA)? 

Yes! 2FA allows you two layers of security in your SpringServe account: password and 2FA code on your mobile device. When enabling 2FA, you will need to install a 2FA app on your mobile device, such as Google Authenticator or Authy. Enable 2FA on the Edit Profile page, which can be accessed from the user menu.

Upon enabling, a QR code will appear. Open your 2FA app and scan this code. Your 2FA app will now provide you with a 6-digit one time password which refreshes periodically.

When logging in, you will be prompted to enter your password and your 2FA code. Open your 2FA app and enter the code for your SpringServe account, ensuring you have a few seconds before the code refreshes. Note that you also have the option to remember your device for 30 days. Checking this box will allow SpringServe to remember your user for 30 days or until you clear your cookies.

What do I do if I Lose My 2FA Device?

If you lose your mobile device with your 2FA app on it, you will have to set up 2FA on your new device. Contact support@springserve.com and tell them that you need to set up 2FA on a new device. 

Back to top

How do I Create a Client Account for My Supply/Demand Partners?

Go to Settings → Users and click +User. Here, you can enter the details of your client. Select Supply/Demand Client in the Type dropdown list. When Supply/Demand Client is selected, a box will appear and you can select the relevant Supply/Demand Partner(s) for this client user.

Once you have created the account for your Supply/Demand partner, they will receive an email with a link that allows them to set their password and enter their name. They can also go to video.springserve.com and click "Forgot your password?" to get a new link. Your account will appear in their dropdown menu when they log into their SpringServe account.

You can log in to Client accounts to see what they will see when they log in to SpringServe. On the Users page, click the icon in the far right column next to the pencil icon.

Back to top

Reporting

How Often is Reporting Updated?

Data in SpringServe is updated on a by-minute basis. If you make a change, you can see its impact quickly.

Back to top

Can I set up a recurring report?

Yes; there are two ways to do this. 

Use the Scheduled Reports feature and create a new report by clicking the +Scheduled Report button, or run a report in the UI and then click the calendar icon next to the Run Report button.

You can also bookmark the URL when you run a report. In fact, when navigate to the Create Report page of SpringServe you are always taken to the report for Today in the timezone America/New York, with dimension of Supply Tag and no additional filters: 

http://video.springserve.com/reports?date_range=Today&interval=&timezone=America%2FNew_York&dimensions%5B%5D=supply_tag_id&domain=&demand_code=

Back to top

What is the Difference Between Detected and Declared Domain?

Whatever is passed through on the domain/url macro is the Declared Domain. SpringServe also has domain detection, which is initiated 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.

When creating domain lists for targeting, use declared domain. If you are using Detected Domain overrides on your supply tags, the detected domain must pass demand tag targeting in order to be passed to demand tags on the waterfall.

Back to top

What are Unclassified Domains and How do I Deal with Them?

Unclassified domains are those which have low request volume (under 15 requests per hour) but no impressions. These requests do come in and have a chance to be monetized, but at the end of each hour they are compiled into "unclassified" in order for reporting to deal with these long tailsOne way to deal with these domains is to talk to your supply partners about the quality of the inventory that they're sending to you. You may want to implement a whitelist in order to reduce the number of long-tail domains. You do have the option of running an hourly domain report at the beginning of the hour before domains have been bucketed into unclassified. This will show you domains that have low volume and no impressions for the last hour.

Note that a domain can be unclassified one hour and not unclassified the next. Consider the case where you have 10 requests and no impressions from lowquality.com in the hour between 12 and 1; it will be unclassified. In the next hour, lowquality.com gets 10 requests and 1 impression; it will appear in your domain report as lowquality.com. The 10 requests from the noon hour remain unclassified. For this reason, it is not necessarily best practice to black list domains that get unclassified. They could start out with low volume and no fill and become better performers in the subsequent hours.

Back to top

Can I Run a Domain Report for a Period Longer than the Last 7 Days?

Yes. SpringServe keeps domain data for 100 days, so you should be able to pull very large reports with a little patience and by making sure to use UTC as the timezone and the custom timeframe setting. We recommend running domain reports on a regular basis if you foresee the need for historical domain data.

Back to top

Can I Run a Report by Both Domain and Country?

Yes; this data is maintained for the last two days. If you foresee needing data beyond this period, create a scheduled report to keep for your archives. Countries are grouped into 9 regions. Mappings can be found here: continent_country_codes.csv

Back to top

Implementation

How do I make a Mobile tag? 

You can make Mobile Web and In-App tags in SpringServe. In the settings tab of your Supply Tag, select your desired environment. Mobile Web and In-App tags are JS VPAID enabled by default. The tag can be made VPAID none by expanding the Advanced section and selecting None in the VPAID Enabled pillbox. Assign Demand tags of type JS VPAID or VAST Only to your mobile tag. Note that you should implement some sort of targeting on your mobile supply tag - we suggest using whitelist, device and geo targeting. 

Back to top

How do I Create a Secure Tag?

SpringServe supply tags are secure by default. Changing https to http in the export tag will make the tag non-secure. Make sure you have secure demand tags attached to the supply tag. You can duplicate a demand tag and change the endpoint URL to be secure - this way you will have a secure and a non-secure copy of the demand tag. Confirm with your demand partner that their adserver supports secure tags. 

Back to top

What does Optimization do?

Enabling Optimization will turn on auto-optimization for your supply tag. 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. For more information on optimization, click here.

Back to top

How do I change the status of a tag?

 You can change the status of a Supply or Demand tag in one of two ways:

  • In the settings tab, toggle to Active/Inactive in the Status field
  • On the Supply/Demand page, click on the red or green icon in the Active column

Back to top

Why Should I Set a Custom Demand Tag Timeout?

The default timeout for a demand tag is 20 seconds. If you see that on average a demand tag is responding slower than 20 seconds, you may want to set a custom timeout in order to give more chances to tags down the waterfall. If a demand tag routinely produces the majority of its demand within 14 seconds, you can lop off those last 6 seconds with little degradation to the demand tag but increased demand opportunities down fall. The distribution graphs shown on the supply tag waterfall page and the demand tag settings page can help you decide what to set your timeout to.

You may find that a demand tag responds quickly in the waterfall for one supply tag and more slowly for another. In this case, you can duplicate that demand tag and set different custom timeouts and assign the tags to the corresponding supply.

Back to top

What Macros Should I Use?

See which macros SpringServe supports here. Default macros for desktop supply tags are Width, Height, Domain, and Cachebuster. If your demand partner requires specific macros to be passed, make sure that they are in both the supply and the demand tag. To add macros to your supply tag, on the Export Tag tab check the box next to the macro name and it will appear in the tag URL; export the tag with the added macros and ensure that the player is passing the correct information.

Back to top 

How Do I Add Domain List Targeting?

You can apply domain list targeting in two ways:

On the Domain List page:

Create your domain list in Settings → Domain lists. You can add new domains to the text box (comma or newline separated) or you can upload a csv file with your domains. In the Supply tab of your new domain list, you will see all of your Supply Tags. Mark the box in the first column to apply the domain list to the tag. In the last column, select Black List or White List. The same procedure is used for the Demand tags in the Demand tab.

On the Targeting tab for your tag:

You can also apply domain list targeting on the Targeting tab of Supply and Demand tags, you can select White List or Black List and a Domain Lists box will pop up. Enter the name or ID of the domain list. 

Note that a tag cannot have both a Black List and a White List. However, you can apply as many domain lists as you like to a single tag.

Back to top

Troubleshooting

Why do I Have Zero Opportunities When I Have Requests?

Your supply partner may be implementing the tag incorrectly. Ask them to send you an example of the tag as it is implemented in their system. If they send you something that does not have the macros populated with actual values, you may not see any opportunities. It is also possible that there could be a player compatibility issue. Ask your supply partner if they can tell you what player is being used.

Back to top

Why do I Have Low Opportunities Relative to Requests?

You may be low on your Supply Partner's waterfall. Talk to them to see how you can get to a higher priority. This may entail being put on a whitelist and/or having a request cap.

Back to top

Why aren't My Supply Tag Requests Turning into Demand Tag Requests?

Note that there is a difference between Supply Tag Requests and Demand Tag Ad Requests. Ad requests are defined as the number of times a demand tag receives a request. This can only happen after there is a Supply Tag opportunity and we start going through the waterfall.

To bring up your number of ad requests for a demand tag, you would need to raise the opportunity rate for its supply tags. Low opportunity rates mean that your tag is low on the waterfall, and you should speak with your supply partners about how you can be moved up the waterfall.

Eliminating Missed Opportunities will also help increase Ad Requests. Find out how to take care of Missed Opportunities on our Create Reports Best Practices page.  

Why is My Demand Tag Not Filling?

You may have conflicting targeting with your Demand partners. If you are getting empty VAST responses, this is likely the case. Run a report by demand tag and include Ads in the metrics. The Ads column shows the number of times that the demand tag returns a non-empty VAST response. If this number is low relative to Ad Requests, talk to your demand parters to see what you need to do to get the tag to return a non-empty VAST response.

Back to top

Where did my tags go?

The default view on the Supply and Demand pages is Active, so if your tag is inactive, it will not show up in this view. Select Any Status or Inactive from the dropdown list to find your inactive tag.

Back to top

Why am I blocking requests when there is no targeting on my supply tag?

Check your basic settings for your account by going to Settings > Basic Settings. You will see that you are blocking unknown domains and/or countries. 

Why do I still have IVT imps when I have pre-bid blocking enabled?

Pre-bid does not guarantee that no IVT impressions will be served. It uses the information that it has upon request, then makes its assessment. If it passes pre-bid it is possible for it to be determined to be IVT after the impression, when the algorithm has much more information to analyze.

Back to top

API

What are the rate limits for API requests?

domain report requests – 3 requests per minute
non-domain report requests – 10 requests per minute
other requests – 240 requests per minute

Back to top

  • No labels