QPS Management Best Practices
Beeswax deploys a custom bidder per customer and prefilters traffic to each individual bidder instance. Because Beeswax can control the volume of traffic sent to your bidder, we can charge a flat monthly fee. This traffic prefiltering is controlled by your Beeswax account manager at your direction. The management of traffic is critical to ensuring your campaigns scale and deliver.
What is QPS?
QPS, or Queries Per Second, refers to the number of auctions that are filtered to your Beeswax custom bidder. Beeswax charges a flat monthly fee per QPS tier.
How do I translate QPS into impressions?
The simple answer is you can turn QPS into the number of daily eligible auctions by multiplying by 86,400 (60 sec * 60 min * 24 hours). So our 10,000 QPS tier gives you 864 million auctions per day. The number of impressions delivered is entirely up to you -- based on your bidding strategy, bid prices, and demand. For example, if you have a high CPM strategy and expect to win 10% of all your auctions, your 864 million daily auctions would yield 86.4 million impressions won.
Where does the QPS come from?
Beeswax is integrated with all of the top RTB exchanges and listens to millions of QPS via 4 AWS data centers:
- US-WEST-2 (Some exchanges route western N.A. based traffic via this data center)
- EU-WEST-1 (Europe, Middle East, and Africa)
- AP-NORTHEAST-1 (Asia-Pacific)
Basic QPS Filtering Options
Customers can filter QPS on almost any targetable keys/values. Some common examples are:
|Ad Sizes||Geos (Country, City, Region, Zip)|
|Content Categories||Placement Types|
|Environment Types (App or Site)||Platforms: Device Make, Operating System, etc.|
Advanced QPS Filtering Options
For an additional monthly fee, customers can utilize Beeswax's Advanced QPS Filtering capabilities:
- Filter QPS by user data provided by customer (Cookies, Device IDs, or IPs)
- Filter QPS by custom lists (Blacklist or Whitelist):
- App Bundles
- Zip Codes
- Placement IDs
QPS Management Best Practices
Your Beeswax Account Manager controls the QPS you receive by creating multiple traffic templates that use OR boolean logic. You can create any number of traffic templates to meet your QPS requirements, but it’s highly recommended to keep the number under 10 for ease of ongoing management. Below are some best practices:
- Create separate QPS templates for broad targeting keys:
- Placement Types
- Utilize Advanced Filtering for Lists and User IDs
- Utilize Ads.txt for web-based QPS templates
- Exclude content categories, content ratings, ad sizes, and other key-values that you might normally exclude for all of your campaigns
Example QPS Traffic Templates
|Template ID||% of Available Traffic||Placement Type||Country||Environment||Operating System||Estimated QPS|
Traffic templates look like the below
Beeswax customers can monitor QPS via Monitoring and Metamarkets under the "Tools" tab in the Beeswax UI: