ติดตั้ง Steam
เข้าสู่ระบบ
|
ภาษา
简体中文 (จีนตัวย่อ)
繁體中文 (จีนตัวเต็ม)
日本語 (ญี่ปุ่น)
한국어 (เกาหลี)
български (บัลแกเรีย)
Čeština (เช็ก)
Dansk (เดนมาร์ก)
Deutsch (เยอรมัน)
English (อังกฤษ)
Español - España (สเปน)
Español - Latinoamérica (สเปน - ลาตินอเมริกา)
Ελληνικά (กรีก)
Français (ฝรั่งเศส)
Italiano (อิตาลี)
Bahasa Indonesia (อินโดนีเซีย)
Magyar (ฮังการี)
Nederlands (ดัตช์)
Norsk (นอร์เวย์)
Polski (โปแลนด์)
Português (โปรตุเกส - โปรตุเกส)
Português - Brasil (โปรตุเกส - บราซิล)
Română (โรมาเนีย)
Русский (รัสเซีย)
Suomi (ฟินแลนด์)
Svenska (สวีเดน)
Türkçe (ตุรกี)
Tiếng Việt (เวียดนาม)
Українська (ยูเครน)
รายงานปัญหาเกี่ยวกับการแปลภาษา
I am comparing Steam monthly report with data provided for each transaction. Data for each transaction has amount in payee's currency and I convert it to USD using rates provided by Steamlytics API. The number of transactions is the same, but gross amount after rates conversion is different for about 10%. This conversion error is very big, given that some payments are already in USD and they are not converted. If USD payments are subtracted, the error in remaining payments is 27% which is very high.
1) I track currency exchange rates by looking at market sales. If no items are sold on the market in those currencies, it won't be recorded in the Steamlytics database. This may be the cause.
2) I only started tracking this data on that date. If you need data before then, I can't really do anything about it.
3) The rates are extrapolated from market sales. Not sure how often it changes though. Are you using the same rate for every transaction, or are you using that specific day's exchange rate for the transaction?
Additional note: I was trying to use different sources for rates:
* Pure FX rates available in some APIs. They give biggest error.
* We have our own Steam sales. They are not in-game sales, they are DLCs. I have extracted exchange rates from there and used for conversion. Error was still bigger, comparing to using your API.
So, your API gives best results, but error is still huge. It would be so nice of Steam to provide this data in native API. But that seems hopeless dream.