Google Search Device Performance: Diagnose the Journey Before Cutting Bids

A device report should tell you what to investigate before it tells you what to cut. Compare suitable customer outcomes, inspect the route and then verify the control your bidding strategy supports. Cheaper forms can still mean more expensive qualified enquiries, while a low enquiry count may reflect a fault customers cannot get past.

Start with a comparable Search slice
Use the same date basis, conversion actions and business-outcome window for each device. Check whether the device groups contain different campaigns, queries or offers. An overall mobile-versus-desktop total can reflect a different traffic mix rather than the effect of the device itself.
Keep cost, clicks, accepted enquiries and qualified outcomes together. Mark unmatched records as unresolved, and give each device group the same opportunity to complete follow-up. A device with older, fully reviewed enquiries has an unfair advantage over one whose sales outcomes are still arriving.
Read a fictional result beyond the form count
In a fictional review, mobile spends $600 and produces 20 accepted forms, eight of which sales confirms as qualified. Desktop spends $400 and produces ten forms, also with eight qualified outcomes. Mobile form CPA is $30, while desktop form CPA is $40. On that metric alone, mobile appears cheaper.
Qualified-enquiry cost reverses the comparison: mobile is $75 and desktop is $50. Qualification rates are 40% and 80%, respectively. These observations justify investigation, not a claim that desktop caused better leads. Check the offer and search mix before transferring budget or excluding a device.
Inspect the route the customer actually used
Follow the advertised destination on representative devices and browsers. Inspect the first screen, form, validation messages and accepted submission. Our mobile landing-page speed guide covers the loading question; this review also checks whether the customer can understand and complete the action after it loads.
Suppose two of six fictional mobile tests fail: a consent overlay covers the form’s required submit control. The useful finding is reproducible obstruction on two named browser-and-device routes. Repair it and repeat those routes, including validation and receipt of the request. Six tests locate a fault; they do not estimate that one-third of all customers experience it.
Confirm what your bidding strategy supports
Google’s bid-adjustment guidance makes compatibility strategy-dependent. Its Maximize Clicks page describes mobile bid adjustments being incorporated. Under Maximize Conversions, regular existing adjustments are not used, with the documented device exclusion at −100% as an exception.
For Target CPA device adjustments, the adjustment changes the CPA target rather than manually multiplying each auction bid. A fictional $30 target with a +20% mobile adjustment becomes a $36 mobile target. It does not instruct Google to bid exactly 20% more for every mobile click.
Put the supported control into plain language before editing: “change the mobile CPA target,” “adjust a supported bid” or “exclude the device.” An exclusion removes the opportunity to serve that device. It needs a stronger reason than a disappointing aggregate CPA or an instruction copied from a different bidding strategy.
A percentage needs a named object. In a separate fictional manual-CPC example, reducing a $2 bid by 20% gives $1.60. That arithmetic is different from raising a $30 CPA target to $36, and neither tells you that the eventual price of every click will change by exactly 20%. Write the supported control, its scope and intended effect in the review note before applying it.
A usable repair ticket might read: “Submit control hidden beneath the consent overlay on mobile routes M2 and M5. After the fix, repeat both routes with required-field errors and a valid request; confirm the request appears once in the receiving record.” This defines completion more precisely than “mobile fixed.”
Use a filled repair-and-review brief
For the fictional business, the brief could be:
Finding: mobile form CPA $30, but qualified cost $75 versus desktop $50.
Fault: the submission control is obstructed in two identified test cases.
Repair acceptance: M2 and M5 can validate, submit and deliver one accepted request each after the overlay fix.
Bid decision: no reflexive percentage change; verify the strategy’s supported control.
Next evidence: a later device comparison with the same offer, query scope, qualification rule and follow-up allowance.
Keep the pre-repair snapshot. If several settings and the website change together, record that the later result cannot isolate a device bid adjustment’s effect.
Finish with a supported action
Fix the demonstrated obstruction first. Keep the earlier snapshot, verify the repaired routes and then review comparable customer outcomes. If qualified mobile cost remains unattractive, investigate the traffic and offer mix with the fault removed. The original form counts alone do not establish a case for excluding mobile.
Our Google Ads management service can help connect device reporting with the customer route and bidding setup. Bring the observed problem and supported control into the review rather than asking a percentage adjustment to repair every difference in a device report.
Comments