Local Customer Optimization in Performance Max: Google Ads' New In-Store Sales Toolkit Explained

If you manage Google Ads for a multi-location retailer, a restaurant group, or a local service business heading into the 2026 holiday season, there is a real chance a meaningful share of your Performance Max budget has been quietly optimizing for the wrong kind of customer. A Performance Max campaign built around store visits, phone calls, and driving directions has historically leaned on the same broad bidding signals as a campaign built around online purchases, even though a shopper standing two blocks away with Google Maps open is a fundamentally different kind of intent signal than someone browsing a product page from three states away. Google Ads started closing that gap in August 2026 with a new toggle called Local Customer Optimization, and in early September widened the story with a second, related change: a far simpler way to feed real offline sales data back into the system through Google Ads Data Manager.

Neither update is a full platform overhaul. Both are narrow, practical additions aimed at one specific audience: businesses with a physical location that customers actually walk into, call, or drive to. But the two features are designed to reinforce each other, and understanding why makes both of them much easier to use well. This post walks through the mechanism behind Local Customer Optimization, the real reason it comes with two hard compatibility limits, why Store Sales in Data Manager matters even though it is not fully live everywhere yet, and exactly how to turn both on in your own account.

TL;DR

• Local Customer Optimization is a campaign-level toggle for Performance Max campaigns running store goals (store visits, directions, contacts, or store sales). Turning it on shifts budget toward nearby, high-intent shoppers using real-time signals pulled from Google Maps, Waze, and local Google Search formats, people who are actively navigating somewhere, planning a trip, or searching for a location right now.
• It is available today, surfaced as a toggle during Performance Max setup once you select an offline or store conversion goal, or under Budget and bidding optimization in an existing campaign's settings.
• It is not compatible with campaigns that also carry online conversion goals, and not compatible with Performance Max campaigns pulling products from a linked Merchant Center feed. Both limits come from a real architectural reason, covered in detail below, not an arbitrary restriction.
• Store Sales in Data Manager is a simplified way to connect offline sales data, from a CRM system or even a plain Google Sheet, directly into Google Ads Data Manager, replacing more technically demanding prior integration methods so real offline revenue can feed back into Smart Bidding and reporting.
• Store Sales in Data Manager is rolling out in the coming weeks as of this writing, not universally live yet. Google Ads Liaison Ginny Marvin framed both updates explicitly around helping multi-location retailers, restaurants, and local service businesses prepare ahead of the holiday shopping season.
• The two features are meant to work as a pair. Local Customer Optimization is only as good as the offline sales data feeding Smart Bidding, and Store Sales in Data Manager is the piece that makes that data pipeline realistic for a business without a dedicated engineering team.

What Changed: Local Customer Optimization Explained

Performance Max has always been able to run campaigns toward offline goals like store visits, requests for directions, and phone calls, not just online purchases. What it lacked, until this update, was a way to specifically weight its bidding and targeting toward the subset of people who are physically close by and showing real-world, real-time intent to visit somewhere right now, as opposed to someone who merely fits the same broad audience profile from a hundred miles away. Local Customer Optimization is Google's answer to that gap. It is a single toggle, available on a campaign that is running store goals, that tells Performance Max to actively prioritize nearby, high-intent consumers over the rest of its usual audience pool.

The signal set behind it is what makes this genuinely different from ordinary location targeting. Google Ads Help describes the feature as reaching customers who are actively searching for services nearby and ready to take immediate action, and the underlying data comes from three real, live behavioral surfaces rather than a static radius drawn around your store address. The first is Google Maps and Waze navigation activity: people who have a destination entered, are actively driving or walking toward somewhere, or are checking travel time and traffic on a route that passes near your location. The second is local Google Search formats, the kind of query and interaction pattern that shows up when someone searches something like a service category plus "near me," taps into a map pack result, or interacts with a local business listing. The third is trip-planning behavior more broadly, the browsing and searching pattern of someone actively deciding where to go today rather than idly researching a category for some point in the future.

That distinction matters more than it sounds. A standard Performance Max campaign optimizing toward a store-visit or store-sales goal will still find plenty of people who eventually convert, but it treats a person who is three miles away and already navigating toward your neighborhood largely the same as a person who fits a similar demographic and interest profile but has shown no immediate, real-world intent to go anywhere. Local Customer Optimization changes the weighting so that the campaign spends more of its budget chasing the first kind of person and less chasing the second, precisely because the first kind of person is dramatically more likely to convert into an actual visit within the current shopping trip, not a hypothetical future one.

