Google Ads guide

How to Set Up Google Ads Device Bidding

To set up Google Ads device bidding, define the device-level business goal, capture a comparable baseline, confirm that the campaign type and bidding strategy support the desired controls, and inspect the mobile, desktop, and tablet conversion paths. Apply the narrowest change with a value guardrail, then verify the saved setting and wait for enough qualified data.

Google’s device-targeting guidance and device bid-adjustment documentation describe supported device controls and their limits. Controls can differ by campaign type and bid strategy. Use current Google Ads help for the exact interface rather than assuming a manual adjustment is available everywhere.

1. Define the device role

Decide what the campaign needs from each device. A mobile lead campaign may care about form completion, calls, speed, and qualification. Ecommerce may care about checkout, payment, delivery, refunds, and margin. A B2B campaign may have a longer desktop research path and delayed conversion.

Record the primary conversion action, qualified outcome, value or margin, conversion lag, capacity, and efficiency guardrail. Do not begin with a rule that every device should have the same conversion rate or bid.

Separate device from correlated factors

Device performance can reflect location, schedule, audience, query intent, browser, network, page speed, creative, and inventory. State which segments will be held steady or reviewed so a device decision does not hide a different problem.

2. Capture the before-state

Choose a comparable period and record device-level impressions, clicks, spend, conversions, qualified outcomes, value, and lag. Add location, schedule, audience, query or product, landing page, and conversion action where they explain the mix.

Preserve current budget, bid strategy, bid limits, device settings, landing pages, forms, calls, app paths, tracking, consent, CRM routing, and offline imports. Annotate promotions, pricing, stock, seasonality, page releases, and other simultaneous changes.

Do not change the device setting before saving the baseline. A small row or a rate without its absolute volume is not enough evidence for a bid decision.

3. Confirm control support

Before editing, verify the campaign type, bidding strategy, network, and current device controls. Some automated strategies incorporate device signals without exposing the same manual adjustment as a manually controlled campaign. Do not apply a manual rule without knowing which setting governs delivery.

4. Audit each device experience

Before applying a bid, test the path users take on mobile, desktop, and tablet. Check page speed, layout, tap targets, form fields, calls, app handoff, checkout, payment, navigation, chat, confirmation, and sales routing. A device bid should not be a substitute for repairing a page that the business can make usable.

Record intentional limitations. If the business cannot handle calls on a device or cannot support a particular checkout path, state that constraint and choose the narrowest supported control. Do not infer that low conversion rate proves low device value when the experience is broken.

5. Connect measurement and qualification

Check device reporting for tags, consent behavior, call tracking, app events, form submissions, CRM routing, offline imports, deduplication, and attribution. Define whether the primary outcome is directly comparable across devices.

Compare qualified rate, accepted leads, order quality, revenue, margin, refunds, support burden, and conversion lag. A device can start a journey that finishes on another device, so use available cross-device evidence before making a strong negative claim.

6. Choose the setting and record the change

Open the correct account and campaign. Confirm device scope, campaign type, bid strategy, current value, budget, schedule, location, audience, and network. Then select the supported device control or adjustment and record:

  • previous and new setting;
  • device and campaign scope;
  • evidence and hypothesis;
  • expected effect and value guardrail;
  • owner, effective time, review window, and rollback condition.

Do not assume the same adjustment number has the same meaning across strategies or campaign types. Keep the official Google Ads help link and interface label in the change record when a control is unfamiliar.

7. Verify the effective setup

After saving, reopen the campaign and check the exact effective setting. Verify that a shared budget, inherited campaign setting, or strategy has not changed the scope. Inspect a representative device branch and one unrelated branch if the change is shared.

Check that ads, assets, landing pages, forms, calls, feeds, and policy status remain eligible. Preserve the effective timestamp and any interface message. If the setting is not visible or behaves differently from the brief, diagnose scope, control support, propagation, or reporting before making another edit.

8. Set the review rule

Define the minimum sample, comparison period, conversion lag, efficiency or value guardrail, capacity limit, owner, and decision options. A high-volume device may need a tighter review; a low-volume device may need more time.

After the normal data window, compare device-level impressions, spend, clicks, qualified outcomes, value, margin, and segment mix. Annotate promotions, pricing, stock, page releases, audience, location, and other changes. Retain, narrow, reverse, or expand the bid using the written rule rather than the headline conversion rate alone.

9. Common setup errors

Avoid these errors:

  • changing a device bid from a tiny or incomplete sample;
  • treating device performance as independent of page quality or intent;
  • raising a bid when tracking or qualification is broken;
  • applying manual adjustments to a strategy that does not support them as expected;
  • comparing unlike campaigns, locations, schedules, or conversion actions;
  • using clicks or micro-conversions as the only device value;
  • applying an account-wide rule to one campaign’s device problem;
  • forgetting to preserve a rollback state.

For a broader framework, see Google Ads device bidding best practices. The existing best Google Ads device bidding settings page covers settings context, while the correct setup companion covers verification. The adz.so product overview is a truthful place to organize device evidence; it does not automatically configure bids.

Sources