Tag: Ad Scheduling

Human Judgment Is the Control Layer for Automated Ads

You have an hour-of-day row with spend and no conversions, an automated campaign that feels opaque, and someone asking you to "fix the waste." Excluding the hour looks decisive. It is also exactly where human judgment matters: not because a person can outbid a system one auction at a time, but because only a person can decide whether that row is mature, meaningful, and worth turning into an eligibility rule.

Your job in automated advertising is no longer to touch every lever. It is to define the right outcome, protect the quality of the inputs, challenge weak evidence, and own changes that remove opportunities. The practical goal is not more manual control. It is better control over what the automation is allowed to decide.

Put human judgment at the decision boundary

Automated systems are strongest when they make frequent decisions inside a clearly defined objective. A bidding system can evaluate an auction, combine contextual signals, and adjust its bid faster than a campaign manager could. It cannot decide whether the objective itself represents a profitable customer, whether an overnight lead will receive an acceptable response, or whether the business should trade margin for growth.

That distinction gives you a usable division of responsibility:

Decision	What automation should do	What a person must own
Auction execution	Evaluate eligible auctions and adjust bids within the chosen strategy.	Choose the business objective, budget, constraints, and acceptable tradeoffs.
Data preparation	Group records, calculate fields, identify anomalies, and assemble recurring reports.	Verify definitions, attribution, data maturity, and whether the records represent real business outcomes.
Campaign eligibility	Respect targeting, schedules, exclusions, and other account settings.	Decide which opportunities the campaign should never be allowed to enter.
Performance diagnosis	Surface patterns and produce candidate explanations.	Determine which explanation is credible and what evidence would disprove it.
Final approval	Prepare a recommendation or execute an approved, bounded workflow.	Accept accountability for the consequences and authorize the change.

A simple boundary works well: let automation make high-frequency, reversible choices within an approved objective. Require human review when a decision changes the objective, conversion definition, customer promise, account eligibility, or exposure to wasted spend.

Before approving an automated recommendation, ask four questions:

What outcome is the system actually optimizing?
Which business facts cannot be seen in the platform data?
Does this recommendation tune execution, or does it remove an audience, location, device, query, or time period from consideration?
Who will decide whether the result was acceptable after conversion lag and downstream sales are visible?

If nobody can answer those questions, the problem is not insufficient automation. It is an undefined decision boundary.

An ad schedule is an eligibility rule, not a cleanup tool

Hour-of-day reports invite a common mistake. You see a weak average, label the period inefficient, and remove it. That reasoning treats every auction in an hour as if it had the same probability and value.

Google Ads Smart Bidding works at a different level. Target CPA, Target ROAS, Maximize Conversions, and Maximize Conversion Value use auction-time bidding, with time of day and day of week among the contextual signals that can inform an individual bid. Device, location, and audience characteristics can also change the assessment. The system is not deciding that an entire hour is universally good or bad. It is evaluating the eligible auctions that occur during that hour.

This makes the effect of scheduling easy to misread. Manual ad-schedule bid adjustments are not used by Smart Bidding, but the schedule itself is respected. Removing Tuesday morning does not tell the bidding system to be more selective on Tuesday morning. It makes every Tuesday-morning auction ineligible, including any valuable ones the hourly average concealed.

A row with four clicks and no conversions proves only that those four recorded clicks did not yet show a conversion. It does not establish that the hour is intrinsically unprofitable. Nor does it estimate what would have happened in future auctions if the campaign had remained eligible.

Scheduling can still be the correct decision when the restriction represents a real business constraint:

Home services and call-driven lead generation: Restricting delivery may be justified if an overnight inquiry cannot be answered promptly and the delayed response materially reduces its value. If those leads perform well when contacted later, the schedule would remove opportunity without fixing a business problem.
Appointment-based businesses: Capacity can be the binding constraint. Acquiring more demand may stop being useful once the available appointments are full.
Ecommerce: Customers can buy outside office hours. Operating hours alone therefore provide little basis for an exclusion; look for persistent differences in conversion value and profitability.
Restaurants: Opening hours, ordering hours, and reservation-search hours are not the same. Someone can make a valuable reservation before the doors open or after service ends.
B2B: Research does not stop at the office door. A nighttime search can produce a qualified inquiry that the sales team handles the following day.
News and publishing: Breaking events, elections, sports, and entertainment can move demand into hours that looked weak historically. A rigid schedule cannot anticipate every shift in attention.

The rule is straightforward: use a schedule when you intend to prohibit participation, not merely because you want the bidding system to be cautious. If you would still want the right customer during that period, an absolute exclusion is a blunt response.

Use a five-part evidence gate before restricting automation

An analyst examines five visual checkpoints leading to a gated automation system.

An automated account can generate more segmented data than a person can sensibly act on. There are 168 hours in a week before you add device, location, audience, campaign, or conversion type. Some rows will look unusually strong or weak by chance. Human judgment begins with refusing to confuse a visible pattern with a reliable decision.

Wait for enough observations. Expand the date range until the pattern has had a reasonable chance to repeat. In many accounts, 60 to 90 days is a more useful starting window than a few recent days, but it is not a universal threshold. A high-volume account may mature sooner; a low-volume account or long sales cycle may need more time. The test is repeated evidence, not compliance with an arbitrary number of days.
Let conversions mature. A click can convert hours or days later. Google Ads generally assigns the conversion to the date of the ad interaction, so a recent period may temporarily show its spend before all associated conversions have arrived. Check the account’s typical conversion delay before declaring yesterday evening inefficient. If the outcome data is still arriving, the conclusion is still changing.
Inspect value below the average. Conversion count and average CPA may omit the result that matters. Review conversion value, lead quality, downstream sales, and customer value where those signals are available. A period with fewer conversions may still acquire better customers. Conversely, a superficially efficient period may be producing low-quality actions that never become revenue.
Identify the business mechanism. Ask why the time period would be less valuable. A credible explanation might involve response time, fulfillment, inventory, staffing, or appointment capacity. If you cannot name a mechanism, treat the pattern as a question to investigate rather than a rule to implement. If the mechanism is operational, consider fixing the operation before suppressing demand.
Test the restriction against broader eligibility. When traffic volume supports a meaningful comparison, test the scheduled version against a version that remains eligible for more hours. Use the business KPI that motivated the decision, allow for conversion lag, and change one major eligibility dimension at a time. One documented restaurant test found that unrestricted delivery produced 12% more conversions while reducing CPA by 3%. That is a single account result, not a universal benchmark; its value is showing why the counterfactual must be measured rather than assumed.

This gate separates two different questions. The report asks, "What performance was recorded during the auctions that occurred?" The decision asks, "Will prohibiting future auctions improve the business result?" You cannot answer the second merely by sorting the first from worst to best.

Document the decision before launch. Record the proposed restriction, the evidence window, known conversion delay, primary KPI, downstream quality check, operational rationale, test design, owner, and review point. That short record prevents a temporary anomaly from becoming permanent account folklore.

Build an operating loop that removes labor, not accountability

Two advertising professionals oversee a circular automated workflow while mechanical arms handle routine tasks.

There are usually two kinds of automation in the same advertising workflow. The ad platform automates delivery and bidding. Analyst-facing AI can summarize meetings, organize exports, flag anomalies, draft formulas, generate basic scripts, and turn findings into review-ready formats. Both can save time, but neither should silently expand its own authority.

Use this operating loop for consequential campaign changes:

Frame the decision. Write one sentence naming the action under consideration and the business result it is meant to improve. "Reduce wasted spend" is too vague. "Determine whether overnight eligibility lowers qualified-lead profitability after leads have matured" can be tested.
Assemble the evidence. Let approved tools merge exports, label time periods, calculate recurring fields, and flag unusual movement. AI is well suited to categorizing large datasets and surfacing changes that require investigation. Keep sensitive data inside approved systems and verify calculated fields before relying on them.
Expose what the platform cannot see. Add sales acceptance, revenue, lead disposition, staffing constraints, inventory conditions, and other business context that is absent from the advertising interface. If the optimization signal rewards form submissions while the business needs completed sales, fix or supplement the signal before asking the algorithm to optimize harder.
Generate challenges, not verdicts. Ask AI to find missing information, contradictory evidence, immature periods, unusually small samples, and alternative explanations. Do not ask it to make a final pause-or-expand decision from a summary table. AI can identify where something changed; the causal explanation still needs validation.
Approve a bounded test. A person chooses the hypothesis, success measure, duration appropriate to the conversion cycle, and rollback condition. The system can then execute within those limits. Eligibility changes deserve particular care because the excluded auctions stop producing evidence once they disappear.
Review and record the outcome. Wait for the agreed data to mature, compare the result with the predeclared KPI, check downstream quality, and record what changed. Meeting transcription and task extraction can remove administrative work by capturing decisions, owners, deadlines, and unresolved debates, but the meeting owner should review the output before it becomes the record.

Prompt design should reinforce that boundary. Instead of asking, "Which hours should we turn off?" ask:

List time periods with persistent performance differences and show the observation count, date range, and conversion maturity for each.
Separate facts in the export from possible explanations that require validation.
Flag periods where conversion count, conversion value, and downstream lead quality point in different directions.
Identify which proposed actions tune execution and which actions remove campaign eligibility.
Draft a test plan and a list of missing inputs, without making the final approval decision.

The same principle applies to technical work. AI can draft spreadsheet formulas, SQL, regex, account scripts, or reporting logic. Those outputs are useful because you can test whether they work. Review generated code, run it in a safe and limited context, and verify its output before it can change a production account. Fluent text is not proof of correct logic.

Measure automation by the labor it removes and the errors it helps catch: rows reviewed, analysis time saved, anomalies surfaced, manual steps eliminated, revision cycles, and error rate. Measure the human control layer by decision quality: valid conversion signals, explicit ownership, mature evidence, reversible tests, and fewer unexplained account restrictions. Faster execution is valuable only when it carries a sound decision forward.

