2-Factor Authentication (2FA)
Forcing 2FA on your account will require all admin and ad-ops users to enable 2FA on their accounts. Once 2FA has been forced on the account, users will receive an email informing them to enable 2FA. They will have seven days to enable 2FA before it will automatically be enabled for them. If they have not enabled 2FA by this time, they will need to contact email@example.com to allow them to log in before setting it up.
Set the contact information that SpringServe partners will see on the DirectConnect page. You can upload your company icon as well. We recommend uploading a 240x240 pixel file.
Set the time zone for your account. Any new user that you create in your SpringServe account will have the account time zone by default. Dashboards, reports, and quickstats summaries will be shown in your user time zone.
Enable your supply tags for Tag Health. If enabled, define what it means to have poor tag health. You can prevent your demand partners from buying flagged supply by updating the Buy Flagged Supply field on the settings tab of a demand partner. If a demand partner is disabled from buying flagged supply, then requests from supply tags that have been flagged for poor tag health will not be passed to that partner's demand tags.
Defining Tag Health
A variety of metrics are available to choose from, including fill rate, IVT, and viewability rates from various data partners. Tag health logic uses groups. When you enable tag health, you can select multiple criteria that all need to be satisfied by using the "+Tag Health Metric" button inside a group, or you can various select criteria that could be satisfied by using the "+Tag Health Group" button.
For example, if Group 1 contains the criteria Moat Bot Rate ≥ 20% and Request Fill ≤ 5%, then supply tags that have a request fill below 5% and a Moat Bot Rate above 20% will be flagged.
If Group 1 contains the criteria Moat Bot Rate ≥ 20% and Group 2 contains the criteria IAS IVT Rate ≥ 20%, then supply tags that meet either of these criteria will be flagged.
To remove the tag health flag, SpringServe must see clean traffic at volume. To reach the required volume, you may need to increase the post-imp sampling rate if you are using a data vendor metric. In order for a tag to be unflagged, it needs to have 500 decisions and not meet the poor health criteria for the last 24 hours.
SpringServe supply tag optimization reprioritizes the waterfall depending on the Optimization parameters - the metric and lookback minutes. SpringServe default optimization parameters are request fill and 60 minute lookback window. Based on these parameters, a demand tag will be prioritized according to its fill rate over the last 60 minutes.
There is not a one size fits all set of parameters for optimization. We have added the ability to set custom optimization parameters on the account level. If you would like to set custom Optimization defaults, toggle to Custom and set your desired metrics.
Note that any changes made to Optimization Defaults 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, you can use bulk actions on the Supply Tags tab in the UI or use the API.
If your account is enabled for Programmatic Connect, you can decide if new supply will be enabled for Open Market demand by default. You can also set your desired IVT Filtering and Detection settings for new supply tags and connected supply.
Demand Defaults show options for IVT filtering and detection. These settings will apply to any new demand tag that is created going forward.
Options for Buy Flagged Supply and Default Tiers apply to new demand partners. When Buying Flagged Supply is disabled, requests will not be passed to the demand if they are coming from a flagged supply tag. The Default Tier can be set for managed and DC demand partners; select from First Look (1L) and tiers 1 through 5. Note that if the Default Tier is 1L, non-Header Bidding demand tags will be added to DC waterfalls at tier 1.
If you have Event Pixels that you want to fire on all your demand, add them in the Pixels section.
Set your preferences to allow or block any requests from unknown domains, apps, IP addresses, device IDs, and countries. You can also apply global blacklists.
This targeting will apply to all supply tag requests in your account. These blocked requests will be included in the Blocked (Targeting) column in reporting.