banners countdowns

Troubleshoot storefront banners

Learn how to troubleshoot storefront banners with a safe Juniper & Trail example, shopper impact, options, and recovery checks. Confirm the app embed, active campaign, attached banner, page targeting, visibility window, locale, and theme placement. Test without admin cookies before treating a cached preview as a rendering failure.

Before you begin

Enable the Badgy theme app embed
Write concise campaign copy and a valid destination
Plan mobile and desktop evidence

Keep the campaign in Draft while you verify the configuration. Use a private storefront window where the guide changes shopper-facing behavior.

Step-by-step setup

Troubleshoot storefront banners shown in the Badgy admin, with numbered callouts for the controls and verification points described below. — Annotated Juniper & Trail example

Switch between banner design and storefront placement controls.
Set the background style, color, opacity, and optional image.
Enter and format banner content, text color, and responsive size.
Inspect the live banner preview at desktop or mobile width.
Save the banner after its preview and placement are verified.

Confirm saved banner Is active and attached campaign is Active.
Confirm Badgy embed/placement and test without admin cookies.
Check page type/specific URL, locale, Market, start/end window, and close-button dismissal state.
For Countdown, verify target and expired behavior; for motion types, inspect message/item configuration.
Check theme header overlap, cache, and mobile crop before escalating with campaign/banner IDs.

Confirm the app embed, active campaign, attached banner, page targeting, visibility window, locale, and theme placement. Test without admin cookies before treating a cached preview as a rendering failure.

Juniper & Trail example

Juniper & Trail uses troubleshoot storefront banners for its Weekend Trail Kit offer. Copy is tested at desktop and mobile widths on an included home page and a direct product page. The documentation fixture uses realistic products, inventory states, variants, collections, and protected exclusions so the preview exercises the same decisions as a merchant catalog.

What shoppers will see

Collection-targeted message on its eligible collection in the Juniper & Trail storefront, marked with one focused verification callout. — Annotated Juniper & Trail example

Confirm the campaign announcement and Shop call to action at the top of the store.
Check the badge and adjusted pricing on an eligible product card.
Compare another product card to verify consistent campaign treatment.

Confirm the campaign announcement and Shop call to action fit the mobile header.
Check that the badge remains readable on the mobile product card.
Scroll through additional products to verify the collection layout stays usable.

The banner renders only on eligible pages while its campaign and visibility rules allow it; the mobile layout may stack content that is inline on desktop. Check the relevant result from product through cart where applicable. For shopper-facing work, compare desktop and mobile and verify both an eligible and an ineligible item.

Common mistakes and troubleshooting

Acting on the wrong shop. Confirm the Shopify store and campaign before following Troubleshoot storefront banners.
Trusting a stale preview. Refresh after catalog, schedule, discount, theme, locale, or market changes.
Repeating a background command. Read status and History first; retry only when Badgy presents a recoverable failure.
Checking only one viewport. Verify desktop and mobile in a private storefront window.

If the status reports revoked authorization, reconnect Shopify before retrying. If the result still differs from the preview, preserve the campaign ID and approximate time, then open support from this identified shop. Never send customer data, access tokens, or full catalog exports in feedback.

Options reference

| Option | Use it when | Consequence | | --- | --- | --- | | Missing everywhere | Embed, active state, campaign context | Global issue | | Missing on one page | Targeting/URL/locale | Eligibility issue | | Wrong content | Variables/translations | Context issue | | Layout overlap | Position/sticky/height/theme | Integration issue |

Badgy behavior in this guide is reviewed against the repository's shipped UI, service rules, and feature design documents. Shopify-owned theme, Markets, Flow, billing, and discount behavior can also depend on the store's Shopify configuration; consult the Shopify Help Center for that platform configuration.