Category: Google Ads

Google Ads API v20 Sunset: Upgrade Before June 10, 2026

If any reporting, bidding, or campaign-management workflow still calls Google Ads API v20, June 10, 2026 is a hard failure boundary. Any request sent to v20 after the cutoff will fail, so a healthy dashboard or successful scheduled job on June 9 does not prove that you are ready for June 10.

Your job is to find every remaining v20 request, move each affected workflow to a newer version, and produce evidence that the replacement works in production. That requires more than changing a version string. It requires an inventory, representative testing, a staged cutover, and monitoring that can distinguish fresh data from stale output.

Know exactly what will fail at the cutoff

The sunset applies at the API request boundary. It does not, by itself, mean that a Google Ads account or campaign disappears. It means a workflow loses access whenever the request it needs still targets v20.

The business consequence depends on what that request does:

Reporting and data pipelines can stop collecting new data, leaving dashboards, attribution processes, or client reports with gaps.
Campaign automation can stop reading or applying intended changes, including workflows connected to bidding and campaign management.
Internal tools can fail when a user opens a screen, requests a report, or submits a change that depends on v20.
Third-party platforms can break even when your own code is current, because the version choice may live inside the vendor’s backend.

A failed reporting job is not always visually obvious. A dashboard may continue showing its last successful dataset unless it also displays data freshness. A failed write does not necessarily leave an account in a safe or paused state; it may simply leave the previous campaign settings in place. Review each workflow’s retry, alerting, and failure behavior so that an API error cannot masquerade as a successful run.

Translate every technical dependency into an operational consequence. Instead of recording only “reporting service uses v20,” document which report stops, who consumes it, how quickly stale data becomes harmful, and who owns recovery. That mapping tells you which migrations must move first.

Key takeaways

Google Ads API v20 requests will fail after June 10, 2026; the deadline is not a warning-only deprecation milestone.
Inventory observed API traffic and stored configuration. Either view alone can miss a dependency.
Test complete workflows on a newer API version, not merely authentication or one sample request.
Run read-only comparisons in parallel where useful, but do not duplicate campaign-changing requests across versions.
Cut over early enough to observe a full operating cycle and restore v20 temporarily if the new implementation fails before the sunset.

Build an inventory that includes hidden and dormant calls

An isometric enterprise system shows visible services and faint hidden connections to legacy jobs, dormant components, and recovery infrastructure.

Start with actual traffic, then reconcile it against code, configuration, schedules, and vendor dependencies. An application list assembled from memory will miss old scripts, shared services, and jobs owned by teams that no longer think of themselves as Google Ads API users.

Recent API activity in Google Cloud Console can help identify the methods and versions used by your projects. Review every relevant project rather than only the one associated with your main campaign application.

List the environments and projects. Include production, staging, reporting infrastructure, serverless jobs, shared integration projects, and systems managed by another team.
Inspect recent activity. Record which projects still produce v20 traffic and which methods they call.
Cover the complete job cadence. Your observation period must include infrequent workloads such as weekly, monthly, or manually triggered jobs. Zero traffic during an idle period proves nothing.
Search stored configuration. Look for literal v20 references, version selectors, client-library dependencies, deployment variables, request builders, infrastructure definitions, and copied scripts.
Attach an owner to every dependency. An unidentified service is not ready merely because it appears inactive. Someone must decide whether it should be migrated, retired, or verified as unused.

Traffic inspection and configuration inspection answer different questions. Traffic tells you what ran. Configuration tells you what may run later. Keep both in the migration register.

Dependency surface	What to locate	Useful readiness evidence
Custom applications	Version settings, client dependencies, request construction, and deployment configuration	Representative requests succeed on the target version and production activity no longer shows v20
Scheduled data pipelines	Job definitions, orchestration schedules, exports, and downstream consumers	A complete scheduled run finishes with fresh, complete output
Campaign automation	Read and write paths, retry behavior, approval controls, and alerts	A controlled test produces the intended state once and failures reach an owner
Third-party platforms	Vendor-owned connectors, reporting modules, and automation features	The vendor confirms the production version and you verify your own affected workflows
Dormant or manual tools	Occasional scripts, archived repositories, runbooks, and analyst utilities	The tool is migrated, formally retired, or blocked from future v20 use

Ask vendors for feature-level confirmation

A generic claim that a platform “supports the Google Ads API” is not enough. One module may be current while a less visible exporter or automation feature still uses v20. Ask the provider:

Which API version does each feature used by your account call in production?
Has every v20 workload been migrated, or only the primary integration?
When will the production cutover occur?
How can you verify that your tenant is using the newer version?
What happens to queued jobs, retries, and cached reports if a request fails?

Keep the response with your migration record, then test the feature yourself. Vendor confirmation transfers information, not operational responsibility.

Migrate the workflow, not just the version label

Choose a newer supported API version that works with your client stack and the capabilities your workflows need. Use Google’s release notes and upgrade guides to identify required changes. Do not assume that editing a version constant is sufficient: client dependencies, available fields, request structures, generated types, and response handling may also need attention.

A practical migration sequence looks like this:

Capture a baseline. Record representative inputs, expected outputs, normal completion signals, and current error behavior for each workflow. Use stable comparisons where possible because live campaign data can change during testing.
Update the client and application together. Change the supported client dependency, version configuration, request construction, and any code affected by the official upgrade guidance. Check deployment manifests and runtime variables as well as the repository.
Test authentication and simple reads. Confirm that the application can connect using the credentials and account scope it will use in production. Connectivity is only the first gate, not the completion criterion.
Exercise representative read workflows. Run the same account scope, date range, filters, pagination path, and downstream transformation used by the real job. Compare required fields, completeness, row-level invariants, and freshness rather than relying on a single successful response.
Test writes under controlled conditions. Do not change live spend merely to prove connectivity. Use an approved test environment, test account, or non-spend-altering path where your setup supports one. Verify that the intended resource changes once and that retries cannot duplicate an action.
Validate downstream consumers. A successful API response does not prove that a dashboard, warehouse load, bid process, notification, or internal interface can consume the new output correctly.
Release in stages. Move a bounded set of workloads first, watch their results, and expand only after the expected operating signals remain healthy.

Parallel validation is useful for read-only workloads. You can run equivalent reporting requests on v20 and the target version, then compare the resulting datasets while v20 remains available. Avoid sending campaign-changing requests through both versions: duplicate writes can produce real account changes and financial consequences. For write paths, use a controlled test followed by a staged production rollout.

Preserve a temporary rollback path during the early cutover, but recognize its expiration date. Before June 10, a rollback to v20 may buy time to fix a problem. After the sunset, v20 is no longer a viable recovery plan because its requests will fail. Your post-cutoff contingency must keep the newer version in place, disable the affected workflow safely if necessary, and route the failure to a named owner.

Define readiness with production evidence

Engineers monitor abstract requests moving through a replacement processing lane with checkpoints, a separated legacy lane, and a rollback route.

“The code was upgraded” is a progress update. It is not a definition of done. Close the migration only when you have evidence across configuration, runtime traffic, workflow output, and ownership.

Every known application, script, scheduled job, and integration has an owner and an explicit migrate-or-retire decision.
Each active workflow completes successfully on the selected newer API version using representative accounts and request types.
Production configuration and deployed client dependencies point to the intended version.
No v20 activity appears across the relevant Cloud projects during a period that covers the full operating cadence of the workflows.
Reporting outputs expose freshness and completeness, so stale data cannot look current.
Campaign-changing automation has controlled retry behavior and a human receives actionable failure alerts.
Third-party features have been confirmed by the provider and verified through your own account-level test.
The rollback plan works before the cutoff, and the post-cutoff contingency does not depend on v20.
Campaign owners, analysts, engineers, and support staff know when the cutover occurred and where failures will be reported.

Be careful with negative evidence. Seeing no v20 requests is meaningful only if every relevant workload had an opportunity to run. A monthly exporter that has not reached its schedule can remain invisible until after the deadline. Pair runtime inspection with the dependency register, then record the last successful target-version execution for every retained workflow.

Set your internal cutover early enough to run a complete operating cycle while v20 can still serve as a temporary fallback. Name the owner, start the inventory, and schedule the target-version validation now. The date that matters internally should be the day you can prove v20 is gone, not June 10 itself.

References

Search Engine Land — Upgrade Google Ads API: Avoid Service Interruptions by June 10

May 1, 2026

Google Marketing Intelligence: Automate Without Losing Control

You have campaign data in Google Analytics, expanding automation in Google Ads, and more landing pages than anyone can inspect every morning. The problem is no longer a lack of information. It is knowing which information should change a campaign, which decisions the system may make, and where a person must remain accountable.

The right goal is not maximum automation. It is a closed operating loop: trustworthy measurement informs a clear campaign brief, automation acts inside defined boundaries, and the results lead to a specific next decision. Build that loop first and Google marketing intelligence becomes useful rather than merely impressive.

Make the data trustworthy before you automate the decision

Marketing intelligence is evidence that changes an action. A dashboard can contain hundreds of metrics without providing intelligence if nobody can explain what decision each metric supports.

Use this five-part loop for every automated campaign:

State the decision. Be precise: expand demand coverage, revise positioning, restrict landing pages, or hold spend.
Name the outcome. Identify the business result that would justify that decision.
Verify the signal. Confirm that the required activity reaches the intended Analytics property and report.
Define the permitted action. Specify what automation may change and what must remain fixed.
Set a stop condition. Decide what evidence would trigger a review, restriction, or pause.

If you cannot complete all five steps, the campaign is not ready for broader automation. You may still run it, but you should not interpret automated activity as informed optimization.

Use Task Assistant as a configuration audit

Where it is available, Google Analytics Task Assistant can expose configuration gaps through a guided workflow for account connections, data collection, and reporting. Its recommendations can be marked complete or skipped, which makes it useful as an audit queue.

Do not confuse completion with correctness. Connecting an account does not prove that the right outcome is being measured. Creating a report does not prove that anyone knows what to do with it. For every Task Assistant item, record the business question it supports. If an item is skipped, record why and what change would cause you to revisit it.

Before expanding automation, perform this minimum measurement check:

Confirm that the intended Analytics property is receiving activity from the campaign journey.
Complete the target journey yourself and verify that the expected signal appears in the reporting path you plan to use.
Separate the primary business outcome from diagnostic interactions. A page view or form start can help diagnose friction, but it is not automatically equal to a completed purchase or qualified enquiry.
Confirm that the people reviewing the campaign use the same definition of success.
Assign an owner to investigate missing, duplicated, or implausible data.

Create a one-page measurement contract

A measurement contract is a short record of how evidence becomes action. It should fit on one page and contain these fields:

Decision: What are we deciding?
Primary outcome: Which result makes the decision worthwhile?
Diagnostic signals: Which observations help explain the result without replacing it?
Permitted action: What may the campaign system change?
Stop condition: What would make us constrain or pause it?
Owner: Who makes the final call when the evidence is ambiguous?

For an AI Max campaign, the decision might be whether to broaden coverage for exploratory searches. The primary outcome might be a qualified commercial action. Query themes and selected landing pages would be diagnostics. Irrelevant demand, an incompatible destination, or omitted mandatory language would be stop conditions. That is enough structure to prevent a campaign team from optimizing a proxy simply because it is easy to see.

Translate strategy into an AI brief the system can use

Automation cannot infer the parts of your strategy that exist only in a planning deck or a stakeholder’s head. You have to express the campaign’s job, its limits, and its required truths in operational language.

AI Max introduces an AI Brief powered by Gemini for natural-language guidance, including messaging direction and query priorities before launch. Treat that brief as an input specification, not as a creative wish list.

A usable automation brief should answer each of these prompts:

Campaign job: Capture demand for which offer, from which type of need?
Eligible intent: Which problems, categories, or buying situations belong in scope?
Out-of-scope intent: Which superficially related searches should not consume attention or budget?
Approved positioning: Which concepts or attributes should the audience connect with the brand?
Supported claims: What can the landing page actually prove?
Prohibited claims: Which wording would be inaccurate, noncompliant, or inconsistent with brand policy?
Mandatory language: Which qualifier or disclaimer must remain present?
Destination boundary: Which pages are suitable for campaign traffic, and which are not?
Success signal: Which measured outcome should guide the decision?
Review trigger: What result or system behavior requires human inspection?

Vague adjectives are weak instructions. If the desired positioning is “premium,” define what supports that position: service model, material, expertise, access, or another verifiable attribute. If the desired association is “sustainable,” separate the brand objective from the factual claims the campaign is allowed to make. Wanting an association does not authorize unsupported environmental language.

Challenge the brief before launch. Ask whether a conversational query could appear relevant while expressing the wrong intent. Check whether an automatically selected page could contradict the ad’s promise. Test whether mandatory wording survives changes in message or destination. If the answer depends on someone noticing the problem later, you have monitoring, not control.

Natural-language guidance makes campaign intent easier to communicate, but prose alone should not carry legal or regulatory obligations. Use the platform’s available controls, preserve approved wording, and require compliance or legal review where claims create exposure. Automation does not transfer accountability away from the advertiser.

Measure the decision, not whatever the dashboard offers

Campaign teams often ask one metric to answer several different questions. Conversion data can show that an action occurred, but not necessarily why. Brand recall can show recognition, but not whether people attach the intended meaning to the brand. Keep the questions separate.

A practical evidence ladder has five levels:

Measurement: Did the expected data arrive correctly?
Delivery: Did the campaign reach demand that belongs in scope?
Response: Did people take the expected intermediate or final action?
Business outcome: Was the action commercially meaningful or qualified?
Brand effect: Did the audience connect the brand with the intended idea?

Do not move up this ladder by assumption. If data collection is unreliable, apparent delivery and response patterns are unstable. If the business outcome is unknown, a rise in response volume does not prove that the automation found better demand.

Google Ads’ Association metric adds a more specific brand question. Within Brand Lift Studies, advertisers can define a concept, category, or attribute and examine which brands surveyed users connect with it. This is useful when the strategic question is not merely “Do people remember us?” but “Do people understand us in the intended way?”

The constraint matters: a Brand Lift study can use only three selected metrics. Association therefore competes with other measurement questions rather than becoming a free extra. Choose the three before launch by writing the decision each one could change. If a metric would produce an interesting slide but no different action, it should not take a slot.

Question	Evidence to inspect	Decision it can support
Can the optimization signal be trusted?	Verified Analytics data path and a completed target journey	Repair measurement or proceed
Is automation finding appropriate demand?	Query and destination patterns considered alongside qualified outcomes	Expand, hold, or constrain coverage
Is the message shaping the intended position?	Association with the selected concept, category, or attribute	Keep or revise positioning and creative direction
Is the campaign creating recognition without meaning?	Awareness or recall considered separately from Association	Decide whether the next campaign should build familiarity or clarify positioning

Keep performance and brand evidence on separate scorecards, then read them together. Improving Association does not prove profitable acquisition. Improving conversion volume does not prove that the intended brand position is taking hold. When one improves and the other does not, you have learned where the campaign is working and where it is not; you have not discovered a reason to redefine the weaker metric.

Put hard boundaries around queries, copy, pages, and spend

Good automation has broad execution capability and narrow permission. The system can evaluate more opportunities than a person can review manually, but it should operate inside a boundary the campaign owner can state without opening the account.

AI Max is expanding beyond its Search role into Shopping and consolidated travel campaign workflows. That expansion increases the value of a shared governance model because targeting, messaging, product information, and destinations can no longer be managed as isolated concerns.

Define these boundaries before enabling or expanding automation:

Demand boundary: List the needs and query themes to prioritize, plus adjacent intent that remains out of scope.
Message boundary: Record approved attributes, supported claims, prohibited wording, and mandatory text.
Destination boundary: Maintain an explicit set of pages suitable for automated selection.
Data boundary: State which outcomes are trusted enough to influence decisions and which signals remain diagnostic only.
Budget boundary: Decide how much financial exposure is acceptable before a person must review performance. Configure account controls to reflect that decision wherever the campaign type permits.
Compliance boundary: Identify claims and destinations that need specialist approval before they can be used.
Reversibility boundary: Write the condition that will cause the team to restrict, pause, or roll back the automation.

Treat every eligible landing page as campaign creative

Final URL expansion allows AI to select a page it considers more relevant, while text disclaimers can accompany URL automation. The operational consequence is simple: the landing page is no longer just a destination chosen once during setup. Every eligible page can become part of the campaign’s message.

Audit each eligible page for five things:

The page addresses the intent the campaign is permitted to capture.
The offer and positioning agree with the approved campaign brief.
The target action works and can be measured.
Required qualifiers, disclaimers, and conditions are visible and current.
The page does not contain stale or contradictory claims that would make the ad misleading.

If a page fails that check, fix it or remove it from the eligible destination scope before turning on URL expansion. Do not rely on the system to understand an internal distinction that the page itself does not express clearly.

For teams managing SEO, AEO, and GEO alongside paid media, this is also a content-governance issue. Keep the visible page, structured data, product information, and campaign claims consistent. Structured data should describe the same reality a visitor sees; it should not be used to compensate for ambiguous or outdated copy.

Shopping and travel need the same controls in different places

For Shopping, AI Max can use Merchant Center data to adapt ads for long-tail and exploratory searches. Product information therefore belongs inside the campaign review, not in a separate feed-management silo. A carefully written AI Brief cannot repair product information that expresses the offer poorly.

For travel advertisers, consolidation reduces operational fragmentation, but it does not remove the need to govern intent, messaging, destinations, and measurement. Fewer campaign containers should produce a clearer decision process, not fewer checks.

Review automation at change points rather than waiting for a generic reporting ritual. Inspect it before launch, after a material change to the offer or destination set, when query or page-selection patterns shift, and when new brand evidence becomes available. Wait for a meaningful pattern before drawing a conclusion from performance data, but investigate missing mandatory copy or an unsuitable destination immediately.

Google campaign automation FAQ

What is Google marketing intelligence?

Google marketing intelligence is the decision system connecting Analytics data, campaign behavior, business outcomes, and brand measurement. It is not another name for Google Analytics. Analytics supplies evidence; intelligence defines what that evidence means and what action it authorizes.

Should you automate a campaign if tracking is imperfect?

You do not need every possible report to be finished, but the decision-critical measurement path must work. If you cannot verify the primary outcome, do not automate toward a convenient proxy as though it were equivalent. Repair the essential path first, then improve optional reporting around it.

Can Association replace conversion measurement?

