How to Set Up Google Ads Auto-Apply Recommendations for Local Businesses

Set up local-business auto-apply recommendations by defining the call, booking, job, or purchase outcome, mapping branches and service areas, checking hours and capacity, writing quality guardrails, and selecting one account-level category at a time. Review the queue, History, and Change history before expanding automation.

Use Google’s auto-apply documentation, management guidance, and apply or dismiss guidance for the current controls.

1. Define the local outcome

Choose connected call, qualified call, confirmed booking, attended appointment, quote request, completed job, store purchase, or another business event. Record the count unit, location, service type, value, source, conversion window, and primary role.

Keep click-to-call, form, booking, completed work, and revenue separate. Decide how missed calls, transfers, repeat customers, cancellations, no-shows, and existing customers are counted. Automation needs a precise event before it can be evaluated.

2. Map branches and operating constraints

List branches, service areas, postal codes, excluded areas, phone numbers, central call routing, hours, holidays, practitioners, languages, products, budget, staffing, and response time. Mark which campaigns can share settings.

Write rules that must not change automatically: location boundaries, hours, regulated claims, promotions, branch assets, service capacity, and conversion goals. A recommendation that increases clicks outside the service area is not useful local automation.

3. Check calls, bookings, and jobs

Compare Ads calls and forms with the phone system, booking tool, CRM, job system, point of sale, or service ledger. Check call qualification, booking attendance, location identity, duplicate behavior, value, consent, and offline delay.

Set a baseline for spend, calls, qualified calls, bookings, completed jobs, revenue, no-shows, service-area fit, response time, and lead cost. Fix a broken conversion path before enabling a recommendation that changes bids or goals.

4. Open account-level Auto-apply settings

Open the Recommendations area and current Auto-apply settings at account level. Google documents account-level auto-apply, so selecting a category does not create a branch-by-branch control.

Review bundles and individual categories, expand each, and read what it can change. Record the date because Google’s available recommendations can change. If an agency manages the account, record branch or client approval.

5. Select one category

Choose a category with clear scope and rollback. Keep location or service-area expansion, new audiences or queries, call or booking conversion changes, target bids, and local or regulated assets under manual review until proven.

Record account, campaign, branch or service scope, effect, owner, approver, enablement date, baseline, first review, and stop condition. Save only the category that fits the written local policy.

6. Inspect the queue

Google says applications run only when relevant. Review the Recommendations queue for new terms, assets, locations, audiences, or bidding changes. Check each against service area, branch, hours, appointment availability, landing page, phone route, and claim policy.

Dismiss a card that conflicts with the business rule. Do not accept every recommendation to improve an optimization score while hiding poor local fit.

7. Track History and Change history

Use the History tab for enabled categories and recent applications. Use Change history to inspect the individual change and account actor.

Keep a local log with category, branch, service, date, approver, applied change, call or booking result, completed-job result, decision, and next review. Name a backup owner when a manager, agency, or franchise operator changes.

8. Measure operations after lag

Compare spend, clicks, calls, qualified calls, bookings, attendance, jobs, revenue, no-shows, repeat customers, and service-area fit by branch, day, hour, device, and campaign. Allow for call duration, booking delay, seasonality, holiday hours, weather, and CRM processing.

Keep website, phone, booking, hours, and service releases beside the report. An integration or schedule change can look like a recommendation result.

9. Define rollback

Stop for calls outside the area, wrong branch, poor call quality, rising no-shows, unapproved claim, budget pressure, conversion inflation, or capacity overload. Turn off future applications in the current settings or History view.

Inspect Change history and restore only affected settings. Disabling auto-apply does not automatically reverse all earlier changes. Record branch, date, reason, owner, evidence, restored state, and follow-up call or job sample.

Common setup mistakes

Automating clicks or calls without a qualified local outcome.
Ignoring branches, hours, holidays, service areas, and capacity.
Expanding locations or audiences before checking lead quality.
Changing conversions without call, booking, or job reconciliation.
Accepting local or regulated assets without owner review.
Evaluating before bookings and jobs mature.
Treating account-level settings as branch-level controls.
Assuming disablement restores every prior change.

The local owner must remain accountable for operational fit.

Local-business setup checklist

Confirm outcome, branch and service area, hours, capacity, measurement health, budget, allowed categories, manual-review categories, baseline, owner, queue and history cadence, stop conditions, and rollback steps. Use the local auto-apply framework and general auto-apply guide for companion reviews.

Start with one branch and one category. Expand after qualified calls, bookings, and completed work stay within the operating plan.