Key takeaways

Let automated bidding make auction-level choices within a business objective that a person has defined and can defend.
Treat schedules, exclusions, and targeting limits as eligibility decisions. They remove opportunities rather than instructing Smart Bidding to bid more carefully.
Do not act on a weak hourly row until you have enough observations, mature conversions, business-value data, and a plausible mechanism.
Test restrictions against broader eligibility when volume permits. Historical averages do not reveal the outcome of auctions you choose not to enter.
Use AI to prepare evidence, find gaps, document decisions, and produce testable technical work. Keep strategy, prioritization, approval, and accountability with people.

At your next account review, take one proposed automation change and label it either an execution aid or an eligibility decision. Automate the labor around the first. Put the second through the evidence gate before approving it. That small distinction is where responsible automated advertising starts.

References

September 3, 2026

Resolving Delays in Google Ads Demand Gen Reviews

I’ve recently experienced frustrations with Google Ads as there’s a known issue causing Demand Gen ads to face review delays of over a week. Google acknowledges this problem and assures us that they’re working on a solution.

Some of us advertising on Google have noticed our ads are lingering in review, taking more than seven days—something that deviates from normal review timelines.

What’s happening. Matthew Skelton, a senior PPC specialist I follow, has pointed out a trending issue: Demand Gen campaigns stuck in review for an unexpectedly long time. This delay is noticeable across various accounts and industries, seemingly without any policy breaches causing it.

Interestingly, other campaign types, like Search and Performance Max, aren’t affected and continue processing as usual, which suggests the problem is isolated to Demand Gen ads.

Why we care. For those of us using Demand Gen to test creatives and drive top-of-funnel results, speed is crucial. Long review times hinder our ability to iterate swiftly, delay launches, and make it challenging to respond to seasonal trends or time-sensitive opportunities.

A delay lasting a week can disrupt our pacing and diminish the effectiveness of campaigns relying on rapid optimization.

The response. Ginny Marvin, a Google Ads Liaison, acknowledged this issue specifically impacting Demand Gen image ads, admitting reviews are taking longer than anticipated. She assured us that Google’s team is actively seeking a solution, but no clear timeline has been provided yet.

Bottom line. If you’re experiencing delays with your Demand Gen ads, know that it’s a widespread issue acknowledged by Google rather than something you can directly address.

First seen. This situation was first reported by Matthew Skelton, who shared his insights on LinkedIn.

Inspired by this post on Search Engine Land.

April 24, 2026

How to Audit Campaign Controls Before You Optimize Spend

Your campaign can look more efficient while becoming harder to control. Spend may be compressed into fewer active days, conversion signals may be incomplete, and a polished dashboard may show activity without giving you the controls needed to explain or stop it.

If performance changes without a clear bid, audience, or creative change, audit the control layer first. You need to know what the platform is allowed to do, what data its optimizer can see, and whether your reports describe the same system you configured.

Key takeaways

Budget, schedule, consent, optimization, and reporting are separate controls. Changing or validating one does not validate the others.
A restricted ad schedule may concentrate spending rather than reduce the campaign’s monthly spending limit.
Consent diagnostics should help you locate missing or inconsistent signals. A consent rate is not a target to maximize at the expense of genuine user choice.
A dashboard is not a mature control system unless you can inspect state, enforce changes, verify their effects, and reconstruct who changed what.
Paid placement in an AI interface and earned visibility in a generated answer require separate attribution and reporting.

Audit the whole control chain before touching bids

Campaign optimization is usually treated as a bidding problem. In practice, bidding is only one link in a chain. The platform first determines whether an ad is eligible, then how much it may spend, which signals it can use, what decision automation should make, and what evidence you get afterward.

A weakness anywhere in that chain can produce a misleading result. A schedule can alter the concentration of spend. A consent implementation can reduce observable conversions. A reporting delay can make a stable campaign appear volatile. Raising or lowering a bid before resolving those conditions adds another variable without answering the original question.

Control layer	Question to answer	Evidence to record
Business constraint	What outcome, total cost, or operational load can you accept?	Approved spending ceiling, capacity limit, and stop condition
Eligibility	When is the campaign allowed to enter auctions?	Active days and hours, plus the business reason for each restriction
Delivery	How may the platform allocate spend while the campaign is eligible?	Budget values, bidding mode, spending caps, and documented pacing behavior
Signal	Which conversions and consent states can the optimizer observe?	Conversion definitions, consent diagnostics, and coverage by relevant dimension
Observation	Can you explain what happened after delivery?	Reporting latency, available breakdowns, exports, attribution settings, and change history

Run the audit in that order. Starting with reports is tempting, but a report cannot tell you whether the configured business constraint was correct. Starting with bidding is worse because the optimizer may be responding rationally to a budget, schedule, or signal state you did not intend.

Write down the campaign’s intended result and its hard constraint. Separate a performance target from a limit the platform must not cross.
Capture the current schedule, budget, bidding mode, conversion actions, consent state, targeting, and exclusions. Use actual settings, not what the launch plan says should be configured.
Translate settings into effective exposure. For example, calculate the monthly spending ceiling and inspect how much delivery could be compressed into eligible periods.
Check whether the optimizer receives the signals you expect across apps, platforms, regions, and traffic sources. Treat gaps as unresolved until you have distinguished user choice from an implementation problem.
Verify that important controls are enforceable. A pause button, budget edit, or exclusion is useful only if you can confirm its scope, timing, and effect.
Record each change with the old value, new value, timestamp, reason, expected effect, evaluation window, and stop condition. Where practical, avoid changing another layer before the first change can be evaluated.

This gives you a baseline that optimization can build on. Without it, every performance movement invites a new theory, and several contradictory theories may fit the same aggregate chart.

Scheduled campaigns need a spend-concentration audit

A hand adjusts a scheduling gate above a blank calendar grid where glowing budget tokens are concentrated into only a few active tiles.

A budget limits spending; a schedule limits eligibility. Those settings may feel interchangeable when a campaign runs only on selected days or hours, but they answer different questions.

Under Google’s scheduled-campaign pacing model, a campaign can pace toward its full monthly spending limit even when its ads are not eligible every day. Disabled days remain disabled, but the system has more reason to capture available demand during the periods that remain open.

The stated limits make the exposure calculable: the monthly spending cap remains 30.4 times the average daily budget, while spending on an individual day can reach up to twice that daily budget. These are ceilings, not promises about what the campaign will spend.

The practical correction is simple: do not assume that fewer eligible days will produce a proportionally smaller monthly bill. If you intend to reduce total exposure, set the budget to reflect that intention. Keep the schedule focused on when the business can serve demand or when traffic is valuable.

Find every non-continuous schedule. Include campaigns limited to particular weekdays as well as those restricted to certain hours.
Write down why the restriction exists. A schedule tied to staffing, inventory, response time, or lead quality is an operational guardrail. Do not remove it merely to smooth a spending chart.
Calculate the monthly ceiling. Multiply the average daily budget by 30.4, then compare that amount with the total monthly exposure you actually approved.
Check the active-day boundary. Ask whether spending up to twice the average daily budget on an eligible day would create a cash-flow, inventory, or service-capacity problem.
Review eligible periods directly. Monthly averages can hide concentrated delivery. Inspect spend, conversions, and downstream quality during the windows when ads were allowed to run.
Change the correct control. Lower the budget when the total amount is too high. Narrow or widen the schedule only when eligibility itself is wrong.

This distinction also improves diagnosis. Faster spending during active periods does not automatically mean bidding has become more aggressive or demand has improved. It may be the predictable result of the pacing system trying to use the same monthly allowance within fewer opportunities.

Consent diagnostics tell you whether the optimizer can learn

An analyst examines anonymous data signals passing through transparent consent gates toward an unbranded optimization engine, with some signals blocked or fading.

An optimizer cannot act on a conversion it cannot observe. That makes consent signal quality part of campaign operations, not a separate technical housekeeping task.

Google Ads’ App Consent Insights exposes consent diagnostics across apps, platforms, regions, and traffic sources. The view includes an overall rating of Excellent, Good, or Poor, a live count of apps sending consented data, and conversion consent rates with EEA and non-EEA differences.

Use those dimensions to localize a gap. Do not interpret the account-level rating as a complete diagnosis. A lower rate could reflect genuine user choices, traffic composition, a deployment inconsistency, or missing signal transmission. Those possibilities need different responses.

List the apps and platforms that should be sending consent information. Compare that inventory with the live count shown in the diagnostic.
Locate the narrowest break. Determine whether the difference belongs to one app, one platform, one region, one traffic source, or a wider implementation.
Compare EEA and non-EEA results without assuming geography is the cause. Review the regional consent implementation and the underlying traffic mix separately.
Validate the technical path from the consent choice to the advertising platform. Confirm that the relevant state is collected, transmitted, and associated with the intended conversion setup.
Annotate the release or configuration change that corrected a gap. Keep unrelated budget and bidding edits out of the same evaluation window where possible.
Reassess campaign performance only after the corrected signal flow has had an appropriate observation period for your normal conversion lag.

The overall rating is a diagnostic indicator, not an optimization objective. Do not make a consent experience more coercive just to lift a platform metric. Changes to consent language or interaction design should remain under the appropriate privacy and legal review. The campaign team’s job is to make sure a valid choice is transmitted accurately and that missing instrumentation is not mistaken for user behavior.

This protects decision quality in both directions. You avoid blaming creative when measurement is incomplete, and you avoid treating every consent-rate difference as a tagging failure. Once signal coverage is understood, bidding and conversion reports become easier to interpret.

Prove an AI ads manager can control delivery before scaling it

