App Targeting in SpringServe

In this release, we discuss native targeting for app names and app bundles, updates to Header Bidding, 2-factor authentication, and UI improvements.

Core Improvements

App Targeting & Reporting

We have released our native support for app name and app bundle targeting. You can now create and manage app name and bundle lists with the same ease as domain lists. App names and bundles must be passed correctly through the app_name and app_bundle query string parameters in order for app targeting to function properly. Management of app targeting starts from the settings menu:

From Basic Settings, you can set your account level targeting of allowing or blocking unknown app names.

List Management

App name and app bundle lists can be managed in the same way as your domain lists. App names or bundles can be added by manually entering names or by uploading a csv file. You can also specify match logic for your app lists. Due to the nature of app names, you may want to use partial match logic for these lists.

In the example above, when you use this app list to target you can match any app name that contains “batman”, “joker”, or “robin”. That is, “batman is the best”, “batman’s app”, “get the joker” will all be targeted when this list is used.

Applying Targeting

App Name and Bundle list targeting will appear in the Base Targeting section of the Targeting tab of your In-App or CTV tags, as well as your partners and campaigns. Select the White or Black List and choose the desired list to target.

If you were using a domain list or custom key-values for app targeting, we encourage you to transition to native app name and bundle lists. The quickest way to remove a domain list from in-app and CTV tags is to go to the Supply and Demand tabs of a domain list and filter by environment.

If you have been using custom key-value lists for app targeting, please send an email to your account manager with your account ID, and the key id(s) for app name and/or bundle and we can automate the list replacement process.

App targeting can also be managed in the API. Please see our wiki for more information about managing your app name and app bundle lists.

App Reporting

You may want to use app name and app bundle reporting to optimize and create your app name and bundle lists. These dimensions are now available to you in the main reporting page.

Filters are also available for both app name and app bundle. As with domain reports, you can run Geo & App reports for the last 48 hours. Countries are grouped into 12 high traffic groups. App data is maintained for 100 days; we therefore recommend running and saving monthly reports if you foresee a need for this data in future.

Header Bidding

Optional Parameters

You can now add optional and custom parameters to your AppNexus and SpotX header bidding demand tags. Once this feature is enabled on your account, you can add these additional parameters under “Bid Parameters” –> “Optional Parameters” on the demand tag Settings tab.

To enable your account for optional header bidding parameters, please reach out to your SpringServe account representative.

For more information on how to implement these new parameters, please reference our wiki.


SpringServe has built support for Rubicon header bidding, adding to the growing list of header bidding platforms our demand tags allow. You can select “Rubicon” from the “Platform” drop-down on header bidding demand tag settings to enable a demand tag for Rubicon header bidding.

Rubicon requires a handful of parameters for header bidding request which are to be inputted into the demand tag settings. These include Account ID, Site ID, Zone ID, and Size ID.

These ids can usually be found within the url of your Rubicon tag, or within the Rubicon UI. For more information on implementing Rubicon header bidding demand tags, please see the SpringServe wiki.

Feature Additions

2-Factor Authentication

You can now enable 2-Factor Authentication (2FA) on your SpringServe account, adding another layer of security. To enable, go Edit Profile in the User menu.

On this page, you can use the pillbox to enable 2FA. You will need to download a 2FA application such as Google Authenticator to complete the process. If your account is enabled for 2FA, you will need to enter the 6-digit code that appears in your 2FA application in addition to your password when logging in.

If you lose your 2FA device, please contact and we can reset your account.

UI Improvements

Supply Tag RPM Floor Rate

When adding supply to a demand tag, you will now see the supply tag RPM floor in the add supply modal. By default, supply is filtered by the maximum RPM floor = the demand tag’s RPM. Supply with RPM floors above the demand tag’s rate will be shown in red. This visual indicator should help you to align your demand to supply and make your desired margins.

RPM Floor rate is also now shown on the supply tags table on the supply tab of a demand tag.

Label Filters

Filters are now available on the supply and demand tabs of a label. This addition will make it easier to find tags when associating them to labels.


Traffic Quality Sunset

The Traffic Quality report will be discontinued. You can access Moat metrics on the main reporting page in the IVT and Quality Metrics sections. If you have any questions or concerns, please email

SpringServe in ads.txt

SpringServe fully supports the IAB’s ads.txt initiative and its goal of increasing industry-wide transparency between buyers and sellers. With increasing adoption of the ads.txt initiative by a number of buying and selling platforms, we encourage all SpringServe clients to implement ads.txt on their domains and any domains with whom they work.

We have included instructions about how to add SpringServe to an ads.txt file below:

Owned and Operated Domains, {{ACCOUNT_ID}}, DIRECT, a24eb641fc82e93d

Resellers, {{ACCOUNT_ID}}, RESELLER, a24eb641fc82e93d

Replace {{ACCOUNT_ID}} with your SpringServe Account ID; this ID can be found in the lower right hand corner of the browser when you are logged into your SpringServe account. In the example below, CrushTown USA has Account ID 17.

Leave a Reply

Your email address will not be published. Required fields are marked *