Search Ads 360 (SA360) is Google's enterprise search management platform, designed for advertisers who manage paid search campaigns across multiple engines. Its core value is normalizing data from Google Ads, Microsoft Ads, Yahoo Japan, Baidu, and other engines into a single reporting and optimization layer — with Floodlight conversion tracking providing a unified attribution framework across all channels.
This guide provides a complete reference of every dimension and metric available in Search Ads 360 as of 2026. We've organized them by category, explained what each one measures, and included practical context on when and how to use them for cross-engine reporting, bid strategy optimization, and conversion analysis.
What Are SA360 Dimensions vs Metrics?
Before diving into the full reference, it's important to understand the difference between dimensions and metrics in Search Ads 360 — and how they differ from native engine data.
Dimensions are descriptive attributes that identify and categorize your data. They include structural identifiers (engine account, campaign, ad group, keyword), configuration attributes (bid strategy, match type, device), and Floodlight activity definitions. Dimensions answer the question: "How do I want to slice this data?"
Metrics are quantitative measurements showing how your campaigns performed. SA360 pulls metrics from each connected engine (impressions, clicks, cost) and adds its own: Floodlight conversions, bid strategy performance, and cross-engine computed fields. Metrics answer the question: "What happened?"
The key difference from native engine reporting is that SA360 normalizes dimensions and metrics across engines. A "campaign" in Google Ads and a "campaign" in Microsoft Ads both map to the SA360 campaign dimension, enabling apples-to-apples comparison. Floodlight conversions provide a single measurement standard across all engines, replacing engine-specific conversion tracking.
How Is SA360 Data Structured?
SA360 data follows a hierarchy of Advertiser > Engine Account > Campaign > Ad Group > Ad / Keyword. The advertiser level represents your organization. Engine accounts are the connections to individual search engine accounts (e.g., a Google Ads account or a Microsoft Ads account). From there, the hierarchy mirrors native engine structures: campaigns contain ad groups, which contain ads and keywords.
SA360 overlays two additional data layers: Floodlight activities (conversion events defined in CM360) and bid strategies (automated bidding rules that span across campaigns and engines). Both of these layers have their own dimensions and metrics that don't exist in native engine reporting.
Engine Account Dimensions
Engine account dimensions identify the search engine connections within your SA360 advertiser account. These are the top-level organizational dimensions that enable cross-engine reporting and management.
| Dimension | API Field | Description |
|---|---|---|
| Advertiser ID | advertiserId | SA360 advertiser identifier (top-level organizational entity) |
| Advertiser Name | advertiserName | Name of the SA360 advertiser account |
| Engine Account ID | engineAccountId | SA360 identifier for the connected engine account |
| Engine Account Name | engineAccountName | Name of the engine account as defined in SA360 |
| Engine Type | engineType | Search engine: GOOGLE_ADS, MICROSOFT_ADVERTISING, YAHOO_JAPAN, BAIDU, YAHOO_GEMINI |
| External Engine Account ID | externalEngineAccountId | The native account ID in the engine (e.g., Google Ads CID, Microsoft Ads account number) |
| Account Currency | currencyCode | Currency used for billing and reporting in the engine account |
| Account Timezone | accountTimeZone | Timezone of the engine account for reporting purposes |
| Engine Account Status | engineAccountStatus | Connection status: ACTIVE, PAUSED, REMOVED, PENDING_LINK |
| Agency | agency | Agency identifier if the advertiser is managed through an agency account |
Campaign and Ad Group Dimensions
Campaign and ad group dimensions mirror native engine structures but are normalized across all connected engines. This normalization enables unified reporting — you can compare campaigns across Google Ads and Microsoft Ads using the same dimension names and hierarchical structure.
| Dimension | API Field | Description |
|---|---|---|
| Campaign ID | campaignId | SA360 identifier for the campaign |
| Campaign Name | campaignName | Name of the campaign as defined in the engine |
| External Campaign ID | externalCampaignId | Native engine campaign ID (e.g., Google Ads campaign ID) |
| Campaign Status | campaignStatus | Status: ACTIVE, PAUSED, REMOVED, ENDED |
| Campaign Type | campaignType | Campaign type from the engine: Search, Shopping, Performance Max, Dynamic Search, etc. |
| Campaign Budget | dailyBudget | Daily budget configured for the campaign in account currency |
| Campaign Labels | campaignLabels | SA360 labels applied to the campaign for custom grouping and filtering |
| Ad Group ID | adGroupId | SA360 identifier for the ad group |
| Ad Group Name | adGroupName | Name of the ad group as defined in the engine |
| External Ad Group ID | externalAdGroupId | Native engine ad group ID |
| Ad Group Status | adGroupStatus | Status: ACTIVE, PAUSED, REMOVED |
| Ad Group Type | adGroupType | Ad group type: SEARCH_STANDARD, SEARCH_DYNAMIC, SHOPPING_PRODUCT, etc. |
| Ad Group Default Bid | adGroupBid | Default bid for the ad group in account currency |
Ad Dimensions
Ad dimensions describe individual ads within ad groups. SA360 normalizes ad data across engines, allowing you to compare ad creative performance across Google Ads and Microsoft Ads in a unified view.
| Dimension | API Field | Description |
|---|---|---|
| Ad ID | adId | SA360 identifier for the ad |
| External Ad ID | externalAdId | Native engine ad ID |
| Ad Type | adType | Ad format: EXPANDED_TEXT_AD, RESPONSIVE_SEARCH_AD, SHOPPING_AD, DYNAMIC_SEARCH_AD, IMAGE_AD |
| Ad Status | adStatus | Status: ACTIVE, PAUSED, REMOVED, DISAPPROVED |
| Headline 1 | headline1 | First headline of the text ad |
| Headline 2 | headline2 | Second headline of the text ad |
| Headline 3 | headline3 | Third headline (for responsive search ads) |
| Description Line 1 | description1 | First description line of the ad |
| Description Line 2 | description2 | Second description line of the ad |
| Display URL | displayUrl | URL shown in the ad |
| Final URL | landingPageUrl | Destination URL the ad links to |
| Ad Labels | adLabels | SA360 labels applied to the ad for grouping and filtering |
Keyword Dimensions
Keyword dimensions describe the search terms you're bidding on and their configuration. Keywords are a fundamental dimension in search advertising — they define when your ads appear and are the primary lever for targeting intent-based audiences.
| Dimension | API Field | Description |
|---|---|---|
| Keyword ID | keywordId | SA360 identifier for the keyword |
| Keyword Text | keywordText | The actual keyword text you are bidding on |
| External Keyword ID | externalKeywordId | Native engine keyword ID |
| Match Type | keywordMatchType | Keyword match type: BROAD, PHRASE, EXACT, BROAD_MODIFIED (deprecated on Google) |
| Keyword Status | keywordStatus | Status: ACTIVE, PAUSED, REMOVED |
| Keyword Bid | keywordMaxCpc | Maximum CPC bid for the keyword in account currency |
| Effective Bid | effectiveBid | Actual bid after bid strategy adjustments (may differ from manual bid) |
| Keyword Landing Page | keywordLandingPage | Destination URL for this keyword (if different from ad-level URL) |
| Keyword Labels | keywordLabels | SA360 labels applied to the keyword for grouping and filtering |
| Search Query | searchQuery | Actual search term the user typed that triggered the ad (from Search Query Report) |
| Negative Keyword | isNegative | Whether this is a negative keyword (excluded from triggering ads) |
Floodlight Dimensions
Floodlight dimensions describe the conversion tracking framework that SA360 shares with Campaign Manager 360. Floodlight provides unified conversion measurement across all search engines and channels — a critical advantage for cross-engine optimization and attribution.
| Dimension | API Field | Description |
|---|---|---|
| Floodlight Activity ID | floodlightActivityId | Unique identifier for the Floodlight conversion activity |
| Floodlight Activity Name | floodlightActivityName | Name of the Floodlight activity (e.g., "Purchase", "Lead Form Submit", "Newsletter Signup") |
| Floodlight Activity Group | floodlightActivityGroup | Group or category the activity belongs to (e.g., "Sales", "Leads", "Engagement") |
| Floodlight Activity Tag | floodlightActivityTag | Tag string identifier used in the Floodlight tag code |
| Floodlight Configuration ID | floodlightConfigurationId | CM360 Floodlight configuration this activity belongs to |
| Counting Method | countingMethod | How conversions are counted: STANDARD (one per click), UNIQUE (one per user), TRANSACTIONS_COUNTER, ITEMS_SOLD_COUNTER |
| Attribution Model | attributionModel | How credit is assigned: LAST_CLICK, FIRST_CLICK, LINEAR, TIME_DECAY, POSITION_BASED, DATA_DRIVEN |
| Lookback Window (Click) | clickThroughLookbackWindow | Days after a click during which conversions are attributed (default 30 days) |
| Lookback Window (View) | viewThroughLookbackWindow | Days after an impression during which view-through conversions are attributed (default 1 day) |
| Custom Floodlight Variables | customFloodlightVariables | Custom variables passed with the Floodlight tag (u-variables) for additional segmentation |
Core Performance Metrics
Core metrics measure the fundamental delivery and cost of your search campaigns. SA360 imports these from each connected engine and normalizes them for cross-engine comparison. These are the baseline metrics for understanding campaign reach, traffic, and efficiency.
| Metric | API Field | Description | Formula / Notes |
|---|---|---|---|
| Impressions | impressions | Number of times your ads were shown on search results pages | Pulled directly from the engine. Definition is consistent across Google and Microsoft |
| Clicks | clicks | Number of clicks on your ads | Includes all click types (headline, sitelinks, call extensions, etc.) |
| CTR | ctr | Click-through rate | (Clicks ÷ Impressions) × 100 |
| CPC | avgCpc | Average cost per click | Cost ÷ Clicks |
| Cost | cost | Total cost in account currency | Actual expenditure as reported by the engine |
| Average Position | avgPos | Average ad position on the search results page | Deprecated by Google Ads in 2019 but still available in Microsoft Ads |
| Impression Share | imprShare | Percentage of eligible impressions your ads received | Impressions ÷ Estimated eligible impressions. Engine-specific metric |
| Lost IS (Rank) | lostImprShareRank | Impression share lost due to ad rank | Indicates bid or quality score issues |
| Lost IS (Budget) | lostImprShareBudget | Impression share lost due to budget constraints | Indicates budget is limiting potential reach |
| Top Impression Rate | topImpressionRate | Percentage of impressions shown above organic results | Google Ads metric — replaced average position for measuring prominence |
| Absolute Top Impression Rate | absTopImpressionRate | Percentage of impressions shown as the very first ad | Google Ads metric — the most prominent ad position |
Floodlight Conversion Metrics
Floodlight metrics measure the conversions and revenue attributed to your search campaigns through the CM360 Floodlight tracking system. These are SA360's primary conversion metrics — providing unified measurement across all connected search engines.
| Metric | API Field | Description | Formula / Notes |
|---|---|---|---|
| Floodlight Conversions | floodlightConversions | Total Floodlight conversion actions attributed to search clicks | Uses the attribution model and lookback window configured for each Floodlight activity |
| Floodlight Revenue | floodlightRevenue | Total revenue from Floodlight conversions | Revenue values passed through the Floodlight tag |
| CPA (Floodlight) | floodlightCpa | Cost per Floodlight conversion | Cost ÷ Floodlight Conversions |
| ROAS (Floodlight) | floodlightRoas | Return on ad spend from Floodlight revenue | Floodlight Revenue ÷ Cost |
| Conversion Rate (Floodlight) | floodlightConversionRate | Percentage of clicks that resulted in a Floodlight conversion | (Floodlight Conversions ÷ Clicks) × 100 |
| View-Through Conversions | floodlightViewThroughConversions | Conversions attributed to ad impressions (no click occurred) | Uses the view-through lookback window from the Floodlight activity config |
| Cross-Environment Conversions | crossEnvironmentConversions | Conversions that occurred on a different device than the ad click | Requires Google sign-in data for cross-device matching |
| Conversion by Activity | floodlightConversionsByActivity | Conversions broken down by individual Floodlight activity | Shows performance for each defined conversion event separately |
| Revenue Per Conversion | floodlightRevenuePerConversion | Average revenue per Floodlight conversion | Floodlight Revenue ÷ Floodlight Conversions |
Engine-Specific Metrics
SA360 exposes certain metrics that are specific to individual engines. These provide additional insight into ad quality and competitiveness but may not be directly comparable across engines since each engine calculates them differently.
| Metric | Engine | Description |
|---|---|---|
| Quality Score | Google Ads, Microsoft Ads | 1-10 score indicating keyword ad relevance, landing page experience, and expected CTR |
| Expected CTR | Google Ads | Predicted click-through rate relative to competitors: ABOVE_AVERAGE, AVERAGE, BELOW_AVERAGE |
| Ad Relevance | Google Ads | How closely the ad matches the keyword intent: ABOVE_AVERAGE, AVERAGE, BELOW_AVERAGE |
| Landing Page Experience | Google Ads | Quality of the landing page experience: ABOVE_AVERAGE, AVERAGE, BELOW_AVERAGE |
| Search Exact Match IS | Google Ads, Microsoft Ads | Impression share for exact match searches of your keywords |
| Search Lost Top IS (Rank) | Google Ads | Percentage of top-of-page impressions lost due to ad rank |
| Search Lost Absolute Top IS (Rank) | Google Ads | Percentage of absolute top-of-page impressions lost due to ad rank |
| Auction Insight Metrics | Google Ads | Competitive metrics: overlap rate, position above rate, top of page rate for competitors |
| Engine Conversions | All engines | Conversions as tracked by the engine's own conversion tracking (separate from Floodlight) |
| Engine Conversion Value | All engines | Revenue from engine-tracked conversions (may differ from Floodlight values) |
Bid Strategy Metrics
SA360 bid strategies use machine learning to optimize keyword bids across all connected engines toward defined performance targets. Bid strategy metrics help you understand how the algorithm is performing, whether it's meeting targets, and where opportunities exist to scale.
| Metric | Description |
|---|---|
| Bid Strategy Name | Name of the bid strategy applied to the campaign, ad group, or keyword |
| Bid Strategy Type | Strategy objective: TARGET_CPA, TARGET_ROAS, MAXIMIZE_CONVERSIONS, TARGET_SPEND, ECP (Enhanced CPC), POSITION |
| Bid Strategy Status | Current state: LEARNING, ACTIVE, LIMITED, INACTIVE. Learning phase typically lasts 1-2 weeks |
| Target CPA | The target cost per acquisition the bid strategy is optimizing toward |
| Target ROAS | The target return on ad spend the bid strategy is optimizing toward |
| Actual CPA | Actual cost per acquisition achieved by the bid strategy during the period |
| Actual ROAS | Actual return on ad spend achieved by the bid strategy |
| Target Achievement Rate | How close the bid strategy is to meeting its target — expressed as a percentage of target CPA or ROAS |
| Bid Adjustment | The factor applied to manual bids by the strategy. A value of 1.3 means bids were increased 30% |
| Headroom | Estimated additional conversions available at the current target — indicates whether there is room to scale by increasing budget |
| Estimated Conversions at Higher Spend | Projected conversion volume if budget or bids were increased, at various spend levels |
| Bid Strategy Conversion Source | Which conversion data the bid strategy optimizes against: Floodlight, engine conversions, or SA360-tracked conversions |
Audience and Targeting Breakdowns
Audience breakdowns let you segment search performance by user characteristics and targeting criteria. These dimensions help you understand which audience segments drive the best search performance and optimize bid adjustments accordingly.
| Dimension | Description |
|---|---|
| Device | Device type: Desktop, Mobile, Tablet. Critical for bid adjustment optimization |
| Day of Week | Day the ad was shown — used for day-parting analysis and bid scheduling |
| Hour of Day | Hour the ad was shown — used for intraday performance analysis |
| Network | Where the ad appeared: Search, Search Partners, Display (for campaigns with display expansion) |
| Country / Territory | Country-level geographic breakdown |
| Region / State | State or administrative region breakdown |
| City / Metro | City or metropolitan area breakdown |
| Audience Segment | Audience list applied to the campaign or ad group (remarketing lists, in-market, affinity, customer match) |
| Product Group | Shopping campaign product group dimension (for product-level performance) |
| Product Category | Google Merchant Center product category for Shopping campaigns |
| Product Brand | Brand attribute from the product feed for Shopping campaigns |
| Product Custom Label | Custom labels (0-4) from the product feed for Shopping campaign segmentation |
Cross-Engine Comparison Metrics
Cross-engine comparison is SA360's primary differentiator. These computed metrics and reporting capabilities let you evaluate search engine performance side by side using normalized data.
| Metric / Feature | Description |
|---|---|
| Cross-Engine CTR | CTR compared across engines for equivalent campaigns or keywords, normalized for impression volume differences |
| Cross-Engine CPC | Average CPC compared across engines — reveals which engine delivers cheaper clicks for the same keywords |
| Cross-Engine Conversion Rate | Floodlight conversion rate by engine — the definitive cross-engine conversion comparison using a single measurement standard |
| Cross-Engine ROAS | Floodlight ROAS by engine — identifies which engine delivers the best return per dollar spent |
| Cross-Engine CPA | Floodlight CPA by engine — shows which engine acquires customers most efficiently |
| Cross-Engine Spend Distribution | Percentage of total search spend allocated to each engine — used for budget reallocation analysis |
| Engine Performance Index | Composite score comparing engine efficiency across multiple metrics simultaneously |
| Incremental Conversion Analysis | Estimated additional conversions each engine contributes beyond what others would capture |
How to Use These Metrics for Cross-Engine Optimization
SA360's value is maximized when you use its unified data model for cross-engine decision making. Here's a framework for using the right metrics at each stage of search advertising optimization.
For budget allocation across engines
Compare Floodlight ROAS and Floodlight CPA across engine accounts. These use the same conversion tracking, making them directly comparable. Engine-native conversion metrics are not comparable because each engine counts conversions differently. Use headroom analysis from bid strategies to identify which engines have room to scale — then reallocate budget from engines hitting diminishing returns to engines with headroom.
For keyword strategy
Track keyword-level Floodlight conversion rate across engines. The same keyword may convert at very different rates on Google vs Microsoft due to audience composition differences. Use match type breakdowns to understand how broad vs exact match performs on each engine. Monitor search query reports from both engines to find keywords that perform well on one engine and could be expanded to the other.
For bid strategy management
Monitor bid strategy status — strategies in "learning" phase should not be evaluated against targets. Check target achievement rate weekly to assess strategy health. Use estimated conversions at higher spend to determine whether increasing budget would be profitable. If a strategy is consistently missing its target CPA, either loosen the target or review the underlying conversion volume — strategies with fewer than 15-20 conversions per week struggle to optimize.
For Floodlight conversion analysis
Break down Floodlight conversions by activity to understand which conversion types each engine drives best. Some engines may excel at purchase conversions while others drive more lead form submissions. Compare click-through vs view-through conversions — search campaigns should primarily drive click-through conversions. Monitor cross-environment conversions to understand the full conversion path across devices.
For creative optimization across engines
Compare ad-level CTR and conversion rate across engines for equivalent ad messaging. The same headline may perform differently on Google vs Microsoft due to audience demographics and SERP layout differences. Use SA360's unified ad reporting to identify winning messages that transfer across engines and engine-specific opportunities where tailored creative outperforms shared copy.
Common Mistakes When Analyzing SA360 Data
Avoid these common errors that lead to flawed cross-engine optimization decisions.
1. Comparing engine-native conversions across engines
Google Ads conversion tracking and Microsoft Ads UET count conversions using different methodologies, attribution windows, and deduplication logic. Comparing Google Ads purchases to Microsoft Ads purchases is misleading. Always use Floodlight conversions for cross-engine comparison — they provide a single measurement standard applied uniformly across all engines.
2. Evaluating bid strategies too early
SA360 bid strategies require a learning phase (typically 1-2 weeks and 15-20+ conversions per week) to calibrate. Evaluating performance during learning phase produces unreliable results. Check bid strategy status before drawing conclusions. Only compare bid strategy performance after the algorithm shows "Active" status and has been running for at least 2-3 weeks.
3. Ignoring impression share metrics
A campaign with strong ROAS but 20% impression share is leaving 80% of potential impressions on the table. Track lost impression share (budget) and lost impression share (rank) to understand why. Budget-limited campaigns need more spend. Rank-limited campaigns need better Quality Scores or higher bids. Ignoring impression share means missing major scaling opportunities.
4. Applying the same bid modifiers across engines
Mobile vs desktop performance varies significantly between Google and Microsoft. Google tends to have more mobile search volume; Microsoft skews desktop. Applying the same device bid modifier across both engines wastes budget. Analyze device breakdown metrics per engine and set engine-specific bid adjustments based on each engine's actual device performance data.
5. Not leveraging cross-engine keyword insights
SA360 lets you compare keyword performance across engines, but many advertisers manage keywords independently per engine. Use cross-engine keyword reports to identify keywords that convert well on one engine but aren't active on the other. Also compare search query reports across engines — Microsoft users may search using different terms than Google users for the same intent.
6. Conflating Floodlight attribution models
Different Floodlight activities can use different attribution models (last click, first click, data-driven, etc.). If your purchase activity uses last-click attribution and your lead activity uses data-driven attribution, the CPA numbers are not calculated on the same basis. Always check the attribution model dimension when comparing conversion metrics across different Floodlight activities. Standardize attribution models when doing cross-activity analysis.
