Display & Video 360 – Import issues for custom reports
Incident Report for Funnel
Resolved
This incident has been resolved.
Posted Sep 30, 2024 - 14:14 CEST
Update
All data sources affected by the issue are now back up and running, and connecting new data sources should work as intended once again.
Posted Sep 30, 2024 - 14:13 CEST
Monitoring
After receiving advice from the Display & Video 360 support team, we have implemented a workaround in our connector for data sources affected by this problem.

The workaround involves creating a new report query using the parameters of the initial report. As a result, you will see new reports in your DV360 account named "original report name - recreated report by Funnel", and the report ID in your data source's definition label will be updated to match the new recreated report ID.

If you wish to make any adjustments to the report on the DV360 side of things, such as adding/removing fields, please make any such adjustments in the recreated report, as changes to the initial report will not be reflected in your Funnel data source.

The fix is deployed and we are now attempting to run import jobs for affected data sources, monitoring closely to ensure that everything works as intended.
Posted Sep 30, 2024 - 11:53 CEST
Investigating
We have noticed that some Display & Video 360 data sources that make use of custom reports are currently unable to import new data.

Existing data sources that are affected by this problem display an error message that states "Date must be included in report" in Funnel, and attempts to connect new DV360 data sources with custom reports may encounter an error that states "Report format must be set to CSV".

Our initial investigation shows that this is the result of unexpected behavior from the Display & Video 360 API, where reports that are configured to be delivered in the CSV file format are instead being returned as XLSX files, which our integration is currently not capable of handling.

We have reached out to the Display & Video 360 team to figure out the cause of this issue.
Posted Sep 27, 2024 - 15:12 CEST