...
Dimension | API Representation | Notes |
---|---|---|
Publisher Name |
| Name of the publisher |
Site |
| Collection of placements that often correspond to a website or application. Example: "Cats.com" |
Primary Domain |
| The primary domain associated with the incoming web request. |
Notable Domain |
| The notable domain associated with the incoming web request. Example: “www.cats.com” |
Country |
| Two or three letter code abbreviation for the country. Example: "US" |
Placement Name |
| Name given to the placement or ad slot. |
Placement Key |
| Integration key associated with incoming request. Example: "bQRKnWWz6KnFqsGmttQmCoGP" |
Device Type |
| Possible values for filtering are:
|
Date |
| Date which the impression was first requested. Example: "2020-08-10" |
Hour |
| Hour an impression was requested. Possible values 1-24. |
Supply Integration |
| The name of the supply integration path to filter by. There are many possible values to supply as filters for this property. Below is a partial list of examples:
|
Type |
| The type of the site (i.e. app or web). Possible values are
|
App Bundle ID |
| The bundle ID for a given app. This is a string whose format varies across providers (e.g. “com.something.else” for Android, “1234567” for iOS, etc.) |
OS Type |
| The operating system of the user, as determined by user agent. Possible values are
|
Placement Size |
| Size of the placement when set up by STR (display only placements) |
Adelaide AU Group |
| Attention Score provided by Adelaide that Use this field to break out results by Adelaide Attention Score. Attention Score can take the values of “High”, “Medium”, or “Low”. Note: not available when |
Adverifai Score Bucket |
| Use this field to break out results by Adverifai’s score bucket. Score buckets are basically score ranges that increment by 0.05 and go from 0 to 1. So, for example, one site might have a score of 0.15, while another might be 0.22. These two entries would be broken out into separate buckets. |
Advertiser Root Domain |
| Use this field to break out results as Advertiser name coming from the DSP and set up in the DSP. Note: not available when |
Jounce Directness |
| Use this field to break out results by directness as defined by Jounce. Possible values are
|
Jounce SPO Segment |
| Use this field to break out results by SPO Segment as defined by Jounce. Possible values are
The value is [not_in_jounce_table] when the combination of Publisher Key, Bundle ID App Only and Primary Domain is not classified by Jounce |
Open vs Deal |
| Use this field to break out results by whether they are “open” or a “deal”. Open means that the advertiser served impression on STX without targeting a deal. Deal means that the advertiser served impression on STX by targeting a deal. Note: not available when |
Fields
The table below describes the header bidding metrics that can be accessed through the API: At least one field is required in the request:
...