Can you please provide any update on the same.
thanks
On Tuesday, November 23, 2021 at 11:00:37 AM UTC+5:30 Akash Prajapati wrote:
> Hello Team,
>
> 1. The modified query still we get aggregated results. -
> query = """
> SELECT
> campaign.id,
> campaign.status,
> campaign.name,
> segments.date,
> segments.ad_network_type,
> metrics.impressions
> FROM campaign
> WHERE segments.date = '2021-11-13' and metrics.impressions >= 0 and
> campaign.status IN ('ENABLED','PAUSED','REMOVED')
> """
>
>
> - The metrics.impressions >= 0 part in the query will include zero
> impressions as well thus it should include zero impressions as well right,
> Kindly correct me if I am wrong.
> PFA *campaign_report_to_csv.py* file that I am currently using to
> fetch and download the report in csv in my local.
>
>
>
> *I have only one doubt why I am getting aggregated data for each
> campaignID, even when I am providing all the filters in WHERE clause? Can
> you please correct the query that is mentioned above in order to get all
> the distinct rows from the resource campaign (campaign performance report)*
> 2. I have set the log level to DEBUG in the logs there is no error and
> there is nowhere I can see the log has the name and not the enumeration.
> Kindly also suggest something else to resolve this.
>
> LOGS-
> Request: customer_id: xyz
>
> query: "\n SELECT\n campaign.id,\n
> campaign.status,\n segments.date,\n
> segments.ad_network_type,\n metrics.impressions,\n
> campaign.name\n \n FROM campaign\n WHERE
> segments.date = \'2021-11-13\' and metrics.impressions >= 0 and
> campaign.status IN (\'ENABLED\',\'PAUSED\',\'REMOVED\') \n "
>
> I am getting nothing in the logs which is pointing out the enums to names.
>
>
> 3. Regarding the deprecated fields for example in campaign performance
> report or campaign resource the *CampaignGroupId. => deprecated, *how
> should we proceed on this ?
>
> 4. I can also see for some attributes it is written like -
> *Labels => Select label.resource_name from the resource campaign_label*
>
> *CampaignDesktopBidModifier => Not available with 'FROM campaign'.
> However, you can retrieve device type bid modifiers via 'FROM
> campaign_criterion' queries. *For such cases do we have to perform a JOIN
> operation in the query to fetch these attributes like for
> *CampaignDesktopBidModifier
> *we have to join the campaign resource with campaign_criterion ?
> and for Labels or lableids we have to just write the whole select phrase
> that is suggested in the documentation?
>
>
> Thanks and Regards
> On Monday, November 22, 2021 at 9:06:21 PM UTC+5:30 adsapi wrote:
>
>> Hi Akash,
>>
>> I work with Peter and will assist you. For the discrepancy in Ads API and
>> AdWords API regarding rows of campaign returned, let me tell you a general
>> rule that most probably applies apply to your situation, that in the Ads
>> API zero impressions are always excluded when segmenting a report, provided
>> *all* metrics are zero. You have segmented on segments.ad_network_type.
>>
>> To prove for certain whether the general rule is applying here, could you
>> privately send us the full request and response log of API communication of
>> the reports from both API's?
>>
>> In the Ads API <https://developers.google.com/google-ads/api/docs/start>,
>> the request and response appears similar to the JSON Mappings in our
>> REST documentation
>> <https://developers.google.com/google-ads/api/rest/design/json-mappings?hl=en>.
>>
>> Our client libraries have loggers with logging instructions, to see these
>> instructions you can click on the client library you use in the sidebar of
>> our client library guide
>> <https://developers.google.com/google-ads/api/docs/client-libs?hl=en> and
>> click on "Logging".
>>
>> In the AdWords API
>> <https://developers.google.com/adwords/api/docs/guides/start> , then a
>> request looks like the 3rd section in request
>> <https://developers.google.com/adwords/api/docs/guides/call-structure#request>
>> and
>> a response looks similar to response
>> <https://developers.google.com/adwords/api/docs/guides/call-structure#response>.
>>
>> Logging instructions are in the read.me on Github of each client library
>> <https://developers.google.com/adwords/api/docs/clientlibraries>.
>>
>> Setting the logger to 'DEBUG' will generate the necessary logs.
>>
>> Regarding getting enumeration instead of the name of the network, using
>> the logging method mentioned above you will see that the log has the name
>> and not the enumeration. You may check your client library setup
>> <https://developers.google.com/google-ads/api/docs/client-libs> to make
>> certain you aren't showing the enumeration instead.
>>
>> Criteria Performance Report has been split up. Instead of having single
>> attribution reports
>> <https://developers.google.com/adwords/api/docs/guides/reporting#single_attribution>
>> which
>> can contain multiple criteria types in a single report, the Google Ads API
>> relies on different *reporting views* for retrieving stats related to
>> different criteria types. For example, you can make use of the
>> keyword_view to retrieve data by keyword, or the product_group_view to
>> retrieve data by product group. Thus, there is no longer a generic report
>> that contains multiple criteria types; you can only get stats for a
>> criteria type by looking up its view.
>>
>> Regarding deprecated fields, in general, the new Ads API matches the
>> current UI, fields that didn't make it to the current UI most probably
>> won't be in the Ads API. You may get back to us on specific fields.
>>
>>
>> Reminder: Share your feedback about the Google Ads (AdWords) API! Take
>> the 2021 Google Ads API and AdWords API Annual Survey
>> <https://google.qualtrics.com/jfe/form/SV_eQbOpf4VxRyyqqO?source=so>
>>
>> Regards,
>>
>> [image: Google Logo]
>> Aryeh Baker
>> Google Ads API Team
>>
>>
>> ref:_00D1U1174p._5004Q2RuglK:ref
>>
>
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
---
You received this message because you are subscribed to the Google Groups
"AdWords API and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/adwords-api/b1d44268-1cca-4595-bf79-d16238c992b3n%40googlegroups.com.
