On June 15, 2026, Google announced Promotion Mode — a beta feature for Search and Performance Max that lets advertisers pre-schedule a temporary relaxation of their ROAS target and a budget boost for a defined date range. When the window ends, the campaign reverts to its baseline settings automatically. The Search Engine Land announcement described it as a way to schedule "temporary ROAS-tolerance changes and extra daily budget for peak events."
For B2B SaaS companies running automated bidding, this solves a specific operational problem: how to increase aggression for a product launch, conference sprint, or end-of-quarter push without manually adjusting targets and risking a forgotten revert that bleeds budget for weeks. This post covers when to use Promotion Mode, how to configure it for B2B SaaS use cases, and how to measure whether a sprint actually paid off.
What Promotion Mode does and does not do
Promotion Mode is a scheduling layer on top of your existing bid strategy. It does not change your campaign type, targeting, or creative. What it changes is the constraint under which Smart Bidding operates during a defined window: the ROAS floor is relaxed, meaning the algorithm is willing to bid on queries it would otherwise decline because the expected return falls below your usual threshold. The budget ceiling is raised, giving the algorithm more to work with during the sprint. When the window closes, both parameters revert automatically without any manual action.
It is important to be specific about what Promotion Mode is not. It is not a separate campaign or a temporary ad schedule — it operates on your existing campaign with your existing keywords, audiences, and negative keyword lists. It does not override your bidding strategy type; if your campaign runs Target ROAS, it remains Target ROAS during the promotion with a temporarily relaxed target. And it is not a substitute for a well-configured baseline: if your conversion tracking is broken or your attribution window does not match your sales cycle, a Promotion Mode sprint will simply buy more of the same mis-attributed traffic at a higher cost. Fix the foundation first — see our conversion tracking guide.
Beta access and eligibility
As of June 2026, Promotion Mode is in beta for Search and Performance Max campaigns. Access is not universal — Google distributes it to eligible accounts on a phased basis. To check whether your account has access, navigate to the budget and bidding settings of an eligible Search or Performance Max campaign and look for a Promotions section. If the field is not present, your account is not yet in the beta pool. According to the ppc.land coverage of the June 2026 announcement, the feature is part of a broader bidding overhaul that includes the August 17 Bidding Target Optimization change and the global expansion of Smart Bidding Exploration.
If your account does not have access yet, the right move is to document the B2B SaaS sprint events on your calendar and plan the configuration in advance. Promotion Mode requires forward scheduling — you set the window ahead of time rather than activating it in the moment. For teams planning Q3 product launches or conference pushes, noting the dates now so the configuration is ready when access arrives will prevent a scramble at launch time.
When Promotion Mode makes sense for B2B SaaS
B2B SaaS has a specific calendar of events where temporary aggression in paid search generates outsized returns. Product launches are the clearest case: there is a defined window when your product is in the news, your sales team is running demos, and high-intent queries for your category see a short-term spike in volume. A two-week promotion window around the launch date — starting a few days before the announcement and running through the first full week of active marketing — captures the intent surge without permanently inflating the budget.
G2 review campaigns and end-of-quarter conversion pushes are two other cases where the sprint model fits B2B SaaS well. G2 review periods correlate with higher purchase intent from buyers researching categories on review sites, and a short Google Ads promotion window running concurrently can capture the buyers who move from G2 to Google. End-of- quarter pushes are common across SaaS sales motions — buyers often have budget to commit before a period closes, and a two-week promotion window in the final weeks of a quarter can meaningfully accelerate pipeline. The key discipline in all these cases is that the sprint has a defined end date and a clear measurement criteria before it begins, not after.
How to configure a sprint
A well-configured Promotion Mode sprint for B2B SaaS starts with three decisions before you touch the platform settings. First, define the event: what is triggering the sprint, when does it start, and when does it end? Sprint windows of 7 to 14 days are a reasonable default — long enough for Smart Bidding to learn the relaxed constraint and act on it, short enough to contain the cost exposure. Second, define success: what metric will you use to evaluate whether the sprint paid off? For B2B SaaS, that should be cost per SQL or cost per qualified opportunity in your CRM, not cost per form fill. Set a threshold in advance: "we will accept up to $X per SQL during the sprint window, measured over a trailing 30 days post-sprint to capture lagging conversions." Third, document the baseline: your pre-sprint tCPA or tROAS, daily budget, and trailing 30-day cost per SQL. Without a clean baseline, post-sprint analysis is guesswork.
For the configuration itself, the ALM Corp 2026 Google Ads update guide notes that Promotion Mode accepts a ROAS flexibility parameter and an optional budget increment. For B2B SaaS product launches, a starting point is a 15 to 25 percent relaxation in your ROAS target and a 30 to 50 percent daily budget lift. These are not universal numbers — they depend on your baseline efficiency, how competitive your category is during the event window, and how much of a pipeline spike you are trying to generate. Run the math from your unit economics: if your average ACV is $30,000 and your acceptable CAC is $3,000, you can afford to relax your ROAS target as long as the campaign is still generating SQLs that close at that rate.
Measuring whether the sprint paid off
Post-sprint measurement for B2B SaaS requires the same offline conversion infrastructure that makes baseline measurement meaningful. A sprint that generated 40 form fills during launch week looks fine in-platform — but if your sales cycle is 60 days, the pipeline outcome of those 40 leads will not be visible for two months. The correct measurement approach is to tag all leads from the sprint window in your CRM (the GCLID field does this automatically if set up), track them through the pipeline over 90 days, and calculate the cost per closed deal attributable to the sprint. Compare that to your baseline cost per closed deal from non-sprint periods.
Three metrics tell you whether the sprint justified its cost. First, did cost per SQL during the sprint window stay within your defined threshold? This is your efficiency guardrail — if it blew past the threshold, the ROAS relaxation went too far. Second, did SQL volume increase meaningfully compared to equivalent non-sprint periods? If you spent 40% more and got 40% more SQLs, the sprint was volume-neutral on efficiency, which may or may not be useful depending on whether you had capacity to work those leads. Third, did the quality of SQLs hold? A sprint that produces 40% more leads at the usual quality is a success; one that produces 40% more leads by pulling in out-of-ICP traffic is a failure disguised as a success. Your sales team's feedback on the sprint batch is the fastest proxy for quality before the CRM pipeline fully resolves.
What to watch for
The most common sprint failure is not a bad configuration — it is a forgotten revert on a manual adjustment that was standing in for Promotion Mode before the feature was available. If you have a habit of manually lowering Target ROAS or raising budgets during launch events and then letting them drift back, Promotion Mode is strictly better because the revert is automatic. However, in accounts that are already running manual adjustments for an ongoing promotion, activating Promotion Mode on top of those adjustments layers the effects — verify that no manual bid adjustments are compounding with the promotion window.
The second pitfall is running a sprint on a campaign without sufficient conversion data. Smart Bidding requires a minimum volume of conversions to operate effectively — for most B2B SaaS accounts, that is at least 30 to 50 conversion events per campaign per month at the baseline before adding a sprint. Below that threshold, the algorithm does not have enough signal to manage a relaxed ROAS efficiently, and the result is unpredictable spend with uncertain return. If your campaign volume is below that level, the better sprint mechanism is a manual budget lift with a manual Target CPA reduction, which is more predictable on thin data than ROAS flexibility. For the overall question of how to structure your bidding before reaching that volume threshold, see our bidding strategies guide for B2B SaaS.
Finally, be aware that the August 17, 2026 Bidding Target Optimization change will affect campaigns that were budget-limited and over-delivering on their stated tCPA or tROAS targets. If your baseline campaign was quietly outperforming its target before August 17 and the change pulls it back toward the stated target, the cost of your sprint windows will be calibrated against a different baseline than before. Audit your targets before August 17 and adjust them to reflect the efficiency you actually want — your promotion windows should be designed as relaxations of a well-calibrated target, not workarounds for a loose one. See also our post on how much to spend on Google Ads for the budget framing behind these decisions.