Campaign Tracking
How to use device targeting
Device targeting sends phones, tablets, and desktops to different destinations from one slug — app stores, desktop checkout, or a simpler mobile page.
Zipy editorial · 2026-07-29 · 7 min
Key takeaways
- User-agent targeting is a hint, not a lab result. Keep a default.
- Send phones to the store or mobile page that can complete the job.
- Combine with geotargeting only when both rules have a fallback.
When one landing page is the wrong door
A desktop pricing page with a tiny tap target wastes a phone click from a Story. An App Store badge on a laptop wastes a click from a newsletter. Device targeting lets the same public slug choose. The person still sees one URL on the card or in the caption.
Typical splits: iOS to the App Store, Android to Play, desktop to the web checkout. Or phones to a short mobile form and desktops to the full configurator.
Read the signal with some humility
The shortener reads the user-agent. People spoof it. In-app browsers lie. Tablets sit in a gray zone. Set an explicit tablet rule or accept that they will hit the default. Log enough to debug a bad week. Do not build a compliance process on user-agent alone.
Rules that stay maintainable
Name destinations by job, not by OS version. When Apple changes a store URL, you edit one target. Pair device rules with campaign UTMs so finance still sees one flight. In Zipy, device targeting ships with geotargeting on paid plans. Test each rule once with a real phone before you print the QR.
Related: what-is-geotargeting · how-to-track-social-media-link-clicks