Skip to main content

Visibility & targeting controls

ShopGuide keeps visibility controls simple on purpose: device-level show/hide, a store-wide pause switch, and per-page-type launch content. There's no time-of-day, geographic, or behavioral-segment targeting, and no scroll or exit-intent triggers — worth knowing up front so you're not hunting for a setting that isn't there.

By device

In Settings: Hide on desktop removes the widget above the mobile breakpoint, Hide on mobile removes it below it. Both are plain booleans — there's no breakpoint picker, since the desktop/mobile split is fixed. See Mobile & desktop chat settings for the exact number and related controls.

Pausing the whole store

One toggle in the admin app — pause chat storefront-wide — disables the widget on every page without touching the theme block itself. Handy during maintenance, or any time you need chat off without going back into the theme editor.

Where content actually varies by page

The widget itself is visible wherever the ShopGuide Chat block is placed, subject to the device toggles above. What does change by page type is the opening message: a different launch message and buttons for the global default, for collection pages, and for product pages, plus a further override on any individual page's block. See Custom launch messages.

During an A/B test

If a test is running for your store, control-group visitors have the widget — bubble, comparison panel, notification bar, all of it — removed from the page entirely for the test's duration; the treatment group sees it as configured. See A/B testing.

What's genuinely not here

No business-hours or time-of-day scheduling. No geographic or customer-segment targeting. No exit-intent, scroll-depth, or cart-abandonment triggers for showing or hiding the widget — the idle-time Auto-Scroll behavior described in Custom launch messages triggers launch content, not visibility. And no per-URL allow/deny list beyond the product/collection/global split above.

If your mental model is "device visibility, a pause switch, and a launch message tuned to each page type," you've basically got the whole feature.

Next steps