When filtering RTB traffic to a Beeswax custom bidder we have available a similar, but slightly different, list of criteria from the List of Targeting Modules and Keys.
Size of ads to filter, passed as a string in the format "WxH"
The type of line_item expected in this placement (0=banner, 1=video, 2=native ).
IAB categories from OpenRTB
Content rating types according to OpenRTB 6.18
Language of site on which ad is shown. Lookup based on ISO 639-1.
Validated against ISO 3166-1 alpha-3
IDs based on MaxMind database which is based on Geonames. The IDs can be found in the Cities view.
Whether the user's latitude and longitude are present on the request. Note, this does not actually target the user's location, just filters impressions where the data is present.
Region in format
Validated against DMA table, based on Google's metro codes, which are similar to Nielsen DMAs
5 or more characters
Enum lookup from OpenRTB 5.4
Deal ID in the format
List of sources, eg. 1=”Rubicon”
Whether the impression is an interstitial, passed as a boolean
Site names in form
List of Sites defined in the customer's Buzz instance
ID in the form
List of Placements defined in the customer's Buzz instance
List of IP Addresses defined in the customer's Buzz instance
Browser name as a string.
Browser version to target, most typically to exclude. Most commonly, you will want to include a browser and exclude one or more browser_versions. If you exclude a browser, but include browser_versions, nothing will serve.
List of mobile carriers by name.
Device type id as described in OpenRTB section 6.16.
Device make as a string.
Device model as a string, including version number. Note OpenRTB keeps the model and the version as separate fields.
Device screen size. Valid values are "S", "M", "L", "XL", and "NA"
Specific OS versions identified by strings such as
Specific version of OSes such as
Whether a user identifier is present, false=not present, true=present
Only match users that are in segment or more user segments in the Buzz instance
Count in minutes from Sunday at midnight (0) to Saturday at 11:59 (10079) in range format
Codes from 1-4 based on OpenRTB 6.6. Example 1= Auto-play with sound on.
Small, medium, or large.
Codes from -2 to 0 based on OpenRTB 6.9. Buzz does not support an exact offset in seconds.
Whether the video is in-stream (1) or in-banner (0).
The video API indicated in the auction request. Note, even though this field is called "video" it includes data for MRAID. This is how it is defined in the OpenRTB protocol.
Different targeting modules can support different "verbs" in targeting. The table below describes the verbs:
Updated almost 2 years ago