New advertising interfaces can improve access long before their control systems become mature. OpenAI is testing a ChatGPT Ads Manager that moves beyond weekly CSV reporting toward real-time campaign management, monitoring, and optimization. That is meaningful progress, but testing an interface is not evidence that every targeting, reporting, governance, or automation capability is complete or broadly available.

Evaluate an emerging ad manager by what you can verify, not by how familiar its dashboard looks. For every requirement, distinguish between a control that is promised, a control visible in the interface, and a control whose effect you have confirmed.

Authority: Can the authorized operator pause delivery, edit budgets, and reverse a change at the required account or campaign scope?
Budget semantics: Is the budget daily, monthly, lifetime, or another form? How is pacing described, and what prevents an unexpected concentration of spend?
Eligibility and exclusions: Which scheduling, targeting, placement, brand-safety, and exclusion controls actually exist? Do not assume parity with Google Ads or Meta because the navigation feels familiar.
Measurement: Which event counts as a conversion, what attribution rules apply, how quickly do results appear, and can reported totals be reconciled with your analytics?
Diagnostic depth: Can you break performance down far enough to separate delivery, audience, creative, placement, and signal problems?
Auditability: Is there a change history showing who changed a setting, when it changed, and what the previous value was?
Portability: Can you export campaign, delivery, and conversion data in a form your reporting system can retain and compare?
Governance: Can access be limited by role, and can a second operator review high-impact changes before they affect delivery?

If a required control is missing or unverified, limit the test to exposure your organization can tolerate and define a manual stop path before launch. A report that arrives quickly is helpful, but speed does not replace enforcement, audit history, or the ability to reconcile results.

Keep paid AI advertising separate from GEO and earned AI visibility as well. An ad impression purchased inside an AI experience is not proof that the brand was selected, cited, or recommended organically by a model. Give paid campaigns their own attribution labels, landing-page tracking, and reporting view so an increase in paid traffic cannot be presented as improved generative visibility.

Before your next optimization cycle, open one consequential campaign and record its monthly spending ceiling, the reason for its schedule, its maximum active-day exposure, its consent-signal coverage, the controls that can stop delivery, and the delay in its reporting. Resolve any unknown that could change the meaning of the results. Once those controls are observable and enforceable, bid and creative changes can produce evidence you can actually use.

References

April 22, 2026

Performance Max Campaign Controls: A Practical Playbook
You do not need complete control of Performance Max to keep it accountable. You need to know which reports merely describe what happened, which settings impose hard limits, and which inputs steer the automation without guaranteeing an outcome.

The most reliable approach is to work in that order: verify what the campaign is optimizing for, remove clearly unwanted traffic, apply narrow constraints where the evidence is strong, and then improve the creative, feed, budget, and bidding inputs. That gives you more control without excluding useful demand just because a report looks uncomfortable.

Key takeaways
- Campaign-level negative keywords, placement exclusions, ad schedules, demographic exclusions, and device controls are the clearest direct controls available in Performance Max.
- A report is not automatically a control. Search terms can lead directly to negatives, but placement impressions do not tell you how much a placement spent or whether it produced conversions.
- Use exclusions for traffic that is demonstrably irrelevant, ineligible, unsafe for the brand, or operationally impossible to serve. Do not use them as a reflex whenever performance is uncertain.
- Creative assets, product feeds, conversion goals, bids, and budgets steer where automation looks for results. They usually deserve attention before you start narrowing reach aggressively.
- Record each material change and its reason. If you change negatives, schedules, devices, assets, and bidding together, the next report cannot tell you which decision helped.
Remove obvious waste with search terms and placement controls

The safest exclusions begin with a simple question: could this traffic ever produce the outcome you want? If the answer is clearly no, blocking it protects the budget. If the answer is merely uncertain, investigate before turning an observation into a permanent rule.

Turn search-term visibility into a disciplined negative list

Campaign-level negative keywords can be added from the Performance Max search terms report. This removes much of the friction that once separated finding an irrelevant query from blocking it.

That convenience makes restraint more important. A query with no recorded conversion is not automatically irrelevant. It may have appeared too infrequently to judge, sit earlier in the buying journey, or suffer from a landing-page or offer problem. Negatives should remove unwanted meaning, not conceal a broader performance issue.

Use this review sequence:
1. Group terms by intent rather than reacting to isolated wording. Repeated patterns reveal more than one unusual query.
2. Separate clearly impossible or irrelevant intent from ambiguous intent. Exclude the first group; investigate the second.
3. Check whether a candidate negative could also match valuable searches. Use the narrowest exclusion that removes the unwanted concept without cutting into legitimate demand.
4. Add the negative from the search terms report and record why it was added. A short reason makes later reversals much easier.
5. Review the effect in the next stable comparison period, allowing for the conversion lag that normally applies to your account.
Common candidates include searches for a service you do not provide, a product category you do not sell, or an intent that cannot become a qualified customer. A merely expensive term belongs in a different bucket. Before excluding it, check the conversion goal, landing page, offer, and query context.

Use placement data for suitability before profitability

Performance Max placement visibility now sits in the campaign’s expanded reporting and exclusion workflow, including the ‘Where ads have shown’ area. The placement report is particularly useful for spotting large volumes of impressions in contexts that do not fit the campaign, such as unintended mobile apps or children’s programming.

The limitation matters: impression-level placement data is not a placement-level profit-and-loss statement. A placement with many impressions has not necessarily consumed an equivalent share of spend, generated the same share of clicks, or caused the campaign’s overall inefficiency. Treating impressions as cost can lead you to exclude inventory for the wrong reason.

Placement exclusions are strongest when the decision is about relevance or brand suitability. If a context is plainly inappropriate, an account-level negative placement may be justified. Because that scope can affect more than the campaign you are reviewing, check which other campaigns rely on the same inventory before applying it.

If the concern is performance rather than suitability, look for corroborating evidence first. Review the campaign’s search intent, channel distribution, assets, conversion goals, and landing pages. The placement report may identify where to investigate, but it does not always identify what to remove.

Apply time, demographic, and device limits without choking reach

Schedules, demographic exclusions, and device settings are genuine constraints. They can improve efficiency when they reflect how the business actually operates. They can also starve the campaign when they are used to compensate for weak data, a broken experience, or impatience with normal variation.

Build an ad schedule around opportunity and operating capacity

The ‘When and where ads showed’ reporting area provides hour-by-hour information even when the campaign began without a restricted schedule. You can apply a schedule under ‘Campaigns > Audiences, keywords, and content > Ad schedule’.

Scheduling is most useful when budget is limited and there is a repeatable mismatch between ad delivery and the business’s ability to convert demand. A lead-driven company may struggle to handle inquiries during certain hours. A campaign with a constrained daily budget may spend during weak periods and lose access to stronger periods later. In either case, the schedule should reflect a demonstrated operating constraint, not a single quiet hour in a report.

Before removing an hour or day, ask three questions:
- Does the pattern repeat across comparable periods, or is it driven by one unusual day?
- Was there enough activity to make the absence of conversions meaningful?
- Could conversion lag, offline follow-up, or the sales process make the hour look weaker than it really is?
If those checks support the same conclusion, restrict the weakest period first rather than rebuilding the entire week at once. A narrow change preserves more eligible inventory and gives you a cleaner result to evaluate.

Reserve demographic exclusions for durable mismatches

Campaign-level demographic exclusions are available under ‘Other settings’. They are appropriate when a group cannot reasonably use or qualify for the offering, or when a consistent body of campaign evidence supports the restriction.

A weak short-term result is not the same as a durable mismatch. Demographic segments may receive different volumes and enter at different points in the customer journey. If you exclude a segment after a small amount of activity, the campaign loses the chance to learn whether better creative, a different landing page, or more complete conversion data would change the result.

Use demographic controls as eligibility rules first and optimization rules second. When the decision is performance-based, document the evidence and plan a later review. An exclusion should remain reversible when the underlying audience or offer could change.

Diagnose the device experience before excluding the device

Device controls in ‘Other settings’ let you review which devices contribute to campaign goals and decide which devices to include or exclude. This is valuable, but device performance often exposes a site or journey problem rather than an audience problem.

Before excluding a device, complete the conversion path on that device. Check whether the page loads cleanly, forms are usable, calls work, product information remains legible, and the final action can be completed without friction. If the experience is broken, repair it. Excluding the device may reduce visible waste, but it also hides the defect and abandons otherwise valid demand.

A device restriction is easier to justify when the offering genuinely cannot be delivered there or when the performance gap persists after the experience and measurement have been checked. Apply the smallest defensible restriction, then monitor whether volume shifts into more valuable inventory or simply disappears.

Steer channel delivery through assets, feeds, goals, and bids

Not every useful lever is an exclusion. In Performance Max, the material you supply tells the system what it can advertise, which formats it can assemble, which customers it should value, and what outcome bidding should pursue. These inputs influence delivery without offering an exact channel allocation switch.

Creative quality matters because Performance Max can serve across visual inventory including Display, YouTube, and Discover. Generic assets may technically make a campaign eligible for more formats while doing little to communicate the offer. Organize each asset group around one coherent product set, service, audience need, or landing-page promise. When several unrelated propositions share the same creative bundle, weak results become much harder to diagnose.

AI-generated images and videos can help fill missing formats and create variants, including assets derived from Shopping feed products. They still require human quality control. Before approving an AI asset, check:
- Whether the product, packaging, proportions, and important visual details remain accurate.
- Whether text is readable in the expected crop and does not introduce unsupported claims.
- Whether video motion, transitions, and product rendering remain coherent from beginning to end.
- Whether the message matches the destination page closely enough that the click does not create a new expectation.
- Whether the asset is acceptable for every type of inventory in which the campaign may use it.
The channel reporting view can show where delivery is occurring, but its actionable controls remain limited. If the campaign is appearing in a channel you would prefer to reduce, first inspect the inputs that made that inventory attractive: the asset mix, product feed, conversion goal, bid strategy, and budget. Changing these does not guarantee a particular distribution, but it addresses the logic the campaign is using.

