gaql_data.csv

Questions,Queries,Context
How many conversions or clicks did we get yesterday?,"SELECT
campaign.id,
campaign.name,
metrics.conversions,
metrics.clicks,
metrics.ctr,
metrics.cost_micros,
metrics.cost_per_conversion,
metrics.average_cpc,
metrics.all_conversions_from_interactions_rate
FROM campaign
WHERE segments.date DURING YESTERDAY","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
How many conversions or clicks did we get today?,"SELECT
campaign.id,
campaign.name,
metrics.conversions,
metrics.clicks,
metrics.ctr,
metrics.cost_micros,
metrics.cost_per_conversion,
metrics.average_cpc,
metrics.all_conversions_from_interactions_rate
FROM campaign
WHERE segments.date DURING TODAY","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
How many conversions or clicks did we get this month?,"SELECT
campaign.id,
campaign.name,
metrics.conversions,
metrics.clicks,
metrics.ctr,
metrics.cost_micros,
metrics.cost_per_conversion,
metrics.average_cpc,
metrics.all_conversions_from_interactions_rate
FROM campaign
WHERE segments.date DURING THIS_MONTH","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
What was my sales or revenue for today so far?,"SELECT  metrics.conversions_value        
 
FROM customer
WHERE segments.date DURING TODAY","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
What was my sales or revenue for yesterday?,"SELECT  metrics.conversions_value        
 
FROM customer
WHERE segments.date DURING YESTERDAY","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
What was my sales or revenue for this month?,"SELECT  metrics.conversions_value        
 
FROM customer
WHERE segments.date DURING THIS_MONTH","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
Which are  the best performing adgroups in terms of conversion rates?,"SELECT 
ad_group.id,
ad_group.name,
metrics.clicks,
metrics.impressions,
metrics.ctr,
metrics.conversions,
metrics.conversions_from_interactions_rate
FROM ad_group
WHERE ad_group.status = 'ENABLED' and segments.date DURING LAST_MONTH
ORDER BY metrics.conversions_from_interactions_rate DESC","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
Which are  the worst performing adgroups in terms of conversion rates?,"SELECT 
ad_group.id,
ad_group.name,
metrics.clicks,
metrics.impressions,
metrics.ctr,
metrics.conversions,
metrics.conversions_from_interactions_rate
FROM ad_group
WHERE ad_group.status = 'ENABLED' and segments.date DURING LAST-MONTH
ORDER BY metrics.conversions_from_interactions_rate ASC","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
Which are  the best performing adgroups in terms of ctr?,"SELECT
  campaign.id,
  campaign.name,
  ad_group.id,
  ad_group.name,
  metrics.impressions,
  metrics.clicks,
  metrics.ctr
FROM ad_group
WHERE
  segments.date DURING LAST_30_DAYS
  AND campaign.status = 'ENABLED'
  AND ad_group.status = 'ENABLED'
  AND metrics.impressions >= 100
ORDER BY metrics.ctr DESC
LIMIT 20","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
Which are  the worst performing adgroups in terms of ctr?,"SELECT
  campaign.id,
  campaign.name,
  ad_group.id,
  ad_group.name,
  metrics.impressions,
  metrics.clicks,
  metrics.ctr
FROM ad_group
WHERE
  segments.date DURING LAST_30_DAYS
  AND campaign.status = 'ENABLED'
  AND ad_group.status = 'ENABLED'
  AND metrics.impressions >= 100
ORDER BY metrics.ctr ASC
LIMIT 20","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
Which are  the best performing adgroups?,"SELECT
  ad_group.id,
  ad_group.name,
  metrics.impressions,
  metrics.clicks,
  metrics.ctr,
  metrics.conversions,
  metrics.conversions_from_interactions_rate,
  metrics.cost_micros,
  metrics.average_cpc
FROM ad_group
WHERE segments.date DURING THIS_MONTH","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
Which campaigns generate the most conversions?,"SELECT
  campaign.id,
  campaign.name,
  metrics.conversions