No. Association addresses whether an audience connects the brand with a chosen concept, category, or attribute. Conversion measurement addresses action. Use Association to evaluate positioning and conversion evidence to evaluate response and business performance.

How do you know automation has too much control?

It has too much control when the campaign owner cannot state five things: eligible demand, mandatory and prohibited messaging, eligible destinations, the trusted success signal, and the stop condition. If any of those exists only as an assumption, narrow the automation until the boundary is explicit.

Start with one active campaign. Write its job in one sentence, trace its primary outcome into Analytics, list the pages automation may select, and define the evidence that would make you expand or constrain it. Once those decisions are visible, automation can accelerate a strategy you understand instead of concealing one you do not.

References

April 30, 2026

Paid Search Optimization Beyond Keywords: A Signal Playbook

You can have tidy ad groups, extensive negative-keyword lists, and a busy search-term report while still training paid search toward the wrong business outcome. If traffic looks healthy but qualified leads, sales, or revenue do not, adding more keywords will rarely solve the underlying problem.

Keywords still help you read intent. They just no longer control the whole match. Your larger job is to give the platform reliable evidence about who should see the offer, what the offer is for, which stage of the journey matters, and what a valuable outcome looks like.

Optimize the customer need state, not just the query

A query tells you what someone typed. It rarely tells you, by itself, whether that person fits your market, why the problem matters to them, how close they are to buying, or what the eventual conversion could be worth.

A need state combines those dimensions: the right type of customer, experiencing a relevant problem, at a meaningful point in the buying journey. A vague search such as “scaling infrastructure” can carry commercial value when first-party signals indicate that the person is an IT decision-maker investigating SOC 2 compliance. Modern matching systems can infer that intent from a collection of signals rather than waiting for one perfectly phrased keyword.

This does not make search terms useless. Use them to learn the language customers use, identify irrelevant themes, protect the brand, and detect changes in demand. Just do not treat the query list as the only control surface in the account.

Control surface	What you are optimizing	Warning sign
Queries and themes	Problem language, intent patterns, exclusions, and brand boundaries	Relevant-looking terms produce the wrong type of inquiry
Audience data	Customer fit, lifecycle status, known value, and verified interests	Traffic converts, but sales repeatedly rejects the leads
Landing pages and creative	Offer meaning, customer context, qualification, and message fit	Clicks rise while conversion quality or revenue falls
Conversion feedback	The outcomes and values that bidding should pursue	Cheap actions attract budget even though they do not predict revenue
Measurement infrastructure	The integrity of data moving between ads, the site, the CRM, and sales	Platform results diverge from the system where the business records outcomes

Build a signal stack the bidding system can understand

Translucent layers containing audience, context, product, time, location, device, and transaction symbols feed into a central bidding engine.

The strongest paid search accounts do not depend on one perfect signal. They combine first-party audience truth, clear page context, qualifying creative, and journey-aware conversion data. Each layer should confirm the same commercial hypothesis.

Start with first-party truth, not a broad persona

Do not feed every contact to the platform as if every contact represented success. Separate records that mean different things to the business: strong customers, qualified opportunities, early inquiries, rejected leads, existing customers, and people who are ineligible for the offer.

Google increasingly uses Customer Match and other first-party inputs to help identify relevant people in an auction. B2B matching can be difficult, so the practical response is to improve the quality and organization of the data, not to collapse every record into one oversized list. Clustering people by a shared pain point and verified behavior can give the system a clearer signal than a loose job-title persona.

For every audience group, document five things before using it:

Who is in the group and what qualifies them for inclusion.
Which observed action, CRM stage, or customer attribute supports that classification.
Which business outcome the group has historically represented.
Which problem and offer should be shown to it.
Whether the group should be acquired, retained, cross-sold, observed, or excluded.

This prevents an audience label such as “high intent” from becoming an unsupported opinion. If you cannot explain the evidence behind the label, the bidding system cannot repair that ambiguity for you.

Turn the landing page into a targeting brief

Your landing page is not merely the place a click arrives. Automated systems use its content to interpret the offer and decide where it fits. A page that clearly says “mid-market manufacturing” provides a more useful market signal than a page promising generic solutions for every organization. That makes landing-page context part of campaign targeting.

Read the page without the campaign open. A qualified visitor and a matching system should both be able to answer these questions from the visible content:

What category of product or service is this?
Who is it designed for?
Which specific problem or need does it address?
What requirements, limitations, or use cases define a good fit?
What should a suitable visitor do next?

If the answers exist only in your keyword list, the page is withholding context from both the visitor and the machine. Rewrite vague headings, name the customer and use case plainly, and keep the ad, page, and conversion action aligned around the same need state.

Use creative to qualify, not merely attract

Creative assets also help define the audience. An ad that names the user, problem, outcome, and relevant constraint gives the system and the prospect more information than a generic promise designed only to win the click.

Build creative around distinct need states rather than producing cosmetic variations of the same claim. One asset set might address a compliance-driven buyer, while another addresses an operational-efficiency problem. Send each to a page that continues the same argument. Then evaluate the combination using qualified outcomes, not click-through rate alone.

Close the click-to-revenue feedback loop before scaling

A circular pathway links an ad click, landing page, qualified customer, and completed sale back to an optimization engine, while an incomplete click path fades away.

Automated bidding learns from the conversion events you return. If a form submission is marked as success but most submissions are irrelevant, the system is being asked to find more people who resemble poor leads. The campaign may be performing exactly as instructed while failing the business.

Define a conversion hierarchy instead of treating every measurable action as equal:

