How to show different Shopify on-site messages on desktop and mobile

Desktop and mobile shoppers often need different on-site jobs. A long exit message that works on a large screen can crowd a phone, and a short cart nudge written for mobile can feel thin on desktop.
Device targeting fixes that split. When a campaign only runs on desktop or only on mobile, the copy, timing and triggers can match the screen the shopper is on. Everyone else keeps the quieter default path.
This guide shows how to use the device condition in Atomato so Shopify on-site messages fit desktop and mobile without one campaign trying to do both jobs.
What device targeting is for
Device is one of the campaign conditions Atomato supports, next to page URL, UTM tags, cart value, cart items, cart products and exit intent. You can require all conditions or any one.
Use device when the job itself changes by screen. Exit intent is desktop only, so a leave message belongs on a desktop campaign. A short free-shipping reminder near the buy path often belongs on mobile. Shared news that anyone can reopen later can stay in a NotiFeed for both devices.
Do not use device as a stand-in for signed-in segments. Segments and chosen customers only match customers signed in to their account. Device only answers which screen is open.
Match the job to the screen
Before you build, write one line for each job: the offer, the device and why that screen needs its own message. If both screens share the same job and the same short copy, one campaign for all shoppers is enough. Split only when the trigger, length or placement should change.
- Desktop exit sale: use exit intent on a desktop-only NotiPop, with a clear end time if the sale is real.
- Mobile cart help: use a short NotiPop on mobile when cart value or cart items match, and keep the buy button clear.
- Shared launch news: put lasting details in NotiFeed so both devices can open the bell later.
- Ad follow-through: pair device with a UTM tag only when the ad set itself is desktop or mobile only.
On desktop, a NotiPop can sit at the top right or top left. On phones it appears full width at the bottom. Plan copy length for that layout, and keep Add to cart clear on mobile the same way you would in the mobile Add to cart guide.
Build one campaign per device job
Start from the goal that matches the job. Promote a sale or launch opens NotiFeed templates. Encourage shoppers to take action opens NotiPop templates. Increase order value opens NotiSell. Grow my email & SMS list opens NotiEmail when your plan includes it.
Add a device condition set to desktop or mobile. Combine it with page URL when the offer should only show on one landing page. Combine it with cart value, cart items or cart products when the nudge depends on what is in the cart. Cart and exit intent conditions work for NotiFeed, NotiPop and NotiSell, not for signups.
Keep exit intent on the desktop campaign only. Pairing exit intent with a mobile device condition will not create a phone leave trigger. For the exit pattern itself, see how to use exit intent without ending the visit.
Write short copy for mobile. Name the offer, one proof point and one next step. On desktop you can add a second line when the layout has room. Do not invent a second discount. Match the page and cart rules you already use when you target by page and cart.
Before and after
Before: one sitewide welcome discount runs on every device. Desktop shoppers never get a leave message tied to the sale window. Mobile shoppers see the same long copy that was written for a wide screen, and attributed revenue mixes both jobs in one campaign.
After: a desktop NotiPop runs only on desktop with exit intent and a real Saturday to Sunday sale line. A mobile NotiPop runs only on mobile with a short free-shipping nudge when cart value is under your threshold. Shared shipping cutoff news stays in NotiFeed for both. Each campaign has its own attributed revenue.
Before (both devices): Welcome. Take 15 percent off your first order with code HELLO15. Free returns for 30 days. Shop new arrivals and bestsellers now.
After (desktop exit): Sale ends Sunday at midnight. Jackets ship free this weekend. Shop the sale.
After (mobile cart): You are $12 under free shipping. Add one more item.
Check results without mixing devices
Revenue is credited to clicks, never to views. A click on a product, collection or search link gives the shopper 6 hours to add products to the cart. Products added in that window count if the shopper orders them within 30 days in the same browser. Only those products count, not the whole order.
Call that figure attributed revenue. Do not claim lift. When a shopper clicks messages in two campaigns, the later click wins. Separate desktop and mobile campaigns make those totals easier to read.
Targeting is included on Free and on every plan. Campaign start and end scheduling needs a paid plan. Free still limits you to one active NotiFeed and one active NotiPop campaign, with one message each. Nothing shows on checkout or Shopify POS.
What this does not do
Device conditions do not detect restocks, form submissions or who is already on your email list. They do not replace your popup app, email platform or SMS platform. Atomato works alongside those tools and passes signups to the platform you already use.
Audience options stay limited to all shoppers, visitors who are not signed in, signed-in customers, chosen segments or chosen customers. Atomato does not target by location, browsing history or new versus returning visitors. For ad-only offers, use UTM targeting instead of guessing the device from the channel.
Next step
Pick one job that fails on one screen today. Split it into a desktop or mobile campaign, set the device condition, and leave shared news in the feed. When traffic mix shifts toward phones, each screen keeps a message that fits how shoppers actually browse.
Ready to show the right message to the right shopper?
Start showing targeted on-site messages without changing your marketing setup. Atomato works alongside the popup, email and SMS tools you already use.
Five-minute setup. No theme code or developer needed.
1