The eligible goals are specific and worth naming exactly, since this is where a lot of advertisers first get tripped up. According to Google's own documentation, Local Customer Optimization works exclusively with offline conversion goals: store visits, store sales, Google-hosted contacts, and Google-hosted directions requests. It is not a general-purpose "local intent" toggle that layers onto any campaign type. It is scoped narrowly to campaigns whose entire measurement model is built around something happening in the physical world, a visit, a call, a sale rung up at a register, a request for directions that implies someone is about to head your way.

It is also worth being precise about the timeline here, since the coverage around this update spans a few weeks and can read as more sudden than it actually was. Local Customer Optimization first began appearing in Google's help documentation and rolling out to advertiser accounts in August 2026. The broader wave of coverage in the first half of September, including reporting from Search Engine Land and a follow-up from Search Engine Roundtable, was really about pairing that already-rolling-out toggle with the second feature covered below, Store Sales in Data Manager, and framing both together as Google's holiday-season push for multi-location and local advertisers. So if you have not seen the toggle in your own account yet despite it technically being available since August, it is worth actively checking rather than assuming it has not reached you, since staggered rollouts across account types and regions are normal for a feature at this stage.

Consider a concrete example. A regional bakery chain with nine locations runs a single Performance Max campaign per store, each one built around a store-visit goal fed by Google Business Profile location data. Before Local Customer Optimization, each campaign's budget was spread across a fairly wide radius and demographic profile matching typical bakery customers in that area, some of whom might visit next month, some who might never visit at all despite matching the profile well. After turning the toggle on for each location's campaign, a meaningfully larger share of that same budget goes toward people who are, at that literal moment, navigating through the neighborhood on Waze, searching "bakery near me" on their phone standing two blocks away, or checking a Maps listing for a nearby competitor and about to compare it against this one. The chain is not spending more money. It is spending the same money on a customer who is measurably closer to walking through the door today.

The Compatibility Limits, and Why They Exist

Google's own documentation is blunt about two restrictions: Local Customer Optimization cannot run alongside online conversion goals in the same campaign, and it is not compatible with a Performance Max campaign that pulls products from a linked Merchant Center feed. It would be easy to read both of those as arbitrary product limitations Google will probably lift eventually, but there is a real, structural reason behind each one, and understanding it changes how you should actually set up your account rather than just working around the restriction blindly.

Start with the online-goal incompatibility. Performance Max's entire bidding engine works by optimizing toward a blended signal built from whatever conversion actions you feed it, weighting and predicting value across all of them at once. Local Customer Optimization works by re-weighting that same engine specifically toward a narrow, real-time behavioral signal set: proximity, active navigation, and local search intent. If a campaign carried both an online purchase goal and a store-visit goal at the same time, the bidding system would need to simultaneously chase two very different kinds of intent signal with one shared budget and one shared model, someone browsing a product catalog from anywhere in the country, and someone standing three blocks from your store with Maps open. Those two behaviors do not share the same real-time signal set at all, and asking one bidding model to weight both cleanly would dilute exactly the kind of precision Local Customer Optimization exists to add. Google's actual account-level behavior reflects this directly: if you try to add an online conversion goal to a campaign that already has Local Customer Optimization turned on, the conversion goal selector becomes unavailable and the interface points you back to the Local Customer Optimization setting, meaning you have to explicitly turn the toggle off first before you can mix in an online goal. The restriction is not a permissions quirk. It is the product enforcing that a campaign has to pick one clean signal set or the other.

The Merchant Center incompatibility follows a related logic. A Performance Max campaign pulling products from a linked Merchant Center feed is, by construction, built around surfacing individual product listings, images, prices, and availability pulled from that feed, the same infrastructure that powers Shopping ads and product-level bidding. That entire mechanism assumes the thing being optimized toward is a product-level interaction: a click on a specific item, a purchase of a specific SKU, or at minimum a browse session anchored around product data. Local Customer Optimization's signal set, real-time navigation and local search behavior, has no natural mapping onto individual product performance. There is no meaningful way to weight bidding toward "people driving nearby right now" at the level of a specific product listing pulled from a feed, because proximity and navigation intent are properties of the person and the moment, not properties of a SKU. A feed-driven Performance Max campaign is optimized around a fundamentally different unit of measurement than Local Customer Optimization is built to weight.

