RTB Demand Management Test

If a DSP's timeout rate is above 4%, it suggests that there is a high percentage of requests that are not being responded to within the specified time limit. This could indicate issues with the DSP's performance or capacity to handle incoming requests. To address this problem, it is recommended to reach out to the DSP for troubleshooting and potential improvements in their system.

The term "advertiser_id=2" refers to an unidentified advertiser. This means that the advertiser's name or URL is not provided or known. It could be a new or unrecognized advertiser, hence classified as an unknown advertiser.

The timeout threshold refers to the maximum amount of time that a system or application will wait for a response before considering it as a timeout. In this case, the correct answer is 100ms, indicating that if a response takes longer than 100ms to be received, it will be considered as a timeout. This suggests that the system or application expects relatively quick responses and has a low tolerance for delays.

Sam Tingleff is the Engineering lead for RTB.

The field that is NOT a part of the bid request is the "floor CPM." The bid request typically includes information such as the IP address, ad size, site name, and site ID. The floor CPM refers to the minimum price that an advertiser is willing to pay for an ad impression, but it is not a field included in the bid request.

Appnexus is the correct answer because it is a demand-side platform (DSP) that does not support deal ID. A deal ID is a unique identifier for programmatic advertising deals between buyers and sellers, allowing them to transact specific inventory at pre-negotiated terms. While Turn, Invite, and Media Math are all DSPs that support deal ID, Appnexus does not offer this feature.

The insights that should be provided to the DSP on a regular basis include information about blocked advertisers by site, QPS levels, sites the DSP isn't spending on, and sites other DSPs are spending on that your DSP isn't spending as much on. These insights help the DSP to optimize its advertising strategy, identify potential issues or opportunities, and make informed decisions about where to allocate spending.

The bid engine logs contain the fields size_id, ip_address, and bid_id. These fields provide information about the size of the bid, the IP address from which the bid was made, and the unique identifier for the bid. Other fields like income and zip_code are not available in the bid engine logs.

DataXu does not support buyer ID. This means that when using DataXu as a DSP (Demand Side Platform), buyers cannot utilize buyer ID functionality. Buyer ID is a feature that allows advertisers to track and identify specific buyers or users across different platforms and devices. However, DataXu does not provide this capability, unlike Appnexus and Turn, which do support buyer ID.

Brandscreen is the DSP that participates in multi-bid response.

Metrics in Microstrategy are quantitative measurements used to analyze and evaluate data. In this case, the metrics mentioned are average bid (weighted), bid rev, and min bid.

- Average bid (weighted) refers to the average value of bids, taking into account their respective weights or importance.
- Bid rev represents the revenue generated from bids.
- Min bid indicates the minimum value of bids.

These metrics provide insights into the bidding process, allowing users to understand the average value, revenue, and minimum value associated with bids.

The data that is NOT available in Microstrategy is the ad engine data.

The correct answer is 350-400k. This suggests that on average, we observe a daily spend of between 350,000 and 400,000 units of currency in the context of RTB (Real-Time Bidding).

Buyers participating in private marketplaces can benefit from preferential pricing based on their spend commitments. This means that the more a buyer spends, the better pricing they can negotiate. Additionally, private marketplaces offer demand floors, which ensure that buyers have access to inventory at a minimum bid price. This allows buyers to secure inventory at a specific price point. Private marketplaces also provide the opportunity for buyers to receive guaranteed impressions that are not usually available in the open RTB marketplace. This ensures that buyers can reach their desired audience effectively. Furthermore, private marketplaces offer more even delivery of these guaranteed impressions, providing a more balanced distribution over time.

The ad engine logs contain information about various fields such as account_id, network_id, rtb_seat_id, rtb_second_price, and size_id. These fields provide important details related to the ad campaigns, including the account associated with the ad, the network where the ad was displayed, the seat ID for real-time bidding, the second price for real-time bidding, and the size ID of the ad. These fields help in analyzing and optimizing the performance of the ad campaigns.

Attributes in Microstrategy are the characteristics or dimensions that define the data being analyzed. They provide additional context and details to the data and are used to group, filter, and analyze the data in various ways. In this case, the attributes mentioned - network, advertiser, date, site, and zone - are likely the dimensions or characteristics of the data being analyzed in a Microstrategy project. These attributes can be used to segment and analyze the data based on different networks, advertisers, dates, sites, and zones.