When the business specifically needs Shopping-focused delivery, a feed-only campaign structure can concentrate the campaign on the product feed rather than supplying a complete cross-channel creative set. That choice trades broader creative reach for tighter inventory focus. Make it deliberately; do not remove assets simply because one channel report looks unfamiliar.

Conversion goals deserve the earliest inspection. If the campaign is rewarded for shallow actions that do not represent business value, exclusions will not solve the central problem. It will continue finding more of the outcome it was told to value. Make sure the selected goal represents a meaningful result and that different conversion actions are not being treated as equivalent when the business values them differently.

Bids and budgets are also steering mechanisms. They affect which opportunities the campaign can pursue and how aggressively it can compete, but they cannot repair an irrelevant goal or misleading creative. Fix the instruction before increasing the resources given to follow it.

Run the controls in a repeatable order

A control is useful only if you can connect it to a decision. Use one review sequence consistently so that urgent-looking reports do not pull you into random edits.
1. Record the current conversion goals, bid strategy, budget, schedule, exclusions, asset setup, and feed configuration. This is the baseline against which later changes will be judged.
2. Confirm that the campaign is optimizing for an outcome the business actually values. Resolve incomplete or misleading measurement before interpreting audience and inventory reports.
3. Review search terms. Add negatives only for clearly irrelevant or impossible intent, and record the reason for each important exclusion.
4. Review ‘Where ads have shown’. Use placement exclusions for documented suitability or relevance problems, remembering that an account-level action can affect other campaigns.
5. Inspect hour-by-hour delivery. Tighten the ad schedule only when the pattern is repeatable and consistent with the way the business handles demand.
6. Review demographic and device performance. Test whether the apparent gap comes from eligibility, the on-site experience, or measurement before removing reach.
7. Audit asset groups and feed inputs. Replace generic, inaccurate, mismatched, or low-utility material, and verify every AI-generated asset before it can represent the brand.
8. Use channel reporting to decide what to investigate. If strict Shopping focus is required, evaluate a feed-only structure; otherwise steer distribution through the available inputs.
9. Change one control layer at a time where practical. Annotate what changed, when it changed, and what outcome you expected.
10. Evaluate the next comparable period only after accounting for normal conversion lag. Keep changes that solve the stated problem; reverse those that merely reduce reach.
Start your next review with the search terms and placement reports, but do not stop at what looks wasteful. Trace each symptom back to the closest controllable cause. One well-supported negative, schedule adjustment, device fix, or asset correction is more useful than a dozen exclusions you cannot later explain.

References
- CrushPress.AI — Google PMax Enhances Control with New Exclusions & Reporting
- CrushPress.AI — Unlock Your Control Over Performance Max Campaigns
March 26, 2026
Google Ads Budget Pacing for Scheduled Campaigns in 2026
If you use ad scheduling to keep a Google Ads campaign from consuming a full month’s budget, check that assumption now. Starting March 1, 2026, Google changed budget pacing for notified campaigns that run on selected days or hours. Your ads still respect the schedule, but Google may concentrate substantially more spend inside the periods when they are eligible to run.

Your immediate task isn’t to remove ad schedules. It is to separate two decisions that may have been hiding inside one setting: when the campaign should run and how much it may spend during the month. Once you calculate those controls separately, you can keep the schedule you need without leaving the monthly cost to an outdated assumption.

Your schedule controls eligibility, not a fixed monthly spend

Under the earlier pacing behavior, campaigns with limited schedules tended to spend less because Google paced their budgets around active days. A campaign scheduled only for weekends could therefore appear to have a predictable monthly cost even when its average daily budget was much higher than the monthly target would normally support.

That relationship has changed for affected campaigns. Google now attempts to use more of the available monthly budget during the existing scheduled windows. The important boundaries remain the same: spend can reach twice the average daily budget on an active day, while the monthly billing limit remains 30.4 times the average daily budget.

Those rules give each setting a different job:
- Average daily budget: establishes the budget Google uses for pacing and the 30.4x monthly billing limit. It is not a promise that spend will equal that amount on every active day.
- Ad schedule: determines the days and hours when the campaign is eligible to serve. The pacing change does not authorize delivery outside those periods.
- Budget pacing: determines how aggressively Google can use the available budget inside the eligible periods.
This is why a schedule that remains visually unchanged can produce a higher bill. The campaign has not gained more serving hours, and its displayed average daily budget has not increased. More of the permitted spend is simply being compressed into fewer active windows.

If an ad schedule exists mainly as a cost-control device, it is no longer a dependable substitute for setting the right budget. Keep schedules that reflect real operating constraints, such as the hours when your team can handle inquiries, but make the budget itself reflect the amount you are prepared to spend.

Calculate a schedule-aware spend ceiling

You can estimate the campaign’s maximum exposure from the two unchanged limits. This calculation is most useful for a full month in which the average daily budget stays constant.

Use these variables:
- D = the campaign’s average daily budget.
- N = the number of calendar dates on which the campaign is scheduled to be active during the month.
- M = the maximum monthly amount you are willing to expose to spend.
Then calculate both constraints:
- Monthly billing ceiling: 30.4 x D.
- Schedule-side ceiling: 2 x N x D.
- Schedule-aware planning ceiling: the lower of 30.4 x D and 2 x N x D.
In compact form, the planning ceiling is min(30.4 x D, 2 x N x D). This is a ceiling based on the stated budget rules, not a spend forecast. Available traffic, auction conditions, bids, targeting and the length of each scheduled window can all leave actual spend below it.

Count active dates, not schedule rows. If a campaign has a morning window and an afternoon window on the same date, that is still one active date for this calculation because the 2x rule applies to the day’s budget, not separately to each time block.

The formula also exposes an important threshold. At least 16 active dates are necessary for the campaign to have enough daily capacity to reach the full 30.4x monthly limit: 15 active dates provide at most 30 x D, while 16 provide up to 32 x D. Sixteen active dates do not guarantee full delivery, but fewer than 16 cannot supply 30.4 daily-budget units under the 2x-per-day limit.

If M is a hard monthly ceiling, a ceiling-first starting budget is:

D = M / min(30.4, 2 x N)

Use that equation for risk control, not as a guarantee that the campaign will spend M. If M is merely a desired spend target, you still need to judge whether the schedule contains enough demand and whether the resulting traffic meets your performance objective.

The $100 weekend-only example

Consider a simplified month with eight weekend dates and a $100 average daily budget. Under the earlier behavior, the campaign might have spent about $100 on each active date, producing an approximately $800 month. Under the new pacing approach, the unchanged daily rule allows as much as $200 on each of those eight dates.
- Monthly billing ceiling: 30.4 x $100 = $3,040.
- Schedule-side ceiling: 2 x 8 x $100 = $1,600.
- Schedule-aware ceiling: $1,600, because it is lower than $3,040.
The result is the practical risk behind the change: a weekend campaign that had been spending around $800 could move toward $1,600 without a change to its $100 budget or schedule. It still cannot reach the full $3,040 monthly limit in this eight-date example because the 2x daily constraint leaves insufficient active dates.

If $800 is a hard ceiling rather than a loose target, divide it by the binding coefficient of 16. That produces a $50 average daily budget. With eight active dates, the campaign could then spend up to $100 per date and $800 across those dates. Its 30.4x monthly limit would be $1,520, but the tighter eight-date schedule-side ceiling would remain $800.

Do not reuse the eight-date assumption for every month. Count the actual eligible dates in the month you are planning, recalculate N, and then reset D. A fixed $50 budget tied to an eight-date example will not preserve the same ceiling when the schedule contains a different number of active dates.

Audit affected campaigns without making blanket budget cuts

Google described this as a gradual rollout affecting advertisers that received a direct notification. That makes notification status part of the audit. A scheduled campaign should not be treated as affected solely because March 1, 2026 has passed, and an unrelated campaign should not have its budget cut merely because another campaign was notified.
1. Confirm the notification’s scope. Locate the direct Google notice and record which account or campaigns it covers. If the scope is unclear, preserve the notice with your audit notes rather than assuming every scheduled campaign changed at once.
2. Inventory scheduled campaigns. For each one, record its average daily budget, eligible days and hours, number of active dates in the month, intended monthly ceiling and current spend. Include paused campaigns that may be reactivated under an old budget.
3. Identify the schedule’s real purpose. If it protects response times, staffing coverage or another operational limit, keep it. If it was primarily expected to reduce monthly spend, move that responsibility to the budget calculation.
4. Calculate both ceilings. Compare 30.4 x D with 2 x N x D. Use the lower number as the schedule-aware exposure ceiling.
5. Compare exposure with approval. If the calculated ceiling exceeds the amount the business is prepared to spend, lower the average daily budget before the next eligible window. Expanding or removing the schedule is a separate operating decision and should not be used merely to make a budget formula work.
6. Record the intervention. Save the previous budget, new budget, effective date, active-date count and calculation. Without that record, a later spend change can be misread as a bidding, demand or performance issue.
Monitor concentration as well as the monthly total

A monthly total can hide the behavior that creates the risk. Review each eligible date after it runs and track:
- Actual spend for the active date compared with D and the 2 x D daily ceiling.
- Cumulative monthly spend compared with your internal maximum and the 30.4 x D billing limit.
- Whether delivery remained inside the configured schedule.
- Conversions or other business outcomes, so higher spend is not mistaken for better performance.
If the budget and schedule stayed unchanged but spend moved closer to 2 x D on eligible dates after a direct notification, the pattern is consistent with more aggressive pacing. It does not prove that pacing is the only cause. Changes in demand, bids, targeting or auction conditions can also move spend. If ads appear outside the configured hours, however, that is not explained by this pacing change because scheduled hours are supposed to remain in force.

