PPC practitioners in two practitioner discussions are debating how much preparation Google's August 17 bidding change requires. The dominant response is restrained: set the CPA or ROAS target the account actually needs, avoid a snap reaction, and watch what campaigns do. The strongest opposing position is more cautious. Commenters with firsthand campaign observations argue that target setting alone does not guarantee the announced behavior, so advertisers should test and prepare before assuming the change is narrow or predictable.

The dominant response is to set the target and observe

Several practitioners in the discussions argue that the update has narrower triggering conditions than the reaction implies. Their comments recommend choosing the CPA or ROAS target the advertiser genuinely wants and then allowing the campaign to produce enough data before making a broader intervention. One participant reports that periods of target-CPA overperformance in their accounts are often followed by weaker periods that bring the longer window back toward the target.

Other commenters describe a similar wait-and-measure approach but stop short of calling the outcome certain. One practitioner says they prepared clients for a potentially unusual week while resisting changes based only on a forecast. A configuration-specific fringe position adds that campaigns using Maximize Conversions without a target CPA may face less direct impact, although those commenters still recommend monitoring results after the change. the available comments present those expectations as tentative, not documented guarantees.

The strongest counter-position says testing is necessary

A common evidence-backed counter-position argues that a correct target is not enough. One practitioner reports smart bidding spending the available budget without reaching its target across several conversion cycles, then reaching the target after the budget was reduced. Commenters use that kind of account behavior to argue for preparation and controlled testing rather than passive confidence in the announced model.

Another participant points to earlier brand-keyword CPC changes associated with phrase-match behavior as a reason to consider effects beyond one campaign's target. these observations do not establish what the August change will do, but they directly challenge the dominant assumption that setting the desired target and waiting is sufficient. In the discussion, this is the most important dissent because it relies on observed account behavior rather than motive speculation.

Shared portfolios may need a separate reading

A minority position distinguishes portfolio campaigns from individually capped campaigns. One practitioner reports wide campaign-level CPA variation inside a portfolio that still meets its blended target. The commenter also relays a platform representative's statement that shared budgets used with shared bid strategies should limit the change's effect on campaign-level CPA ranges.

A reply in the discussion narrows that expectation by arguing that the shared budget's constraint still matters. Under that view, an unlimited shared budget and a budget-limited portfolio should not be treated as the same setup. the exchange does not resolve the product behavior, but it identifies a configuration that practitioners believe deserves separate observation.

The argument over motive remains unsupported

A common reaction in the older source discussion describes the change as revenue-driven or a cash grab rather than credible preparation for AI advertising. Commenters criticize the communication and express distrust of the strategic explanation. the discussion offers no documentation of motive, so those claims remain attributed interpretations rather than facts about why the platform made the change.

A minority view accepts that a longer-term move away from per-click buying is plausible. Commenters point to Local Services Ads and the apparent integration of that pay-per-lead product with Performance Max as a visible product direction. They present that path as speculation grounded in existing product behavior, not as confirmation that the August update is part of a declared roadmap.

Pay-per-lead creates its own disagreement

The discussion also preserves an evidence-backed objection to a pay-per-lead future. One practitioner describes reviewing Local Services Ads calls that included existing customers, wrong numbers, and silent callers among charged leads. Another commenter reports repeated behavior from an earlier display pay-per-conversion experiment and treats current lead-quality disputes as a warning.

Those practitioners argue that advertiser-defined conversions, inconsistent attribution, and disagreement over lead quality make outcome-based billing difficult. Other commenters still see a platform incentive to improve the search-to-lead path and reduce reliance on advertiser landing pages. the available material therefore supports a plausible direction and a practical constraint at the same time; it does not settle which will dominate.

What remains unresolved

The two source discussions do not show how accounts performed after the August 17 change, which campaign configurations were ultimately affected, or whether the long-term AI and pay-per-lead interpretations were correct. They show a dominant preference for measured observation, an evidence-backed case for active testing, configuration-specific questions about shared portfolios, and unresolved disagreement over motive and future billing models.

Coverage remains limited to the discussions reviewed, not practitioners as a whole.