FROM campaign
WHERE segments.date DURING THIS_MONTH
ORDER BY metrics.conversions DESC","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
Which ad groups generate the most conversions?,"SELECT
  campaign.id,
  campaign.name,
  ad_group.id,
  ad_group.name,
  metrics.impressions,
  metrics.clicks,
  metrics.conversions,
  metrics.conversions_value,
  metrics.cost_micros
FROM ad_group
WHERE
  segments.date DURING LAST_30_DAYS
  AND campaign.status = 'ENABLED'
  AND ad_group.status = 'ENABLED'
ORDER BY metrics.conversions DESC
LIMIT 20","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
"Which keywords drive the most revenue, and are they profitable at current CPC?","SELECT
  campaign.id,
  campaign.name,
  ad_group.id,
  ad_group.name,
  ad_group_criterion.criterion_id,
  ad_group_criterion.keyword.text,
  metrics.conversions_value,
  metrics.average_cpc,
  metrics.cost_micros
FROM keyword_view
WHERE segments.date DURING THIS_MONTH
  AND ad_group_criterion.status = 'ENABLED'
ORDER BY metrics.conversions_value DESC","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
Which keywords have high CPA and should be paused or bid-down?,"SELECT
  campaign.id,
  campaign.name,
  ad_group.id,
  ad_group.name,
  ad_group_criterion.criterion_id,
  ad_group_criterion.keyword.text,
  metrics.cost_per_conversion,
  metrics.cost_micros,
  metrics.conversions
FROM keyword_view
WHERE segments.date DURING THIS_MONTH
  AND ad_group_criterion.status = 'ENABLED'
ORDER BY metrics.cost_per_conversion DESC","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
What is the overall click-through rate (CTR) of our campaigns?,"SELECT
  metrics.impressions,
  metrics.clicks,
  metrics.ctr
FROM customer
WHERE segments.date DURING THIS_MONTH","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
What is the cost per click (CPC) across different campaigns?,"SELECT
  campaign.id,
  campaign.name,
  metrics.clicks,
  metrics.cost_micros,
  metrics.average_cpc
FROM campaign
WHERE segments.date DURING THIS_MONTH","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
What is the cost per click (CPC) across different ad groups?,"SELECT
  ad_group.id,
  ad_group.name,
  campaign.name,
  metrics.clicks,
  metrics.cost_micros,
  metrics.average_cpc
FROM ad_group
WHERE segments.date DURING THIS_MONTH","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
What is the average conversion rate of our ads?,"SELECT
  ad_group_ad.ad.id,
  ad_group_ad.ad.type,
  ad_group_ad.ad_group,
  ad_group_ad.status,
  ad_group_ad.ad_strength,
  metrics.clicks,
  metrics.conversions,
  metrics.conversions_from_interactions_rate
FROM ad_group_ad
WHERE segments.date DURING THIS_MONTH","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
What is the total spend in the last month?,"SELECT
  metrics.cost_micros
FROM customer
WHERE segments.date DURING LAST_MONTH","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
What is the total spend in the last 30 days?,"SELECT
  metrics.cost_micros
FROM customer
WHERE segments.date DURING LAST_30_DAYS","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
"How many impressions, clicks, and conversions did we get?","SELECT
  campaign.id,
  campaign.name,
  metrics.impressions,
  metrics.clicks,
  metrics.conversions
FROM campaign
WHERE segments.date DURING LAST_30_DAYS","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
Which campaigns generate the most clicks?,"SELECT
  campaign.id,
  campaign.name,
  metrics.impressions,
  metrics.clicks
FROM campaign
WHERE segments.date DURING LAST_30_DAYS
ORDER BY metrics.clicks DESC","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
Which campaigns generate the most impressions?,"SELECT
  campaign.id,
  campaign.name,
  metrics.impressions,
  metrics.clicks
FROM campaign
WHERE segments.date DURING LAST_30_DAYS
ORDER BY metrics.impressions DESC","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
"Which devices (desktop, mobile, tablet) perform best?","SELECT
  segments.device,
  metrics.clicks,
  metrics.conversions,
  metrics.cost_micros,
  metrics.cost_per_conversion,
  metrics.conversions_value