Do not raise D automatically when a campaign falls short of a desired target. The ceiling formula shows what Google may be allowed to spend; it does not establish that suitable traffic exists or that additional spend will be productive. Resolve a hard overspend risk first, then evaluate delivery and performance as a separate decision.

Key takeaways
- For affected campaigns, ad scheduling still controls when ads can run, but it may no longer reduce monthly spend in the way your historical results implied.
- The 2x active-day rule and the 30.4x monthly billing limit remain unchanged; the change is how Google paces budget within scheduled windows.
- Use min(30.4 x D, 2 x N x D) to calculate a schedule-aware planning ceiling for a full month with a constant budget.
- A $100 campaign with eight active dates has a $1,600 schedule-side ceiling, even if its earlier spend was around $800.
- Only directly notified advertisers were identified as affected during the gradual rollout, so confirm scope before changing unrelated campaigns.
- Treat a calculated ceiling as cost exposure, not a delivery promise. Monitor outcomes separately from spend.
Open each notified scheduled campaign before its next active window. Count the month’s eligible dates, calculate both ceilings, and tie the average daily budget to the amount you are actually authorized to expose. That one calculation lets the schedule keep doing its operational job without quietly making your spending decision for you.

References
- CrushPress.AI – Google’s New Ad Scheduling Update: Maximize Campaign Budgets Effectively
February 25, 2026

Google Ads API v23: A Practical Upgrade Plan for 2026

Your Google Ads integration may be stable, but that does not make the v23 decision automatic. You need to know whether upgrading will close a real operational gap: opaque Performance Max reporting, difficult invoice reconciliation, date-only scheduling, fragmented store data or an audience workflow that still depends on manual interpretation.

Google Ads API v23 brings those changes into the same release, while also beginning a faster API release cycle for 2026. The practical response is not to adopt every feature at once. It is to connect each capability to a decision, migrate the safest read paths first and put tighter controls around anything that can change targeting, schedules or spend.

Choose the upgrade scope from the decisions you need to improve

Start with the workflow that consumes the data, not the endpoint that exposes it. A feature has upgrade value only when someone can name the decision it will improve, the current workaround it will replace and the failure you need to prevent.

v23 capability	Decision or workflow it can improve	First acceptance test
Performance Max breakdown by ad network type	Explaining where campaign results are occurring	Segmented values reconcile with the unsplit control query for every additive metric you publish
Campaign-level invoice details, regulatory fees and adjustments	Billing reconciliation and client cost allocation	Every amount remains traceable to its original charge type instead of being forced into media spend
Campaign start and end date-times	Precise launch, promotion and shutdown scheduling	A controlled write-read test preserves the intended date, time and governing timezone convention
PerStoreView location details	Store-level reporting and local performance analysis	The account and location scope agrees with the corresponding Stores report
LIFE_EVENT_USER_INTEREST	Life-event dimensions in audience insight workflows	The new dimension survives extraction, storage and review without being collapsed into a generic interest label
Surface-specific Demand Gen conversion-rate forecasts	Planning separately for placements such as Gmail and Shorts	Surface remains part of the forecast key through the planning layer
Free-text descriptions converted into structured audience attributes	Drafting audience definitions from a strategist’s brief	The generated attributes are visible, validated and approved before downstream use
Additional Shopping competitive and conversion-date metrics	Competitive analysis and conversion reporting	Every metric carries its date basis and aggregation rule into the dashboard

This map also exposes ownership. Performance Max and Shopping changes usually begin with analytics engineering. Invoice changes require a finance or billing consumer. Date-time scheduling belongs to the team that owns campaign mutations. Audience generation needs both a technical owner and the person accountable for targeting decisions.

A low-risk migration sequence starts on the read side. Capture representative outputs from your existing integration, upgrade the required client libraries and code in an isolated path, add one v23 capability, and compare its result with your control data. Move write operations only after your storage, validation and monitoring layers understand the new values.

List every query, scheduled job, report, billing export and campaign writer affected by the upgrade.
Record the account scope, selectors, reporting window and downstream consumer for each path.
Capture baseline responses and the totals currently shown to users.
Upgrade the client dependency and generated types without changing business logic in the same step.
Add one v23 capability behind a separately testable query or writer.
Define a reconciliation rule, an owner and a rollback condition before releasing it.
Keep the old output available until the new consumer passes both data and operational checks.

Rebuild reporting around the new data grain

An analyst examines an opaque campaign object as it passes through a prism and separates into distinct reporting components.

The reporting additions are useful because they expose distinctions that were previously difficult to retrieve. They can also break a pipeline that assumes one row per campaign, one meaning for a date or one reporting grain across every metric.

Performance Max network breakdowns need a new row key

Google Ads API v23 adds an ad-network-type breakdown for Performance Max reporting. Once that segment enters a result, a campaign can occupy more than one row. Any transformation keyed only by campaign can overwrite rows, duplicate joined values or accidentally recombine the split before an analyst sees it.

Add the network dimension to the unique key at ingestion. Then run a paired query: one result at the original campaign grain and one with the network split. Reconcile metrics that your reporting contract treats as additive. For ratios and calculated metrics, recompute from their underlying components where your data model supports that; do not sum percentages merely because they arrived in separate rows.

Label the output narrowly. A network breakdown provides a more useful view of distribution, but it should not be presented as complete Performance Max transparency. That wording matters because analysts will otherwise infer visibility into decisions the field does not actually expose.

Shopping conversion-date metrics need an explicit time basis

Expanded Shopping reporting includes new competitive and conversion metrics organized by conversion date. A conversion-date series answers a different question from a series organized around the ad interaction. If your warehouse stores both under an undifferentiated date column, a dashboard can produce a plausible trend with the wrong meaning.

Give every affected metric a semantic contract. At minimum, record its metric name, date basis, source grain and permitted aggregation behavior. Carry the date basis into the BI model and display label. If you show conversion-date and interaction-date views together, identify them explicitly instead of blending them into one unlabeled total.

Competitive metrics deserve the same discipline. Do not assume a newly available value can be summed across products, campaigns or dates. Preserve the returned grain first, then implement only the aggregation behavior your reporting definition supports.

Use PerStoreView as a controlled local-data migration

PerStoreView exposes store location details aligned with the Stores report. That alignment gives you a practical acceptance test. Select a known account and location scope, retrieve both views, and compare the location set and identifying details before replacing an existing store feed.

Preserve the identifiers exposed by the API instead of matching stores only by display name. Names can be formatted inconsistently in downstream systems, while a durable identifier gives you a defensible join. Keep store attributes separate from campaign measures as well; duplicating a location attribute across performance rows does not make it an additive metric.

Your exception report should show missing locations, duplicate mappings and conflicting attributes. Do not hide those cases inside an inner join. A clean-looking dashboard that silently drops an unmatched store is harder to repair than a visible migration exception.

Keep billing detail and scheduling precision from creating new errors

Two v23 features move beyond analytical convenience. More detailed invoices affect financial reconciliation, while precise campaign date-times affect when ads can run. Both deserve stronger controls than a new reporting column.

Model invoice charges by type before calculating totals

InvoiceService can now return campaign-specific costs, regulatory fees and adjustments. Those amounts may contribute to the same billing reconciliation, but they do not mean the same thing. Putting all of them into an internal field named spend destroys the distinction that makes the new detail valuable.

Retain the raw response, then normalize each amount into a typed financial record. Your internal model should distinguish campaign cost, regulatory fee and adjustment, preserve the campaign association when supplied, and record the sign convention used by your system. Never change the raw value to make a reconciliation pass.

Reconcile typed amounts to the billing total your finance workflow expects.
Flag an adjustment whose sign cannot be interpreted confidently instead of silently treating it as a cost.
Keep fees visible as fees in client and internal reports.
Surface campaign references that cannot be mapped to your internal campaign table.
Make repeated ingestion idempotent so rerunning a billing job does not duplicate a charge.

Release the richer invoice feed beside the existing reconciliation for at least one normal billing run in your own workflow. The purpose is not merely to reach the same final number. Finance should be able to explain which campaign costs, fees and adjustments produced it.

Treat date-time scheduling as a write-path migration

Campaigns can use precise start and end date-times rather than date-only boundaries. That is an operational change, not just a more detailed field. A database column, serializer or form built around dates can strip the time and still produce a syntactically valid value with the wrong schedule.

Trace the value from the user’s input through storage, request construction and the returned campaign state. Confirm the timezone or normalization convention required by the API and your client library rather than guessing. Keep the user’s intended local time available for audit even if your integration also stores a normalized representation.

Test a same-day start and end.
Test a boundary near midnight.
Test a date affected by a daylight-saving transition when the campaign’s market uses one.
Test that an end earlier than the start is stopped by your own validation.
Read the campaign back after writing and compare the returned schedule with the submitted intent.
Verify that legacy date-only jobs do not overwrite the newer time values on their next run.

Do not move this writer into production while the timezone or end-boundary behavior remains ambiguous. An incorrect boundary can allow spend outside the intended promotion window or stop a campaign while it should still be active. Use a controlled, low-risk campaign for the final lifecycle check and require an explicit rollback path.

Put human review between AI assistance and campaign changes

A campaign manager reviews AI-generated adjustment modules before allowing one to pass through an approval gate into an advertising system.

Google Ads API v23 expands AI-assisted audience and planning workflows in three different ways: a new life-event dimension, free-text audience generation and surface-specific Demand Gen forecasting. They should not be merged into one opaque automation step. Each produces a different kind of planning input and needs a different validation rule.

Preserve LIFE_EVENT_USER_INTEREST as its own dimension

