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.

DimensionAPI FieldDescription
Advertiser IDadvertiserIdSA360 advertiser identifier (top-level organizational entity)
Advertiser NameadvertiserNameName of the SA360 advertiser account
Engine Account IDengineAccountIdSA360 identifier for the connected engine account
Engine Account NameengineAccountNameName of the engine account as defined in SA360
Engine TypeengineTypeSearch engine: GOOGLE_ADS, MICROSOFT_ADVERTISING, YAHOO_JAPAN, BAIDU, YAHOO_GEMINI
External Engine Account IDexternalEngineAccountIdThe native account ID in the engine (e.g., Google Ads CID, Microsoft Ads account number)
Account CurrencycurrencyCodeCurrency used for billing and reporting in the engine account
Account TimezoneaccountTimeZoneTimezone of the engine account for reporting purposes
Engine Account StatusengineAccountStatusConnection status: ACTIVE, PAUSED, REMOVED, PENDING_LINK
AgencyagencyAgency 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.

DimensionAPI FieldDescription
Campaign IDcampaignIdSA360 identifier for the campaign
Campaign NamecampaignNameName of the campaign as defined in the engine
External Campaign IDexternalCampaignIdNative engine campaign ID (e.g., Google Ads campaign ID)
Campaign StatuscampaignStatusStatus: ACTIVE, PAUSED, REMOVED, ENDED
Campaign TypecampaignTypeCampaign type from the engine: Search, Shopping, Performance Max, Dynamic Search, etc.
Campaign BudgetdailyBudgetDaily budget configured for the campaign in account currency
Campaign LabelscampaignLabelsSA360 labels applied to the campaign for custom grouping and filtering
Ad Group IDadGroupIdSA360 identifier for the ad group
Ad Group NameadGroupNameName of the ad group as defined in the engine
External Ad Group IDexternalAdGroupIdNative engine ad group ID
Ad Group StatusadGroupStatusStatus: ACTIVE, PAUSED, REMOVED
Ad Group TypeadGroupTypeAd group type: SEARCH_STANDARD, SEARCH_DYNAMIC, SHOPPING_PRODUCT, etc.
Ad Group Default BidadGroupBidDefault 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.

DimensionAPI FieldDescription
Ad IDadIdSA360 identifier for the ad
External Ad IDexternalAdIdNative engine ad ID
Ad TypeadTypeAd format: EXPANDED_TEXT_AD, RESPONSIVE_SEARCH_AD, SHOPPING_AD, DYNAMIC_SEARCH_AD, IMAGE_AD
Ad StatusadStatusStatus: ACTIVE, PAUSED, REMOVED, DISAPPROVED
Headline 1headline1First headline of the text ad
Headline 2headline2Second headline of the text ad
Headline 3headline3Third headline (for responsive search ads)
Description Line 1description1First description line of the ad
Description Line 2description2Second description line of the ad
Display URLdisplayUrlURL shown in the ad
Final URLlandingPageUrlDestination URL the ad links to
Ad LabelsadLabelsSA360 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.

DimensionAPI FieldDescription
Keyword IDkeywordIdSA360 identifier for the keyword
Keyword TextkeywordTextThe actual keyword text you are bidding on
External Keyword IDexternalKeywordIdNative engine keyword ID
Match TypekeywordMatchTypeKeyword match type: BROAD, PHRASE, EXACT, BROAD_MODIFIED (deprecated on Google)
Keyword StatuskeywordStatusStatus: ACTIVE, PAUSED, REMOVED
Keyword BidkeywordMaxCpcMaximum CPC bid for the keyword in account currency
Effective BideffectiveBidActual bid after bid strategy adjustments (may differ from manual bid)
Keyword Landing PagekeywordLandingPageDestination URL for this keyword (if different from ad-level URL)
Keyword LabelskeywordLabelsSA360 labels applied to the keyword for grouping and filtering
Search QuerysearchQueryActual search term the user typed that triggered the ad (from Search Query Report)
Negative KeywordisNegativeWhether 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.

