Google Ads Device Bidding Checklist

Use this Google Ads device bidding checklist before changing a device bid, after a site or app release, and during recurring campaign reviews. Confirm the business goal, mobile/desktop/tablet evidence, campaign-type support, experience, measurement, value guardrail, effective scope, and rollback path. Then wait for enough qualified data before treating a device change as a success or failure.

Google’s device targeting guidance and device adjustment documentation describe supported controls and limits. Campaign type and bidding strategy can change what is available. Use the current Google Ads interface for the final setting and preserve the source campaign in the change record.

1. Define the device decision

[ ] Campaign, type, network, market, and owner are recorded.
[ ] The primary outcome and qualified definition are clear.
[ ] Value or margin, efficiency guardrail, conversion lag, and capacity are documented.
[ ] The device decision protects a defined role rather than a universal percentage.
[ ] Mobile, desktop, and tablet are compared as business journeys, not only as click rates.
[ ] Minimum sample, review window, and rollback owner are named.

Do not start with “mobile is worse.” State whether the problem is qualified value, page experience, measurement, capacity, or a supported bid control.

Separate correlated factors

[ ] Location, schedule, audience, query or product, browser, network, and landing page are considered.
[ ] The device result is not being read from a small or unusual sample.
[ ] Cross-device journeys and conversion lag are acknowledged.

2. Verify campaign support and scope

[ ] Campaign type and bidding strategy support the intended device control.
[ ] Current device settings, bid limits, budget, and shared budgets are recorded.
[ ] Manual device adjustments are not assumed to apply to an automated strategy.
[ ] Account, campaign, ad group, device, location, schedule, audience, and network scope are confirmed.
[ ] An inherited or shared setting will not affect unrelated campaigns.
[ ] The current Google Ads help reference is attached to the record.

3. Preserve the baseline

[ ] A comparable date range is selected.
[ ] Device-level impressions, clicks, spend, conversions, qualified outcomes, value, margin, and lag are recorded.
[ ] Location, schedule, audience, query or product, page, and campaign role are available where they explain device mix.
[ ] Current budget, bidding, bid limits, device settings, pages, forms, calls, apps, and feeds are preserved.
[ ] Tags, consent, attribution, CRM routing, offline imports, and deduplication are checked.
[ ] Promotions, pricing, stock, page releases, and support changes are annotated.

Do not overwrite the before-state after the first change. A device rate without absolute volume or conversion-lag context is not a reliable bid decision.

4. Audit the device experience

[ ] Mobile speed, viewport, tap targets, form length, calls, app handoff, payment, and confirmation are tested.
[ ] Desktop navigation, long-form content, chat, forms, and sales handoff are tested.
[ ] Tablet breakpoints and product or lead completion are tested.
[ ] Landing-page, form, call, app, checkout, and policy issues are separated from the bid decision.
[ ] Intentional device limitations are documented.
[ ] A device bid is not being used to hide a repairable page problem.

5. Measure quality and value

[ ] Conversion definitions are consistent across devices or differences are recorded.
[ ] Qualified rate, accepted leads, order quality, revenue, margin, refunds, support burden, and call outcomes are reviewed where relevant.
[ ] Cross-device paths and later-stage conversion lag are included.
[ ] Clicks and micro-conversions are not the only decision metrics.
[ ] Capacity to process additional demand is documented.

6. Make and record the change

[ ] The observation and hypothesis are written.
[ ] One principal constraint is selected.
[ ] Current and proposed device settings are recorded.
[ ] Expected effect, value or efficiency guardrail, and review window are defined.
[ ] Owner, effective time, and rollback condition are named.
[ ] Unrelated budget, targeting, creative, and page changes are held steady where possible.

7. Verify the saved state

[ ] The correct account and campaign are open.
[ ] Device, campaign, ad-group, location, schedule, audience, and network scope are correct.
[ ] Bid or target value and effective status are reopened and checked.
[ ] Budget, strategy, shared settings, and inheritance are reviewed.
[ ] Ads, assets, pages, forms, calls, apps, feeds, and policy status remain eligible.
[ ] The effective timestamp and interface result are preserved.

A Save message is not evidence of business success. Verify the source campaign, then wait through the normal reporting and conversion window.

8. Review and decide

[ ] Device-level spend, impressions, clicks, qualified outcomes, value, margin, and capacity are compared.
[ ] Location, schedule, audience, query or product, landing page, and campaign branches are segmented.
[ ] Concurrent changes and demand events are annotated.
[ ] Retain, narrow, reverse, and expand conditions are applied.
[ ] The previous state remains available for rollback.

9. Compact device change ticket

Copy this into a launch or review record:

[ ] Campaign and device scope:
[ ] Business role and qualified outcome:
[ ] Baseline period and source view:
[ ] Experience and measurement findings:
[ ] Current and proposed control:
[ ] Expected effect and value guardrail:
[ ] Owner, effective time, review date:
[ ] Rollback trigger and previous-state location:
[ ] Decision: retain / narrow / reverse / expand:

For implementation, see how to set up Google Ads device bidding. The optimization guide covers ongoing testing, how to fix Google Ads device bidding covers diagnosis, and Google Ads device bidding best practices provides the broader framework. The adz.so product overview is a truthful evidence-review entry point; it does not automatically set device bids.