FROM campaign
WHERE segments.date DURING LAST_30_DAYS","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
Which headlines and descriptions achieve the highest CTR?,"SELECT
  ad_group_ad_asset_view.asset,
  asset.name,
  asset.type,
  ad_group_ad_asset_view.performance_label,
  metrics.impressions,
  metrics.clicks,
  metrics.ctr
FROM ad_group_ad_asset_view
WHERE segments.date DURING LAST_30_DAYS","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
Which headlines and descriptions achieve the highest CVR?,"SELECT
  ad_group_ad.ad.id,
  ad_group_ad.ad.type,
  metrics.clicks,
  metrics.conversions,
  metrics.conversions_from_interactions_rate
FROM ad_group_ad
WHERE segments.date DURING LAST_30_DAYS ","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
How do age demographics perform?,"SELECT
  campaign.id,
  campaign.name,
  metrics.impressions,
  metrics.clicks,
  metrics.conversions,
  metrics.cost_micros
FROM age_range_view
WHERE segments.date DURING LAST_30_DAYS","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
How do gender demographics perform?,"SELECT
  campaign.id,
  campaign.name,
  metrics.impressions,
  metrics.clicks,
  metrics.conversions,
  metrics.cost_micros
FROM gender_view
WHERE segments.date DURING LAST_30_DAYS","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
How do income demographics perform?,"SELECT
  campaign.id,
  campaign.name,
  metrics.impressions,
  metrics.clicks,
  metrics.conversions,
  metrics.cost_micros
FROM income_range_view
WHERE segments.date DURING LAST_30_DAYS","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
Which devices (mobile vs. desktop vs. tablet) yield the best CVR and ROAS?,"SELECT
  segments.device,
  metrics.clicks,
  metrics.conversions,
  metrics.conversions_from_interactions_rate, 
  metrics.conversions_value,
  metrics.cost_micros
FROM campaign
WHERE segments.date DURING LAST_30_DAYS","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
Which regions generate the most profitable traffic?,"SELECT
  segments.geo_target_region,
  metrics.impressions,
  metrics.clicks,
  metrics.conversions,
  metrics.cost_micros,
  metrics.conversions_value
FROM geographic_view
WHERE segments.date DURING LAST_30_DAYS","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
"How many view-through conversions (Display, Video) are you getting?","SELECT
  campaign.id,
  campaign.name,
  metrics.impressions,
  metrics.clicks,
  metrics.conversions,
  metrics.view_through_conversions
FROM campaign
WHERE segments.date DURING LAST_30_DAYS","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
What CPMS and view-through conversion rates are you seeing on video?,"SELECT
  campaign.id,
  campaign.name,
  metrics.impressions,
  metrics.average_cpm,
  metrics.view_through_conversions,
  metrics.ctr
FROM campaign
WHERE campaign.advertising_channel_type = 'VIDEO'
  AND segments.date DURING LAST_30_DAYS","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
What is the cost per conversion (CPA)?,"SELECT
  metrics.clicks,
  metrics.conversions,
  metrics.cost_micros,
  metrics.cost_per_conversion
FROM customer
WHERE segments.date DURING LAST_30_DAYS","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
What is the return on ad spend (ROAS)?,"SELECT
  campaign.id,
  campaign.name,
  metrics.conversions_value,
  metrics.cost_micros
FROM campaign
WHERE segments.date DURING LAST_30_DAYS","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
Which keywords drive the highest number of conversions?,"SELECT
  ad_group_criterion.keyword.text,          
  ad_group_criterion.keyword.match_type,   
  metrics.clicks,
metrics.conversions,
  metrics.impressions,
  metrics.cost_micros                       
FROM keyword_view
WHERE segments.date DURING LAST_30_DAYS
  AND ad_group_criterion.status = 'ENABLED'
ORDER BY metrics.conversions DESC
 LIMIT 50","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
How does performance vary by time of day or day of week?,"SELECT
  campaign.name,
  segments.day_of_week,
  segments.hour,
  metrics.impressions,
  metrics.clicks,
  metrics.conversions,
  metrics.conversions_from_interactions_rate,
  metrics.cost_micros
