DCM API & CM360 joint error, possible date settings bug

[JUBA PLUS]

Hi,

I was advised by dcm-support that I should try contacting the dcmapi-support for an error I’ve been running into, but I am not provided any ways to establish a private email thread on this issue. 

My team has been facing a possible bug, which seems to involve both the API and CM360 Dashboard.

Since late June one of our application has been facing an ”TypeError: 'int' object is not iterable”

When calling

service = dfareporting_utils.setup([])

……

service.placements().insert(profileId=_profile_id, body=placement)

with the placement payload as

placement['pricingSchedule'] = {

                                'startDate': _start_date,

                                'endDate': _end_date,

                                'pricingType': 'PRICING_TYPE_CPM'

                }

This script has been used on a weekly basis for the past 2 years and from past experience, ”TypeError: 'int' object is not iterable” at this section of the script is usually caused by conflicting date ranges, i.e. placement start, end date outside of campaign date range.

However, upon inspecting the CM360 dashboard, the campaign date range well includes the intended placement schedule.

For further investigation, we tried importing a spreadsheet via CM360 dashboard and received an error

Failed:"Placement pricing period start date 2023-08-22 must be before or same as end date 2023-05-12.;Placement pricing period end date 2023-05-12 must be in placement date range 2023-08-22 - 2023-09-08"

Oddly, the date 2023-05-12 is nowhere to be found in any of our settings and even after trying different campaigns, the same 2023-05-12 is popping up in error reports.

In addition, if we upload the spreadsheet in legacy format on the CM360 dashboard, we will not receive an error, which makes me believe this could possibly be a bug. Given such, I am not aware of any parameter that will allow me to alter my API call to legacy mode and it also does not appeal to the established workflow of my team. I’ve tried looking up if there were any  major API changes late June but wasn’t aware of any and since the CM360 Dashboard also produces a seemingly related error, I highly suspect that the API error is related to this date that is repeatedly appearing during Import Spreadsheet. Since the error is more obvious on the CM360 dashboard side, I tried contacting the dcm-support team first, but has had no progress to solving this issue for the past two months. 

I would really appreciate if attention can be raised for the issue I am facing right now.

Thank you,

[DCM API (DoubleClick Campaign Mgr)]

Hello,

Thank you for reaching out to the DCM API support team.

By reviewing your concern, I understand that you are facing issues while generating a report using the DCM API. Please note that we can resolve technical issues or concerns related to the CM360 API. I could see you are using the Python client library and facing "TypeError". If the problem is only with the Python client library, I would suggest you contact the developer's specialist support team as they are better equipped to address your concerns.

However, regarding the placement date range issue, kindly share the following details to investigate further:

• DCM Account Id.
• User profile Id.
• Complete JSON request and response logs.
• Report Id and Query Id generated from UI.
• Downloaded report file from UI. 

This message is in relation to case "ref:_00D1U1174p._5004Q2o9wsS:ref"

Thanks,
 

DCM API Team

[DCM API (DoubleClick Campaign Mgr)]

Hello,

Thank you for reaching out to the DCM API support team.

Please ignore my previous email, kindly check the response below:

By reviewing your concern, I understand that you are facing issues while generating a report using the DCM API. Please note that we can resolve technical issues or concerns related to the CM360 API. I could see you are using the Python client library and facing "TypeError". If the problem is only with the Python client library, I would suggest you contact the developer's specialist support team as they are better equipped to address your concerns.

However, regarding the placement date range issue, kindly share the following details to investigate further.

• DCM Account Id.
• User profile Id.
• Complete JSON request and response logs.
• Report Id and Query Id generated from UI.
• Downloaded report file from UI. 

You may send the requested details privately via "Reply To Author" option.