Targeting and scheduling
Controlling which pages a drawer appears on, on which devices, and between which dates.
By default a drawer appears everywhere. Targeting narrows that, and every condition is optional.
Where it shows
Page type. Home, product, collection, cart, search, blog, and the rest. Choose the ones a drawer belongs on.
Specific URLs. Include or exclude paths, with * as a wildcard — /collections/sale* covers
everything under it. Useful when page type is too broad.
Device. Desktop or mobile. The split is the viewport being 749px or narrower, measured on the shopper’s screen rather than guessed from their browser, so a desktop window dragged narrow counts as mobile — which is the behavior you want, because it is what the layout is responding to.
When it shows
A schedule gives a drawer a start, an end, or both.
Dates and times are your store’s time zone. A drawer scheduled from Friday at 9am starts at 9am for your store, wherever the shopper is, and stays correct across daylight saving on both sides of the change.
A drawer outside its schedule is not hidden with CSS — it is not sent to the page at all.
When more than one drawer matches
Only one drawer shows per page view. Two competing for the same corner is a worse experience than either alone, so the app picks one.
The one highest in your Drawers list wins. Reorder the list to change the priority.
Two filters run, in sequence, and understanding the split explains what you will see when you test:
- On the server, as your page is built, the app narrows your drawers to those whose page and URL conditions match. If none match, nothing is sent to the page — no markup, no script, no stylesheet.
- In the browser, where the viewport is finally known, device and schedule conditions are applied to what survived. The first one that passes is the one that renders.
So a drawer targeted at mobile still reaches a desktop page as a candidate, and is then declined there. That is correct: the page is often cached and cannot know the viewport, and the alternative is a drawer that is wrong for half your visitors.
What is not here yet
Targeting by customer state, visitor type, sales channel or country is designed and specified but not built, so it is not offered in the editor. A control for a setting that silently does nothing costs more trust than a missing feature does.