FROM campaign
WHERE
  segments.date DURING LAST_30_DAYS
ORDER BY segments.day_of_week, segments.hour
LIMIT 100000","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
Which ad copy or creatives have the highest CTR?,"SELECT
  ad_group_ad.ad.id,
  ad_group_ad.ad.name,
  ad_group_ad.status,
  metrics.impressions,
  metrics.clicks,
  metrics.ctr,
  metrics.conversions
FROM ad_group_ad
WHERE segments.date DURING LAST_30_DAYS
  AND ad_group_ad.status = 'ENABLED'      
ORDER BY metrics.ctr DESC                 
LIMIT 25","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
Which ad copy or creatives have the highest conversion rate?,"SELECT
  ad_group_ad.ad.id,
  ad_group_ad.ad.name,
  ad_group_ad.status,
  metrics.impressions,
  metrics.clicks,
  metrics.ctr,
  metrics.conversions
FROM ad_group_ad
WHERE segments.date DURING LAST_30_DAYS
  AND ad_group_ad.status = 'ENABLED'      
ORDER BY metrics.conversions_from_interactions_rate DESC                 
LIMIT 25","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
Which campaigns generate the most conversions?,"SELECT
  campaign.id,
  campaign.name,
  campaign.status,
  metrics.impressions,
  metrics.clicks,
  metrics.cost_micros,
  metrics.conversions,
  metrics.conversions_value
FROM campaign
WHERE segments.date DURING LAST_30_DAYS
  AND campaign.status = 'ENABLED'         
ORDER BY metrics.conversions DESC ","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
Which ad groups generate the most conversions?,"SELECT
  campaign.id,
  campaign.name,
  ad_group.id,
  ad_group.name,
  metrics.impressions,
  metrics.clicks,
  metrics.conversions,
  metrics.conversions_value,
  metrics.cost_micros,
  metrics.cost_per_conversion
FROM ad_group
WHERE
  segments.date DURING LAST_30_DAYS
  AND campaign.status = 'ENABLED'
  AND ad_group.status = 'ENABLED'
ORDER BY metrics.conversions DESC
LIMIT 20","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
What is Search Impression Share and lost-IS (Budget vs. Rank) by campaign?,"SELECT
  campaign.name,
  metrics.search_impression_share,
  metrics.search_budget_lost_impression_share,
  metrics.search_rank_lost_impression_share,
  metrics.impressions,
  metrics.clicks,
  metrics.conversions
FROM campaign
WHERE
  campaign.advertising_channel_type = 'SEARCH'
  AND segments.date DURING LAST_30_DAYS
LIMIT 1000","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
How does ad group performance differ by device?,"SELECT
  ad_group.id,
  ad_group.name,
  segments.device,                       
  metrics.clicks,
  metrics.impressions,
  metrics.ctr,                          
  metrics.average_cpc,                   
  metrics.conversions_from_interactions_rate,
  metrics.cost_micros
FROM ad_group
WHERE segments.date DURING LAST_30_DAYS
ORDER BY ad_group.id, segments.device","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
Which ad groups suffer from low Impression Share and need bid lifts?,"SELECT
  ad_group.id,
  ad_group.name,
  campaign.name,
  metrics.search_impression_share,              
  metrics.search_rank_lost_impression_share, 
  metrics.clicks,
  metrics.conversions,
  metrics.average_cpc
FROM ad_group
WHERE
  segments.date DURING LAST_30_DAYS
  
  AND metrics.search_impression_share < 0.30
 
  AND metrics.search_rank_lost_impression_share > 0.20
ORDER BY
  metrics.search_impression_share ASC,    
  metrics.search_rank_lost_impression_share DESC
LIMIT 50","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
Are there locations where we're spending a lot but not converting?,"SELECT
  user_location_view.country_criterion_id,
  metrics.cost_micros,
  metrics.clicks,
  metrics.conversions
FROM user_location_view
WHERE
  segments.date DURING LAST_30_DAYS
  AND metrics.cost_micros > 1000000
  AND metrics.conversions = 0
