The new and recommended for use Monetization Stats API endpoint inserts BOM in the beginning of requested CSV.
There should not be BOM in the beginning of CSV.
Hello amjaliks,
we are sending a byte order mark for compatibility reasons: Microsoft Excel requires a BOM in CSV to understand utf-8 content instead of ANSI. Can you share which application/program you are having issues with?
Alternatively, if you request “Accept: application/json” you will get the content in JSON format which is easier to parse in custom data pipelines.
We import revenue stats to our database using the in-house parser powered by Apache Commons CSV.
I can adjust our code to handle BOM properly, but this API behavior is odd. The old API hasn’t BOM.
And no, JSON isn’t easier to parse. It is bulky and has huge overhead for such application as this.
Thank you for the information amjaliks,
we will look into removing the BOM from direct API integration and include it only to the dashboard CSV download for the above-mentioned compatibility reasons. I’ll post an update when we have investigated that option.
Hello amjaliks,
we decided to remove the BOM from direct API integrations and the change is already deployed to production. I hope you are unblocked and can remove your tweak.
Thank you for reaching out to us and sorry for the extra effort!
-Jussi and the Unity Ads Reporting Team
Thanks for a quick fix!
I also have noticed issue with source IDs. However, I don’t want to discuss it in the forum, because of some private info. Where I can submit my question/issue?
Sure,
can you create an official support ticket by emailing unityads-support@unity3d.com Please, refer this thread, me and Unity Ads Reporting Team so that our support knows who to direct the request to. I’ll add a heads-up internally as well.