The practical upshot is straightforward, even if it takes an extra campaign to execute. If your business runs a Performance Max campaign pulling from Merchant Center for online product sales, and you also want Local Customer Optimization for driving store visits, you need two separate campaigns rather than one campaign trying to do both jobs. The Merchant Center-linked campaign keeps doing what it already does well for online shopping demand. A second, store-goal-only campaign, with no product feed attached and no online conversion goal mixed in, is where Local Customer Optimization actually gets applied. This is more setup work than flipping one toggle, but it is the only structure the underlying bidding architecture can actually support cleanly, and it mirrors a pattern worth recognizing from Google's other recent Performance Max changes: the platform has been steadily adding more granular, purpose-built controls rather than one campaign type trying to be everything at once, a trend also visible in the steering and reporting controls covered in Miraflow's Performance Max optimization breakdown.

The table above is worth referring back to before you touch your own account. The middle and right columns are not failure states, they are simply a different job that Performance Max is already doing well. The point of Local Customer Optimization is not to replace those campaigns, it is to give you a clean, dedicated lane for the specific job of driving nearby foot traffic that neither of those other setups was ever built to prioritize.

Store Sales in Data Manager: Why the Offline Data Pipeline Matters

Local Customer Optimization solves the front half of a local advertiser's problem: getting the right nearby, in-market person to actually see the ad and act on it. It does nothing, by itself, to solve the back half: proving that the visit actually turned into a sale, and feeding that real revenue number back into Smart Bidding so the system keeps learning what a genuinely valuable visit looks like. That back half is exactly what Store Sales in Data Manager is built to simplify.

Offline conversion data has always been importable into Google Ads in some form, but the prior methods were genuinely demanding for a typical local retailer or restaurant group. Getting real point-of-sale data connected usually meant building a structured offline conversion import file to strict formatting requirements, setting up a recurring upload process, or building a custom API integration, work that realistically required a developer or a dedicated data analyst on staff. For a nine-location bakery chain or a regional service business, that was often simply out of reach, not because the business lacked valuable sales data, but because turning that data into something Google Ads could actually ingest was a real technical project, not a marketing task.

Store Sales in Data Manager collapses a large chunk of that technical distance. Instead of a custom integration, advertisers can connect a CRM system directly, or in a genuinely simplified case, connect a plain Google Sheet holding transaction records, straight inside Google Ads Data Manager, the same first-party data hub Google has been building out as the connective layer between an advertiser's own data and its ad products. The result is meant to be a setup a marketing team can complete on its own, without waiting on engineering resources to build and maintain a custom pipeline.

Why does this matter enough to sit alongside Local Customer Optimization in the same announcement, rather than being a separate, unrelated update? Because Smart Bidding is only as good as the value signal it is optimizing toward. A store-sales goal that is fed by thin, delayed, or incomplete offline sales data teaches the bidding model an inaccurate picture of what a good customer actually looks like, no matter how precisely Local Customer Optimization has aimed the campaign at nearby, in-market shoppers. If the system cannot see which of those nearby visits actually became a real, valuable transaction versus a browse-and-leave, it has no way to reinforce the behavior that is actually working. Local Customer Optimization improves who Performance Max chases. Store Sales in Data Manager improves what Performance Max learns from the outcome. Neither one is complete without the other for a business whose real goal is measurable in-store revenue rather than just foot traffic for its own sake.

It is important to be accurate about where this feature actually stands as of this writing rather than overstating it. Google has framed Store Sales in Data Manager as rolling out in the coming weeks, not as something universally available across every account today. Coverage from the Search Engine Journal on the same announcement also notes real mechanical requirements once it is available: customer data such as emails, phone numbers, and addresses still needs to be hashed before upload, daily or weekly upload cadence is recommended for the data to stay useful to Smart Bidding, and Google generally wants roughly the trailing 30 days of transactions available for dynamic conversion value reporting to work well. Eligibility is also not universal. If you check your account's Data Manager section and do not see a Store Sales connection option yet, that is expected rather than a sign something is broken on your end, and it is worth checking back over the following weeks rather than assuming the feature has skipped your account permanently.

How to Turn On Local Customer Optimization

Here is the practical setup path, whether you are building a new campaign or adjusting one that already exists.

