Why improving device mix is worth the effort
Device mix is the breakdown of scans by device and operating system. It tells you which phones your audience actually uses, so you can test and optimise for the devices that matter instead of the one in your pocket.Device mix is about coverage, not preference. A group that is small in scans can still be large in revenue.
Diagnose before you change anything
Improvement starts with diagnosis, not with redesign. Before changing a code, split device mix by operating system, device model group, and browser and look for the weakest segment. The weakest segment is where a fix buys the most, because it holds the largest pool of lost value. Also check the steps around device mix: a problem upstream, such as poor placement, can masquerade as a problem with the code itself, and a problem downstream, such as a slow landing page, can waste scans that were earned fairly. Fix the constraint, not the symptom.Write down your diagnosis in one paragraph before you touch anything. State what you observed, which segment is weakest, and what you believe is causing it. This paragraph is your hypothesis, and it keeps the work honest: if the fix does not move the number, the hypothesis was wrong, and you learn something instead of merely changing things.
Levers that move device mix
- Test the destination on both major phone systems, not just your own. - Fix layout and speed problems on the device group that converts worst. - Keep the payload short so older or slower phones decode quickly.Work through the levers in order of expected impact per unit of effort. A lever that costs nothing and affects every scanner beats a lever that costs a print run and affects one placement. For each lever, state the change, the cost, and the segment it should move, then implement only that change. Bundling several changes together feels productive, but it destroys your ability to learn which one worked.
Test the change properly
Device share = scans from one device group divided by total scans, multiplied by 100.Illustrative example numbers, not real-world data: 240 of 400 scans from one operating system gives 240 / 400 x 100 = 60% for that group. If the remaining 40% come from the other major system, both deserve testing, not just the majority.
Run the change as a comparison wherever you can: the old version against the new version, on comparable placements, over the same kind of period. Keep everything else stable, and decide in advance how long the test runs and what counts as a win. A test that ends the moment one variant pulls ahead is not a test, it is a reaction. If traffic is too small for a formal test, change one thing, record the before and after numbers, and treat the result as suggestive rather than proven.