If you're building custom analytics for Google Shopping campaigns, understanding the Google Ads API metric fields is essential. Queries like metrics.conversions_value appearing in your Search Console indicate users are looking for guidance on these API fields. This guide covers the most important metrics available through the Google Ads API for Shopping campaign analysis.
The Google Ads API provides access to hundreds of metrics. For Shopping campaigns, we'll focus on the fields that matter most for tracking revenue, costs, conversions, and competitive position at the product level.
API Version Note
This guide covers Google Ads API v23 (released January 28, 2026). Field names and availability may vary slightly between versions. For the latest changes, see our Google Ads API v23 update guide or check the official API documentation for the most current reference.
Core Performance Metrics
These fundamental metrics track the basic performance of your Shopping ads: how often they're shown, clicked, and what they cost.
metrics.impressions
Type: INT64
Description: Count of how often your ads were shown on a search results page or website on the Google Network.
Use case: Track visibility and reach. Low impressions indicate bid, budget, or feed issues limiting your products' exposure.
metrics.clicks
Type: INT64
Description: The number of clicks your ads received.
Use case: Measure engagement. Clicks represent users actively interested in your products who visited your site.
metrics.ctr
Type: DOUBLE
Description: Click-through rate: the number of clicks divided by the number of impressions. Returned as a decimal (0.02 = 2%).
Use case: Evaluate ad appeal and relevance. Low CTR suggests poor titles, images, or pricing compared to competitors.
metrics.cost_micros
Type: INT64
Description: The sum of your cost-per-click (CPC) and cost-per-thousand impressions (CPM) costs during this period. Returned in micros (divide by 1,000,000 for actual currency).
Use case: Track ad spend. Essential for calculating ROAS and identifying wasted spend on non-converting products.
Important: Understanding Micros
The Google Ads API returns monetary values in "micros" to avoid floating-point precision issues. To convert: actual_cost = metrics.cost_micros / 1,000,000. For example, 2,500,000 micros = $2.50 USD.
metrics.average_cpc
Type: DOUBLE (micros)
Description: The total cost of all clicks divided by the total number of clicks received. Also in micros.
Use case: Monitor cost efficiency. Rising CPCs without corresponding conversion improvements reduce profitability.
Conversion Metrics
Conversion metrics are the heart of Shopping campaign performance. They tell you what actually matters: did clicks turn into sales, and how much revenue did they generate?
metrics.conversions
Type: DOUBLE
Description: The number of conversions for all conversion actions that are set to "Include in Conversions."
Use case: Track completed purchases attributed to your ads. This is typically your primary success metric for Shopping campaigns.
metrics.conversions_value
Type: DOUBLE
Description: The total value of conversions for all conversion actions that are set to "Include in Conversions." This is your revenue from Shopping ads.
Use case: Essential for calculating ROAS. Combined with cost data, this tells you if your ads are profitable.
ROAS calculation using API fields:
ROAS = metrics.conversions_value / (metrics.cost_micros / 1000000)
metrics.conversions_from_interactions_rate
Type: DOUBLE
Description: Conversions from interactions divided by the number of ad interactions (clicks for Shopping). This is your conversion rate.
Use case: Measure how effectively clicks convert to sales. Low rates indicate landing page, pricing, or trust issues.
metrics.cost_per_conversion
Type: DOUBLE (micros)
Description: The cost of ad interactions divided by conversions. Also known as Cost Per Acquisition (CPA).
Use case: Determine what you're paying for each sale. Compare to your target CPA based on product margins.
metrics.value_per_conversion
Type: DOUBLE
Description: The value of conversions divided by the number of conversions. This is your Average Order Value (AOV).
Use case: Understand revenue per transaction. Higher AOV can justify higher CPCs while maintaining profitability.
All Conversions vs. Conversions
Google Ads provides two sets of conversion metrics. Understanding the difference is crucial for accurate analysis:
| Field | Includes |
|---|---|
metrics.conversions |
Only conversion actions marked "Include in Conversions" |
metrics.all_conversions |
All conversions including cross-device, view-through, and secondary actions |
metrics.conversions_value |
Value of included conversions only |
metrics.all_conversions_value |
Value of all conversion types |
metrics.all_conversions
Type: DOUBLE
Description: The total number of conversions including cross-device conversions and conversions not marked "Include in Conversions."
Use case: Get a complete picture of conversion activity. The gap between all_conversions and conversions shows your cross-device and view-through attribution.
metrics.all_conversions_value
Type: DOUBLE
Description: The value of all conversions including cross-device and view-through conversions.
Use case: Capture the full revenue impact of your Shopping ads across all touchpoints.
Impression Share Metrics
Impression share metrics reveal how much of the available market you're capturing. These are critical for understanding growth opportunities and competitive position.
metrics.search_impression_share
Type: DOUBLE
Description: The impressions you've received on the Search Network divided by the estimated number of impressions you were eligible to receive. Returned as a decimal (0.65 = 65%).
Use case: Understand market coverage. Low impression share means competitors are showing when you're not.
metrics.search_click_share
Type: DOUBLE
Description: The clicks you've received on the Search Network divided by the estimated maximum number of clicks you could have received.
Use case: Measure market share of engaged shoppers. Click share higher than impression share indicates strong ad appeal.
metrics.search_top_impression_share
Type: DOUBLE
Description: The impressions you've received in the top location (above organic results) divided by the estimated number of top location impressions you were eligible to receive.
Use case: Track premium position visibility. Top positions drive significantly more clicks.
metrics.search_budget_lost_impression_share
Type: DOUBLE
Description: The percentage of time your ads weren't shown on the Search Network due to insufficient budget.
Use case: Identify scaling opportunities. High budget lost IS with good ROAS suggests increasing budget could capture more profitable conversions.
metrics.search_rank_lost_impression_share
Type: DOUBLE
Description: The percentage of time your ads weren't shown on the Search Network due to poor ad rank (bid x quality).
Use case: Diagnose visibility issues. High rank loss means increasing bids or improving feed quality could help.
Shopping-Specific Metrics and Segments
For Shopping campaigns, you'll often want product-level data. The shopping_performance_view resource combined with product segments gives you SKU-level analytics.
Key Segments for Product-Level Data
| Segment | Description |
|---|---|
segments.product_item_id |
The offer_id from your product feed (your SKU) |
segments.product_title |
The product title from your feed |
segments.product_brand |
The brand attribute from your feed |
segments.product_category_level1-5 |
Google product category hierarchy |
segments.product_custom_attribute0-4 |
Custom labels from your feed |
segments.date |
Daily breakdown of metrics |
Example GAQL Query for Product Performance
Here's a sample Google Ads Query Language (GAQL) query to retrieve product-level Shopping performance:
SELECT
segments.date,
segments.product_item_id,
segments.product_title,
segments.product_brand,
metrics.impressions,
metrics.clicks,
metrics.ctr,
metrics.cost_micros,
metrics.conversions,
metrics.conversions_value,
metrics.search_impression_share,
metrics.search_click_share
FROM shopping_performance_view
WHERE segments.date DURING LAST_30_DAYS
ORDER BY metrics.cost_micros DESC
LIMIT 1000
Pro Tip
When querying large date ranges, paginate your requests and consider using async processing. The API has rate limits and response size limits that can affect queries with thousands of products.
Additional Useful Metrics
Beyond the core metrics, these fields provide deeper insights for advanced analysis:
metrics.average_cost
Type: DOUBLE (micros)
Description: The average amount you pay per interaction. For Shopping, this is essentially the same as average CPC.
Use case: Monitor cost trends over time to identify competitive pressure changes.
metrics.cross_device_conversions
Type: DOUBLE
Description: Conversions that started on one device (e.g., mobile) and completed on another (e.g., desktop).
Use case: Understand the cross-device customer journey. High cross-device conversions suggest your mobile ads drive desktop purchases.
metrics.view_through_conversions
Type: DOUBLE
Description: Conversions from users who saw (but didn't click) your ad, then later converted.
Use case: Capture brand awareness impact. View-through conversions show influence beyond direct clicks.
metrics.engagement_rate
Type: DOUBLE
Description: How often people engage with your ad after it's shown. Engagements include clicks and other interactions.
Use case: Broader measure of ad effectiveness beyond just clicks.
Metrics Not Available for Shopping
Some Google Ads metrics aren't available or behave differently for Shopping campaigns:
- Quality Score - Not available for Shopping; feed quality factors work differently
- Search Terms - Available through search_term_view but requires additional permissions
- Ad-level metrics - Shopping doesn't have traditional ads; product data comes from your feed
- Keyword metrics - Shopping targets products, not keywords
Best Practices for API Data Analysis
1. Account for Conversion Lag
Conversions can be attributed up to 90 days after a click (depending on your settings). Recent data will understate true performance. For accurate analysis, exclude the last 7-14 days or use the conversion lag report to understand your typical delay. This is especially important when optimizing your Shopping campaigns based on recent performance data.
2. Handle Nulls and Zeros
Some metrics return null when there's insufficient data (especially impression share metrics). Your code should handle these cases:
impression_share = row.metrics.search_impression_share or 0
if impression_share > 0:
# Safe to use in calculations
3. Aggregate Appropriately
Some metrics can be summed (impressions, clicks, cost, conversions) while others must be recalculated from their components:
- Sum directly: impressions, clicks, cost_micros, conversions, conversions_value
- Recalculate: CTR (clicks/impressions), ROAS (value/cost), conversion rate (conversions/clicks)
- Average weighted: Impression share metrics (weight by eligible impressions)
4. Use Date Segments for Trends
Always include segments.date when building time-series dashboards. This lets you track performance changes over time and identify trends.
Key Takeaway
The most important API fields for Shopping analysis are: metrics.conversions_value (revenue), metrics.cost_micros (spend), metrics.conversions (sales), and metrics.search_impression_share (market coverage). Master these four and you can calculate ROAS, track profitability, and identify growth opportunities.
Frequently Asked Questions
What is metrics.conversions_value in Google Ads API?
metrics.conversions_value is the total monetary value of all conversions attributed to your ads. For e-commerce, this typically represents revenue from purchases. The value is returned as a decimal number representing the currency amount (not in micros).
Why does metrics.cost_micros return such large numbers?
Google Ads API returns cost in micros (millionths of a currency unit) to avoid floating-point precision issues. Divide by 1,000,000 to convert to your currency. For example, 1,500,000 micros equals $1.50 USD.
How do I get product-level metrics from the Google Ads API?
Query the shopping_performance_view resource with segments.product_item_id to get metrics broken down by individual products. This gives you impressions, clicks, cost, and conversions at the SKU level.
What's the difference between metrics.conversions and metrics.all_conversions?
metrics.conversions includes only your primary conversion actions (marked "Include in Conversions"), while metrics.all_conversions includes all conversion types including cross-device conversions, view-through conversions, and secondary conversion actions.
Conclusion
Understanding Google Ads API metrics is essential for building custom Shopping analytics. The fields covered in this guide—from basic performance metrics like metrics.impressions and metrics.clicks to critical business metrics like metrics.conversions_value and impression share—provide the foundation for comprehensive campaign analysis.
Key points to remember:
- Cost fields use micros (divide by 1,000,000) as documented in the Google Ads reporting guide
- Percentage fields return decimals (0.65 = 65%)
- Use
shopping_performance_viewwith product segments for SKU-level data - Account for conversion lag when analyzing recent data
- Understand the difference between conversions and all_conversions
For more on interpreting these metrics once you have the data, see our metrics glossary, ROAS guide, and analytics guide. Tools like SKU Analyzer automate the API data collection and present these metrics in a unified dashboard, saving you from building and maintaining custom integrations.