The new LIFE_EVENT_USER_INTEREST audience dimension gives Insights workflows a structured way to work with life-event interests. Store the dimension type separately from its returned value. Mapping it immediately into a generic interest bucket removes the distinction before a strategist can use it.

Add explicit handling for unknown or newly returned values. A resilient integration should retain a value it does not recognize, route it for review and continue processing the rest of the response. Hard-coded mappings that discard an unfamiliar value make API evolution look like missing audience demand.

Handle generated audience attributes as a proposal

Generative audience tooling can translate a free-text audience description into structured attributes. That can reduce manual setup, but the structured result is still the consequential output. The input may sound reasonable while the generated attribute set is broader, narrower or simply different from what the strategist intended.

Make generation a reviewable draft. Store the original description, the complete structured result, the version of your internal mapping logic, the reviewer decision and the eventual change applied downstream. Show the strategist a diff between the current audience definition and the proposed one. Empty attributes, unsupported values and unexpectedly broad additions should block automatic application.

This audit trail is also how you make the feature debuggable. If campaign behavior later raises a question, you can distinguish the user’s brief, the generated interpretation and the approved configuration instead of treating them as one decision.

Keep Demand Gen forecasts separated by surface

Demand Gen conversion-rate forecasts can now vary across surfaces such as Gmail and Shorts. Include surface in the storage key, API-to-warehouse mapping and planning view. Otherwise, one surface can overwrite another or an early average can erase the difference the feature was designed to expose.

Use each forecast as a planning input, not a guaranteed outcome. Retrieve the forecast without automatically changing budget or targeting, show the surface-level values to the planner, record the decision they support and compare eventual performance using the same surface distinction where your measurement data permits it.

Key takeaways for your v23 upgrade sequence

Adopt v23 by workflow value, not by feature count. Tie every capability to a named decision and consumer.
Move read-only reporting first. Baseline, dual-run and reconcile before replacing an existing output.
Add the new dimension to your data key. Network, store, surface and date-basis distinctions must survive ingestion.
Keep financial meanings separate. Campaign costs, regulatory fees and adjustments should remain typed and traceable.
Test scheduling end to end. Database precision, serialization, timezone handling and legacy writers can all alter the intended date-time.
Keep AI-generated audience attributes behind validation and human approval.
Build reusable migration checks now. A faster 2026 release cadence makes a repeatable test harness more valuable than a one-off v23 patch.

Your next step is to create one migration ticket for each capability you intend to use. Give it an owner, affected consumer, baseline sample, reconciliation rule, failure alert and rollback condition. Start with the highest-value read-only gap. Move invoice and scheduling changes only when the teams responsible for billing and campaign operations have approved the acceptance tests.

That approach lets you capture v23’s useful reporting and planning gains without turning the upgrade into an uncontrolled rewrite. It also leaves you with a migration pattern you can reuse as the Google Ads API release pace increases.

References

CrushPress.AI – Boost Your Google Ads in 2026 with v23 API Insights

January 29, 2026

Google Ads Campaign Mistakes That Undermine Your Results

You can make a Google Ads account look more polished while making its decisions less reliable. Raise Ad Strength, accept recommendations, expand match types, and adjust bids, and you may still have no trustworthy answer to the question that matters: are the campaigns producing valuable business outcomes?

If performance has become difficult to explain, resist the urge to rewrite everything at once. Audit the account in this order: measurement, search-term routing, campaign settings, and automation. That sequence protects the signal you need to decide what should change next.

Fix measurement before tuning bids or targeting

A specialist traces cables from a laptop, shopping bag, phone, and blank form to a measurement hub with one duplicate and one disconnected signal.

Google Ads optimization inherits whatever definition of success you give it. If that definition changes from one campaign to another, the account can look internally consistent while comparing unlike outcomes.

The common fault lines are attribution methods, count settings, conversion windows, and campaign-level overrides. Two campaigns may generate the same kind of customer action yet value the associated clicks differently because their conversion configurations differ. More traffic cannot solve that problem. It only produces more data under incompatible definitions.

Create a conversion contract for the account

A conversion contract is a simple record of what the account considers success. It does not need to be a complex measurement document. It needs to answer the same questions for every campaign you intend to compare:

What real business event does this conversion action represent?
Is the action used by bidding, or is it retained only for observation?
Which attribution method assigns credit?
Which count setting is used?
How long is the conversion window?
Does the campaign inherit the account configuration, or does it override it?
If there is an override, what business reason requires it?

Consistency does not mean forcing every conversion action into one configuration. A purchase, a qualified lead, and an informational interaction are different events. The goal is to measure the same event the same way wherever it appears and to document intentional exceptions.

Campaign-level overrides deserve special attention because they can make one campaign accurate in isolation while weakening account-level comparisons. If an override no longer has a clear owner and rationale, treat it as configuration drift rather than strategy.

Changing conversion settings can alter the signals used by automated bidding and therefore affect spend. Record the date and reason for each correction. Avoid changing conversion definitions, bid strategy, and keyword scope at the same time. When several inputs move together, you cannot tell which change produced the next result.

Rebuild query control around real search terms

An analyst sorts abstract search-query tokens into separate campaign channels and diverts irrelevant tokens through a side gate.

Keywords are planning inputs. Search terms show the language people actually used. When the two diverge, the account can send valuable intent to inconsistent ads, bids, or landing pages.

Do not abandon exact match because broad match is prominent

The interface may encourage broad match, but that does not make exact match obsolete. Exact match can still be the highest-converting match type in an account. That is not a guarantee for every advertiser; it is a reason to preserve exact coverage where the account has already identified valuable intent.

Start with the search-term report, not a speculative keyword expansion. Find terms that repeatedly produce the business outcome you care about. Then ask three questions:

Does the term have an exact-match keyword in the account?
Is that keyword located with the ad message and landing page best suited to the intent?
Does the term appear under several keywords or campaigns, producing different user experiences?

If a proven term has no clear home, add exact-match coverage in the most relevant campaign or ad group. The aim is not to promise perfect routing. It is to give valuable intent a deliberate destination with a suitable message, bid context, and landing page.

Find search terms that wander between keywords

Looser matching can allow one search term to trigger multiple keywords. That duplication matters when those keywords sit behind different offers or messages. A person can express the same intent twice and receive two materially different paths through the account.

Group repeated search terms by intent and identify the keyword, campaign, ad message, and landing page associated with each appearance. Choose a preferred destination for every important intent. Add exact coverage there and correct the surrounding message. Use negative keywords to prevent overlap only after checking the possible effects, because an overly broad negative can block demand beyond the conflict you intended to resolve.

Evaluate broad match and bidding as one decision

Broad match does not have one fixed performance profile. Its results depend partly on the bid strategy and on the conversion data supplied to that strategy. This is why broadening keyword eligibility before fixing tracking is especially risky: the system receives more freedom while pursuing an unreliable goal.

Before expanding a keyword, write down the campaign objective, the bid strategy, the conversion actions informing it, and the search intents you are willing to buy. If any of those answers is unclear, the match-type change is premature. When you do test broader eligibility, keep the bidding and measurement definitions stable so the result remains interpretable.

Treat negative keywords as living controls

A negative keyword list captures an old decision. Products change, positioning changes, search behavior changes, and campaigns are reorganized. A list that was sensible when created can later block relevant searches and remove opportunities.

Audit shared lists and campaign-specific negatives together. Classify each negative into one of three groups: always irrelevant, relevant only to an older campaign structure, or uncertain. Keep the first group, investigate the second, and compare the third against current keyword themes and converting search terms.

Do not delete a large negative list merely because it is old. Removing negatives can immediately admit new traffic and increase cost. Correct confirmed conflicts in controlled batches, then inspect the resulting search terms before opening more traffic.

Standardize campaign settings before comparing performance

Campaigns sometimes need different settings. A regional campaign may require a unique location boundary, and a campaign tied to staffed sales hours may require a different schedule. The mistake is not variation. The mistake is unexplained variation that gets mistaken for performance.

Build a settings matrix with campaigns as columns and the following controls as rows. The matrix makes invisible configuration differences easy to inspect:

Control	What to compare	Decision to record
Conversion configuration	Actions used for optimization, attribution method, count setting, window, and overrides	Which campaigns should share the same definition of success?
Locations	Included and excluded regions	Which geographic differences are required by the offer?
Ad schedules	Days and periods when ads can serve	Is each restriction operationally necessary?
Bid strategies	The objective pursued by each campaign	Does the strategy match the campaign goal and available conversion signal?
Keyword controls	Match-type mix and exact coverage for proven terms	Which search intents should have a deliberate home?
Negative lists	Shared and campaign-specific exclusions	Which exclusions are permanent, contextual, or obsolete?
Automation	Recommendation auto-apply status and allowed changes	Which changes require human approval?

Review each difference as either intentional or accidental. An intentional difference gets a short rationale and an owner. An accidental difference gets corrected in a controlled change. If nobody can explain why one campaign excludes a region, runs a different schedule, or uses a different bid strategy, do not assume the setting is harmless.

This matrix also prevents a common analytical error: crediting ads or keywords for a result created by campaign configuration. A campaign with wider geography, longer serving hours, or different conversion rules is not a clean comparison with its neighbors.

Put interface scores and automation behind approval gates

Google Ads can recommend an action, score an ad, and execute certain changes automatically. None of those mechanisms knows whether the change respects your commercial constraints unless those constraints are represented in the account’s data and settings.

Ad Strength is a diagnostic, not the business objective

A lower Ad Strength rating can reflect a deliberate decision to limit how ad content is combined. It can also coexist with stronger conversion performance. That relationship is not universal, but it is enough to reject the idea that maximizing the interface score should override measured outcomes.

Before adding assets to improve the rating, identify what the existing constraints protect. They may preserve a required promise, keep a qualifier attached to an offer, or maintain alignment with the landing page. If a proposed variation weakens that connection, a higher score does not make it a better ad.

Evaluate ads with the conversion action that represents the campaign’s goal. Use Ad Strength to notice possible limitations, then decide whether those limitations are intentional. Do not use it as a substitute for conversion quality or commercial value.

Disable unattended changes that alter strategy

Recommendation auto-apply can introduce changes such as adding keywords or modifying bid strategies. Those are not cosmetic edits. They can change which searches become eligible, how aggressively the account bids, and how budget is distributed.

Review the account’s auto-apply status and turn off unattended changes that alter keyword scope, bidding, or other strategic controls. Recommendations can remain inputs to a review process. They should not bypass it.

Apply the same standard to AI-generated recommendations. Automation works from the objectives and data it receives. If the conversion definition rewards low-value actions, the system can become efficient at producing the wrong result. If a stale negative list hides valuable demand, automation cannot optimize traffic it is never allowed to see.

Require a short change brief before approving an automated recommendation:

What account setting or campaign element will change?
Which business outcome is the change expected to improve?
Does it alter the definition of a conversion, query eligibility, bidding, or message control?
Which result will show that the change helped?
What condition would justify reversing it?

If the recommendation cannot survive those questions, it is not ready to run. AI is useful for generating possibilities and finding patterns. Judgment is still required to decide which objective deserves optimization and which constraints should remain.

Key takeaways: audit the account in a safe order

Align attribution methods, count settings, conversion windows, and campaign overrides before trusting comparisons.
Document the business event behind every conversion action used for bidding.
Add exact-match coverage for proven search terms that lack a deliberate destination.
Investigate valuable search terms that move between keywords, campaigns, messages, or landing pages.
Evaluate broad match together with its bid strategy and conversion signal.
Review negative keyword lists for conflicts before expanding traffic or removing exclusions.
Explain differences in locations, schedules, bid strategies, and other campaign settings.
Judge ads by relevant outcomes, not Ad Strength alone.
Turn off unattended strategic changes and require an approval brief for automated recommendations.
Change one decision layer at a time so the next result remains interpretable.

Open the account and build the conversion and settings matrix before touching bids, budgets, or creative. Make the smallest correction that restores consistency, record it, and let the resulting signal determine the next move. That is slower than accepting every prompt in the interface, but it gives you something far more useful: an account whose results you can explain.

References

CrushPress.AI – Must-Avoid Google Ads Mistakes in 2026 for Success

January 9, 2026

How TV Advertising Changes Search Behavior and Demand

A TV campaign can do its job and still look inefficient in your dashboard. The spot creates curiosity, the viewer searches, and search receives the click and often the conversion. If the channels are reported separately, search gets credit for demand it did not create while TV loses credit for the action it caused.

When a campaign is approaching, your practical problem is not whether TV affects search. It is whether the questions created by the commercial will meet the right result, whether your pages and paid campaigns can capture the resulting demand, and whether measurement can distinguish demand creation from demand capture. Treat those as one operating system.

TV changes the query, not just the number of searches

TV advertising does more than send extra people toward keywords that already exist. It can change what people search for, how specific their searches become, and which brand they include in the query.

Someone who might otherwise search for a category such as car insurance may search for a particular insurer after seeing its commercial. Someone who was not shopping at all may search for the actor, song, claim, product, offer, or scene they remember. A later search may become more commercial: price, reviews, availability, eligibility, alternatives, or where to buy.

That produces several distinct kinds of demand:

Navigational demand: The viewer remembers the company or product and wants the official destination.
Campaign-identification demand: The viewer remembers a celebrity, character, song, phrase, or plot but not necessarily the brand.
Informational demand: The commercial creates a question about what the product does, how an offer works, or whether a claim applies to the viewer.
Commercial-investigation demand: Interest turns into searches for pricing, reviews, comparisons, specifications, availability, or alternatives.
Transactional demand: The viewer looks for a store, application, booking page, product page, or other way to act.

The sequence is not always linear. A viewer can search during the commercial on a second device, later that evening after another exposure, or days afterward when a related need appears. Comscore’s 2024 work connected coordinated TV and digital activity with stronger engagement and second-screen actions. In February 2025, YouTube also said television had overtaken mobile as the primary device for its U.S. viewing, based on Nielsen data. Your TV-to-search plan therefore needs to cover broadcast, connected TV, and streaming rather than treating them as separate consumer journeys.

The timing can be fast. Google and Nielsen found in 2015 that TV ads could increase branded search queries by up to 20%, often within hours of an airing. DAIVID, a creative-analytics provider, has offered a higher vendor estimate of up to 60%, with the possibility of more in well-coordinated campaigns. Those figures demonstrate the possible scale, but they are upper bounds from different contexts, not universal planning assumptions. Reach, repetition, creative attention, prior brand awareness, category demand, market conditions, and the clarity of the call to action all affect the result.

Do not place 20% or 60% into a forecast as if TV produces a fixed search multiplier. Build your planning range from your own previous airings, separated by market, creative, product, and schedule. If this is your first flight, treat branded search lift as a measurement question rather than a promised outcome.

A useful working model is: exposure → attention → memory or curiosity → query → result → action. Search teams control the final handoffs. If the memorable clue from the commercial is absent from your pages, ads, video metadata, and entity information, viewers can be interested and still fail to find you.

Build the search surface from the creative itself

A television, phone, and laptop display matching unbranded visual elements connected by glowing lines.

Keyword tools show existing demand. A new commercial can create language that did not have meaningful volume before the campaign. Start with the finished creative, not with last month’s keyword export.

Watch the commercial without the creative brief in front of you. Record what an ordinary viewer could actually remember: the spoken brand name, product name, campaign line, spokesperson, character, visual device, offer, claim, date, location, and requested action. Then watch it again without sound. Connected-TV viewers may be distracted, and visual memory can produce a different query from the approved campaign wording.

Turn those observations into a search-intent inventory:

List exact entities. Include the brand, product, service, campaign, spokesperson, featured organization, and location named or shown in the spot.
Write identification queries. Model the fragments a viewer might remember, such as [brand] commercial actor, ad with [scene], or what company made the ad about [theme].
Write promise and explanation queries. Include the central benefit, claim, offer, qualification, or problem depicted in the commercial.
Write action queries. Cover price, availability, release date, eligibility, locations, applications, bookings, trials, and where to buy when those intents apply.
Add natural variants. Include abbreviations, common misspellings, shortened product names, and spoken versions of stylized brand names.
Map every query family to a destination. Assign an existing page, create a new one, or document why paid coverage is the appropriate route.
Inspect the live results. Search the phrases from the target market and device context. Check whether the correct page appears and whether the title and description make the relationship to the commercial obvious.

The map should connect each memory or intention to an answer, not merely to your home page.

Search signal	Likely query pattern	Best destination	Failure to catch before airing
Brand or product recall	`[brand]`, `[product name]`	Official brand or product page	An outdated page, reseller, or competitor is more prominent
Memory of the creative	`[brand] commercial song`, `ad with [person or scene]`	Campaign page, video page, or concise commercial FAQ	The creative clue appears nowhere in crawlable text or video metadata
Offer or claim	`[offer] terms`, `how does [claim] work`	Offer page with conditions, dates, and next step	The landing page repeats the slogan but does not explain it
Evaluation	`[product] reviews`, `[product] vs [alternative]`	Product details, evidence, comparison, or review resources	The viewer must leave the site to understand basic differences
Availability or location	`where to buy [product]`, `[service] near me`	Store locator, local page, product listing, or booking flow	Inventory, locations, or business information is inconsistent
Eligibility or application	`who qualifies for [offer]`, `apply for [service]`	Eligibility explanation and application page	Important restrictions appear only after the user starts converting

The destination should visibly repeat the language and visual identity of the commercial. A viewer who searches after seeing an ad is looking for recognition as much as information. If the page uses a different product name, campaign line, image, or offer, the visitor has to decide whether they found the right company before they can consider the product.

Put the answer to the commercial’s main unresolved question near the beginning of the page. Include dates, eligibility, price conditions, inventory limits, or geographic restrictions when the campaign depends on them. A memorable slogan is not an explanation. Sending every query to a generic home page wastes the context that made the search valuable.

Prepare the machine-readable layer with the same discipline. Use Organization, Product, Offer, or VideoObject structured data only when the visible content supports it. Keep names, URLs, images, availability, dates, and offer details consistent across the page and markup. If you publish the commercial, include a useful title, description, transcript or summary, thumbnail, and campaign context. Structured data can clarify entities and relationships for search and answer systems, but it cannot repair an absent answer or an unsupported marketing claim.

Write a few direct, self-contained answers for people who search conversationally or ask an AI assistant to identify the ad. State what the campaign promotes, which product or service appears, how the offer works, and where someone can act. Do not bury those facts in brand language that only makes sense after a visitor has watched the full commercial.

Run paid and organic search as one response system

Organic pages cannot be switched on at the moment an ad airs. They need to be published, crawlable, internally linked, indexed, and tested beforehand. Paid search can respond more quickly, but it still needs the right keywords, creative, budgets, locations, schedules, landing pages, and measurement conventions before volume arrives.

Before the flight

Create one airing log with the creative ID, campaign name, product, market, channel or platform, planned timestamp, and time zone. Search and analytics teams should use the same identifiers.
Verify that every mapped landing page is indexable, uses the intended canonical URL, works on mobile, and completes its conversion path without errors.
Check page titles, descriptions, headings, visible copy, video metadata, structured data, and internal links against the language viewers will remember.
Build paid coverage for brand, product, campaign, offer, and high-value action queries. Review match types and negative keywords so a new campaign phrase is not accidentally blocked.
Confirm that budgets and targeting reflect the markets and times receiving media. A national paid-search increase is a poor response to a limited regional TV schedule.
Record a baseline for branded, product, campaign-related, and non-brand category queries before the campaign changes demand.
Test site capacity, inventory feeds, forms, phone routing, store data, and analytics events. A search spike has little value if the next step fails.

