CSV report fields not matching

Posted in General by Alex Tue Nov 19 2019 16:52:52 GMT+0000 (Coordinated Universal Time)·1·Viewed 117 times

Hello, starting today Performance report (CSV) returns values not matching with header row, Example: hour,"line item id","creative id",spend,impressions,"viewable impressions","measurable impressions",clicks,"video plays","video q1s","video midpoints","video q3s","video completes","video skips",conversions,"viewable seconds","media spend","inventory cost","conversion value","conversion orders",revenue,"gross margin percent","vendor fees","net margin","net margin percent","video companion views","video companion clicks","video companion ctr" "2019-09-04 09:00",198,456,0.54,103,0,0,0,0,0,0,0,0,0.00,0.00,0.00,0.00,0.00,-0.54,0.00,0,0,0.00,0.51,0,0,0.00,0.54 as you can see last columt should be "video companion ctr" and value shown is "0.54" but if we request same report with "report_format":"none" we can see correct order: "payload": { "0": { ... "video companion ctr": "0.00", "media spend": "0.54" }, Request is: {"report_id":1,"report_format":"none","request_details":{"offset":0,"rows":500,"field":["bid_hour","line_item_id","creative_id"],"metric":["spend","impression","viewable_impressions","measurable_impressions","clicks","video_plays","video_Q1s","video_midpoints","video_Q3s","video_completes","video_skips","conversions","viewable_seconds","media_spend","inventory_cost","conversion_value","conversion_order","revenue","gross margin percent","vendor_fees","net_margin","net_margin_percent","video_companion_views","video_companion_clicks","video_companion_CTR"],"sort_by":[{"bid_hour":0},{"line_item_id":0},{"creative_id":0}],"filter":[{"account_id":2},{"advertiser_id":18},{"campaign_id":53},{"bid_hour":">=2010-05-18 00:00:00&&<=2019-11-19 23:59:59"}]}} Can you please provide any info on that?
Jan 10, 2020

I've got response by email, thanks:
"It turns out the header label <> data mismatch issue was a side effect of an improvement we made to exported reports last month, this was caught and resolved on November 20th. This should no longer be happening."

  
Markdown is allowed