Step 1: Decide whether you need a new campaign or can adjust an existing one. If you already run a Performance Max campaign built purely around store goals, with no online conversion goal and no Merchant Center feed attached, you can likely enable Local Customer Optimization directly on it. If your current store-goal campaign also carries an online goal or pulls from a product feed, plan on a separate, dedicated campaign instead of trying to retrofit the existing one.

Step 2: For a new campaign, select an offline or store conversion goal during setup. Local Customer Optimization surfaces as its own panel with a toggle once you choose store visits, store sales, contacts, or directions as your goal during campaign creation. If you select an online goal instead, or add one alongside a store goal, the toggle will not appear, which is the setup itself confirming the incompatibility described above.

Step 3: For an existing store-goal campaign, find the toggle under Budget and bidding optimization. Open the campaign's Settings, and look for the Local customer optimization control inside the Budget and bidding optimization section. Turning it on here does not require rebuilding the campaign, it is a direct setting change on a campaign that already qualifies.

Step 4: Confirm the campaign has no online conversion goal and no linked Merchant Center feed before flipping the toggle. If either is present, remove the online goal or plan a separate campaign for feed-driven Shopping traffic first. Trying to enable the toggle on a disqualified campaign will either hide the option or block the online goal selection, so it is faster to check both conditions up front than to troubleshoot after the fact.

Step 5: Give the campaign a real evaluation window before judging results. Because Local Customer Optimization is reweighting toward a real-time behavioral signal set rather than a static audience list, it needs a genuine learning period to find and prioritize the right in-market shoppers, the same general patience any new Performance Max signal change requires. Watch store-visit and store-sales conversion volume and quality over at least a few weeks, not a few days, before deciding whether to keep it on.

Connecting Store Sales in Data Manager

Since this feature is still rolling out, treat the following as the general shape of the setup rather than a guarantee every account can complete it today.

Step 1: Check whether Store Sales appears as a connection option inside Data Manager. Sign into your Google Ads account and open Data Manager. If a Store Sales or offline sales connection option is not visible yet, that reflects the staged rollout rather than a configuration mistake, and it is worth rechecking periodically over the following weeks.

Step 2: Choose your data source, a CRM system or a Google Sheet. For a business with a point-of-sale or CRM platform already tracking transactions, connecting that system directly is the more durable option. For a smaller operation, or one still centralizing its sales data, a well-structured Google Sheet is explicitly supported as a legitimate starting point, not a stopgap Google merely tolerates.

Step 3: Prepare customer match data in hashed form. Whichever source you connect, identifying customer fields like email, phone number, and address need to be hashed before upload, a standard privacy requirement across Google's customer match and offline conversion products, not something unique to this feature.

Step 4: Set a realistic upload cadence. Daily or weekly uploads keep the data fresh enough for Smart Bidding to actually use it, and Google's own guidance points toward keeping roughly the trailing 30 days of transaction history available so dynamic conversion value reporting has enough recent data to work from.

Step 5: Pair it deliberately with a store-goal Performance Max campaign, ideally one already running Local Customer Optimization. The real payoff of this feature is closing the loop between a campaign chasing nearby, in-market shoppers and a bidding model that can actually see which of those shoppers turned into real, valuable sales. Setting the two up together, rather than treating them as unrelated projects on different timelines, is where the combined value actually shows up.

Who Benefits Most

These two features land differently depending on the shape of the business running them, and it is worth being specific about each case rather than treating "local advertisers" as one uniform group.

A single-location small business gets the most immediate, least complicated win from Local Customer Optimization alone. A single storefront, restaurant, or service shop typically runs one Performance Max campaign, so there is no cross-campaign structure to untangle, no Merchant Center feed conflict to plan around unless the business also sells online, and the toggle is often a genuinely quick change: confirm the campaign is store-goal-only, flip the setting, and let it run. Store Sales in Data Manager is the bigger lift for this group, since a small business is exactly the kind of advertiser who previously lacked the technical resources to build a custom offline conversion pipeline, which is precisely the gap this update targets. A single well-organized Google Sheet tracking daily transactions can now realistically become a usable Smart Bidding signal, something that was out of reach for most small operators before.

A multi-location retail chain faces more structural work but a proportionally larger payoff. Each location typically needs its own campaign consideration, since store-visit intent and local competition differ block by block, and any location still selling online through a Merchant Center feed needs its store-goal campaign kept genuinely separate from its Shopping-driven one, exactly the split covered in the compatibility section above. The advantage at this scale is that Store Sales in Data Manager, once connected to a real CRM or point-of-sale system across all locations, gives Smart Bidding a much richer, location-level picture of which stores and which nearby shopper segments are converting into real revenue, not just visits. That is a meaningfully more useful signal for a chain deciding where to shift budget across a whole footprint of stores heading into a holiday period.

