Hello,
I am encountering what is (at least to me) puzzling behavior when attempting to download report data via the Google Ads API when increasing the number of fields in a query. I am using the Python client library.
The following query returns the expected data, and I compared it to data for the same dates and customer id that was retrieved through the AdWords API and confirmed it matched up:
SELECT ad_group.id, campaign.name, segments.date, metrics.cost_micros, metrics.impressions FROM ad_group WHERE segments.date >= '2022-03-01' AND segments.date <= '2022-03-03'
However, when I expanded that query in order to gather all of the data from ad_group that I could, the search request returned no data and there was no error response from the API. This is the expanded query (it is a lot of fields):
SELECT ad_group.ad_rotation_mode, ad_group.audience_setting.use_audience_grouped, ad_group.base_ad_group, ad_group.campaign, ad_group.cpc_bid_micros, ad_group.cpm_bid_micros, ad_group.cpv_bid_micros, ad_group.display_custom_bid_dimension, ad_group.effective_cpc_bid_micros, ad_group.effective_target_cpa_micros, ad_group.effective_target_cpa_source, ad_group.effective_target_roas, ad_group.effective_target_roas_source, ad_group.excluded_parent_asset_field_types, ad_group.explorer_auto_optimizer_setting.opt_in, ad_group.final_url_suffix, ad_group.id, ad_group.labels, ad_group.name, ad_group.percent_cpc_bid_micros, ad_group.resource_name, ad_group.status, ad_group.target_cpa_micros, ad_group.target_cpm_micros, ad_group.target_roas, ad_group.targeting_setting.target_restrictions, ad_group.tracking_url_template, ad_group.type, ad_group.url_custom_parameters, segments.ad_destination_type, segments.ad_network_type, segments.date, segments.day_of_week, segments.hour, segments.month, segments.quarter, segments.week, segments.year, metrics.clicks, metrics.all_conversions, metrics.all_conversions_from_interactions_rate, metrics.all_conversions_value, metrics.average_cpc, metrics.conversions, metrics.conversions_from_interactions_rate, metrics.conversions_value, metrics.cost_micros, metrics.cost_per_all_conversions, metrics.cost_per_conversion, metrics.interactions, segments.device, accessible_bidding_strategy.id, accessible_bidding_strategy.maximize_conversion_value.target_roas, accessible_bidding_strategy.maximize_conversions.target_cpa, accessible_bidding_strategy.name, accessible_bidding_strategy.owner_customer_id, accessible_bidding_strategy.owner_descriptive_name, accessible_bidding_strategy.resource_name, accessible_bidding_strategy.target_cpa.target_cpa_micros, accessible_bidding_strategy.target_impression_share.cpc_bid_ceiling_micros, accessible_bidding_strategy.target_impression_share.location, accessible_bidding_strategy.target_impression_share.location_fraction_micros, accessible_bidding_strategy.target_roas.target_roas, accessible_bidding_strategy.target_spend.cpc_bid_ceiling_micros, accessible_bidding_strategy.target_spend.target_spend_micros, accessible_bidding_strategy.type FROM ad_group WHERE segments.date >= '2022-02-28' AND segments.date <= '2022-03-03'
Can you please clarify why the second query doesn't contain any data? If some of those fields are not relevant for the customer id in question I would expect that either an error would be returned or those fields simply not be returned, not to have a blank response.
I can provide the customer ID in a direct message if needed (this is happening with all customer IDs).