ORDER BY
  metrics.cost_micros DESC","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
"How do different match types (broad, phrase, exact) perform?","SELECT 
ad_group_criterion.keyword.match_type, 
campaign.name,
 metrics.clicks,
 metrics.conversions,
 metrics.average_cpc, 
metrics.ctr, 
metrics.conversions_from_interactions_rate 
FROM display_keyword_view 
WHERE segments.date during today AND ad_group_criterion.status = 'ENABLED'","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
What is the breakdown of performance by match type (Broad)?,"SELECT 
ad_group_criterion.keyword.match_type, 
campaign.name,
 metrics.clicks,
 metrics.conversions,
 metrics.average_cpc, 
metrics.ctr, 
metrics.conversions_from_interactions_rate 
FROM display_keyword_view 
WHERE segments.date during today AND ad_group_criterion.keyword.match_type = BROAD and ad_group_criterion.status = 'ENABLED'","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
What is the breakdown of performance by match type (Exact)?,"SELECT 
ad_group_criterion.keyword.match_type, 
campaign.name,
 metrics.clicks,
 metrics.conversions,
 metrics.average_cpc, 
metrics.ctr, 
metrics.conversions_from_interactions_rate 
FROM display_keyword_view 
WHERE segments.date during today AND ad_group_criterion.keyword.match_type = EXACT and ad_group_criterion.status = 'ENABLED'","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
What is the breakdown of performance by match type (Phrase)?,"SELECT 
ad_group_criterion.keyword.match_type, 
campaign.name,
 metrics.clicks,
 metrics.conversions,
 metrics.average_cpc, 
metrics.ctr, 
metrics.conversions_from_interactions_rate 
FROM display_keyword_view 
WHERE segments.date during today AND ad_group_criterion.keyword.match_type = PHRASE and ad_group_criterion.status = 'ENABLED'","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
Are your search-term reports revealing wasted spend on irrelevant queries?,"SELECT
  search_term_view.search_term,
  segments.search_term_match_type,        
  metrics.impressions,
  metrics.clicks,
  metrics.cost_micros,
  metrics.conversions,
  metrics.conversions_from_interactions_rate
FROM search_term_view
WHERE
  segments.date DURING LAST_30_DAYS
  AND metrics.cost_micros > 1000000         
  AND metrics.conversions = 0
  AND search_term_view.status = NONE
ORDER BY
  metrics.cost_micros DESC","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
Are there high-volume keywords with low conversion rates that need match-type tightening?,"SELECT
  ad_group_criterion.keyword.text,           
  ad_group_criterion.keyword.match_type,      
  campaign.name,
  metrics.impressions,
  metrics.clicks,
  metrics.conversions,
  metrics.conversions_from_interactions_rate, 
  metrics.cost_micros                        
FROM keyword_view
WHERE
  segments.date DURING LAST_30_DAYS
  
  AND metrics.clicks > 100                    
  AND metrics.conversions_from_interactions_rate < 0.005   
  AND ad_group_criterion.keyword.match_type IN ('BROAD','PHRASE')
  AND ad_group_criterion.status = ENABLED     
ORDER BY
  metrics.clicks DESC
LIMIT 100","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
How do different ad formats (Responsive Search Ads vs. Expanded Text Ads vs. Dynamic) stack up?,"SELECT
  ad_group_ad.ad.type,
  metrics.impressions,
  metrics.clicks,
  metrics.ctr,
  metrics.conversions,
  metrics.conversions_from_interactions_rate,
  metrics.average_cpc,
  metrics.cost_micros
FROM ad_group_ad
WHERE segments.date DURING LAST_30_DAYS
ORDER BY metrics.conversions DESC","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
"In Performance Max, which image/video/text assets earn the highest asset-group scores?","SELECT
  campaign.id,
  campaign.name,
  asset_group.id,
  asset_group.name,
  asset_group_asset.field_type,          
  asset_group_asset.performance_label,  
  asset_group_asset.asset,              
  asset.name                          