An agency managing many local accounts has the most to gain from treating this as a repeatable checklist rather than a one-off change. The realistic workflow is an audit pass across every client account: flag which store-goal campaigns already qualify for Local Customer Optimization outright, which ones need an online goal split out first, and which ones are tangled with a Merchant Center feed that needs its own separate campaign. Layering Store Sales in Data Manager on top, client by client as it becomes available to each account, turns this from a single feature toggle into a genuine service offering an agency can point to heading into Q4, a concrete, dated capability improvement to bring to a client review rather than a vague promise of "better local targeting."

Common Mistakes

A handful of setup mistakes come up often enough with a change like this to call out directly.

Trying to add an online conversion goal to a campaign that already has Local Customer Optimization on, and getting stuck. The conversion goal selector will simply refuse to let you add an online goal while the toggle is active, pointing you back to the Local Customer Optimization setting instead. This is not a bug, it is the incompatibility described above being enforced at the interface level. Decide upfront whether a campaign is a pure store-goal campaign or a blended one, rather than discovering the restriction mid-setup.

Not realizing a Merchant Center-linked Performance Max campaign needs a fully separate campaign. It is tempting to assume you can simply flip the toggle on your existing Shopping-driven Performance Max campaign and get the best of both worlds. You cannot, and trying to force it wastes setup time. Plan for two campaigns from the start if your business sells both online, through a product feed, and drives in-store visits.

Assuming Store Sales in Data Manager is instantly available everywhere. Because this update was covered widely in the same news cycle as Local Customer Optimization, it is easy to assume both are equally live today. They are not. Store Sales in Data Manager is a staged rollout, and checking your account's Data Manager section without finding it yet does not mean anything is misconfigured.

Turning on Local Customer Optimization and judging it within days. A real-time behavioral signal set needs a genuine learning period to find the right pattern of nearby, in-market shoppers. Evaluating conversion volume after two or three days is judging the campaign before it has had a fair chance to learn.

Uploading offline sales data inconsistently once Store Sales in Data Manager is connected. A sporadic, once-a-month upload gives Smart Bidding a stale, thin picture of real conversion value. Committing to a daily or weekly cadence, as Google's own guidance recommends, is what actually makes the connection useful rather than symbolic.

Forgetting that phone numbers and addresses still need to be hashed before upload. This is a standard privacy requirement across Google's customer match and offline conversion tools generally, not something unique or new here, but it is an easy step to overlook when a feature is being marketed as "simplified."

Making Sure the Rest of the Campaign Earns the Extra Foot Traffic

Getting Local Customer Optimization and Store Sales in Data Manager configured correctly solves the targeting and measurement half of this update. The other half, less discussed but just as real for a Performance Max campaign built around store visits, is whether the actual creative assets in that campaign give a nearby shopper a real reason to choose your store over the next listing down. Performance Max asset groups still need images and video that hold up next to a competitor's, and a campaign that is now successfully reaching someone three blocks away with Maps open is wasted if the image that shopper sees is a blurry storefront photo from years ago.

This is a natural spot for Miraflow's own tools to fit into a local advertiser's workflow. Miraflow's AI Image Generator supports image-to-image editing and inpainting, so a business can take an existing storefront or product photo and refresh specific parts of it, a faded sign, an outdated display, a seasonal window, without a full reshoot, useful for keeping a Performance Max asset group current as holiday merchandising changes week to week. For a short video asset showing a store's actual atmosphere or a product in use, Miraflow's Cinematic AI Video Generator can turn a written prompt into a polished clip without booking a production crew, the same kind of fast asset-refresh workflow covered in Miraflow's breakdown of Gemini Omni inside Google Ads Asset Studio. And for the bold, high-contrast still images that tend to perform well as Performance Max display-style assets, Miraflow's YouTube Thumbnail Maker works just as well repurposed for eye-catching Display and Performance Max creative as it does for actual video thumbnails, since the underlying need, a bold image that stops a scroll and communicates one idea fast, is largely the same.

