> ## Content Index
> Fetch the complete content index at: https://cascader.io/blog/llms.txt
> Use this file to discover other available public pages before exploring further.

# Did the August 17 Bidding Change Cause Your Google Ads Drop? How to Tell
- URL: https://cascader.io/blog/august-17-bidding-change-google-ads-drop/
- Published: 2026-11-13T15:00:00.000Z
- Updated: 2026-11-13T15:00:00.000Z
- Description: Google's August 17 bidding change altered how only budget-limited target campaigns bid, yet it was soon blamed for drops in campaigns whose bidding it never changed. If that explanation is being handed to you, the date alone doesn't settle whether it's true.
- Author: Rick Hecker
- Tags: Cascader Research, Google Ads

Last verified November 2026

From late August 2026, a great many Google Ads drops came with an explanation already attached: "it's the August 17 update." The update was real. On August 17 Google changed how Target CPA and Target ROAS campaigns bid when they are limited by budget, and it finished rolling the change out on August 27\. Some advertisers were plainly hit by it. Many others had a drop that merely landed in the same weeks. If you manage established Search, Shopping or Performance Max accounts, and a client, a boss, a Google rep or a Reddit thread tells you your drop is the update, two questions decide what you should do next. Did that change touch this campaign at all? And if it did, is it what moved your numbers? This piece shows how to answer both from your own account before you change anything, by following one real campaign through each check.

Getting it wrong is expensive in both directions. Blame the update when it wasn't the cause, and you rewrite a target that was never the problem while the real fault (a broken form, a new competitor, your own edit) keeps running. Dismiss the update when it was the cause, and you spend weeks auditing tracking while the one setting whose meaning changed on August 17, the campaign's target, sits untouched.

The campaign we'll follow is a Standard Shopping campaign that its manager, posting as THE-SD, described in [r/Google\_Ads](https://www.reddit.com/r/Google%5FAds/comments/1wch4v4/google%5Fshopping%5Fcpc%5Ftripled%5Fafter%5Faug%5F17%5Fsmart/?ref=cascader.io) on September 10\. It had run for years for an online marketplace, on an $18 daily budget and a 200% Target ROAS. From around August 19 its cost per click rose from about $0.06 to $0.15–$0.20, and on some days it bought about 100 clicks where it used to buy 250 to 350, while still spending its budget. The manager asked whether Google's change had "fundamentally changed how my campaign bids". Every figure from that thread is the manager's own report, and we'll say where a number can't carry what it's asked to carry.

## Why a shared date can't settle it

To see how the August 17 explanation travels, we read Reddit threads posted between November 2025 and October 2026 in r/PPC, r/googleads, r/Google\_Ads and r/GoogleAdsDiscussion, plus one thread in r/adwords. The first group was 60 threads in which a poster tied a drop to a date or a named update and asked whether others were seeing it; we'll call these the dated threads. We found them by searching for dates and update names ("august 17", "nov 17", "core update", "ai max", and "anyone else" next to drop words) and through the link list of an r/PPC megathread about August 17\. The second group was 41 ordinary drop threads, found through searches such as "conversions dropped", "tanked" and "stopped converting". In both groups we screened titles, took threads in a random order, and kept only established Search, Shopping and Performance Max campaigns. The figures below count what people said in those threads, and every one of them comes from the dated threads except the count of repeat repliers at the end of this paragraph. They aren't rates of anything happening in Google Ads accounts. And because about a hundred Reddit users replied in more than one thread across the two groups, the replies aren't independent witnesses either.

The first thing the threads show is that "August 17" works less like a date than like a season. The onsets people tied to the change ran from "roughly 14 August", "around august 15", "the end of July / beginning of August", 8/31, the week of September 14, and mid-September into October. Some replies got the update's date wrong outright: one said "28thbof August was a major bidding update", another that it "took place between August 17 and September 17". The same weeks also held an organic spam update that began on August 18, Google's automatic move of some Search campaigns to AI Max from September 1, US Labor Day, and the summer-to-fall shift several posters mentioned themselves.