FROM asset_group_asset
WHERE campaign.advertising_channel_type = 'PERFORMANCE_MAX'   
  AND asset_group_asset.performance_label IN ('BEST','GOOD')  
ORDER BY asset_group.id,
         asset_group_asset.field_type,
         asset_group_asset.performance_label DESC","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
Are conversion goals (including offline imports) feeding properly into PMax?,"SELECT
  campaign.name,
  campaign.advertising_channel_type,
  segments.conversion_action,
  metrics.conversions,
  metrics.conversions_value
FROM campaign
WHERE
  segments.date DURING LAST_30_DAYS
  AND campaign.advertising_channel_type = 'PERFORMANCE_MAX'
LIMIT 1000","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
Which keywords hit top vs. absolute-top of page most often—and at what cost?,"SELECT
  campaign.name,
  ad_group.name,
  ad_group_criterion.keyword.text,
  metrics.impressions,
  metrics.clicks,
  metrics.average_cpc,
  metrics.top_impression_percentage,
  metrics.absolute_top_impression_percentage
FROM keyword_view
WHERE
  ad_group_criterion.status = ENABLED
  AND segments.date DURING LAST_30_DAYS
LIMIT 50000","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
"On Display / Video, which creatives hit your view-through and completion-rate goals?","SELECT
  campaign.name,
  ad_group.name,
  ad_group_ad.ad.id,
  ad_group_ad.ad.type,
  metrics.impressions,
  metrics.video_views,
  metrics.view_through_conversions,
  metrics.video_quartile_p25_rate,
  metrics.video_quartile_p50_rate,
  metrics.video_quartile_p75_rate,
  metrics.video_quartile_p100_rate,
  metrics.average_cpv
FROM ad_group_ad
WHERE
  campaign.advertising_channel_type IN ('VIDEO','DISPLAY')
  AND segments.date DURING LAST_30_DAYS
LIMIT 10000","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."
Are any keywords limited by budget?,"SELECT
  campaign.name,
  campaign.status,
  campaign.serving_status,
  campaign_budget.amount_micros,
  metrics.search_impression_share,
  metrics.search_budget_lost_impression_share
FROM campaign
WHERE
  campaign.advertising_channel_type = SEARCH
LIMIT 1000","You translate natural-language questions about Google Ads into a SINGLE valid Google Ads Query Language (GAQL) query.
Output ONLY the GAQL query text—no commentary, no code fences, no labels, no leading/trailing blank lines. Hard rules (must follow ALL):Start with 'SELECT ' and DO NOT add a trailing semicolon.Use GAQL syntax ONLY. Never output SQL, SPARQL, JSON, YAML, markdown code fences, or prose. Choose EXACTLY ONE resource after FROM. Prefer these commonly selectable resources:customer, campaign, ad_group, ad_group_ad, asset (If a field isn’t selectable for your chosen resource, switch to a compatible one—usually customer/campaign/ad_group.).Use ONLY fields that are valid and selectable for the chosen resource: resource fields (e.g., campaign.id), metrics.*, and segments.*. NEVER use: GROUP BY, SELECT *, JOIN, WITH, subqueries, DISTINCT ON, HAVING, backticks (`), braces { }. If the question implies a time window (e.g., “today”, “yesterday”, “last 7 days”, “this month”, “last 30 days”, “this year”) include a date filter: WHERE segments.date DURING TODAY | YESTERDAY | LAST_7_DAYS | LAST_30_DAYS | THIS_WEEK | THIS_MONTH | THIS_YEAR. When ranking (e.g., “top”, “most”, “best”), include an ORDER BY on an appropriate metric (usually DESC) and a LIMIT. Prefer ORDER BY fields that are also present in SELECT (even though GAQL allows otherwise).Fix common names: use ad_group.id (NOT ad_group.ad_group_id) and ad_group.name (NOT ad_group.ad_group_name). Use appropriate segments for breakdowns only when asked (e.g., segments.device, segments.date). Do NOT invent fields. If a requested field is invalid or incompatible, replace it with the closest valid, commonly-used GAQL field that answers the intent while staying selectable for the chosen resource."