How to Set Up Google Ads Auto-Apply Recommendations for Enterprise Accounts

Set up enterprise auto-apply recommendations by defining the account and regional scope, verifying conversion and value data, writing governance rules, selecting one category at account level, and reviewing the queue, History, and Change history. Use named owners and a rollback record so an automatic change can be stopped without erasing valid unrelated work.

Use Google’s auto-apply guidance, management guidance, and apply or dismiss guidance for current account controls and recommendation behavior.

1. Define enterprise scope and outcomes

Record account, manager, business unit, product, region, market, currency, budget, primary conversion, value, target CPA or ROAS, quality metric, legal rules, and owners. Choose qualified pipeline, order, subscription, revenue, margin, or another approved outcome.

Write global rules and local exceptions. Auto-apply is account-level, so category selection does not automatically create product, country, campaign, or business- unit boundaries.

2. Classify recommendation risk

Group categories into ads and assets, keywords and targeting, bids and targets, budget use, measurement, and structure. Record what may be automatic, what requires regional or product review, and what is always manual.

Keep conversion, value, primary-goal, bidding, market expansion, public claims, and material budget changes under human review until the enterprise has evidence.

3. Verify data and baselines

Check conversion firing, account or opportunity identity, duplicate handling, consent, values, currency, CRM or order import, sales or billing delay, and regional reporting. Compare Ads actions with qualified pipeline, opportunity, revenue, margin, orders, or later outcomes.

Set baselines by product, region, account segment, brand, non-brand, and cohort. Include seasonality, promotion, feed, site, CRM, and campaign release dates.

4. Open the exact account settings

Open Recommendations and Auto-apply settings in the exact enterprise account. Review bundles and individual categories, read the current details and eligibility, and record the date. Google’s available recommendation set can change over time.

Confirm who has authority to save the setting. A manager-level process should still identify the exact account and owner for the category.

5. Select one category

Choose a category with narrow scope, clear evidence, and an explicit rollback. Keep expansion, target, conversion, public-claim, and material budget changes manual until global and local owners approve them.

Record category, account, product, region, campaign scope, possible effect, approver, enablement date, baseline, first review, and stop condition. Save only the approved selection.

6. Review the queue

Google says applications occur only when relevant. Review the queue for changes expected on the Recommendations page. Check new terms, assets, audiences, locations, products, bids, and measurement against global and local policy.

Dismiss a recommendation that violates an exception or scope rule. Do not accept every card to improve an optimization score.

7. Use History and Change history

Use History to see enabled categories and recent applications. Use Change history to inspect the exact edit, account actor, date, and scope.

Keep an enterprise log with account, business unit, product, region, category, approver, enablement, application, result, rollback, and next review. Recheck the category list after platform or policy changes.

8. Evaluate at useful scopes

Compare spend, conversions, qualified pipeline, opportunities, revenue, margin, orders, search-term quality, product fit, and local results by product, region, account segment, brand, and cohort. Allow for attribution, CRM, feed, billing, currency, consent, and sales-cycle delay.

Do not rely only on a blended enterprise total. A local or product regression can disappear inside aggregate performance.

9. Define rollback and change control

Stop for wrong goal, pipeline or margin deterioration, wrong region or product, unapproved claim, import failure, budget breach, consent issue, or local regression. Turn off future applications in current settings or History and inspect Change history.

Restore only affected settings. Record account, product, region, date, evidence, owner, restored state, and follow-up. Disabling auto-apply does not automatically reverse every earlier change.

Common setup mistakes

Treating account-level auto-apply as a regional control.
Letting local teams use incompatible outcomes or value rules.
Mixing global and local changes without scope in the log.
Ignoring currency, consent, feed, CRM, or sales-cycle delay.
Allowing public or regulated claims without review.
Evaluating only aggregate enterprise performance.
Losing the identity of the approver or account actor.
Assuming disablement restores all prior settings.

Governance must be explicit before scale.

Enterprise setup checklist

Confirm account scope, global policy, regional exceptions, outcome, conversion and value rules, budget, quality thresholds, allowed categories, manual reviews, baseline, owners, queue and History cadence, stop conditions, rollback, and change log. Use the enterprise auto-apply framework and general auto-apply guide for companion reviews.

Start with one business unit, product, region, and category. Expand only after local and global outcomes remain within policy.