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.
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 you have Event Pixels that you want to fire on all your demand, add them in the Pixels section.
Variable macros allow you to define macros that will be replaced universally in your account.
You can set your desired IVT Filtering and Detection settings for new supply tags and connected supply. If your account is enabled for Programmatic Connect and/or SpotX Connect, you can decide if new supply will be enabled for Open Market these demand sources by default. You Defaults for additional supply tag settings can be set as well, including Environment, RPM Floor margin default, and Waterfall Management. If your default Environment is CTV, you can also set your desired IVT Filtering and Detection settings for new supply tags and connected supplypod defaults.
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 as well as SpotX Connect; 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 section10.
Guard rails apply to new objects in your account, allowing you to be cautious when creating new demand objects so they don't result in an unexpected overspend.
Set the status of new and duplicated Demand tags in the New Object Status panel. You can also add budgets that will be included when a new demand tag or campaign is created.
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.