What you'll learn in this article
- The exact path I use to pull Google Ads reporting by state location targeting instead of the account-level average that hides everything
- Why the distribution of spend and conversions by state changes my budget decisions before any bid change
- The single most expensive misread of the google ads geographic report: treating location of interest as location of presence
- How the two report views (where users were, vs. where they showed interest) tell completely different stories on the same campaign
- The order I read the report in, so I don't cut a state that is actually pulling its weight
- When a state-level pattern is a real signal and when it is just thin data I should leave alone
Every account I inherit gets the same first look: I break performance down geographically before I touch a bid. Google Ads reporting by state location targeting is where account-level averages stop lying to me, because a campaign that looks healthy overall rarely performs the same in every state. Two or three states usually carry the account while a long tail quietly drains budget, and you cannot see that from the summary row.
This is how I work the google ads geographic report: where I pull it, how the by-state split reshapes budget, and the mistake that ruins geo decisions, reading it without separating location of interest from location of presence. The pillar overview of Google Ads reporting shows where this fits among the other reports.
How I pull the by-state report
The location report lives under the Locations view inside Campaigns. "State" is not a default row, you drill from country down to the region level for spend, conversions, value, and cost per conversion per state. Two views exist and are not interchangeable: one shows the physical location where users were when they engaged, the other shows the geographic areas users searched about, regardless of where they actually were. I toggle between both, then push the breakdown into a Looker Studio geo dashboard to keep the trend visible.
Why the distribution by state moves budget
The point of the report is not to admire the map, it is to reallocate. On one lead-gen account, five states produced roughly 70% of qualified leads well below target cost, while others ran two to three times more expensive with almost no volume. The account-level number looked fine, so nobody had touched it. Reading it by state made the call obvious: concentrate budget where efficient volume sits and stop subsidizing the tail. When a state pattern is stable, that is a signal worth feeding into Smart Bidding as a location-based input, so the bid strategy leans on the geographic evidence instead of blunt manual adjustments.
The error that ruins geo decisions: interest vs presence
This is the most important part. With the default location settings, your google ads geographic report can list a state where the user was never physically present, because they merely show interest in it. Someone in Chicago searching "plumbers in Miami" appears under Miami even though they are in Illinois. Reading that as "people in Florida" shifts budget to the wrong place.
According to Google's official documentation on location targeting in Google Ads, the default "Presence or Interest" option lets you show your ads to people who are in, regularly in, or have shown interest in your targeted locations. Location targeting can span countries, regions, cities, or a radius, and those targeting options each carry the same interest component that pollutes a naive state reading.
How I separate the two
Before I trust a state row, I check the view and the targeting set on the campaign. If it runs "Presence or Interest," I switch to the presence view to see where users actually were, then compare. A state huge in interest but tiny in presence means the demand is remote: for a local service business that is wasted spend, hurting conversion rates; for travel or e-commerce it may be valuable out-of-area demand. When interest traffic is not useful, I tighten toward presence or exclude those target areas, then export the raw state data into Sheets to document the change.