DimensionAPI FieldDescription
Floodlight Activity IDfloodlightActivityIdUnique identifier for the Floodlight conversion activity
Floodlight Activity NamefloodlightActivityNameName of the Floodlight activity (e.g., "Purchase", "Lead Form Submit", "Newsletter Signup")
Floodlight Activity GroupfloodlightActivityGroupGroup or category the activity belongs to (e.g., "Sales", "Leads", "Engagement")
Floodlight Activity TagfloodlightActivityTagTag string identifier used in the Floodlight tag code
Floodlight Configuration IDfloodlightConfigurationIdCM360 Floodlight configuration this activity belongs to
Counting MethodcountingMethodHow conversions are counted: STANDARD (one per click), UNIQUE (one per user), TRANSACTIONS_COUNTER, ITEMS_SOLD_COUNTER
Attribution ModelattributionModelHow credit is assigned: LAST_CLICK, FIRST_CLICK, LINEAR, TIME_DECAY, POSITION_BASED, DATA_DRIVEN
Lookback Window (Click)clickThroughLookbackWindowDays after a click during which conversions are attributed (default 30 days)
Lookback Window (View)viewThroughLookbackWindowDays after an impression during which view-through conversions are attributed (default 1 day)
Custom Floodlight VariablescustomFloodlightVariablesCustom 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.

MetricAPI FieldDescriptionFormula / Notes
ImpressionsimpressionsNumber of times your ads were shown on search results pagesPulled directly from the engine. Definition is consistent across Google and Microsoft
ClicksclicksNumber of clicks on your adsIncludes all click types (headline, sitelinks, call extensions, etc.)
CTRctrClick-through rate(Clicks ÷ Impressions) × 100
CPCavgCpcAverage cost per clickCost ÷ Clicks
CostcostTotal cost in account currencyActual expenditure as reported by the engine
Average PositionavgPosAverage ad position on the search results pageDeprecated by Google Ads in 2019 but still available in Microsoft Ads
Impression ShareimprSharePercentage of eligible impressions your ads receivedImpressions ÷ Estimated eligible impressions. Engine-specific metric
Lost IS (Rank)lostImprShareRankImpression share lost due to ad rankIndicates bid or quality score issues
Lost IS (Budget)lostImprShareBudgetImpression share lost due to budget constraintsIndicates budget is limiting potential reach
Top Impression RatetopImpressionRatePercentage of impressions shown above organic resultsGoogle Ads metric — replaced average position for measuring prominence
Absolute Top Impression RateabsTopImpressionRatePercentage of impressions shown as the very first adGoogle 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.

MetricAPI FieldDescriptionFormula / Notes
Floodlight ConversionsfloodlightConversionsTotal Floodlight conversion actions attributed to search clicksUses the attribution model and lookback window configured for each Floodlight activity
Floodlight RevenuefloodlightRevenueTotal revenue from Floodlight conversionsRevenue values passed through the Floodlight tag
CPA (Floodlight)floodlightCpaCost per Floodlight conversionCost ÷ Floodlight Conversions
ROAS (Floodlight)floodlightRoasReturn on ad spend from Floodlight revenueFloodlight Revenue ÷ Cost
Conversion Rate (Floodlight)floodlightConversionRatePercentage of clicks that resulted in a Floodlight conversion(Floodlight Conversions ÷ Clicks) × 100
View-Through ConversionsfloodlightViewThroughConversionsConversions attributed to ad impressions (no click occurred)Uses the view-through lookback window from the Floodlight activity config
Cross-Environment ConversionscrossEnvironmentConversionsConversions that occurred on a different device than the ad clickRequires Google sign-in data for cross-device matching
Conversion by ActivityfloodlightConversionsByActivityConversions broken down by individual Floodlight activityShows performance for each defined conversion event separately
Revenue Per ConversionfloodlightRevenuePerConversionAverage revenue per Floodlight conversionFloodlight 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.

