Multiple rows with same segment value

[Anant Prasad]

Hi team,

We were having some issues with a particular segment called `segments.click_type` in `campaign` resource. When we query the data from the API, we are getting segmented results as expected but the issue is that whenever the segment value is `UNKNOWN`, the API is returning multiple rows with the same segment name. Isn't it expected that the data will be combined if the segment value is same?

To be more precise about the issue I am describing, here is a link to a CSV which signifies how we are receiving this data on our side.

https://docs.google.com/spreadsheets/d/1DjD3XzB_zuf1sAPiYOY4rkOyXCydWNyQUBv6DoKfxto/edit?usp=sharing

Based on this data, I think that the API is not treating the `UNKNOWN` values as a unique value and hence returning multiple rows.

Since this behaviour is not visible in other segment types, wanted to know if this is an expected behaviour on the API's end or some issue with the `click_type` segment.

Please let me know if any more information is required to look into this. Thanks!

Best,
Anant P.

[Google Ads API Forum Advisor]

Hi Anant,

Thank you for raising this concern to the Google Ads API Forum.

It would be helpful to check this in our end by providing the complete logs within the format of the request and response logs with request-id and login-customer-id that generated on your end. This information will help our team to further investigate why these issues occurred. For security purposes, you can provide it via Reply privately to the author option. If this option is not available, then send it instead on this email address googleadsa...@google.com.

However, for the attached CSV file you've shared, I am afraid that the file does not contain enough statements on how you are receiving this data in your side.

Best regards, 

Jinky Google Ads API Team

ref:_00D1U1174p._5004Q2arvXW:ref

[Vijay Kumar]

Hi Jinky,

Thanks for your response. Following up on the issue, I've sent the requested details through the "private-reply-to-author". Please let me know if you need any additional information.

Regards,

Vijay Kumar

[Google Ads API Forum Advisor]

Hi Vijay,

Thank you for sending the requested information. In order for us to investigate, could you please provide the sample rows from API response with this scenario "I think that the API is not treating the `UNKNOWN` values as a unique value and hence returning multiple rows.", that you mentioned so that I can check it on my impersonation report. You can provide it via Reply privately to the author option. If this option is not available, then send it instead on this email address googleadsa...@google.com.

[Vijay Kumar]

Hi Jinky,

I've sent a private reply for the response log. Please let me know if you need more details.

Best Regards,

Vijay Kumar

[Google Ads API Forum Advisor]

Hi Vijay,

Thank you for sending the response log too. When segmenting the UI campaign screen by Click type I found 2 types in your account that don't match any of the enums. They are Mobile app extension and Image extension. This is the reason you have some campaigns with extra 'UNKNOWN' rows, the different metrics match the 2 types mentioned above.

To get a sense of priority, could you give us a business use case for updating the enums in segments.click_type to match the UI?

Regards,

Aryeh Google Ads API Team

ref:_00D1U1174p._5004Q2arvXW:ref

[Vijay Kumar]

Hi Aryeh,

Thanks for getting to the cause of the issue. Before I get back to you on the business use case, I've one question. Why the invalid ENUM values "Mobile app extension" and "Image extension" are even allowed to be used? We are a reporting platform for the performance marketing teams and have thousands of accounts integrated. As a service provider, we can get back on their use cases, but I'm afraid this could be a fundamental issue with the ads API backend and there could be more such accounts. What do you think? Please correct me if I missed something.

On a side note, this is pretty urgent because google ads customers are unable to use the click-type segment reports due to this.

Regards,

Vijay Kumar

[Google Ads API Forum Advisor]

Hi Vijay,

The Ads API can only be a conduit to the Ads product as exposed in the Ads UI. There may be a feature availability time lag when using the API. All currently supported click types return correctly while unsupported types get their own row. Could you also elaborate how this makes the report unusable?

[Vijay Kumar]

Hi Aryeh,

> ...Could you also elaborate how this makes the report unusable?

The "multiple rows (with a duplicate identifier)" for a segment type, due to the cause that you found, is not a standard expectation, and neither it's made explicit on the doc. So it didn't make sense and seemed like a bug. So, we wanted to confirm the reason for it.

> ...2 types in your account that don't match any of the enums...this is the reason you have some campaigns with extra 'UNKNOWN' rows

We are fine with the confirmation on the issue and can change our application logic to suit this behavior. I'll close this thread here until the google ads customers have a requirement to see the segmented view of the UNKNOWN segment values.

Thanks for the support.

Vijay Kumar

Software Engineer