Waze Ads in Performance Max 2026: Navigation Inventory in 42 Markets
On September 4, 2026, Google quietly updated a help page. No blog post, no in-account notification. The change: Waze ad inventory is now available in 42 markets — all 27 EU member states plus the UK, Switzerland, Norway, Iceland, Liechtenstein, the US, Canada, Brazil, Mexico, Colombia, Argentina, Chile, Australia, Malaysia and Israel. Advertisers found out the way they usually do: impressions in a store-goal campaign moved, and a new line appeared in channel reporting. That is how most people learned that Waze ads in Performance Max had reached their market.
Waze ads in Performance Max are not a campaign type you switch on. They are inventory inside Performance Max for store goals, and there is no documented campaign-level toggle to exclude driver-facing placements. Which means the only lever you have is account structure and measurement discipline.
This article covers the format itself, the five prerequisites you need before launch, where the spend shows up in reporting, which verticals actually get store visits out of it, and how to isolate the inventory so your numbers stay readable.
Why Waze ads in Performance Max exist at all
Google acquired Waze in 2013 and ran its ad product on a separate platform for years. The advertising side relaunched in the US in July 2025, and on November 6, 2025 the inventory was folded into Performance Max alongside channel-level reporting. September 2026 is not a launch — it is a geographic expansion of the same formats into 41 additional markets.
The rationale is straightforward. A driver in a navigation app has already committed to moving to a physical location. They are not browsing a feed or researching a category. If your tire shop, drive-through or garden center sits 500 meters off their route, a brand impression at that exact moment is closer to a purchase than almost any display placement.
That is why the inventory is tied to store goals. It is not designed to produce clicks or web leads. It is designed to make a car turn.
What the driver actually sees
The single creative format is a branded square pin placed along the route — labeled as a Promoted Place when tapped, opening a location card with the address, hours and a “navigate here” action. No video, no three-line headlines, no carousels.
One limitation worth noting: QR code and barcode promotions do not serve on this inventory (nor on Search, Shorts or in-stream video). If your offer mechanic depends on scanning a code at the register, it will not travel here.
| Parameter | How it works |
|---|---|
| Campaign type | Performance Max for store goals only |
| Format | Branded route pin, Promoted Place card on tap |
| Location source | Linked Business Profile or affiliate locations |
| Radius | Set in the campaign, or determined automatically from travel-distance behavior, vertical, population density and competitors |
| Conversions | Store visits, store sales, local actions (directions, calls) |
| Standalone opt-out | Not documented as a campaign-level control |
Five prerequisites before you launch
- Verified locations and a live Business Profile link. Locations come from the linked profile or affiliate locations. If a chain has 40 stores and 31 are verified, 31 are advertised. Check verification status per location, not just the account-level link.
- Accurate addresses and hours. This traffic is physical. A stale address is not a wasted click — it is a customer arriving at a closed door. The place card pulls straight from the profile.
- A campaign-level store goal. Google’s documentation is internally inconsistent here: one section lists Store Visits, Store Sales or Local Actions (Directions) as eligible goals, another treats directions as mandatory. The safe read: enable local actions with directions so the inventory gets an unambiguous signal.
- Working visit measurement. Without store visit conversions you will see impressions and taps but no outcome. Visit modeling requires data volume and verified locations, and Google does not publish the threshold — small chains frequently sit below it.
- A deliberate radius. Leave it blank and the system decides based on how far people typically travel in your vertical. That default optimizes for reach, not for your unit economics. Drive-through coffee and a furniture warehouse do not share a radius.
Where the spend shows up
Channel-level reporting landed in Performance Max with API v23 in January 2026, splitting spend across Search, Shopping, YouTube, Display, Discover, Gmail and Maps. The documentation does not clarify whether Waze appears as a discrete channel or gets bundled into a broader local bucket — in practice, look at the local/Maps segment and watch visit trends alongside it.
How to read that report without over-interpreting it is covered in Performance Max channel-level reporting. The core caveat still applies: the report shows distribution, not control. You can see that 18% of budget went to local inventory. You cannot tell the system to make it 5%.
When a channel cannot be switched off, campaign structure becomes the switch. Isolate what you cannot exclude.
Who gets visits, and who only gets impressions
The inventory works where three conditions overlap: the purchase happens offline, the decision is fast, and the detour is small enough to take right now.
| Vertical | Potential | Why |
|---|---|---|
| Fuel, car wash, tires, auto service | High | The customer is already in the vehicle; need arises en route |
| Drive-through food and coffee | High | Impulse decision, minimal detour |
| Home improvement, building supplies, garden centers | Medium-high | Bulky goods mean people drive; radius is naturally wide |
| Grocery, roadside pharmacy | Medium | Works on commute routes, but store loyalty is sticky |
| Furniture, appliances, car dealerships | Medium | Long cycle, but a showroom visit is a valid conversion |
| Appointment-based services (clinics, salons) | Low | You cannot drop in; the conversion is not the visit |
| Pure e-commerce, B2B, SaaS | None | Store goals do not apply at all |
Geography matters as much as vertical. In a dense transit-first city, the share of drivers in your audience may be a fraction of what it is in a car-dependent suburb, and identical campaigns will return very different numbers. Segment by metro before you judge the channel.
How to isolate the inventory and keep measurement honest
- Separate goals into separate campaigns. Store goal in its own Performance Max campaign, with locations and local actions only. Online sales and lead gen elsewhere. Mixed together, local inventory competes for budget with channels that produce measurable online conversions, and you will never untangle the overlap — see campaign cannibalization between PMax, Search and Shopping.
- Set the radius manually at launch, based on where your customers actually come from: loyalty data, receipt postcodes, a two-question survey at the register.
- Check presence vs interest targeting. Offline almost always wants presence only — the cost of getting this wrong is explained in location targeting: presence vs interest.
- Wire measurement before launch. Store visits, local actions, and where possible offline conversion import from the POS or CRM. Otherwise you get a spend report with no answer to “did anyone show up”.
- Run a geo holdout. It is the only credible way to learn whether the inventory adds visits you would not have gotten anyway. Design details in incrementality and geo experiments.
The economics of a store visit
Local campaigns feel unreadable mostly because nobody has calculated what a visit is worth. Without that number there is no way to say whether traffic was cheap or expensive. Four steps, no analyst required:
- Visit-to-purchase rate. From the POS: transactions over footfall for the same period (door counter, Wi-Fi analytics, or a manual count across one representative week).
- Average order value and gross margin per location, not per chain — the spread between stores is routinely 2×.
- Acceptable share of margin you are willing to spend on acquisition.
- Target cost per visit = AOV × margin × acceptable share × visit-to-purchase rate.
A worked example (illustrative numbers, not a benchmark): $32 AOV, 35% margin, 25% acceptable acquisition share, 40% of visitors buy. Target cost per visit = 32 × 0.35 × 0.25 × 0.4 ≈ $1.12. Visits cheaper than that are profitable; more expensive ones are not. Everything else — CTR, impressions, channel share — is diagnostic, not a decision criterion.
The number gets more generous once repeat purchase is included, since a first visit often starts a relationship rather than ending one. Method in unit economics and LTV.
The place card is your creative
There are no headlines, descriptions or CTAs in this inventory. The only thing you control is the Business Profile, which makes creative work look unusual:
- Brand icon. The pin is small and seen peripherally by someone driving. An intricate logo with small type disappears; a simple high-contrast shape survives.
- Location name. Not “Acme Holdings Retail Unit 7” — the name a human recognizes.
- Photos and category. The card opens on tap and the driver decides in about a second whether the detour is worth it. Dark five-year-old photos argue against you.
- Hours, including holidays. An error here does not cost a click, it costs a customer who drove to a closed door and will remember it.
- Reviews and rating. Displayed right next to the place and more persuasive than any offer. It is the one creative asset you cannot buy — only earn.
The paradox of local advertising is that most of the performance work happens outside Google Ads: in the profile and in the store itself.
The first 30 days, week by week
| Period | Do | Don’t |
|---|---|---|
| Week 1 | Launch the isolated campaign, record pre-launch store baselines, define holdout regions | No bid or budget edits, no added goals |
| Week 2 | Confirm all locations are serving; adjust radius if reach clearly mismatches the real catchment | No conversion conclusions — data is not mature |
| Week 3 | First channel-report read, cross-checked against local actions | Don’t pause over “expensive” visits |
| Week 4 | Test versus holdout comparison, cost-per-visit calculation, scaling decision | Don’t shuffle budgets between campaigns mid-measurement |
One change at a time is the rule for this month. Local conversions are modeled, delayed and noisy — change radius, budget and goals on the same day and no shift will ever be explainable.
Mistakes that show up in week one
- Adding a store goal to an existing Performance Max campaign “just to test”. New goal, new inventory, reset learning — and no way to attribute the dip afterwards. What actually resets the algorithm is covered in the Smart Bidding learning period.
- Judging the channel by CTR. A tap on a route pin is not a click on a text ad. The outcome metric is visits and local actions.
- Launching on unverified locations. Half the chain silently sits out and you spend a month analyzing “weak results” that were never a full test.
- Reading three-day data. Store visits are modeled and arrive late — see conversion windows and conversion lag.
- Ignoring weather and seasonality. Driving volume is volatile. A rainy week against a sunny one is not a test result.
Launch checklist
- Verify every location in the Business Profile and confirm the Google Ads link is active.
- Refresh addresses, hours, phone numbers and photos — the place card renders them directly.
- Set up measurement: store visits, local actions with directions, offline sales import if available.
- Create a dedicated Performance Max store-goal campaign instead of editing an existing one.
- Set the radius from real catchment data, not from a default.
- Restrict location targeting to presence and exclude irrelevant regions.
- Hold out a matched set of regions for a 4–6 week incrementality read.
- After a month, reconcile channel-level reporting with store-level sales — look for lift where the local share of spend is highest.
The bigger pattern
Waze fits a trend that defined Google Ads in 2026: Performance Max keeps absorbing inventory, and advertisers keep trading toggles for signals. The same story played out with local inventory ads enabled by default and with Display campaigns migrating into Demand Gen.
In that environment, the advantage belongs to accounts with clean structure, real offline measurement and enough data volume for modeling to work — not to whoever finds a hidden checkbox. Teams running many markets and client structures in parallel usually solve the operational half of that with Google Ads agency accounts; the rest of what we do is on the PPC Rebels services page.
Two companion pieces published alongside this one cover adjacent shifts: AI Mode native checkout and agentic commerce, where the purchase leaves your site entirely, and the 500×500 product image requirement, which will remove non-compliant products from Shopping outright.
FAQ: Waze ads in Performance Max
Can I run Waze ads as a standalone campaign?
No. The inventory exists only inside Performance Max for store goals. There is no separate Waze campaign type in Google Ads.
How do I opt out of Waze placements?
No campaign-level exclusion is documented. The practical approach is to avoid store goals in campaigns where you do not want local inventory, and keep local objectives in an isolated campaign.
Which countries are eligible?
42 markets: all 27 EU states, the UK, Switzerland, Norway, Iceland, Liechtenstein, the US, Canada, Brazil, Mexico, Colombia, Argentina, Chile, Australia, Malaysia and Israel. Japan, India, South Korea, Turkey, New Zealand and African markets are not included.
Does the inventory get its own budget?
No. It spends from the Performance Max campaign budget, which is exactly why a dedicated store-goal campaign matters — it caps the total pool the inventory can draw from.
What conversions can it produce?
Local actions such as directions and calls, store visits and store sales. Do not expect on-site conversions; the format does not send traffic to a website.
Do I need a Business Profile?
Yes. Locations come from a linked Business Profile or affiliate locations. Without verified locations there is nothing to promote.
Is there a minimum spend or minimum number of stores?
Google has not published spend minimums or location thresholds for the new markets. Visit measurement, however, needs volume — a one or two location business may never see a store visit report populate.
Will Waze appear as its own line in reporting?
Unclear. Channel-level reporting exists since API v23, but the documentation does not specify whether Waze is discrete or bundled into a local segment. Track the local/Maps slice and correlate it with visit data.
Does this work for appointment-based businesses?
Rarely. Drivers cannot walk into a clinic or salon without a booking, so the meaningful conversion happens elsewhere. Call-first formats usually fit better — see call tracking and call campaigns.
How do I prove incrementality rather than interception?
A geo holdout: matched regions with and without the campaign, four to six weeks minimum, compared on store-level visits and revenue. In-platform reporting will always read higher than the true lift.
What budget does a first test need?
Google publishes no minimum. A workable rule is to budget for enough visits to read a result: take your target cost per visit, multiply by the number of visits you would need to see a difference at store level (usually a few hundred across the test regions), and treat that as the four-week test budget. Anything smaller produces a number you cannot act on.
Is it worth testing with a single location?
You can, with realistic expectations: visit modeling on one store is noisy, so judge it on revenue and a “how did you hear about us” question. Keep the budget small and the test time-boxed.
My online conversions dropped after enabling store goals — why?
Most often because the goal was added to an existing campaign, resetting learning and reallocating budget. Split campaigns by objective, then verify the timeline against change history when diagnosing a performance drop.