The second thing is that the name often came from someone else. Call any named Google change a "platform event": the August 17 change, the September AI Max upgrade, a core update, the November 2025 jump in Shopping CPCs, or just "an update". Among the dated threads posted on or after August 17 whose poster hadn't named one, a reply supplied one in 6 of 10\. Among the dated threads posted before August 17 it was 2 of 13, though earlier threads had events available to name too. That comparison describes how repliers behaved, not how many drops there were, and it's reason enough to read a thread full of "same here" as one explanation repeated rather than many confirmations.

The third thing is that the deciding question often got asked. Across the 60 dated threads, 82 repliers, each counted once per thread, asked something that could tell one explanation from another, such as whether the campaign had been limited by budget or what its target was. Often the poster never answered. In one thread a reply asked whether results had been running better than the target before September, and the poster never came back to say.

So a shared date gives you a short list of documented changes worth testing. It gives you no evidence that any of them touched your campaign. For that you need to know what each change does.

## What the August change does to a campaign's numbers

The August 17 change edits nothing in your account. Google's [help page on the change](https://support.google.com/google-ads/answer/17061251?ref=cascader.io) says that "Campaigns that are limited by budget and use a target-based bid strategy now perform more consistently toward your bid target". It also says Google "won't automatically adjust your bidding targets or budgets." The [companion FAQ](https://support.google.com/google-ads/answer/17125145?ref=cascader.io) adds: "This is specifically a bidding change. Google Ads auction mechanisms won't change." What changed is how the bidder pursues the target you had already set.

Before the change, Google says, a budget-limited target campaign "may be overperforming on bidding targets", a behavior the FAQ calls confusing and liable to "create unpredictable results when budgets are adjusted". An r/googleads poster, whose German Search campaign comes up again below, put the old behavior more bluntly: budget-limited campaigns "used to ration and cherry-pick the cheap auctions". Now the campaign bids toward its target. Google's worked example is a $10 Target CPA campaign that had been achieving $5 and "now delivers more closely to a $10 USD actual CPA."

Google fixes the two ends of what follows. The budget doesn't move: "Your daily and monthly budget limits will always be respected." And results move toward the target. For a Target CPA campaign, CPA rises toward the target. For Target ROAS the same thing runs the other way: say a campaign has a 400% target and has been returning 600%; it gets steered down toward 400%. What lies between those ends is arithmetic and practitioner report, not Google's wording. A campaign that spends the same money at a worse CPA or return gets fewer conversions for it. The extra cost can arrive as dearer clicks or as weaker ones. When it arrives as dearer clicks, fewer clicks fit inside the same budget, and the higher bids tend to win higher positions. So a campaign the change reached should show a recognizable pattern: spend about where it was, CPA or ROAS moving toward the target, and either CPC up with clicks down and position steady or higher, or clicks about flat with fewer conversions from them.

Two conditions decide whether a campaign can show that pattern at all. It uses Target CPA or Target ROAS (or Target CPC in Demand Gen), and its status is "Limited by budget." The target counts wherever it is set. Google's page describes Maximize conversions and Maximize conversion value as strategies that "optimize to spend your full budget without a target", and that's true only while no target is set. A Maximize conversions campaign with a target CPA, or a Maximize conversion value campaign with a target ROAS, is a target campaign. Target campaigns that aren't budget-constrained "won't change their behavior," and the change doesn't touch manual CPC or Target Impression Share. In this piece, a campaign that meets both conditions is called "covered".

A third condition decides where the change *shows*. Google's help page puts it plainly: "If you have a campaign that's limited by budget that has historically overachieved its stated target, you may experience performance volatility". A covered campaign whose target already matched its results is still covered, but Google says aligning target to actual "shouldn't" bring "noticeable volatility." For Performance Max and Demand Gen, Google adds one more sign: "you may also find shifts in how traffic is distributed across different channels."

The other changes people name do different things:

If columns extend beyond the page, scroll sideways. With a keyboard, focus the table and use the arrow keys.