None of that replaces the mechanical setup covered earlier in this post: confirming your campaign qualifies, splitting Merchant Center-linked campaigns out correctly, and getting real offline sales data connected. But once that groundwork is done and Local Customer Optimization starts sending more nearby, in-market shoppers toward your listing, the businesses that convert the most of that extra attention tend to be the ones whose actual creative gives that shopper a real reason to walk in. It is also worth reading this update alongside a few other recent Performance Max and local-advertiser changes covered on the Miraflow blog, including the shift toward Local Inventory Ads as a default in Shopping campaigns and the ongoing migration of Local Services Ads into Performance Max, since Google has clearly been building out its local and in-store advertising toolkit as a connected set of changes rather than isolated, unrelated updates.

Frequently Asked Questions

Which conversion goals actually qualify for Local Customer Optimization?

Store visits, store sales, Google-hosted contacts, and Google-hosted directions requests. It does not work with online conversion goals like purchases or lead form fills, and a campaign carrying one of those alongside a store goal will not be able to enable the toggle until the online goal is removed.

Can I use Local Customer Optimization on a campaign that also runs Shopping ads from Merchant Center?

No. Google's own documentation states plainly that it is not compatible with Performance Max campaigns pulling products from a linked Merchant Center feed, for the structural reasons covered earlier in this post. You would need a separate, feed-free, store-goal-only campaign to use it.

Is Store Sales in Data Manager available in every Google Ads account right now?

Not yet universally. Google has described it as rolling out in the coming weeks as of the September 2026 announcements, and account eligibility is expected to expand gradually rather than switch on everywhere at once. Check your account's Data Manager section periodically if you do not see the option yet.

Do I need a developer to connect Store Sales in Data Manager?

Not necessarily, which is the entire point of the update. The simplified flow supports connecting a CRM system directly or using a Google Sheet, both meant to be manageable by a marketing team without a dedicated engineering integration project, unlike many prior offline conversion import methods.

Does turning on Local Customer Optimization cost more or change my bids directly?

Google has not described this as a separate pricing tier or a forced bid change. It reweights which audience segments within your existing budget and bidding strategy get prioritized, shifting spend toward nearby, high-intent shoppers rather than adding a new cost layer on top of your campaign.

How long should I wait before judging whether Local Customer Optimization is working?

Give it a genuine learning period, generally a few weeks rather than a few days, since it is reweighting toward a real-time behavioral signal set that needs time to identify the right pattern of nearby, in-market shoppers for your specific business and location.

What happens to my customer data once it is uploaded through Store Sales in Data Manager?

Identifying fields like email, phone number, and address must be hashed before upload, consistent with Google's existing customer match and offline conversion privacy requirements, and the data is used to connect real transactions to ad interactions for measurement and bidding, not shared as raw, readable customer information.

Conclusion

Local Customer Optimization and Store Sales in Data Manager are a genuinely useful pair, not two unrelated feature announcements that happened to land in the same news cycle. One improves who your Performance Max campaign chases, weighting budget toward the nearby shopper actively navigating, searching, or planning a trip right now instead of treating every demographically similar person the same. The other improves what your campaign learns from the outcome, replacing a technically demanding offline data integration with something a marketing team can realistically set up and maintain on its own.

The compatibility limits are real and worth respecting rather than fighting. A campaign with online conversion goals or a linked Merchant Center feed needs a separate, dedicated store-goal campaign to take advantage of Local Customer Optimization, and that extra setup step is a small price for a bidding model that can actually specialize in driving real foot traffic rather than splitting its attention across two different kinds of intent. And Store Sales in Data Manager, while not universally live yet, is worth getting ready for now: cleaning up CRM data, deciding whether a Google Sheet or a direct system connection fits your business better, and understanding the hashing and upload cadence requirements ahead of time, so you can connect it the moment it reaches your account rather than scrambling once the holiday shopping season is already underway.

Getting the mechanics right is only half the job. Once nearby shoppers start seeing your listing more often, the creative in front of them needs to hold up, which is where a quick pass through Miraflow's AI Image Generator, Cinematic AI Video Generator, or YouTube Thumbnail Maker can keep a Performance Max asset group looking current without a full production cycle every time the season changes. Anyone building out a full local advertising workflow from scratch can explore more of Miraflow's tools from the Miraflow homepage, and the Miraflow blog has more breakdowns of recent Google Ads changes worth reading alongside this one, including the Performance Max Asset Studio prefill update and the Local Services Ads direct booking expansion.