Overview

Customers can utilize Advanced Filtering to filter incoming traffic on User IDs (Cookie, Device ID, Liveramp IDL, IP addresses, and Customer ID). This feature allows you to further customize the volume and nature of bid requests coming through to your bidder.

User ID Filtering

There are two options for filtering on User IDs:

1. Realtime User Filtering (RUF): This filters traffic based on all 1st party segments for a customer. Traffic is filtered as soon as the user is added to a segment. This is ideal for retargeting use cases. RUF uses the following IDs to search for 1st party segments:
   • Cookie IDs (BITO)
   • Device ID (MAIDs)
   • RampID
   • IP Address
   • Customer ID

   Also, you can enable cross-device amplification on your RUF inventory that is supported with FreeWheel ID Network, Tapad, and LiveRamp. Reach out to your CSM to activate this feature.
   
   

2. Segment Filtering: This filters traffic based on specific segments (1st or 3rd party) and can be used to include or exclude users. Segments are updated asynchronously and not updated in realtime for filtering, so this is not ideal for retargeting use cases.

Please note, deactivating a 1st party segment in Buzz UI does not delete users from the segment and subsequently, remove them from traffic filtering.

Additionally, Beeswax supports filtering of QPS based on lists, either include or exclude. Upon adding new list items in Buzz to the desired list on which filtering is already set, we will begin sending traffic from the item if it is included in an INCLUDE list and halt sending traffic if it is included in an EXCLUDE list.

Please note that regardless of your QPS filtering, you should ALWAYS use the line item to target exactly what you want to bid against. While our QPS filtering is very robust, it is not designed to act as targeting. For example, if you want to exclude domains from targeting, you should do you on your line item in addition to QPS filtering.