| Named change                 | When                                            | What it changes                                              | Which campaigns                                                                                                                                                    | What it leaves in your account                                                                                                                             |
| ---------------------------- | ----------------------------------------------- | ------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Target-based bidding change  | Aug 17–27, 2026 (rollout)                       | How the bidder pursues an existing target; no setting edited | Target CPA or Target ROAS, including a target set inside Maximize conversions or Maximize conversion value (and Demand Gen Target CPC), that are Limited by budget | Possibly a service announcement, a "Review your campaign targets" prompt or a target recommendation; nothing in Change history, because no setting changed |
| AI Max auto-migration        | Sep 1–30, 2026                                  | Campaign settings, in place                                  | Search campaigns with the campaign-level broad match setting or standalone automatically created assets                                                            | In-account notice beforehand; "AI Max" match type in the search terms report; migration-date fields in the API                                             |
| Organic core or spam update  | Start dates on Google's Search Status Dashboard | Organic ranking                                              | Not ads (no documented Ads mechanism)                                                                                                                              | Nothing in Google Ads                                                                                                                                      |
| Other advertisers' reactions | Any time                                        | The prices and positions in auctions you share               | Any campaign, covered or not                                                                                                                                       | Auction insights; prices on campaigns whose bids you didn't move                                                                                           |

