Sorry, we don't support your browser.  Install a modern browser

Feature request — close Google Ads data gaps (audience, product-level, asset ratings, new-vs-returning, QS, field combos)#1800

We use the Windsor.ai Google Ads connector for client account audits and reporting. It’s been great for most dimensions, but we’ve hit several data gaps that currently force us back into the Google Ads UI. Requesting the following be exposed/fixed (field names from your connector noted for reference):

Audience segment data returns null. The audience field comes back null for every campaign, so we can’t report audience/Customer Match segment performance (spend, conv, ROAS by segment). Please populate the audience/segment dimension.

Shopping product-level (listing group) values return null. ad_group_criterion_listing_group_case_value_product_brand_value and …_product_category_category_id return null, so SKU/brand/category-level Shopping analysis isn’t possible. Please expose product-partition / product-item-level data (item ID, title, brand, category).

Asset/extension performance ratings return null. asset_performance (Low / Good / Best) is null — only asset_type comes through. Please populate asset performance labels so we can audit creative/extension quality.

new_versus_returning_customers cannot be combined with cost/spend. Querying it alongside spend/cost_micros errors with “unsupported metric.” Please allow new-vs-returning customer segmentation together with cost and conversion-value metrics (needed for new-customer acquisition / NCA analysis).

Field-combination limits force extra pulls. campaign_optimization_score + budget_amount + ad_rotation_mode cannot be requested in one query (“cannot be queried together”). These are all campaign-level settings — please allow them in a single pull.

Numeric Quality Score is unusable. quality_score / quality_info_quality_score / historical_quality_score return aggregated/summed values (e.g. 720, 900) instead of the 1–10 score. The categorical components (quality_info_creative_quality_score, etc.) work fine, but the numeric QS should return the true 1–10 value (ideally at keyword grain, no date aggregation).

(Nice-to-have) Custom-goal → campaign mapping and conversion-action primary/secondary status aren’t exposed — useful for auditing conversion setup.

3 hours ago