Total spend across all campaigns. Sibling to gads_roas in the executive view.
At a glance
The total amount the merchant paid Google for ad placement across every campaign in the account during the period, summed in the account’s billing currency. The single most important cost figure on the Google Ads side, and the denominator for ROAS, CPA, and every efficiency metric in the executive view. Brands that fly without watching this card daily routinely discover four-figure or five-figure overspends only when the monthly invoice arrives, by which point the spend cannot be recovered.
| What it counts | SUM(metrics.cost_micros) ÷ 1,000,000 across every campaign in the account, summed in the account’s primary billing currency. Includes Search, Shopping, Display, YouTube, Performance Max, and Demand Gen campaign types. |
| Cost basis | Accrual-based, the moment a click or impression is billed (not when Google’s invoice is generated). Spend appears in the card immediately even though the invoice arrives a month later. |
| Currency | Account currency (set when the Google Ads account was created and not changeable). Multi-account brands operating accounts in different currencies see each account’s spend in its own currency; the gads_spend_by_country card surfaces the multi-currency view. |
| VAT / tax treatment | Excludes VAT. Google adds VAT (or sales tax in the US) on top of the figure surfaced here as a separate invoice line. Brands reconciling card spend to invoice spend should add the local VAT rate (typically 20 percent in the UK, varying by US state, 0 percent for most B2B reverse-charge invoices in the EU). |
| Conversion attribution model | The spend itself is not attribution-affected; you paid Google what you paid Google regardless of attribution model. The interaction matters for efficiency metrics: if the account is on data-driven attribution, a campaign showing high spend with low ROAS may be feeding upstream conversions that Google attributes elsewhere. The gads_roas card surfaces this. |
| Bot / invalid traffic | Google credits invalid clicks (bot traffic, accidental clicks, automated bid abuse) within 60 days. The credit appears as a negative cost adjustment in the period the credit was issued, NOT in the period the invalid click occurred. Brands tracking month-over-month spend may see “negative spend” anomalies on credit-issuance days; this is normal and the gads_alert_wasted_spend_burst card excludes these credits to avoid false alarms. |
| Auto-applied recommendations | If the account has Google’s auto-applied recommendations enabled (a default Google increasingly pushes), spend can grow above plan because Google’s auto-actions raise budgets, broaden keywords, or activate audience expansions without explicit merchant approval. The gads_overspending card and gads_alert_wasted_spend_burst flag this pattern. |
| Smart Bidding behaviour | Smart Bidding (tCPA, tROAS, Maximize Conversions, Maximize Conversion Value) controls bids dynamically inside a fixed daily budget. Daily budgets can spend up to 2x on high-opportunity days (Google smooths to the budget over the calendar month). Brands seeing daily spend at 1.4-1.8x of nominal daily budget should not panic; the monthly cap is what’s enforced. |
| Performance Max accounting | Performance Max campaigns spend across Search, Shopping, Display, and YouTube inventory simultaneously. The card shows the total Performance Max spend; the channel-level decomposition is not available via the Google Ads API (a notable transparency gap that affects reconciliation with channel-specific spend cards). |
| Time window | T/7D/30D vsP (today, 7 days, and 30 days vs prior periods). The “today” view is intra-day fluctuating because Google reports spend with a 3-hour delay in the API. |
| Alert trigger | burn rate >2 sigma vs 30D baseline (a daily spend that exceeds the rolling 30-day mean by more than two standard deviations). Captures both runaway-spend events (auto-applied recommendation went wrong) and aggressive-spending campaign-launch days. |
| Sentiment key | gads_spend_burn |
| Roles | owner, marketing, finance |
Calculation
Calculated automatically from your Google Ads data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A US-based DTC home goods brand on Shopify running a £45,000/month Google Ads programme split across Search, Shopping, Performance Max, and a small YouTube remarketing layer. Snapshot for the 30-day window ending Wednesday 15 May 26.| Campaign | Type | 30-day spend | Conversions | Revenue | ROAS |
|---|---|---|---|---|---|
| Brand search (own brand keywords) | Search | $4,200 | 1,840 | $185,200 | 44.1 |
| Non-brand search (category keywords) | Search | $11,800 | 620 | $58,800 | 5.0 |
| Shopping standard (product feed) | Shopping | $9,400 | 1,180 | $103,200 | 11.0 |
| Performance Max (catch-all) | Performance Max | $14,200 | 1,920 | $148,400 | 10.5 |
| YouTube remarketing | Video | $2,800 | 142 | $9,800 | 3.5 |
| Display retargeting | Display | $1,800 | 88 | $4,200 | 2.3 |
| Account total | $44,200 | 5,790 | $509,600 | 11.5 |
- The 45,000/month plan within 1.8 percent variance, healthy for budget governance. No alert fires here because the spend rate is within the plan envelope. The board-level number tells the right story; the diagnostic value sits in the per-campaign decomposition.
- Brand search at 44.1x ROAS is the typical pattern but raises a strategic question. Brand search is people who already searched for the merchant by name; they were going to convert anyway. The spend on brand search is partly defensive (preventing competitors from bidding on the merchant’s brand name) and partly opportunistic (intercepting customers Google might otherwise route through organic results). Brands debating whether to cut brand search to zero often do not realise that organic share of brand-name searches drops 30-40 percent when paid is removed because Google demotes organic clicks for queries with active paid auctions. The 44x ROAS is real but the incremental ROAS (revenue from paid that would not have come through organic) is closer to 8-12x.
- Non-brand search at 5x ROAS is the genuine demand-generation engine and should be the primary focus for both growth and efficiency optimisation. A 1.2x improvement in non-brand search ROAS adds roughly 44,000 but is largely attribution-shift rather than incremental. Smart Bidding tROAS adjustments compound here.
- **Performance Max at 14,200 went to Search vs Shopping vs Display vs YouTube) is not visible in the API. Brands relying on Performance Max for more than 25 percent of total spend should request the channel-distribution report from their Google account manager; without it, optimisation is blind.
- YouTube remarketing at 3.5x and Display retargeting at 2.3x are the weakest performers. Both are sub-fold-line ROAS for a brand whose blended target is 8x. Two interpretations: (a) these are upper-funnel awareness layers whose value is in assist conversions not in last-click revenue, and the cross-channel attribution (Vortex Mind’s Customer Recovery Opportunity report) shows their assist value; (b) they are genuine waste and should be cut. The right diagnostic is to pause them for 14 days and watch whether non-brand search and brand search efficiency degrade: if they do, the awareness layers were doing real work; if they do not, the spend was waste.
-
The Vortex Mind Paid Traffic Waste report runs this analysis automatically: it ranks campaigns by ROAS, surfaces zero-conversion spend, flags Performance Max channel-distribution opacity, and proposes specific paused-campaign tests with statistical confidence intervals. The headline
gads_total_spendcard surfaces “are we within budget”; the Paid Traffic Waste report surfaces “is this spend doing meaningful work”.
- Decompose by campaign,
gads_spend_by_campaign. The spike concentrates somewhere; identify which campaign drove it. - Check for auto-applied recommendations in the Google Ads dashboard. Google’s “Recommendations” tab shows recently auto-applied changes; budget increases, audience expansions, and keyword broadening are the usual culprits. Roll back the auto-application if the recommendation was not deliberately approved.
- Cross-reference with
gads_overspendingwhich surfaces campaigns spending above their nominal daily budget for sustained periods. Smart Bidding can do this within a calendar-month cap, but sustained overspend across multiple campaigns is the failure mode. - Pair with
gads_roas. A spend spike with steady ROAS is a “good problem” (more demand at the same efficiency); a spend spike with falling ROAS is a “bad problem” (more spend chasing weakening response). The two together drive the response. - Check
gads_alert_disapproved_burstfor ad-disapproval-induced spend pattern shifts. A wave of disapproved ads can leave the budget concentrated on a smaller set of remaining ads, raising effective CPC and total spend without merchant action.
| Time horizon | Action |
|---|---|
| First 1 hour after alert | Check Google Ads dashboard for auto-applied recommendations in the last 24 hours; roll back unintended ones immediately. |
| First 4 hours | Decompose by campaign type. Search vs Shopping vs Performance Max vs Display patterns each suggest different fixes. |
| First 24 hours | Cross-reference with ROAS trend. Determine whether the spend spike is “demand-driven” (incoming traffic surge) or “auction-driven” (competitor bid activity raising CPCs without traffic increase). |
| First week | If sustained, brief leadership with the decomposition. The Vortex Mind Paid Traffic Waste report runs the same decomposition automatically and is the executive-ready version. |
Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
gads_total_revenue | The numerator alongside spend’s denominator. ROAS = revenue ÷ spend; both numbers drive the efficiency calculation. |
gads_roas | The headline efficiency view that pairs with this spend card in the executive overview. |
gads_spend_trend | The daily-granularity view for spotting in-period spikes that the 30-day total may smooth over. |
gads_spend_by_campaign | The campaign-level decomposition. Required for any spend-spike investigation. |
gads_spend_by_country | The geographic decomposition for multi-market brands. |
gads_spend_by_device | The device-level decomposition. Mobile vs desktop spend patterns reveal Smart Bidding behaviour and audience-quality differences. |
gads_spend_by_hour | The hourly decomposition. Useful for identifying spend concentration in low-conversion windows. |
gads_overspending | Campaigns spending above their nominal daily budget. Smart Bidding can do this within monthly caps, but unmonitored overspend is the failure mode. |
gads_underspending | The inverse view, campaigns failing to spend their allocated budget. Often signals impression-share constraints or budget-allocation issues. |
gads_wasted_spend | Spend on impressions or clicks that produced zero conversion attribution. Where to start when looking for cuts. |
gads_zero_conversion_spend | Stricter version of wasted-spend: campaigns with literally zero conversions in the period despite spend. |
gads_alert_wasted_spend_burst | The alert that fires when wasted-spend exceeds a velocity threshold. |
gads_xc_revenue_share | Cross-channel view comparing Google Ads spend share to revenue share, alongside email, SEO, and other channels. |
Amazon Ads total_spend | The Amazon parallel for brands running both. Marketplace-vs-DTC spend allocation discussions live here. |
Meta Ads total_spend | The Meta parallel. Cross-platform paid-mix decisions use both numbers. |
Reconciling against the vendor’s own dashboard
Where to look in Google Ads’s own dashboard:- Google Ads → Campaigns is the primary view. The “Cost” column for the same date range is the closest 1-to-1 comparison to this card. Set the date picker to match the Vortex IQ period.
- Google Ads → Tools → Billing → Summary (ads.google.com/aw/billing/summary) shows the invoice-level totals. This is where VAT is added and where invalid-click credits appear; brands reconciling card spend to bank-statement debits should anchor here.
- Google Ads → Reports for custom decompositions across campaign type, device, geo, network. Save the template once for repeated reconciliation queries.
| Reason | Direction | What to do |
|---|---|---|
| Time zone. Google Ads dashboard uses the account’s configured time zone; Vortex IQ uses UTC for period boundaries. | Boundary days differ | Largest impact on T (today) and 7D windows; for 30D the drift averages out. For UK brands on a London time zone GA account, the drift is typically 4-7 percent of single-day spend. |
| Refresh lag. Google reports spend with a 3-hour delay in the API; the Vortex IQ refresh cadence (every 6 hours) compounds this. | Vortex IQ lower for the most recent 6-9 hour window | Wait for next refresh; check last_synced_at in the card metadata. The dashboard catches up earlier. |
| Invalid-click credits. Google issues credits within 60 days of the invalid click. Credits appear as negative cost on the credit-issuance day, not the original click day. | Either direction depending on credit timing | Cross-reference with the billing summary, which shows credits as separate line items. |
| VAT. This card excludes VAT; the billing summary includes it. | Vortex IQ lower by VAT rate when comparing to billing summary | Add the local VAT rate (typically 20 percent in the UK, varying by US state) to compare against billing-summary totals. |
| MCC vs single-account view. If the merchant operates a Manager (MCC) account aggregating multiple sub-accounts, Vortex IQ’s view depends on which account is connected. Connecting only the MCC may show child-account spend that’s not visible in single-account dashboards, and vice versa. | Either direction | Confirm whether the Vortex IQ connection is at MCC or single-account level. The connector’s safe-credentials view exposes the connected customer_id. |
| Pending bills (post-pay accounts). Some accounts use post-pay billing where Google issues an invoice when spend reaches a threshold. The “current bill” view in the dashboard may differ from the period spend view by the unbilled amount. | Either direction | The campaign-level Cost column is the cleaner comparison; avoid the billing summary for short-period reconciliations. |
| Comparison | Expected relationship | When divergence is legitimate |
|---|---|---|
gads_total_spend ↔ gads_total_revenue | ROAS = revenue ÷ spend | Both numbers come from the same customer API resource, so they share time-zone and refresh-lag timing exactly. Cross-card divergence indicates a bug in the metric pipeline, not a data condition. |
gads_total_spend ↔ Shopify Marketing → Google Ads spend | Should match if Shopify’s Google Ads integration is connected | Shopify pulls spend from the same Google Ads API; a mismatch usually indicates Shopify is connected to a different customer_id than Vortex IQ. |
gads_total_spend ↔ GA4 traffic_acquisition paid clicks revenue cost | GA4 cost figures should match Google Ads spend (Google auto-imports) | When auto-import is misconfigured, GA4 shows zero cost for paid traffic. The fix is in GA4 admin, not in the Vortex IQ card. |
gads_total_spend ↔ Stripe / bank statement debits | Bank statement = (spend × (1 + VAT)) - any invalid-click credits for the bill cycle | Multi-month spend never matches bank debits exactly because the bill cycle and the calendar month are different. Use 90-day reconciliation for finance close. |
Known limitations / merchant FAQs
My total spend is up 30 percent month-over-month but my campaign budgets did not change. What happened? Three common causes, in order of likelihood. (1) Auto-applied recommendations: Google’s auto-apply feature can raise budgets, broaden keywords, or activate audience expansions without merchant intervention. Check Google Ads → Recommendations → Auto-applied for the last 30 days. (2) Smart Bidding behaviour during high-opportunity periods: tCPA and Maximize Conversions can spend up to 2x of the daily budget on high-opportunity days; if the period included a major shopping day (BFCM, Prime Day equivalent, or a category-specific peak), this is normal. (3) Auction pressure increase: competitor bid activity drives up CPCs, and a fixed budget then buys fewer clicks at higher cost. The blended figure looks unchanged for clicks but spend rises. Cross-referencegads_cpc_trend to confirm.
Why is my Vortex IQ spend lower than my Google Ads invoice?
The invoice includes VAT (or sales tax in the US); this card excludes VAT. Add the local VAT rate to reconcile. For UK merchants this is typically 20 percent; for EU B2B reverse-charge invoices it is 0 percent; for US accounts the sales tax varies by state. The card matches the campaign-level “Cost” column in the dashboard, not the billing summary.
Should I cut Google Ads spend if ROAS is below my target?
Not without further analysis. Two questions matter. (1) Is the under-target ROAS uniform or concentrated? A blended 4x ROAS against a 6x target may mask a 12x brand-search component plus a 2x Performance Max component. Cutting the Performance Max layer might fix the blended number; cutting brand search would not. (2) Are the under-performing campaigns providing assist value? Upper-funnel campaigns (Display, YouTube, broad-match Search) often have low last-click ROAS but contribute to assist conversions visible only in cross-channel attribution. The Vortex Mind Customer Recovery Opportunity report quantifies this. Cutting paid spend without understanding assist contribution is the most common avoidable revenue loss in DTC ecommerce.
Why does my “today” spend appear to grow throughout the day, sometimes by hours after I make changes?
Google reports spend with a 3-hour delay in the API. Spend on impressions and clicks that happened at 09:00 may not appear in the API until 12:00. The Vortex IQ refresh cadence (every 6 hours) means today’s view always shows partial-day spend with up to a 9-hour delay. For real-time monitoring during BFCM or major launches, the Google Ads dashboard’s “Today” view is closer to real-time because it uses internal data not exposed to the API. The card is accurate for periods of 7 days or longer; “today” is for trend-direction only.
My account spends in USD but I report in GBP. How do I get a single number?
The card surfaces spend in the account’s billing currency. Cross-currency consolidation is a downstream concern; merchants needing a single GBP figure should multiply by the period’s average GBP/USD exchange rate. Vortex IQ does not perform this conversion automatically because (a) the right rate to use depends on the brand’s accounting policy (period-average, period-end, transaction-date), and (b) FX volatility means a single conversion can mislead during fast-moving periods. The gads_spend_by_country card surfaces the multi-account view if the merchant operates separate accounts per market.
My spend dropped to zero overnight. Did the connector break?
Possibilities, in order of likelihood. (1) Account suspension: Google can suspend an account for policy violations (often without warning). Check Google Ads → Tools → Status for an account-level alert. (2) Billing failure: a card on file expired and Google paused all campaigns until billing is updated. Check Tools → Billing → Settings. (3) Manual all-campaign pause: someone with account access paused all campaigns. Check Audit Log. (4) API permission revoked: the OAuth token Vortex IQ uses to query the account was revoked. Reconnect from the Sources page. (5) Genuine zero-spend day, rare but possible if all campaigns hit their daily budget caps simultaneously and Google had no eligible auctions; the dashboard would also show zero in that case.
Can Vortex IQ pause campaigns or cap spend automatically?
Read-only by design. Vortex IQ surfaces spend patterns, anomalies, and waste signals; the merchant’s marketing team executes inside Google Ads. The Vortex Mind Paid Traffic Waste report generates merchant-side Actions (specific campaigns to pause, with confidence intervals) but the pause itself sits with the merchant. This is deliberate; an automated pause-loop on a 5-figure-per-day budget is a high-blast-radius operation that benefits from human approval at each step.
Is total spend the right north-star, or should I track ROAS or revenue instead?
Spend is the cost ceiling that frames every efficiency metric, but it is not a north-star on its own. The right framing: revenue is the goal, ROAS is the unit economics, spend is the leverage you apply to reach the goal. Reporting spend without revenue or ROAS is meaningless; reporting revenue or ROAS without spend hides the cost of acquisition. Most brands report all three together as a triplet. The Executive Command Centre on the Nerve Centre dashboard surfaces spend, revenue, and ROAS side-by-side for exactly this reason.
Why does Performance Max spend dominate but I cannot see what it is doing?
This is a real and widely-acknowledged transparency gap with Performance Max. Google does not expose the channel-level breakdown (Search vs Shopping vs Display vs YouTube) via the API or the standard dashboard. Brands relying on Performance Max for more than 25 percent of total spend should request the channel-distribution report from their Google account manager (typically a quarterly export). Without it, optimisation is genuinely blind, which is one reason the gads_wasted_spend card is particularly valuable for Performance-Max-heavy brands; it surfaces zero-conversion spend that Performance Max’s optimisation should have prevented but did not.