The AI Max upgrade, described on Google's [page about the broad match campaign setting](https://support.google.com/google-ads/answer/13389795?ref=cascader.io) and in the [Ads Developer Blog](https://ads-developers.googleblog.com/2026/08/migrate-campaign-level-broad-match-and.html?ref=cascader.io), switched on search term matching by default. Google also notes that after the move, broad keywords "are not treated as exact match keywords in prioritization", which can change which of your own campaigns serves a query. For the auction row, Google's [troubleshooting page](https://support.google.com/google-ads/answer/12077891?ref=cascader.io) is direct: "The choices that other advertisers, who are participating in the same auctions as you, make can affect your campaign's performance."

The table already rules a lot out. A campaign on manual CPC, Target Impression Share, Maximize conversions or Maximize conversion value with no target set, or a target campaign with budget to spare, didn't have its bidding changed on August 17\. Now take a campaign that might have been covered, and walk it through the checks in order.

## Was the campaign covered before August 17?

THE-SD's campaign ran on a 200% Target ROAS and, in its manager's words, "was consistently Limited by Budget" before the change. On that description it was covered. Most posters who blamed the update could settle this from their own words. Of the 28 posters in the dated threads who blamed August 17 themselves, their descriptions settle both of Google's conditions for 17: 12 covered, 5 not. The other 11 stayed unknown, often because nobody answered the reply that asked.

The catch is timing, and it introduces the problem that runs through this whole diagnosis: most of the numbers you'd use to check whether the update touched a campaign are numbers the update itself moves. Status is the first. A large brand campaign on Target ROAS, described in [r/PPC](https://www.reddit.com/r/PPC/comments/1xcxbr7/brand%5Fsearch%5Fcpcs%5Fskyrocketing%5Fsince%5F91/?ref=cascader.io), saw brand CPCs double from September 1 and impression share lost to budget go "from 0% to 90%". It became budget-limited *because* its clicks got dearer, so its status afterwards says nothing about what caused the jump. Another poster [wrote](https://www.reddit.com/r/PPC/comments/1we3xy5/impression%5Ftanked%5Fovernight%5Fafter%5Fthe%5Faug%5F17/?ref=cascader.io) that their campaigns "none of them show limited by budget", after impressions fell by half overnight on August 26\. A campaign that suddenly buys half the traffic will rarely run out of budget, so its status in September can't tell you what it was in early August. THE-SD's campaign shows it too: its impression share fell below 10% after the change, so any share read in September describes the update's effect, not the campaign it arrived in.

So read status from before the date. The column to open is impression share lost to budget, by day or week, for July and the first half of August. A campaign that was steadily losing a share of its impressions to budget through those weeks was limited by budget when the change arrived. One that lost almost none wasn't, whatever its status says today. [Data Bid Machine](https://databidmachine.com/post/why-did-my-google-ads-performance-drop?ref=cascader.io)'s "Why Did My Google Ads Performance Drop? A Diagnostic Checklist", a ten-step guide to within-account triage, also tells readers to "Review lost impression share where available", and on Performance Max the posters in these threads read lost impression share to budget too.

Google's in-account signals can help. The FAQ says the mandatory service announcement "notifies any advertiser who might face an impact", which means possibility, not effect. Recommendations are generated only "for campaigns that recent data shows will likely be affected", and none are calculated for campaigns with fewer than 7 conversions. Google also built a Bid Target Adjustment Tool, available from July 6, 2026 according to its [Search troubleshooting page](https://support.google.com/google-ads/answer/12266223?ref=cascader.io), for reviewing targets ahead of the change. THE-SD saw the "Review your campaign targets" prompt on this campaign. If you see none of these, it isn't proof you were safe.

Coverage can also start later. Google describes the new behavior by status, so a campaign that begins hitting its budget in September gets the new behavior then. That's one reason onsets keep appearing after Google's stated completion date. THE-SD's second Shopping account, also on Target ROAS and limited by budget, showed the same pattern from around September 8\. A small Performance Max advertiser in the Netherlands, who [posted in r/adwords](https://www.reddit.com/r/adwords/comments/1wnyls6/pmax%5Fperformance%5Fdropped%5F2025%5Fafter%5Faugust%5F17/?ref=cascader.io), saw volume fall in the week of September 14 and reported that Google support said the campaign "is affected by the new behavior for budget-limited Target ROAS campaigns" (that's the advertiser's account of the conversation). A late onset doesn't rule the update out. It means the date alone can't decide; the campaign's status and target history around your own onset have to.

If the campaign wasn't covered, the update didn't change how it bids, and the only route left is other advertisers' bids. That route has its own test, which comes after the question of who raised the prices.

## Was it running ahead of its target?

A campaign that's covered, meaning it runs on a target and is Limited by budget, won't necessarily show a visible change. Google expects one where the campaign had been beating its target. THE-SD's campaign had been beating it by a wide margin: its manager listed, under the heading "Before the change", an August ROAS of about 538% against the 200% target, without saying which days of August that covers, and the Bid Target Adjustment Tool, by its manager's report, showed "Pre-Aug-17 actual performance shown by Google: 747.41%". That's exactly the profile Google warned about. Among the 28 posters who blamed August 17 themselves, only 8 described a campaign that met all three of Google's conditions.

The check is the campaign's actual CPA or ROAS, week by week, for the months before August 17, set against its target. If the actual figure was well ahead of the target, the change had room to show. If the two matched, Google's own line says you shouldn't expect much from the update, and that changes where you look. One r/PPC poster ran small, budget-limited Target CPA campaigns in which "all of them already had a pretty good match between the actual CPA and the target CPA." Their CPAs still "exploded" in September, during what [they called](https://www.reddit.com/r/PPC/comments/1whtzrs/aftermath%5Fof%5Fthe%5Fgoogle%5Fads%5Faugust%5F17%5Fupdate%5Fhad/?ref=cascader.io) one of the two biggest seasonal shifts of their year. In a comment on September 16, the same poster added that their other campaigns hadn't seen CPA move by more than 10%, while the tCPA campaigns had been fine until a week or two before that comment and then "hit a sudden wall". So this example leaves open how far a matched target rules the update out. The poster named both the summer-to-fall traffic shift and the algorithm change as reasons the campaigns had become unstable, and nothing in the thread separates the two; the pattern confined to the tCPA campaigns rests on the poster's own comparison across their accounts. The case shows that matched targets didn't keep these campaigns steady, but not which of those two causes was behind the jump.

## Does the drop look like what the change does?

THE-SD's campaign kept spending "roughly the full $18/day", while its CPC more than doubled and its clicks and impressions fell. That's the dearer-clicks form of the pattern a covered campaign can show: the same spend, dearer clicks, fewer of them. The thread gives no ROAS figure for those weeks beyond its manager's later "ROAS suffered", so the last link, return moving toward the target, isn't shown. The rest fits.

A drop that leaves results well worse than the target, not just moved toward it, points away from the update. An r/PPC poster, MikeLavosmile, [reported](https://www.reddit.com/r/PPC/comments/1vysvjc/roas%5Ftargets%5Fvs%5Factual%5Froas%5Fafter%5Faug%5F17th/?ref=cascader.io) campaigns that had run at 700–800% ROAS all year on a 700% target. Around August 17 the poster raised the target to 750% to match recent results, and in the nine days that followed, ROAS fell to about 350%. A reply from Either\_Guess2405 put the figures side by side: "700 to 750 is a 7 percent tightening. It cannot mechanically produce a 53 percent fall in delivered ROAS." And the change can't explain it either: "A mechanism that pulls you toward your number cannot be the reason you are at half your number." That holds whether or not the campaign was covered, which the thread never settled. If it was covered, its results were already close to the new 750% target, so the change had almost nothing to pull, and nothing that could pull it down to 350%. If it wasn't covered, the change didn't touch its bidding.

The first alternative to check is conversions that haven't arrived yet. Google's page on [conversion reporting](https://support.google.com/google-ads/answer/6270625?ref=cascader.io) explains that the main Conversions and Conv. value columns are "calculated based on the time of the click, not the time of the conversion", so a sale made this week from last week's click is filed under last week. A nine-day-old window is therefore still filling in. Note the conversion value for the days just after the date in those click-date columns, wait a few days, and look at the same days again. Google notes reporting can lag 24 to 48 hours, so don't take the first reading the same day. If the figures have grown materially, the 350% isn't final yet. If they haven't moved, lag isn't the story, and the next place to look is whatever else happened that week: a feed change, tracking, a promotion, a budget move. (The "by conv. time" columns file each conversion under the day it happened, so the days after August 17 hardly change there. They're for comparing with other analytics, not for this check.)

## Did anything else change that week?

THE-SD reported no major budget changes, healthy products and feed, conversion values still arriving, and no catalog changes that explained the timing. The manager's own target edit came on September 10, three weeks after the onset, so it can't explain the August drop, though it muddies anything read after it.

In many threads the poster's own edit sat right on top of the date. An [r/googleads poster](https://www.reddit.com/r/googleads/comments/1wskwfh/pmax%5Fperformance%5Fdropped%5Fafter%5Faug%5F17%5Fread%5Fdetails/?ref=cascader.io) with two budget-constrained Performance Max campaigns raised Target ROAS from about 450% to about 700% "Following Google's Bid Target Adjustment guidance", ahead of the change, and orders then fell about 28%. A legal-services advertiser [wrote](https://www.reddit.com/r/GoogleAdsDiscussion/comments/1wnibps/target%5Fcpa%5Flimited%5Fby%5Fbudget%5Factual%5Fcpa%5Fhasnt/?ref=cascader.io): "On August 17, we adjusted the Target CPA." When your edit and Google's change land in the same week, the data can't separate them, and only one of the two is a variable you control. Check Change history for the exact date of any target edit. Check the History tab for auto-applied recommendations too: Google lists "Adjust your CPA targets" and "Adjust your ROAS targets" among those that [can be applied automatically](https://support.google.com/google-ads/answer/10279006?ref=cascader.io). Google's [Change history page](https://support.google.com/google-ads/answer/19888?ref=cascader.io) also says that changes "made by Google representatives during consultations" aren't always listed, so if a rep made changes on a call, write down what they were.

## Did its own bids rise, or was it outbid?

The pattern of dearer clicks and fewer of them has a twin. It's also what you'd see if competitors started bidding harder and you paid to keep up. Data Bid Machine's checklist, the ten-step guide mentioned above, lists "Auction pressure, changed targets, or a different traffic mix" as the possible causes when CPC rises while click volume holds, and points to bid targets, query mix and auction insights as the places to start. Those are the right places. The checklist doesn't say what reading in them would rule a cause out.

An r/googleads poster running a German e-commerce account [found a sharper test](https://www.reddit.com/r/googleads/comments/1w9vjtq/the%5Faug%5F17%5Ftargetenforcement%5Fchange%5Flanded%5Fon%5Fmy/?ref=cascader.io): "The thing that made it click for me was checking position rather than cost." The main Search campaign ran Maximize Conversion Value with a Target ROAS of 11 (1,100%) on €60 a day, losing about 90% of its impression share to budget. From August 8 to 26 it bought clicks at €0.22, 429 a day, at 33× ROAS. On August 27, CPC jumped to €0.67 and clicks fell to 172 a day, and ROAS went to 9.1×, near the target of 11\. Absolute-top impression share rose from 30% to 48%, and impression share lost to rank fell from 5.8% to 4.2%. "So we weren't pushed out by anyone — we climbed the page while paying 3x."

That's the test. If you pay more and climb, your own bids went up. If competitors had outbid you, your position would have held or fallen. A rising position doesn't prove nobody else bid up at the same time, but it puts your own bidder at the center of the story.

The post's own numbers don't all hold up. At 429 clicks and €0.22, the campaign spent about €94 a day before the jump; at 172 clicks and €0.67, about €115 after. Both are above the €60 budget, and neither supports the poster's line that "Spend didn't change". The CPC chart also shows prices already climbing from August 18 to 23, before the jump. So don't lean on the size of the jump or on the spend claim. The position inference doesn't need either: it rests on two impression-share columns moving the opposite way to cost, and nothing in the discrepancies touches those. Read the case for its method, not its magnitude.

The same poster's next move is a warning. On September 1, because ROAS was falling, the target was lowered from 11 to 9.5, and CPC rose again, from €0.55 to €0.75\. In a budget-limited campaign, a lower ROAS target is permission to pay more per click.

THE-SD's Shopping campaign has no position figures in its thread, but it has two other readings. Its manager checked auction insights and found "no major new competitors". Then the manager changed the campaign's own bidding. On September 10 the target went from 200% to 400%, and by September 11 that day-old 400% target was removed, with the same $18 budget. By midday on the first full day out of learning, with the campaign still limited by budget, CPC was back around $0.06–$0.07 from the $0.15–$0.18 of the previous weeks. Volume came back with the price: within a few days the manager was reporting roughly 300 clicks a day at around $0.06, against 250 to 350 before the change. If competitors had pushed up prices across the auctions this campaign could enter, a different setting at the same budget would have struggled to buy clicks that cheap, and that many of them, again within a day or two. That price and volume returned together points to the campaign's own bidder as enough to produce the expensive pattern. It doesn't show that competitors raised nothing, and it isn't proof. A bidder without a target can choose different searches, so part of the fall could be a change in traffic mix rather than price, which is why the manager planned to compare product, search-term and device mix. And the manager wrote that seeing the same pattern in two accounts "doesn't prove the Aug update caused it".

The position test above ran on a Search campaign, where Google reports Search top and absolute top impression share alongside impression share lost to rank. Other campaign types need their own reading. In Standard Shopping, the position column is absolute top impression share, which Google's [page on impression share](https://support.google.com/google-ads/answer/2497703?ref=cascader.io) defines as "the percentage of your Shopping ad impressions that are shown in the most prominent Shopping position", reported for campaigns, ad groups and product groups. Dearer clicks with a steady or rising absolute top share, and less lost to rank, point to your own bids, provided the budget stayed the same across the date: Google's [tips for improving that share](https://support.google.com/google-ads/answer/7103386?ref=cascader.io) list a bigger budget, as well as a higher bid, so a budget change moves the column too.

Performance Max needs a different route. Google's impression-share page describes only one impression share for it, combined across Search and Shopping, plus auction insights for comparing the campaign with other advertisers in the same auctions. That page describes no position measure for Performance Max, so the reading to use is the one THE-SD's Shopping campaign gave above, and it exists only after the campaign's own bidding has been changed at the same budget and read. It runs in three steps. First, make the bidding change one under which the campaign keeps spending its budget, as removing the target did for THE-SD. That matters because THE-SD's campaign was "still Limited by Budget" when its price came back, so price and volume could both be read. If daily spend falls below the budget after your change, volume is being set by the target, and a lower price alone can't separate your own bidder from other bidders, because a more selective bidder can find cheaper clicks even if others raised prices. Second, compare where the campaign's spend went by channel, before and after the date and again before and after the bidding change, because Google's page on the change says: "For multi-channel campaigns like Performance Max and Demand Gen, you may also find shifts in how traffic is distributed across different channels." Spend moving to cheaper channels can lower the blended price on its own. Third, read whether price and volume came back together, with the same limits THE-SD's case carries; that counts only once the channel split has been compared. In all three campaign types, dearer clicks with more lost to rank and competitors gaining in auction insights point to other bidders, except where your own target is moving those shares, as the Performance Max case below shows.

Each instrument here can be moved by the thing it's meant to detect. The threads show two ways that happens:

- A comparison campaign that shares your auctions isn't a control. The German poster offered the account's brand campaign, on Target Impression Share, as confirmation: its CPC fell 53% over the same days. But it differs in strategy and queries, and Google notes that your own campaigns can be "eligible to enter overlapping auctions". A covered campaign bidding harder can take auctions, and prices, from a sibling campaign.
- Impression share lost to rank can move with your own target. The Performance Max poster who raised targets from about 450% to about 700% later reported lost impression share to rank at about 49% before August 17, 55% just after, 52% in September at 700%, and 71% in the first five full days after lowering the target to 600%, while loss to budget fell to about zero. A reply read that as being outbid. Another reply pointed out that impression share is impressions over eligible impressions: "if pmax at 600% started qualifying for a lot more generic auctions, the denominator grows". The poster's generic search-term spend had risen from about 23% to 30%. The biggest jump in lost share followed the poster's own target cut, and a falling share can mean a campaign entering more auctions, not losing old ones.

## Outside coverage, the update can reach you only through other bidders

If your campaign wasn't covered, the August change didn't alter how it bids. It could still have been affected, because covered competitors re-pricing shared auctions move the prices you pay. Google allows exactly that route, and posters outside coverage did read their changes that way. One poster, whose Maximize conversion value campaigns the change didn't cover, [saw](https://www.reddit.com/r/PPC/comments/1vrn8g1/my%5Fmax%5Fconv%5Fcampaigns%5Fgot%5Fa%5Fnice%5Fbump%5Fon%5Faug%5F17/?ref=cascader.io) a one-day 40% jump in return on August 17 and wondered whether target campaigns had stepped back from the same auctions. The manager of the large brand campaign on Target ROAS, mentioned earlier, whose campaign wasn't budget-limited when its CPCs doubled, blamed Google rather than the campaign's own bidding and suspected auction insights of hiding new competitors. Neither checked in a way that separates the auction from the campaign's own bidding. Reports from untouched campaigns went both ways. One advertiser whose Shopping and Search campaigns weren't limited by budget in August saw [overall CPC up only 4%](https://www.reddit.com/r/PPC/comments/1weqlyq/what%5Fis%5Fgoing%5Fon/?ref=cascader.io). [Another wrote of manual CPC](https://www.reddit.com/r/googleads/comments/1wj1xtz/how%5Fhas%5Fmanual%5Fcpc%5Fon%5Fgoogle%5Fsearch%5Ffared%5Fwith/?ref=cascader.io): "No change for the campaigns I have on it. Same Imp Share, CPC, Conversion Rate." And some posters outside coverage were still looking for the cause: one saw "CPC is stable , impressions are stable , but [conversions fell off cliff](https://www.reddit.com/r/Google%5FAds/comments/1x41fb5/my%5Fsearch%5Fterms%5Freport%5Flooks%5Ffine%5Fbut%5Fconversions/?ref=cascader.io)", and another, with ad positions and clicks about the same, said [most of their enquiries came by phone and email](https://www.reddit.com/r/Google%5FAds/comments/1x0n1x0/postaugust%5Fupdate%5Fhelp%5Ffor%5Fb2b%5Faccount%5Fplease/?ref=cascader.io), which they didn't track.

There is a clean way to test the auction route, proposed in r/PPC on August 18 by the same Either\_Guess2405\. A manual CPC campaign's bid doesn't move unless you move it. "So if actual CPC drops while my max bid sits still, that's the auction changing rather than my own bidding reacting to it." The same holds for a rise. If you have a manual CPC campaign you didn't touch, in the same market as your affected campaigns, compare its CPC and impression share lost to rank by day either side of the date. If they moved, other bidders changed. If they didn't, the auction route probably isn't your story. One caution: if that campaign shares queries with one of your covered campaigns, only one of your keywords goes into each auction. Google's prioritization rules send the one with the highest Ad Rank when keywords share equal priority, so your covered campaign, bidding harder, can take the manual campaign's impressions. The manual campaign then stops being a clean reading of the market.

Until you've run something like that, treat "competitors reacting to the update" as a hypothesis. In the meantime a within-account checklist (tracking, search terms, landing page, budget) is the right tool, and Data Bid Machine's is a good one.

## What to do with a campaign the change reached

The threads are full of advice pulling in opposite directions, and one thread shows why. In it, the small Performance Max advertiser in the Netherlands whose late onset came up earlier, posting in r/adwords, ran one Performance Max campaign on €50 a day, limited by budget for a long time, with a Target ROAS of 466.59% that Google itself had recommended. After the drop, the advertiser lowered the target to 390%. One reply called that "100% the right move", because a lower target would let the campaign be less selective and bid higher. Another said: "Lowering tROAS is the wrong direction while you're budget-limited." Both were about the same capped campaign. The disagreement is over what a lower target does when spend can't rise, and the September 1 cut in the German e-commerce poster's Search campaign, from a Target ROAS of 11 to 9.5, already answered it: a lower ROAS target is permission to pay more per click, and, as the second reply put it, "with a capped budget higher bids just buy fewer clicks for the same money." Four days later the advertiser reported a real ROAS of 100%. That's an early reading that mixes €147 sales with €10 webinar sign-ups, so it settles nothing, but it gives no support to lowering.

THE-SD went the other way, first raising the Shopping campaign's target from 200% to 400%, toward the 747% the tool had shown. Then, not wanting to chase a historical figure that "isn't necessarily my business-required ROAS", the manager removed the target and ran Maximize Conversion Value on the same $18 budget, which is one of the options Google's own page lists. Over the following weeks the manager reported CPC around $0.04–$0.06, 300 to 400 clicks a day, the status moving from Limited by budget to Eligible, impression share recovering to about 40%, and ROAS reported at about 800% over a week and later 900–1,000%. Sales were erratic in the first days, and these are the manager's figures, unaudited. Another poster in the same thread raised a Shopping campaign's target about 1.3 times, in steps, until "Limited by budget" disappeared, and reported regaining "the original performance".

Raising a ROAS target toward the return the campaign actually earned, and removing the target, both fit what the change does: each stops the bidder paying more per click to reach a return the campaign was already beating. Lowering a ROAS target in a capped campaign does the opposite. For a covered campaign that had been running well ahead of its target, we'd take the option Google's page gives for exactly that case: move the target toward the return or CPA the campaign was actually achieving before August 17, then leave it for one to two conversion cycles before judging. If the new target is more efficient than what the campaign is delivering now, Google's FAQ adds a condition: "keep in mind that your daily spend will likely be impacted." So watch daily spend after the move. If it falls below the budget, the campaign is no longer limited by budget, and so no longer covered: Google says target campaigns that aren't budget-constrained "won't change their behavior", and the target, not the budget, is now what holds spend down. For a Performance Max campaign, that also ends the price-and-volume reading described in the section on whether the campaign's own bids rose: once spend is below the budget, that reading isn't available. That's when to decide whether you want the whole budget spent. If spending less at the new return suits the business, hold. If you want the budget spent, there are two ways to ask for it, and Google's FAQ lists both. One is to loosen the target a step and read it again after another conversion cycle or two; the FAQ notes you can "adjust your bid targets to manage campaign spend", and with the campaign no longer capped, a looser target buys more spend rather than only dearer clicks. The other is to remove the target and switch to Maximize conversions or Maximize conversion value, which the FAQ offers for a budget that's "strictly inflexible". Removing the target is what THE-SD's campaign did, and by its manager's unaudited report its results recovered. Which target and budget combination is right for a given campaign, depending on whether its budget is a fixed limit or one you'd raise whenever conversions pay, is the subject of our essay [What a Target Does When the Money Runs Out](https://cascader.io/blog/what-a-target-does-when-money-runs-out/). The steps for setting and reading a target are in our [Target CPA and Target ROAS guide](https://cascader.io/blog/google-ads-target-cpa-target-roas/).

Before any of that, you can usually say something true within a day. Google changed how budget-limited target campaigns bid from August 17 to 27, and it changed no settings and no auction rules. In the weeks before, this campaign was or wasn't losing impressions to budget on a target. Its CPA or ROAS was or wasn't running well ahead of that target. We did or didn't change the target that week. The days since the date have or haven't finished filling in with late conversions. Its position rose or fell as its costs went up, or, for a Performance Max campaign, where Google's impression-share page describes no position measure, we'll read price, volume and the channel split after the change we're making, provided the campaign is still spending its budget. And here is the one change we're making, and the date we'll read it, one to two conversion cycles out, as Google advises.

That statement is less dramatic than "it's the update" and less dismissive than "it's probably your tracking." It's also the only version anyone can check. The next time a thread fills with "same here", the reply worth writing is the question these threads so often left unanswered: in the weeks before August 17, was the campaign losing impressions to budget, and was it beating its target?