Share creative changes immediately. A late edit to an offer, product name, spokesperson, or campaign line can invalidate keyword coverage and landing-page copy even when the media schedule stays the same.

During the flight

Monitor around actual airings where the volume supports that level of analysis. Look at branded and campaign-cue queries, paid impression share, spend, click-through rate, organic impressions, landing-page traffic, page errors, conversion events, on-site searches, and customer questions. Use the time zone recorded in the airing log; otherwise an apparent lag or lead may be a reporting error.

Paid copy should repeat the recognizable product, benefit, and offer from the commercial, then add the practical detail the viewer needs. If the spot is emotional and the search ad sounds like unrelated direct-response copy, the handoff feels broken. Consistency does not require copying the script. It requires confirming that the searcher has reached the right answer.

Do not automatically raise bids on every branded query. Blanket increases can make you pay for visits your organic result would have received anyway. Paid brand coverage is more defensible when competitors are present, the results are ambiguous, the campaign needs a precise destination, or the organic page is not yet strong enough. Where volume allows, compare markets or airing windows with and without paid brand coverage to estimate whether the ads add clicks and conversions rather than merely moving them from organic search.

Watch the mix, not just total volume. If searches grow for the actor or song but not the brand or product, the entertainment may be more memorable than the advertiser. If viewers search for basic eligibility, pricing, or meaning, the spot has created interest but left a consequential question unresolved. Update paid copy and owned answers while the campaign is still running.

After an airing or flight

Do not remove campaign pages the moment paid media stops. Search can lag an exposure, and commercials can continue circulating through streaming, video sharing, press coverage, and memory. Use your own query and visit decay to decide how long active paid support should remain.

When an offer expires, keep a useful destination if people are still searching. State clearly that the promotion ended, preserve relevant campaign context, and direct visitors to a current product, offer, or support page. Replacing a known campaign URL with a generic error page converts residual demand into confusion.

Annotate changes to the creative, media weight, search campaigns, pages, offers, pricing, and tracking. Without that change log, a later analyst may attribute a search shift to the wrong channel or assume that two materially different commercials were the same treatment.

Measure incremental demand without giving search all the credit

Two miniature neighborhoods show different levels of glowing activity from televisions to phones and destinations.

Last-click reporting answers which channel completed the recorded journey. It does not answer which channel created or accelerated the need to search. A branded search conversion after a commercial may be captured by PPC or SEO while being caused partly by TV. The reverse mistake is also possible: not every branded search during a TV flight was caused by the campaign.

Separate three layers in your reporting:

Demand response: Incremental brand, product, campaign-cue, and relevant category searches associated with the airing.
Search capture: The portion of available demand reached through organic and paid results, followed by clicks and useful landing-page behavior.
Business outcome: Incremental leads, purchases, store actions, applications, bookings, or other outcomes after accounting for the demand that would have existed without TV.

This distinction prevents a common misreading. A successful TV campaign can lower the conversion rate of search traffic because the commercial brings in a broader, earlier-stage audience. More curious visitors may arrive before they are ready to buy. Total incremental conversions can rise even while the percentage of visits that convert falls. Judge the campaign using volume and incrementality alongside conversion rate, not conversion rate in isolation.

Use a repeatable measurement sequence:

Define the expected baseline. Compare with similar non-airing periods, matched weekdays and dayparts, previous weeks, or comparable markets. Adjust the baseline when seasonality or an established trend makes a simple average misleading.
Align the airing log. Use actual timestamps and markets when available, not merely the campaign’s overall start and end dates.
Group queries by intent. Separate brand, product, campaign identifier, offer, high-intent non-brand, navigational, and unrelated searches. A total branded-search line can conceal what changed.
Inspect multiple response windows. Look for an immediate second-screen response and a later memory response. Do not force one universal attribution window onto every product, creative, or buying cycle.
Control overlapping activity. Promotions, product launches, email, public relations, influencer activity, news, seasonality, competitor campaigns, site changes, and search-platform changes can all move demand at the same time.
Use a comparison design when feasible. Matched geographic markets, staggered schedules, non-airing periods, or carefully chosen holdouts produce a stronger estimate than a simple before-and-after chart.
Reconcile the channels. Report how much demand appeared, how much search captured, and how much converted. Do not add TV-attributed and search-attributed conversions if both labels include the same people.

A simple diagnostic calculation is: search lift (%) = (observed query volume – expected query volume) / expected query volume x 100. The difficult part is not the arithmetic. It is constructing a credible expected value. A baseline contaminated by a promotion or product launch will produce a precise-looking but unreliable lift figure.

No single platform supplies the complete denominator. Google Trends shows relative interest rather than absolute query counts. Search Console shows impressions and clicks involving your properties, not every search in the market. Paid-search reporting describes the auctions and traffic your campaigns entered. Web analytics describes visits and recorded outcomes after a user reaches the site. Read those alongside airing data, direct traffic, on-site search, video search behavior, sales, calls, and customer-service questions.

Search terms also function as creative feedback, but only when you interpret their meaning:

A rise in exact brand and product searches indicates that viewers connected the message to the advertiser.
A rise dominated by the celebrity, song, or scene can indicate strong entertainment recall but weak brand linkage.
Queries such as what company is that ad or repeated misspellings can expose a naming or pronunciation problem.
Growth in pricing, availability, location, or application queries signals movement toward action and tells you which destination must be strongest.
Growth in eligibility, explanation, or what does it mean queries reveals an information gap. The gap may be intentional curiosity, but the search result still has to resolve it.
Complaint, skepticism, or confusion queries should not be counted as favorable response merely because volume increased. Investigate the underlying issue and adjust the answer or campaign where warranted.

Branded search volume is therefore a useful creative-response indicator, not a standalone verdict. It tells you that the commercial entered behavior. Query composition, result quality, incremental visits, and business outcomes tell you whether that behavior helped.

Key takeaways

TV can create navigational, informational, commercial, and transactional searches; it can also shift an existing generic search toward a named brand.
Search response may begin within minutes or hours, so pages, paid campaigns, tracking, and operational systems must be ready before the commercial airs.
Build the keyword and content map from what viewers can remember in the creative, including the product, offer, person, phrase, scene, and unresolved question.
Give every important query family a recognizable destination instead of sending all TV-driven demand to a generic home page.
Coordinate paid-search schedules and budgets with actual markets and airings, while testing whether branded ads add incremental value over organic results.
Measure demand creation separately from search capture, then use matched baselines or holdouts to estimate the incremental effect.
Read the query mix as feedback: product searches, campaign-identification searches, action searches, and confusion searches tell you different things about the creative.

Before the next creative lock, bring the media schedule, search team, analytics owner, web team, and campaign decision-maker into the same handoff. Leave with four concrete artifacts: a query inventory, a destination map, a scheduled paid-search plan, and a measurement sheet with baselines and comparison markets or periods.

If one of those is missing, the campaign is not fully ready. The goal is not to make TV look like search or search look like TV. It is to ensure that the demand your commercial creates reaches a clear answer, and that each channel receives credit for the part of the journey it actually performed.

References

CrushPress.AI – Unveiling How Breakthrough TV Ads Amplify Search Impact

December 12, 2025

Tag: Ad Scheduling

Put human judgment at the decision boundary

An ad schedule is an eligibility rule, not a cleanup tool

Use a five-part evidence gate before restricting automation

Build an operating loop that removes labor, not accountability

Key takeaways

References

Key takeaways

Audit the whole control chain before touching bids

Scheduled campaigns need a spend-concentration audit

Consent diagnostics tell you whether the optimizer can learn

Prove an AI ads manager can control delivery before scaling it

References

Key takeaways

Remove obvious waste with search terms and placement controls

Turn search-term visibility into a disciplined negative list

Use placement data for suitability before profitability

Apply time, demographic, and device limits without choking reach

Build an ad schedule around opportunity and operating capacity

Reserve demographic exclusions for durable mismatches

Diagnose the device experience before excluding the device

Steer channel delivery through assets, feeds, goals, and bids

Run the controls in a repeatable order

References

Your schedule controls eligibility, not a fixed monthly spend

Calculate a schedule-aware spend ceiling

The $100 weekend-only example

Audit affected campaigns without making blanket budget cuts

Monitor concentration as well as the monthly total

Key takeaways

References

Choose the upgrade scope from the decisions you need to improve

Rebuild reporting around the new data grain

Performance Max network breakdowns need a new row key

Shopping conversion-date metrics need an explicit time basis

Use PerStoreView as a controlled local-data migration

Keep billing detail and scheduling precision from creating new errors

Model invoice charges by type before calculating totals

Treat date-time scheduling as a write-path migration

Put human review between AI assistance and campaign changes

Preserve LIFE_EVENT_USER_INTEREST as its own dimension

Handle generated audience attributes as a proposal

Keep Demand Gen forecasts separated by surface

Key takeaways for your v23 upgrade sequence

References

Fix measurement before tuning bids or targeting

Create a conversion contract for the account

Rebuild query control around real search terms

Do not abandon exact match because broad match is prominent

Find search terms that wander between keywords

Evaluate broad match and bidding as one decision

Treat negative keywords as living controls

Standardize campaign settings before comparing performance

Put interface scores and automation behind approval gates

Ad Strength is a diagnostic, not the business objective

Disable unattended changes that alter strategy

Key takeaways: audit the account in a safe order

References

TV changes the query, not just the number of searches

Build the search surface from the creative itself

Run paid and organic search as one response system

Before the flight

During the flight

After an airing or flight

Measure incremental demand without giving search all the credit

Key takeaways

References