Use * syntax for faster search
Page History
| Column | |||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||
|
...
Overview
| Multiexcerpt | ||
|---|---|---|
|
...
This page details user targeting keys and recommendations |
...
for segment targeting. For information on how to properly filter and favorite while searching segments, see Segment Filtering and Favorites. |
Segments can be searched by name, segment key or alternative id. Once you’ve found the desired segment, information including user count and CPM will be displayed (where applicable).
| Targeting Key | Description | Recommendation |
| Segment | Segments are typically user segments (cookies, MAIDs, IP addresses), which can either be your 1st party user segments or 3rd party user segments from data providers like Oracle or Liveramp. Segments can also be custom values that are added by your Data Augmentor. Targeting user segments or custom segments added by your augmentor work in the same fashion. By default, if you target multiple segments by INCLUDE they will be OR'd together. However, you can force AND statements by using REQUIRE or writing custom boolean Logic in the advanced targeting section. Read more about the targeting verbs here. | Use INCLUDE, EXCLUDE, or REQUIRE targeting. |
| User ID | User IDs can either be web cookies or mobile device IDs. This field allows you to target those auctions that have a User ID present or not present. Note: When excluding User ID Present to target users without an ID, Targeting will match bid requests the do not carry an ID. However, in situations where a user does have a Beeswax cookie but this user has not yet been synced with the exchange in question, our reporting will populate the user ID that came through on the impression notification. | Use INCLUDE or EXCLUDE targeting |
| IP Range | A range of valid IPV4 addresses. Alternatively, use IP segments as detailed here. | Use INCLUDE or EXCLUDE targeting |
...