Mobile or desktop? What a user-agent string in an open log can and cannot tell you
Many tracking logs show a user-agent string next to each open: a line of text the client sends to identify itself. It is tempting to read "iPhone" or "Outlook" from it and picture where the person was. Sometimes that works. Often the string describes something else entirely.
What the string is
When a mail app fetches an image, it usually sends a User-Agent header. A desktop client might send something naming Windows and its rendering engine. A phone app might name iOS or Android. Webmail opened in a browser sends the browser's string. That is all you get. No screen size and no app version beyond what the string includes.
When it is replaced
- Gmail's image proxy fetches images with its own generic agent, so Gmail opens on phone and desktop look the same.
- Apple Mail Privacy Protection fetches through relays with a generic string, regardless of device.
- Security scanners may send a browser-like string, or nothing useful at all.
So a large share of modern opens carry a string that tells you which service fetched the image, not which device the reader holds.
What a device guess is worth
When a genuine client string does come through, it can be mildly useful. A phone open in the evening may mean a quick glance, and a desktop open the next morning may mean a closer read. Use it to adjust tone and timing gently, if at all. Avoid building a story out of it. "They read it on their phone on the train" is speculation dressed up as data.
Practical habits
- Group opens by "proxy" versus "direct client" first. Only the second group says anything about devices.
- Look for patterns over several messages, not one.
- Keep device guesses out of your messages. Never refer to how or where someone read your email.
A simple tracker like MailPixel shows the raw string so you can make these calls yourself. The most honest reading of it is often "fetched through a proxy", and that is fine.