Hi,
Those files are definitely temporary and usually we request if you can repro strange issues like this with ‘twurl’ both so that we can easily repro and make sure that it’s not something with the implementation. I will take your word for it that the file contains this sort of data, and I am not sure of a reason for it be like that besides a bug.
For helping us prioritize…It would be good if you can check 1) does it still happen, 2) is it only happening with this particular campaign / time period)
The analytics data will be the same between Ads UI and Ads API - so you are free to report issue like this from ads.twitter.com from an advertiser perspective and this particular case (if it’s a totally one off thing) may be easier to escalate about from that angle.
Thanks,
John