MetricEngineDescription
Quality ScoreGoogle Ads, Microsoft Ads1-10 score indicating keyword ad relevance, landing page experience, and expected CTR
Expected CTRGoogle AdsPredicted click-through rate relative to competitors: ABOVE_AVERAGE, AVERAGE, BELOW_AVERAGE
Ad RelevanceGoogle AdsHow closely the ad matches the keyword intent: ABOVE_AVERAGE, AVERAGE, BELOW_AVERAGE
Landing Page ExperienceGoogle AdsQuality of the landing page experience: ABOVE_AVERAGE, AVERAGE, BELOW_AVERAGE
Search Exact Match ISGoogle Ads, Microsoft AdsImpression share for exact match searches of your keywords
Search Lost Top IS (Rank)Google AdsPercentage of top-of-page impressions lost due to ad rank
Search Lost Absolute Top IS (Rank)Google AdsPercentage of absolute top-of-page impressions lost due to ad rank
Auction Insight MetricsGoogle AdsCompetitive metrics: overlap rate, position above rate, top of page rate for competitors
Engine ConversionsAll enginesConversions as tracked by the engine's own conversion tracking (separate from Floodlight)
Engine Conversion ValueAll enginesRevenue 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.

MetricDescription
Bid Strategy NameName of the bid strategy applied to the campaign, ad group, or keyword
Bid Strategy TypeStrategy objective: TARGET_CPA, TARGET_ROAS, MAXIMIZE_CONVERSIONS, TARGET_SPEND, ECP (Enhanced CPC), POSITION
Bid Strategy StatusCurrent state: LEARNING, ACTIVE, LIMITED, INACTIVE. Learning phase typically lasts 1-2 weeks
Target CPAThe target cost per acquisition the bid strategy is optimizing toward
Target ROASThe target return on ad spend the bid strategy is optimizing toward
Actual CPAActual cost per acquisition achieved by the bid strategy during the period
Actual ROASActual return on ad spend achieved by the bid strategy
Target Achievement RateHow close the bid strategy is to meeting its target — expressed as a percentage of target CPA or ROAS
Bid AdjustmentThe factor applied to manual bids by the strategy. A value of 1.3 means bids were increased 30%
HeadroomEstimated additional conversions available at the current target — indicates whether there is room to scale by increasing budget
Estimated Conversions at Higher SpendProjected conversion volume if budget or bids were increased, at various spend levels
Bid Strategy Conversion SourceWhich 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.

DimensionDescription
DeviceDevice type: Desktop, Mobile, Tablet. Critical for bid adjustment optimization
Day of WeekDay the ad was shown — used for day-parting analysis and bid scheduling
Hour of DayHour the ad was shown — used for intraday performance analysis
NetworkWhere the ad appeared: Search, Search Partners, Display (for campaigns with display expansion)
Country / TerritoryCountry-level geographic breakdown
Region / StateState or administrative region breakdown
City / MetroCity or metropolitan area breakdown
Audience SegmentAudience list applied to the campaign or ad group (remarketing lists, in-market, affinity, customer match)
Product GroupShopping campaign product group dimension (for product-level performance)
Product CategoryGoogle Merchant Center product category for Shopping campaigns
Product BrandBrand attribute from the product feed for Shopping campaigns
Product Custom LabelCustom 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 / FeatureDescription
Cross-Engine CTRCTR compared across engines for equivalent campaigns or keywords, normalized for impression volume differences
Cross-Engine CPCAverage CPC compared across engines — reveals which engine delivers cheaper clicks for the same keywords
Cross-Engine Conversion RateFloodlight conversion rate by engine — the definitive cross-engine conversion comparison using a single measurement standard
Cross-Engine ROASFloodlight ROAS by engine — identifies which engine delivers the best return per dollar spent
Cross-Engine CPAFloodlight CPA by engine — shows which engine acquires customers most efficiently
Cross-Engine Spend DistributionPercentage of total search spend allocated to each engine — used for budget reallocation analysis
Engine Performance IndexComposite score comparing engine efficiency across multiple metrics simultaneously
Incremental Conversion AnalysisEstimated 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.