Mastering MySQL Database Architecture: Deep Dive into MySQL Shell and MySQL R...
RTB-D support training
1. RTB-D – RM Support Training
Architecture, Reports, Client Issue
Resolution Plan, and YM Setup Review
RM Internal Only
2.
3. Essential Links
• IDs for RTB buyers, and on-boarding progress/status
– US: http://twiki.corp.yahoo.com/view/Apex/3PIBetaOnboardingPage
– EMEA: http://twiki.corp.yahoo.com/view/YsmEu/EmeaRtb
• XAF: https://xaf.data.yahoo.com:9999/xaf/en-US/index.php#
• Ad Server Charts (requires socks proxy setup):
– [deprecated]http://graph10.rm.ac4.yahoo.com:9999/perl/autoview.cgi?view=BidGateway+%2
83pi%29+Statistics+%28by+tparty%29&graphcolo=bf1&time=7d&width=500&height=300&m
ax=&grep=&grepnot=&limit=&legend=on×tart=×top=&tz=US%2FEaster
– YAMAS [New Chart system, charts are pretty much the same] -
http://yms.ops.yahoo.com/ngd/ygrapher/dashboard?dashboard=RTBD_BidGateway_3rdparty
– Chart showing RTB Wins in near real-time -
http://yms.ops.yahoo.com/ngd/ygrapher/dashboard?dashboard=NGD.adserver_auction
• Cookie Mapping
– Temp - http://twiki.corp.yahoo.com/view/ChinaRDC/2013-02-02
• RTB-D Documentation in the KB: https://kb.yieldmanager.com/category.php?id=81
• Interpreting debug log:
http://twiki.corp.yahoo.com/view/NgdExchangeServing/RTBD_Log_Investigation
4. IDs for RTB-D
• The mA ID from the buying seat is key to most
tables & settings for RTB-D. In some places it is
pre-pended with 10000.
5. Yield Manager Reports
• Profit Report
– Authoritative impression (win) numbers. Should
be used for discrepancy comparison with bidder.
• Analytics Report
– Can easily see who is buying via RTB-D
• Though I believe we saw one bug with that
16. XAF
• Most used fields: Eligible, Total, Bid Request, Throttle,
Error, Response OK, Bid, Win (Impressions)
• Calculated fields: Bid/Request, Win/Bid, Bid eCPM
• I prefer to use “raw data” from XAF, and derive
calculated fields in Excel
• Be wary of differences between RTB traffic hosted in
XAF Reports
• XAF RTB Glossary:
http://twiki.corp.yahoo.com/view/XAF/RTBGlossary
17.
18.
19.
20. QPS Caps Settings
• There is no precendence for these rule. A given bid request must
satisfy all rules to be sent out by the Bid Bateway.
• trf_prod.rtbd_adv_qps (set_by=“thirdparty”) - Bidder Set QPS per
Colo, per Adv ID
• trf_prod.rtbd_techprovider_qps - MarketSol Set QPS Cap per Colo,
per Tech Provider
– Controlled by MarketSol in the UI, client tells us what they want
• trf_prod.rtbd_adv_qps (set_by=“admin”) MarketSol controlled
System Protection QPS Cap per colo, per Adv ID
– Set using a script on Bgway box, mainly used to control qps during on
boarding, and to reduce it during emergencies
• SE controlled QPS Cap per Colo, per Adv Id
– Set using a config file, only used in emergencies. Normally not applied
(unlimited QPS permitted).
21. QPS Arithmetic
1 billion bid requests 1,000,000,000 per day Seconds per day: 86,400
10k QPS Avg 11,574 per second
10k QPS Peak 27,778 Peak factor: 2.4
• The relationship between total bid requests per day, and Average
QPS for that day, is simply 86k, the number of seconds in a day
• The Peak Factor is the relationship between the average and peak
QPS. It will be different for different kinds of publisher content,
but as a rough guide we can use the number across different
supply.
• The Peak Factor allows you to convert between average and peak
qps (as an estimate). To estimate bidder capacity QPS, multiply it
by the average QPS on a high inventory day for a given bidder.
Remember to include throttling (if any) into the average QPS, as
that is part of the available inventory (which we don’t send due to
throttling).
32. Refer to this twiki for enable_rtbs/d flags: http://twiki.corp.yahoo.com/view/RightMediaExchange/ApiRealTimeBidding#Schema_changes
http://twiki.corp.yahoo.com/view/NgdExchangeServing/RTBD_flags
RM Object RTB-D RTB-S
Universal Targeting
Adv. Creative is_3pi in bit_flags (or “is_rtb” in bit_flags)
Adv. Campaign is_3pi in bit_flags
Adv. Line Item is_3pi in bit_flags enable_rtbs
Adv. Insertion Order
Buyer Advertiser is_3pi in allow_bits (not essential) enable_rtbs
Seat is_3pi in allow_bits (not essential) enable_rtbs
Linked Publisher
Linked Publisher IO
Linked Line Item
Linked Pub. Line Item
Linked Adv. Line Item enable_rtbd enable_rtbs
Linked Advertiser IO
Linked Advertiser
Seat
Seller Publisher enable_rtbd in allow_bits
Publisher IO default_enable_rtbd=1 (optional, convenience only)
Publisher LI enable_rtbd in bit_flags is_rtbs
Section
Universal Targeting
Hinweis der Redaktion
Regions At the very top you can select colo (region)PartnersThe case-sensitivegrep and grepnot fields can be used to filter which partners to report on. For non-configured partner names, the RTB Advertiser ID will be shown. DatesI use the time field, with something like 7d, which means 3 days back.Percent chartsFor each chart documented below, there is also a corresponding percent chart (where applicable). Eg. you can see timouts as a percent of all requests send to the bidder.
Third Party RequestsThe number of bid requests that went out to the bidderThird Party Latency AverageThe average time from request sent to response received, only for those responses received within the timeout window.Third Party Response NoBidThe number of responses that came back as a NoBid, meaning the bidder chooses not to offer to buy the impression at any cost.Third Party Response OKThe number of responses that came back and were processed by our BidGateway system without error. This includes both bids and NoBid responses.
Third Party Response TimeoutNumber of bid requests we sent for which we did not receive a response before the timeout window period.Third Party Response ZeroBidThe number of responses that came back with $0 as the bid amount, meaning the bidder chooses to offer to buy the impression at no cost. This is essentially the same as NoBid.Third Party Response Size AverageAverage response size in Kb (normally shows in 1/1000s of Kb, with an m for milli(Kb) after the number on the left axis). Note: there is a bug causing this to always be empty for bundled responses.Third Party Response NoAdBlobThe number of responses that were a bid, but did not include an AdBlob (creative). This outcome is an error in the response.
Responses ThrottledThe number of impressions which passed targeting, and were send from the AdServer to the BidGateway, but were not sent on to the bidder due to either the client set or admin set QPS cap (see QPS Cap slide).Third Party Missing MetadataThe number of impressions which passed targeting, and were send from the AdServer to the BidGateway, but were not sent on to the bidder due to missing BidGateway configuration for this bidder (bidder url, QPS, or mangling key).Third Party Transport ErrorThe number of bid requests that resulted in a network error, eg. host cannot be reached, connection lost, etc.Third Party XML ErrorThe number of bid requests that received a response we could not interpret, eg. missing fields, wrong signature, etc.
In this flow, the goal is be on the top left. Assuming there is some issue, we can methodically move away from the top left to narrow down the issue, and see what to investigate, and how to resolve. That is the theoretical approach. In practice, I always begin by quickly scanning the AdServer charts to get a quick review of the technical integration, then if needed I confirm impressions won in profit report, and finally, if needed seek further detail in XAF.