<!– wp:list {

April 27, 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 Test Google Ads Acquisition Tools Without Skewing ROAS
You have more ways than ever to tell Google Ads what kind of customer to pursue. The difficult part is knowing whether a performance lift came from acquiring better customers, adding extra value to those customers, counting conversions after ad views, or testing an unfinished feature.

If those signals are mixed together, an improving ROAS can hide unchanged revenue. The safer approach is to separate customer economics, attribution, and experimentation before you let automated bidding act on them.

Start with the acquisition decision, not the campaign type

A campaign cannot repair an undefined customer strategy. Before choosing Demand Gen, Performance Max, a customer acquisition goal, or an experimental app feature, write down the business decision the campaign is supposed to make.
1. High-value acquisition: Find new customers who resemble the people your business considers valuable.
2. Retention: Re-engage customers who meet your definition of lapsed, with a separate distinction for high-value lapsed customers when the data supports it.
3. Demand creation: Reach people in discovery-oriented environments where an ad view may influence a later conversion even when no click occurs.
4. Product experimentation: Test an early Google Ads capability without making the business dependent on a feature that may disappear.
These are different jobs. In particular, customer acquisition and retention bidding goals cannot both be applied to the same campaign. That restriction is useful: it forces you to decide whether a campaign should spend more to acquire a certain new customer or spend to win back an existing one.

Do not use “new customer” as shorthand for “good customer.” A first-time buyer with a small, one-off order may be less valuable than an existing customer ready for a premium service. Define value using evidence your business already understands, such as order value, repeat purchasing, margin, or interest in a premium offering. Then decide which of those attributes can be represented reliably in a customer list.

A clean campaign map usually has one lane for high-value new-customer acquisition, another for lapsed-customer retention, and a separate learning lane for experimental features. Demand Gen can support acquisition, but it should still inherit one clearly defined customer objective. The campaign type is the delivery mechanism; the customer decision comes first.

Make customer states usable before Smart Bidding sees them

Define high value and lapsed in your own data

Google’s predictive bidding can look for likely high-value customers, but your Customer Match list supplies the examples. If the list contains a mixture of loyal buyers, discount-only buyers, recent customers, and stale records, the label “high value” carries little usable meaning.

Create a short data definition before creating the audience. It should answer four questions:
- What observable behavior makes a customer high value?
- How does that definition differ from merely having a large first order?
- What period without an eligible purchase or action makes a customer lapsed?
- Which condition takes precedence when someone qualifies for more than one list?
There is no universal lapse window. A sensible definition follows your buying cycle, not an arbitrary calendar interval. Document the rule so that a future list refresh classifies customers the same way.

List scale matters as well. High-value Customer Match audiences need at least 1,000 active members on YouTube or Search networks to serve effectively. Treat that as an operational floor, not proof that the audience is representative. If only a narrow or unusual slice of high-value customers matches, bidding can still learn from a distorted picture.

Include eligible identifiers such as phone numbers and addresses alongside the other customer data you upload; richer records can improve match rates. Direct audience integrations, including Klaviyo, can reduce the manual work of keeping lists current. Automation only solves the transfer, however. It will reproduce a bad definition just as efficiently as a good one.

Treat additional customer value as a bidding instruction

Lifecycle settings are managed in the customer lifecycle optimization area under Goals > Summary, followed by Edit Goal. For a high-value acquisition campaign, you can assign an additional new-customer value so bidding is more aggressive when Google predicts that a conversion will come from the desired customer type.

That additional value is not money collected at checkout. It is a bidding adjustment layered onto the sale or lead value. If a conversion has an actual value and the lifecycle setting adds another amount, the value used in reporting and optimization can include both.

Google may suggest an adjustment based on higher lifetime value, but the suggestion still needs to be reconciled with your own economics. A value that is too small will barely change bidding. A value that is too large can cause the campaign to overpay for customers who merely look like the uploaded audience.

The reporting consequence is especially important under a ROAS strategy. Additional customer value increases the conversion-value numerator even though it does not increase booked revenue at the moment of conversion. The discrepancy is less influential when decisions are based on cost per conversion, but it can materially change the interpretation of ROAS. Use the reporting column that separates true conversion value from additional lifecycle value, and keep all three figures visible in your working report:
- Actual sale or lead value.
- Additional value assigned for the customer state.
- Total value presented to the bidding and reporting system.
If stakeholders see only the total, label it as optimization value rather than revenue. Otherwise, a campaign can appear to produce more economic value when the account has simply changed how much value it assigns to the same type of conversion.

Choose click, view, and lifecycle signals for different jobs

Customer lifecycle and attribution answer different questions. Lifecycle data asks who converted: new, existing, lapsed, or high value. Attribution asks how the advertising interaction receives credit: through a click, a view, or another eligible touchpoint. Combining those dimensions is useful, but only if you continue to report them separately.

Demand Gen extends acquisition beyond click-heavy intent capture. Its Commerce Media Suite integration can use retailers’ first-party catalog and conversion data across YouTube, Discover, and Gmail. This is most relevant when you have commerce data capable of identifying products and outcomes, not merely a broad audience label.

View-through conversion optimization gives the system another signal. It can focus on conversions that occur after someone views an ad, even when that person does not click at the time. That fits discovery environments such as YouTube, where exposure may precede a later visit or purchase.

A view-through conversion is still an attributed conversion, not automatic proof of incremental demand. It tells you that an eligible view occurred before the conversion under the account’s attribution rules. It does not establish that the conversion would have been lost without the ad.

That distinction should change how you evaluate a Demand Gen test. Keep click-associated and view-through outcomes visible as separate paths. Then compare actual customer and revenue outcomes, not just the total number of attributed conversions. If view-through volume grows while qualified new customers and true conversion value remain flat, the campaign has changed how credit is assigned more clearly than it has demonstrated business growth.

Creative must follow the same separation. High-value acquisition messaging should make sense to someone who has not bought from you. Retention messaging should acknowledge the reason a lapsed customer might return. In Performance Max, lapsed customers may encounter several ads across the campaign, so a generic asset mix can undermine an otherwise well-configured retention goal.

Before launch, inspect each eligible asset from the perspective of the customer state attached to the campaign. If the ad would be confusing to that person, targeting precision will not rescue it.

Run App Labs as a reversible test, not a permanent dependency

App Labs is narrower than its name may imply. It is a tested hub inside the app advertising area for limited-time experimental campaign features, not a general replacement for every Google Ads experiment. If the tab appears in your account, it offers app advertisers a chance to try features still in development and provide feedback.

Early access can produce useful learning before a capability becomes widely available. It also carries product risk: an App Labs feature is not guaranteed to become permanent. Build the test so that losing access would remove an option, not break your acquisition program.

Use this protocol for an App Labs test or any other early acquisition feature:
1. Write one hypothesis. State which customer behavior or business outcome the feature is expected to change and why.
2. Freeze the customer definitions. Do not change high-value or lapsed-list rules while evaluating a campaign feature.
3. Select one primary business measure. Prefer true conversion value, qualified new customers, or another observed outcome over adjusted ROAS alone.
4. Record the feature state. Note the settings, audience lists, attribution configuration, creative, and eligibility present when the test begins.
5. Keep a stable comparison. Where the interface supports a control, use it. If it does not, document the limitations of the nearest comparable stable campaign rather than presenting the comparison as causal proof.
6. Cap the learning spend. Put only an amount you are prepared to spend on uncertain learning at risk, and define the condition that will stop the test.
7. Wait for the normal conversion lag. Reading the result before delayed conversions arrive will favor whichever path reports fastest, not necessarily the one that creates more value.
Avoid changing the lifecycle value, attribution treatment, audience definition, and experimental feature at the same time. If the result moves, you will not know whether customers changed, credit changed, or bidding changed. Sequence the changes so each test resolves one decision.

An experimental feature can still teach you something even if Google later removes it. Preserve the customer insight, creative finding, or measurement lesson in your test log. Do not build an essential workflow around the beta’s exact interface or availability.

Key takeaways for your next campaign cycle
- Define high value and lapsed status from your business data before uploading Customer Match lists.
- Keep customer acquisition and retention goals in separate campaigns because both bidding goals cannot run on the same campaign.
- Separate actual conversion value from the additional lifecycle value used to influence bidding, especially when evaluating ROAS.
- Use view-through optimization for discovery journeys, but do not treat attributed views as proof of incremental conversions.
- Match creative to the customer state; acquisition and reactivation messages have different jobs.
- Test App Labs features in a bounded learning lane because limited-time experiments may never become permanent products.
Your first move does not need to be a new campaign. Open Goals > Summary and identify every lifecycle adjustment currently affecting reported value. Then verify the attached customer lists, their definitions, and whether your report separates real conversion value from added bidding value.

Once those numbers reconcile, choose one next experiment: a high-value acquisition goal, a retention goal, view-through optimization, or an App Labs feature. One clear change will teach you more than four simultaneous upgrades and a better-looking ROAS you cannot explain.

References
April 23, 2026

Google Ads AI: Better Call Leads Without Losing Control

Your call campaign can look productive while your sales team hears something very different: spam, robocalls, service questions, and conversations that never had a realistic chance of becoming revenue. If those calls are counted as valuable conversions, automated bidding learns from a distorted signal.

Google Ads is trying to solve that problem with AI-qualified call leads, while Ads Advisor is taking a larger role in policy, certification, and account security. The opportunity is better optimization with less manual work. The risk is allowing a model’s classification or recommended fix to become a business decision without verification. You need a controlled system for both.

Define a qualified lead before Google defines one for you

Call duration is a weak substitute for commercial value. It tells you that two people remained connected, not whether the caller wanted what you sell, met your requirements, or agreed to a meaningful next step. That is why optimizing toward long calls can reward campaigns that generate time-consuming but unproductive conversations.

Google’s AI-qualified call leads use machine learning to assess whether calls represent valuable business opportunities. The system also produces summaries and tags, then incorporates the qualification data into reporting and bidding. This is more useful than duration alone, but the model’s label is still a prediction. It is not the same thing as a sale, accepted opportunity, booked appointment, or collected revenue.

Before you let the new signal influence spend, write a qualification rule that a sales manager and a campaign manager would apply the same way. Keep it short enough to use consistently. A practical definition should answer four questions:

Did the caller express a commercial need that your business actually serves?
Does the caller fit the locations, customer types, or other eligibility conditions you accept?
Did the conversation produce a meaningful next step, such as an estimate, consultation, appointment, or sales follow-up?
Which calls must be excluded, including spam, robocalls, existing-customer support, job inquiries, vendor pitches, and wrong numbers?

Do not define a qualified lead as merely a pleasant or detailed call. A lengthy support conversation may be valuable to the customer service team and still be the wrong signal for acquisition bidding. Your definition must reflect the outcome the ad budget is meant to create.

Validate the signal before automated bidding scales it

A phone-call signal passes through multiple validation checkpoints before entering a branching automated system, while noisy signals are diverted.

A bad manual label affects one report. A bad label fed into automated bidding can affect where the next portion of your budget goes. Validation therefore belongs before optimization, not after performance has already moved.

Confirm that your account and calls are eligible. At rollout, AI-qualified call leads were limited to calls in the United States and Canada. Do not build a measurement plan around a control that is absent from your account or unavailable for the calls you receive.
Document your internal lead taxonomy. Separate qualified opportunities, unqualified prospects, non-sales calls, spam, and genuinely ambiguous calls. Preserve ambiguity instead of forcing every conversation into a positive or negative bucket.
Review a representative set of calls. Include calls the model marked as qualified and unqualified, plus obvious spam and borderline cases. Looking only at the apparent successes will hide the mistakes that matter to bidding.
Compare the AI result with the business outcome. Use the call summary and tag as inspection aids, then compare them with the disposition recorded by sales or in your CRM. Downstream evidence should settle disagreements whenever it is available.
Track false positives and false negatives separately. A false positive is a call the AI qualifies but your business rejects. A false negative is a real opportunity the AI fails to qualify. The first can steer budget toward poor traffic; the second can cause good demand to be undervalued.
Investigate patterns, not isolated disagreements. Repeated errors associated with a campaign, offer, location, call type, or routing path are more actionable than one unusual conversation. Correct the underlying measurement or campaign problem before increasing reliance on the signal.

Google allows advertisers to adjust call-length thresholds, so duration can remain a secondary diagnostic or fallback control. It should not overrule stronger evidence from the conversation and the eventual sales disposition. If AI says a call is valuable but your CRM consistently says otherwise, the disagreement is the finding.

Repeat this validation after material changes to your offer, call routing, sales script, service area, or campaign mix. The label may have looked reliable under the old traffic pattern and become less useful when the kind of calls entering the system changes.

Treat call recording as a governance decision

The qualification system needs access to call content to judge lead quality. That makes recording more than a measurement setting. It becomes part of your privacy, security, and access-control responsibilities.

Call recording is enabled by default for most advertisers, with exceptions including healthcare and financial services. Advertisers can change call-length thresholds or disable recording in account settings. A default setting is not proof that recording is appropriate for every business, caller, or jurisdiction.

Before leaving recording enabled, assign an owner to answer these questions:

What notice or consent does your business need before recording callers in every location you serve?
Which employees, agencies, and vendors can access recordings, summaries, or tags, and which of them genuinely need that access?
Where are call details copied after Google Ads, including your CRM, analytics tools, support systems, or exported reports?
How are access removal and retention handled when an employee, agency, or vendor relationship ends?
What is the escalation path if a recording or AI-generated summary exposes sensitive information?

Have the person responsible for privacy or legal compliance verify the recording rules that apply to your callers. Do this before activation because the downside is not merely an untidy report; inappropriate recording or excessive access can create legal, contractual, and reputational exposure.

Treat summaries and tags with the same care as the underlying audio. A shorter AI-generated record can still reveal why someone called, what they wanted, and how your business responded. Convenience does not make the information harmless.

If you cannot establish a lawful recording process and appropriate access controls, disable recording and accept that you may lose or limit the call-content analysis behind AI qualification. A less sophisticated measurement system is safer than collecting information you cannot govern.

Let Ads Advisor operate, but give it boundaries

A human operator supervises a geometric AI agent working inside a transparent boundary beside locked account, recording, and security assets.

Lead quality is only one part of Google Ads AI safety. Ads Advisor can proactively scan accounts and sites for policy problems, surface or apply fixes, monitor security risks, and confirm resolutions. Its security dashboard looks for issues such as suspicious domains and dormant users, while passkey support reduces dependence on passwords. Google also positioned the system to accelerate some certification workflows.

These capabilities can shorten the distance between detection and correction. They should not erase the approval boundary around changes that affect your ads, site, claims, access, or spend. Use a simple control record for every consequential AI-proposed or AI-applied action:

Trigger: What policy, security, or certification issue caused the action?
Scope: Which campaign, ad, domain, user, landing page, or account setting is affected?
Change: What exactly will be different after the fix?
Owner: Who is responsible for approving and verifying it?
Evidence: What account or site state confirms that the issue is resolved without breaking tracking, accuracy, or the customer journey?
Recovery: Can the change be reversed, and who will act if performance or compliance worsens?

Prioritize security alerts by potential account impact. A suspicious domain may indicate traffic is being sent somewhere you do not control. A dormant user may still retain access after their role has ended. Confirm ownership before taking action, remove access that is no longer required, and use passkeys where your account supports them.

Fast certification is an administrative benefit, not evidence that every claim in an ad or landing page is accurate. Keep the supporting eligibility information current and verify the public-facing campaign after approval. The same principle applies to policy fixes: a resolved warning does not automatically mean the resulting experience is commercially or legally sound.

Area	What the AI contributes	What you must confirm
Call qualification	Call assessment, summary, and tags	The call meets your written business definition and agrees with downstream disposition
Automated bidding	A higher-quality conversion signal	Qualified-lead cost and eventual business value improve, not merely the reported conversion count
Policy management	Proactive detection and proposed or automated resolution	The exact change is accurate, compliant, and safe for the landing experience and tracking
Account security	Continuous monitoring for suspicious domains and dormant users	Domain ownership, user need, and the appropriate containment or access-removal action
Certification	A faster path through eligible certification workflows	Your evidence remains valid and your ads and pages make supportable claims

At rollout, the newer Ads Advisor safety capabilities were directed first to English-speaking accounts, with other languages intended to follow. Availability may therefore differ by account. Verify the controls you can actually see before assigning responsibilities or retiring an existing review process.

Review the system when an event changes its risk: immediately after enabling a feature, after an AI-applied fix, after a change to call routing or campaign strategy, when lead-quality patterns shift, or whenever the security dashboard flags a domain or user. Event-driven review is more reliable than waiting for a generic report to expose the damage later.

Key takeaways

If you do not have a written definition of a qualified lead, do not let an AI label become a bidding objective yet.
Validate both false positives and false negatives against sales or CRM dispositions; call duration alone is not enough.
Confirm geographic and account availability before redesigning your measurement around AI-qualified calls or Ads Advisor safety controls.
Make recording, access, and retention explicit governance decisions. Disable recording if your business cannot handle it appropriately.
Require an owner, change record, verification step, and recovery path for consequential policy or security actions.
Judge the system by downstream lead value and reduced account risk, not by how many tasks it automates.

Start with one call campaign. Write the qualification rule, review where the AI and your sales outcome disagree, and resolve the recording requirements before increasing the signal’s influence on bidding. At the same time, assign a named owner for Ads Advisor alerts and fixes. That small operating boundary gives the automation useful evidence without handing it unchecked control.

References

April 21, 2026

Google Ads Automation: A Practical Optimization Framework

You want Google Ads automation to remove repetitive work, not remove your control over spend. The problem is that an automated campaign can look efficient inside the platform while attracting weak leads, claiming conversions that would have happened anyway, or scaling a creative idea that has never proved incremental value.

The answer is not to choose between manual management and full autonomy. Build a control system in which machines execute within explicit boundaries, experiments establish causality, and a person remains accountable for the objective, economics and exceptions.

Key takeaways

Automate repeatable execution, but keep conversion definitions, economic thresholds, exclusions and stop conditions under human control.
Fix the conversion signal before optimizing against it. Faster optimization only magnifies a bad definition.
Treat attributed conversions and incremental conversions as different measures. Attribution assigns credit; incrementality tests whether advertising caused an additional result.
For a Demand Gen asset uplift experiment, isolate one creative variable, use a 50/50 cookie-based split, protect the budget for at least four weeks and aim for at least 50 conversions across the test groups.
Scale only when a change passes two gates: it produces acceptable business economics and it operates without violating your controls.

Choose exactly what automation is allowed to control

A modular control console shows separate guarded mechanisms for budget, audiences, bidding, creative selection, and conversion quality.

Automation is not one switch. Bidding, budgets, keyword or query expansion, audiences, creative, campaign construction and landing-page testing are separate control layers. Give each layer its own permission, boundary and owner.

Some commercial platforms are marketed as handling campaign builds, bids, ad copy, keyword expansion, landing-page experiments and reporting. That feature scope is a vendor claim, not independent evidence that full autonomy will improve profit or generate incremental demand in your account. Evaluate the decision rights behind the feature list.

Control layer	What automation may do	What you must define	When to pause it
Conversion measurement	Receive events and values used for optimization	Which event represents a real business outcome and how its value is calculated	Tracking breaks, duplicates appear or the mix of conversion events changes unexpectedly
Bidding and budget	Adjust bids and allocate spend within approved campaigns	Maximum acceptable acquisition cost, minimum acceptable return and hard spending limits	Spend or unit economics moves outside the approved boundary
Queries and audiences	Explore demand patterns and expand reach	Markets, exclusions, customer fit and intent boundaries	Traffic drifts toward irrelevant intent, excluded regions or low-value prospects
Creative	Assemble, rotate or test approved assets	Claims, tone, brand rules and the hypothesis being tested	A policy or brand risk appears, or simultaneous changes make the test uninterpretable
Landing pages	Route traffic or test approved variations	Permitted page elements, data handling and the required user journey	Forms, tracking, consent mechanisms or essential page functions fail

Write these boundaries before connecting a tool that can make changes. At minimum, your operating brief should contain:

<!– wp:list {

April 21, 2026

How to Test Google Ads Visual Creative in Local Search

If you advertise physical locations, Google’s local video experiment puts a practical decision in front of you: prepare visual assets now, or wait until the format is more established and rush production later. You don’t need to gamble your local budget or commission a polished brand film to get ready.

The useful move is to build a small, reusable creative system around proof of place. Show what a nearby customer needs to see, connect each asset to the correct location, and test it against business outcomes. That approach remains valuable even while access to the emerging placement is uncertain.

Local video should prove the place, not merely promote the brand

A camera operator films the entrance, counter, staff, and customers inside an unbranded neighborhood cafe.

Google has been testing video ads inside the local pack through an immersive, map-style experience. This puts paid visual creative in a context where the user is already comparing nearby businesses. The format is still preliminary, and its performance against conventional local ads hasn’t been established.

That context changes the creative brief. A general brand montage may look polished but still leave the local decision unanswered. Your video should help the viewer confirm that this is the right place, understand what is available there, or feel confident about the next step.

Give each asset a clear local job:

Confirm the place. Show a recognizable exterior, entrance, sign, storefront, or other accurate location detail.
Reduce arrival friction. Show the approach, parking arrangement, reception area, pickup point, or check-in process when that information matters.
Demonstrate the local offering. Show the product, service, equipment, room, menu item, or experience that is actually available at the advertised location.
Set an honest expectation. Let the viewer see the environment they will encounter rather than substituting generic stock imagery.
Support the next action. Align the ending with the action you want the customer to take, such as calling, booking, ordering, requesting directions, or visiting.

Don’t force every job into the same edit. A short asset focused on finding the entrance can be more useful than a compressed tour of the brand, building, staff, services, offers, and history. If the customer uncertainty is specific, the creative answer should be specific too.

Write the local promise before you choose footage

Use a brief that can fit on a small card. Complete these fields before opening a production tool:

Search situation: What is the nearby customer trying to find or decide?
Question to answer: What uncertainty could stop that person from choosing this location?
Visual proof: What real image or sequence resolves that uncertainty?
Destination: Where should the ad send the person, and does that page continue the same promise?
Business outcome: Which available action or conversion will tell you the creative helped?

A useful brief might be as simple as showing a first-time visitor where to enter and then sending them to that location’s booking page. It doesn’t need a cinematic concept. It needs continuity from search, to image, to arrival or conversion.

Keep that promise location-specific. If footage shows the flagship branch’s amenities while the ad is attached to a smaller branch, the creative may win attention by creating an expectation the business can’t meet. Treat location accuracy as part of ad accuracy, not as a final production check.

Make the location connection part of creative QA

Business photo thumbnails are connected by colored cords to matching pins on a generic map, while one mismatched image is set aside for review.

The reported implementation appears connected to Google Ads Location Manager and may involve a pre-opted control in the Shared Library. Because the placement is experimental, you shouldn’t assume that uploading a video makes an account eligible, that every account exposes the same controls, or that an asset will appear in the local pack.

Before changing a setting or adding assets, create a record of the current configuration. That gives you a clean way to distinguish a creative change from an account or location change.

Document the existing setup. Record the location groups, business identities, campaigns, Location Manager configuration, and relevant Shared Library controls already in use.
Map every asset to a physical location. Use a naming convention that includes the location, the creative job, and the version. A filename such as a generic video final is almost impossible to audit later.
Verify visible facts. Check signage, entrances, products, services, prices, offers, opening information, and amenities represented in the creative. Remove anything that isn’t true for the linked location.
Inspect the destination. The landing page should name or clearly represent the same location and make the intended local action easy to complete.
Check the scope before enabling anything. If a control is already selected or its reach is unclear, determine which campaigns and locations it can affect before changing it across the account.
Preserve a change log. Note when assets and settings were added, removed, or replaced so later performance shifts can be interpreted responsibly.

An unfamiliar pre-enabled setting isn’t a reason to switch the entire account on or off. Use the smallest reversible scope the interface allows, and confirm which locations are included. The downside of a mismatched local ad isn’t merely a weaker click-through rate. It can send a customer toward the wrong branch, offer, entrance, or service.

Also separate inventory from eligibility. Having an approved video in the account means you have an asset available; it doesn’t prove that the experimental local format served it. If delivery doesn’t occur, investigate placement access, campaign configuration, location linkage, and asset status before declaring the creative ineffective.

Build a production system that survives Asset Studio’s limits

Google Ads Asset Studio, available through Google Ads > Tools > Asset Studio, can manage visual assets and turn supplied images into video variations. AI-assisted features such as Veo and Nano Banana can make simple animation and versioning more accessible when you don’t have a full production workflow.

Speed is not the same as direction, though. Asset Studio has shown limited scene-level control, errors involving face-like content, and constrained audio choices without custom-track uploads. Those constraints matter most when your concept depends on exact motion, a human performance, precise pacing, or a distinctive soundtrack.

Use the tool as a production lane, not as the owner of your creative strategy. Decide what must be shown before generating anything, and choose the production route according to how much control the idea requires.

Creative requirement	Recommended starting route	What to verify
Simple motion from accurate location or product images	Asset Studio template or AI-assisted generation	Signs, architecture, product details, sequence, and location identity
Exact scene order, movement, or pacing	A manually edited master	Every required shot survives the final placement treatment
Human-led demonstration or testimonial	Approved original footage, with Asset Studio used only where the input is accepted	Identity, consent, facial integrity, gestures, and spoken claims
Custom music or a tightly timed audio concept	External production or editing	Audio rights and whether the visual story remains understandable without relying on the score
Fast variations of a stable concept	Asset Studio trimming, templates, or image-to-video tools	Each version still represents the same location and offer accurately

Keep the master assets modular

Start with a library of accurate source material rather than a single finished video. Capture or collect the exterior, entrance, arrival path, interior, product or service detail, staff activity where appropriate, and a clean ending image. Label every file by location and keep its usage approval with it.

Then storyboard the sequence outside the generator. This can be plain language: establish the place, show the relevant proof, and support the next action. The storyboard becomes your acceptance test. If a generated version changes the order, invents a feature, deforms a sign, alters a product, or obscures the local proof, reject it rather than trying to justify the output after production.

Keep original images and edited masters outside Asset Studio as well. A modular library lets you rebuild the ad when placement requirements change, a location is renovated, an offer expires, or the generator can’t reproduce an acceptable version. It also prevents the generated file from becoming the only surviving copy of your creative.

If the available audio choices don’t fit, simplify the concept instead of attaching unsuitable music. The visual sequence should communicate the local point on its own. If sound is central to the idea, move that concept into a workflow that gives you the necessary audio control.

Test business outcomes, not the novelty of video

Performance for the emerging local format remains unclear, while easier production can create more assets than a team can evaluate responsibly. The right question isn’t whether Asset Studio produced a video quickly. It is whether the creative improved conversions, sales, or another meaningful campaign outcome without compromising accuracy.

Set up the test so you can make a decision when the data arrives:

State a local hypothesis. Describe the customer uncertainty and why the proposed visual proof may resolve it. Avoid a circular hypothesis such as video will perform better because it is video.
Choose the primary outcome in advance. Use a local action or business conversion your existing setup can measure, such as an eligible call, booking, order, qualified lead, store action, or sale. Don’t select the winner afterward based on whichever metric happened to rise.
Preserve a comparison. Keep a suitable existing asset or campaign state as a control where account settings allow it. If Google selects assets automatically and the format can’t be isolated, annotate the introduction date and describe the result as directional rather than causal.
Change one creative idea at a time. Test proof of entrance against proof of service, for example, rather than changing the footage, destination, offer, audience, and bidding setup together.
Read results by location when locations differ. A pooled average can hide a useful asset at one branch and a misleading one at another.
Review quality alongside performance. Check the served or approved asset for visual errors, outdated facts, mismatched locations, and promises the destination doesn’t support.

Use the pattern in the data to decide what to inspect next:

No meaningful delivery: investigate eligibility, settings, campaign scope, location linkage, and asset status before revising the creative concept.
Delivery without useful interaction: inspect the opening image, local relevance, clarity, and whether the asset answers a real customer question.
Interaction without a local action: inspect the gap between the visual promise, landing page, offer, and conversion path.
A higher click-through rate without better business outcomes: treat the video as attention-getting, not proven. Don’t scale it on clicks alone.
Better business outcomes with accurate creative: expand carefully to comparable locations, then verify that the result holds rather than assuming every branch will respond the same way.

Production efficiency is still useful. Templates, trimming, and image-to-video generation can lower the effort required to reach a testable asset. But the time saved in production should be reinvested in location verification, experiment design, and outcome review. Otherwise, automation simply helps you publish weak creative faster.

Key takeaways

Treat local video as proof of place: answer a nearby customer’s practical question with accurate visual evidence.
Audit Location Manager, Shared Library controls, campaign scope, and location-to-asset mapping before enabling an unfamiliar format.
Use Asset Studio when the concept can tolerate template and generation constraints; use controlled production when exact scenes, faces, pacing, or custom audio are essential.
Keep source images and masters modular, labeled by location, and available outside the generation tool.
Separate lack of delivery from creative failure, especially while the local placement remains an early test.
Choose winners by conversions, sales, or another preselected business outcome, not by novelty or click-through rate alone.

Start with the location where you can verify the visual promise, destination, and business outcome most cleanly. Build one focused brief, prepare accurate source assets, and document the account state before launch. That gives you a controlled pilot without betting the wider local program on an unproven placement.

References

April 20, 2026

Google Ads Security and Conversion Infrastructure Runbook

Your Google Ads stack can fail in two opposite ways: access becomes too loose to trust, or security controls become so brittle that the people and automations responsible for measurement are locked out. Meanwhile, a conversion tag can deploy cleanly and still measure the wrong action.

The practical goal is not merely to enable multi-factor authentication or create a Google Tag Manager tag. You need a traceable path from an authorized identity to a tested conversion event, with an owner and a recovery route at every handoff. This runbook shows you how to build that path without turning an access change or tagging shortcut into a campaign outage.

Key takeaways

MFA enforcement matters most when someone creates a new OAuth 2.0 refresh token. An integration that works now can still fail during reconnection, onboarding, or credential replacement.
Service accounts remain the better fit for supported automated or offline workflows, but they still need explicit ownership, limited access, and a tested handoff process.
A pre-filled Google Tag Manager configuration can remove transcription work. It cannot decide whether you selected the right container, conversion action, trigger, or counting logic.
Never revoke a working credential or remove a working conversion tag until its replacement has passed a controlled test. Otherwise, your rollback path disappears at the moment you need it.
Security and measurement should share one release record: identity owner, authentication method, Ads account, conversion action, GTM container, test evidence, publisher, and rollback decision.

Map authentication before MFA exposes a hidden dependency

A cutaway security system shows human, automated, and recovery access routes converging on one gateway, with one route blocked and a backup route remaining open.

Google’s announced rollout made MFA mandatory for new user-based Google Ads API authentication from April 21, with enforcement expanding over the following weeks. The important boundary is token creation: OAuth 2.0 refresh tokens that were already in use were not invalidated by the change, but fresh authentication requires the additional identity check.

That boundary explains why an account can look healthy until a routine maintenance task causes a failure. A scheduled process may continue using its existing refresh token, while a new employee, replacement integration, revoked credential, or reconnection attempt reaches the MFA gate. Passing today’s automated run is therefore not proof that your recovery workflow is ready.

Start with an authentication inventory. Do not begin by changing credentials. For every connection that can read from or act on a Google Ads account, record:

Workflow: the API job, reporting transfer, desktop tool, script, dashboard, or application that depends on access.
Authentication pattern: user-based OAuth or a service account.
Named owner: the person responsible for approving access, completing MFA, and handling recovery.
Operational owner: the person who can prove the workflow still runs correctly after an authentication change.
Credential event: what would force a new authorization flow, such as onboarding a user, replacing a connection, or rebuilding an integration.
Recovery route: who can restore access if the primary owner is unavailable, without sharing a personal password or MFA prompt.
Evidence: the last successful controlled authentication and the workflow result it enabled.

For user authentication, make the MFA rehearsal realistic. Use the same consent and token-generation path that the production workflow expects. Confirm that the designated person can complete the second factor, which may be a phone prompt or an authenticator app. Then verify that the resulting credential reaches the intended account and supports the intended workflow. A successful Google sign-in alone is not enough.

Choose user authentication or a service account deliberately

Keep user-based OAuth when the workflow is genuinely tied to a person’s authorization and an interactive sign-in is acceptable. Use a service account for a supported automated or offline workload when the connection should survive staff changes and should not depend on a person responding to an MFA prompt. Google left service-account workflows outside the new MFA requirement and recommends them for automated or offline scenarios.

Do not migrate to a service account merely to avoid MFA. A service account is a machine identity, not an exemption from governance. Confirm that the application supports it, grant only the access the workflow needs, document who owns that identity, and test what happens when its permissions or connection must be replaced.

Expand the inventory beyond custom API code. The same security change reaches authentication used by Google Ads Editor, Scripts, BigQuery Data Transfer, and Data Studio. If those tools are owned by different teams, give one person responsibility for the complete dependency map. Otherwise, each team may believe another team owns the failing sign-in.

Most importantly, do not revoke the working refresh token while you are only testing its replacement. Prove the new path first, record the result, and then retire the old credential through a reviewed change. Revoking first can stop reporting or automation without leaving you a quick way back.

Use direct GTM setup to remove copying, not judgment

Google Ads has tested a Set up in Google Tag Manager option inside the conversion setup flow. Where the option is available, you can select a GTM container and open a suggested, pre-filled tag configuration instead of manually carrying the conversion ID and label between products.

Treat this as a safer handoff, not an automatic implementation. It reduces opportunities for transcription errors, but it does not know whether your chosen website action represents a qualified lead, a completed sale, an internal test, or an accidental page view. It also cannot resolve a poor container naming convention or decide whether an existing tag will overlap with the new one.

The integration is described as a test, so do not make a launch deadline depend on the button appearing in your account. If it is absent, continue with the established manual setup and apply the same review process. Availability and implementation correctness are separate questions.

Confirm the conversion definition. Write down the user action that should count, where it occurs, and what must not count. Do this before opening GTM.
Match the account and container. Verify the Google Ads account, conversion action, website, GTM account, and container as one set. Similar client or environment names are not proof of a match.
Inspect the pre-filled values. Check the conversion ID and label against the intended conversion action even when Google populated them. Automation should reduce copying, not eliminate review.
Review the trigger separately. The tag configuration identifies where data should go; the trigger determines when it goes there. Confirm that the trigger represents the business event you defined in the first step.
Check for an existing implementation. Search the container for tags and triggers that already send the same action. Publishing a second path may produce duplicate events or conflicting behavior.
Test before publishing. Use GTM’s preview process and complete a controlled conversion path. Confirm that the tag fires on the intended action and remains silent on nearby actions that should not count.
Publish a traceable version. Record the conversion action, reason for the change, reviewer, test performed, and rollback instruction in the version description or release record.
Verify both ends. Confirm the expected firing behavior in GTM and then confirm that Google Ads recognizes the intended conversion setup. A passing browser-side test proves the trigger ran; it does not by itself prove that the account mapping is correct.

Avoid deleting the old tag before the new configuration has been verified. At the same time, do not publish two equivalent live paths and hope to compare them later. Modify the existing implementation when that is the cleanest route, or make the old and new triggers mutually controlled during the release. Your rollback should restore a known configuration, not create a second unknown one.

Operate access and tagging as one controlled release

Two specialists approve access and inspect a digital event as it passes through secure testing, monitored release, and rollback stages.

Authentication and conversion tracking are often assigned to different specialists, but they meet at the same operational boundary. The person publishing a tag needs reliable account access. The automation consuming conversion data needs a stable identity. The campaign owner needs confidence that the event still means what its name claims.

Use one release record for both sides. In a larger team, assign an access owner, GTM implementer, independent reviewer, and business owner for the conversion definition. In a smaller team, one person may hold several roles, but the checkpoints should remain separate. Pause between configuring, reviewing, publishing, and validating so that familiarity does not replace evidence.

Freeze unrelated changes. Keep other credential, container, and conversion-action edits out of the same release so a failure has a narrow set of possible causes.
Capture the known-good state. Record which automation currently succeeds, which tag and trigger currently fire, and which conversion action they serve.
Prove recovery access. Confirm that the named owner can complete a fresh user-authentication flow with MFA, or that the supported service-account workflow can be restored by its documented owner.
Stage the measurement change. Build or review the pre-filled GTM configuration without publishing it. Confirm the account, action, ID, label, trigger, and duplication check.
Run the controlled path. Exercise the actual conversion behavior and preserve enough evidence for another person to understand what was tested.
Publish and validate. Confirm the container version, the live firing conditions, the Google Ads destination, and the next successful dependent automation run.
Retire only what has been replaced. Revoke an old credential or remove an old tag only after the new path is proven and the rollback decision is documented.

Use the failure layer to choose your first check

When something breaks, identify whether the failure occurs at identity, authorization, container configuration, trigger logic, publishing, or destination mapping. Rolling back everything at once can hide the actual defect.

Symptom	Likely layer	First check
An existing API job runs, but a new connection cannot generate a refresh token	User authentication and MFA	Repeat the fresh consent flow with the named owner and confirm that the second factor can be completed.
A connection succeeds for one person but cannot be recovered by the team	Ownership and recovery	Check whether the workflow depends on one personal identity and whether a supported service-account pattern is more appropriate.
Editor, Scripts, a transfer, or a dashboard fails during sign-in	Shared authentication policy	Identify the actual Google identity behind the tool instead of treating it as an isolated application error.
The direct GTM option does not appear	Feature availability	Use the manual tag setup rather than delaying the release; the integration is being tested and may not be available in every flow.
The tag does not fire during preview	Container or trigger logic	Confirm the selected container, preview environment, trigger conditions, and exact user action.
The tag fires, but it points to the wrong conversion action	Destination mapping	Compare the conversion ID and label with the intended Google Ads action and account.
More than one tag fires for a single intended action	Duplicate implementation	Search for older tags, overlapping triggers, and parallel containers before changing the conversion definition.
The browser-side test passes, but the dependent automation fails	API authorization or workflow logic	Test the automation separately with its own identity and permissions; the GTM test does not validate API access.

At your next planned change window, exercise one fresh authentication flow and trace one controlled conversion from the user action through GTM to the intended Google Ads action. If either path lacks a named owner, test evidence, or a safe rollback, fix that gap before you scale the campaign or add another integration. Your infrastructure is ready when another authorized person can understand it, test it, and recover it without guessing.

References

April 17, 2026

Gemini Ad Safety: A Practical Google Ads Compliance Plan

Your Google Ads campaign can be commercially legitimate and still fail before its first impression. A stray phrase is no longer the only concern. Gemini-powered enforcement is designed to interpret intent across the creative, destination, account, and activity surrounding an ad.

You do not need to reverse-engineer the model. You need a campaign that remains accurate, consistent, and explainable from every angle. The following workflow will help you review campaigns before launch, distinguish a correct enforcement action from a possible mistake, and respond without creating a larger account problem.

Gemini makes policy review a pre-launch control

Google says it blocked or removed 8.3 billion ads globally and suspended 24.9 million advertiser accounts in 2025. More than 99% of the policy-violating ads it identified were stopped before they ran.

Those are Google-supplied, systemwide enforcement figures. They are not an independent audit, and they do not reveal the probability that a legitimate advertiser will be flagged. They do establish the operational reality: automated review is happening at enormous scale, and most harmful ads identified by the system never receive a live testing period.

By the end of 2025, most Responsive Search Ads were reportedly assessed instantly. You therefore cannot treat policy review as something to clean up after launch. Approval is a launch dependency, alongside tracking, budget, bidding, and landing-page readiness.

Gemini also changes what a useful review looks like. Google describes the system as better able to understand ad intent while evaluating billions of signals, including account age and user patterns. That does not mean every one of those signals determines an outcome, and Google has not disclosed a decision formula. It does mean that replacing one questionable word may not solve a problem rooted in the offer, destination, identity, targeting method, or account behavior.

There is evidence of improving precision, but not perfection. Google attributed an 80% reduction in incorrect advertiser suspensions to Gemini and said it processed four times as many user reports as in the previous year. Advertisers in the UK and US nevertheless reported waves of disapprovals they could not readily explain. The useful position is neither blind trust nor blanket suspicion: investigate the complete campaign before deciding that an enforcement action is wrong.

Policy maintenance matters as much as initial setup. Google made 35 policy updates during 2025. Add a last-reviewed date to your compliance checklist and assign someone to own it. An undated checklist quietly becomes a historical record rather than a control.

Audit the connected ad system, not just the copy

Compliance becomes difficult to diagnose when it lives only in a copywriting checklist. Treat an ad as a connected system: claim, offer, destination, business identity, targeting, and account activity must tell the same defensible story.

The following is an advertiser-side audit model, not a description of Gemini’s unpublished decision rules. Its purpose is to expose contradictions before automated review or a user report does.

Review layer	Question to answer	Evidence to retain
Ad claims	Can you prove each objective promise, price, result, qualification, or comparison as written?	Current substantiation, approval notes, and the exact qualifying language
Offer and destination	Does the landing page present the same product, entity, conditions, and user outcome as the ad?	Final URL, redirect path, and dated page captures
Business identity	Do the advertiser name, domain, billing entity, and customer-facing identity align accurately?	Current business records and a log explaining legitimate changes
Targeting and personalization	Is the audience or data practice acceptable independently of the creative?	Campaign settings, audience rationale, and applicable consent records
Account and site changes	Can an internal reviewer explain recent changes in ownership, payment, domains, tracking, or campaign behavior?	Owner, date, reason, and approval for each material change

This broader review is necessary because enforcement is not confined to offensive language. In the United States, the leading reasons associated with enforcement included abuse of the ad network, misrepresentation, sexual content, personalization violations, and dating or companionship ads. Google removed 1.7 billion ads and suspended 3.3 million advertiser accounts in the US during 2025.

Start with misrepresentation even if your business does not operate in an obviously sensitive sector. A campaign can become misleading through inconsistency rather than an outright false sentence. A headline may omit an important condition. A landing page may use a different company name. A promotion may have ended while an older asset remains eligible. A redirect may send some users to a page the campaign owner never reviewed.

Personalization deserves its own check. Compliant wording does not repair an unacceptable audience or data-use practice. Have the person responsible for targeting confirm the settings and rationale rather than asking the copywriter to approve the campaign as a whole.

If a campaign touches consumer-protection, privacy, discrimination, or another legal requirement, obtain the appropriate legal review. Google Ads approval is not legal clearance, and this operational checklist is not a substitute for advice on the law that applies to your business.

Use this pre-launch safety workflow

A useful pre-launch review produces evidence, not a vague assurance that someone looked at the ads. Run these steps after the creative and landing page are stable but before the launch depends on immediate approval.

Assign one accountable owner. Record who approved the campaign, which policy version or internal checklist was used, and the review date. Contributors can review separate areas, but one person must confirm that the pieces agree.
Inventory every eligible component. Include headlines, descriptions, images, videos, business names, extensions or assets, audience settings, final URLs, tracking redirects, and the destination users actually reach. Do not review only the combination shown in an editor preview.
Map every material claim to proof. Copy the exact claim into a review sheet, identify the evidence, and note any qualifier needed in the ad or on the destination. If no one can produce the proof, revise or remove the claim before submission.
Run a consistency check from ad to conversion. Confirm that the same advertiser, offer, conditions, geography, and expected next step appear throughout the journey. Test the final destination while logged out and on the device types the campaign targets.
Review Responsive Search Ad assets as possible combinations. Each headline and description must remain accurate when paired with other eligible assets. Do not rely on one preferred preview to supply context that another combination could omit.
Review targeting and personalization separately. Confirm who is included, what data supports that decision, and whether the practice complies with the relevant Google policy and your own obligations. Record the decision rather than relying on an undocumented verbal approval.
Freeze a launch record. Save the approved copy, campaign settings, final URLs, landing-page captures, claim evidence, and material account changes. Keep personal or confidential customer data out of this packet unless it is genuinely required and appropriately protected.

When practical, avoid combining an important launch with unrelated account, payment, domain, and tracking changes. This does not guarantee approval, but it reduces the number of variables you must investigate if something is flagged.

Use a strict pass rule: every campaign component must have an owner, the material claims must be supported, and the ad-to-destination journey must be consistent. A reviewer who is merely unsure should not mark the campaign compliant. The uncertainty needs to be resolved, documented, or removed from the campaign.

Respond to disapprovals without making the case harder

An ad disapproval and an account suspension require different responses. A disapproval gives you a bounded place to begin: identify the affected ad, asset, destination, or policy area. A suspension is an account-level incident with a greater business consequence, so preserve the evidence and control changes before anyone starts experimenting.

Stop repeated resubmission. Sending the same material again does not establish compliance and can obscure the sequence of events you need to explain.
Classify the scope. Determine whether the action affects one asset, one ad, several campaigns, a destination, or the advertiser account. Check for a shared claim, URL, audience, business identity, or recent change.
Preserve the reviewed state. Capture the exact policy label, enforcement message, affected items, URLs, page contents, account notices, and time observed. Dynamic landing pages can change while you investigate.
Read the stated policy against the whole campaign chain. Check the copy, offer, destination, identity, targeting, and account history. Do not assume the highlighted asset is the only relevant input.
Make the smallest complete correction. Change the root inconsistency and all affected instances, but avoid unrelated edits that make the before-and-after state difficult to explain.
Appeal with traceable evidence when you believe the campaign complies. State what was affected, how you evaluated the policy, what you corrected if anything, and which evidence supports your position. Keep the explanation factual and specific.
Record the outcome. Add the cause, resolution, evidence, and any checklist change to an incident log so the same pattern is caught before the next launch.

Do not route around a suspension by opening a replacement account. Apart from any policy consequences, that move fragments your records and makes a legitimate explanation harder to establish. Abuse of the ad network was already among the main US enforcement reasons in 2025. Use the authorized review or appeal path and involve the account owner responsible for business identity and billing.

Do not label an action a false positive until you have completed the connected-system audit. At the same time, do not assume automation is infallible. Google’s claimed 80% reduction in incorrect suspensions is encouraging, but an 80% reduction is not elimination, and documented advertiser complaints persisted. Your evidence packet is what lets you challenge a mistake without relying on indignation or guesswork.

A concise appeal should answer four questions: What was flagged? Which policy did you review? What evidence shows compliance or what root issue was corrected? What specific review are you requesting? Long narratives, repeated submissions, and unrelated account changes make those answers harder to see.

Key takeaways

Gemini-powered enforcement operates before delivery at enormous scale, so policy review belongs in the launch plan rather than the post-launch cleanup.
Intent-aware review makes copy-only compliance checks inadequate. Audit the offer, destination, identity, targeting, and account changes as one connected system.
Responsive Search Ads need asset-level and combination-level review because one favorable preview cannot represent every eligible message.
Google reports fewer incorrect suspensions, but unexplained disapprovals have not disappeared. Preserve evidence before editing or appealing.
The safest incident response is controlled and traceable: classify the scope, preserve the state, correct the root issue, and use the authorized appeal process.

Before your next launch, choose one scheduled campaign and run the full audit table against it. Save the evidence, name the accountable owner, and date the checklist. That single dry run will expose whether your current process can explain a Gemini-era enforcement decision or only react to one.

References

CrushPress.AI – Gemini’s AI Takes Ad Safety to New Heights: Over 99% Bad Ads Blocked

April 16, 2026

Category: Google Ads

Know exactly what will fail at the cutoff

Key takeaways

Build an inventory that includes hidden and dormant calls

Ask vendors for feature-level confirmation

Migrate the workflow, not just the version label

Define readiness with production evidence

References

Make the data trustworthy before you automate the decision

Use Task Assistant as a configuration audit

Create a one-page measurement contract

Translate strategy into an AI brief the system can use

Measure the decision, not whatever the dashboard offers

Put hard boundaries around queries, copy, pages, and spend

Treat every eligible landing page as campaign creative

Shopping and travel need the same controls in different places

Google campaign automation FAQ

What is Google marketing intelligence?

Should you automate a campaign if tracking is imperfect?

Can Association replace conversion measurement?

How do you know automation has too much control?

References

Optimize the customer need state, not just the query

Build a signal stack the bidding system can understand

Start with first-party truth, not a broad persona

Turn the landing page into a targeting brief

Use creative to qualify, not merely attract

Close the click-to-revenue feedback loop before scaling

Start with the acquisition decision, not the campaign type

Make customer states usable before Smart Bidding sees them

Define high value and lapsed in your own data

Treat additional customer value as a bidding instruction

Choose click, view, and lifecycle signals for different jobs

Run App Labs as a reversible test, not a permanent dependency

Key takeaways for your next campaign cycle

References

Define a qualified lead before Google defines one for you

Validate the signal before automated bidding scales it

Treat call recording as a governance decision

Let Ads Advisor operate, but give it boundaries

Key takeaways

References

Key takeaways

Choose exactly what automation is allowed to control

Local video should prove the place, not merely promote the brand

Write the local promise before you choose footage

Make the location connection part of creative QA

Build a production system that survives Asset Studio’s limits

Keep the master assets modular

Test business outcomes, not the novelty of video

Key takeaways

References

Key takeaways

Map authentication before MFA exposes a hidden dependency

Choose user authentication or a service account deliberately

Use direct GTM setup to remove copying, not judgment

Operate access and tagging as one controlled release

Use the failure layer to choose your first check

References

Gemini makes policy review a pre-launch control

Audit the connected ad system, not just the copy

Use this pre-launch safety workflow

Respond to disapprovals without making the case harder

Key takeaways

References