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
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
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
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
On Thursday, June 16, 2022 at 6:55:29 PM UTC+5:30 adsapi wrote:
> Hi Vijay,
>
> Thank you for sending the requested information. In order for us to
> investigate,
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
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
On Thursday, May 12, 2022 at 4:13:36 PM UTC+5:30 adsapi wrote:
> Hi Anant,
>
>
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
