Skip to content
Badgy Help

banners countdowns

Use banner content and variables

Learn how to use banner content and variables with a safe Juniper & Trail example, shopper impact, options, and recovery checks. Banner variables resolve from campaign context. Use only variables supplied by the selected discount and schedule, and verify the preview after changing either.

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

Use banner content and variables shown in the Badgy admin, with numbered callouts for the controls and verification points described below.
Annotated Juniper & Trail example

  1. Switch between banner design and storefront placement controls.

  2. Set the background style, color, opacity, and optional image.

  3. Enter and format banner content, text color, and responsive size.

  4. Inspect the live banner preview at desktop or mobile width.

  5. Save the banner after its preview and placement are verified.

  1. Enter Banner text, alternate messages, conveyor items, or slide content as supported.
  2. Insert only tokens provided by the selected discount/schedule, such as discount code/value or countdown context.
  3. Write surrounding copy that remains grammatical for the longest resolved value.
  4. Change discount route or timing, then revisit token warnings.
  5. Preview eligible and missing-value contexts before saving.

Banner variables resolve from campaign context. Use only variables supplied by the selected discount and schedule, and verify the preview after changing either.

Juniper & Trail example

Juniper & Trail uses use banner content and variables 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

Resolved SAVE 20% campaign copy with no raw token in the Juniper & Trail storefront, marked with one focused verification callout.
Annotated Juniper & Trail example

  1. Confirm the campaign announcement and Shop call to action at the top of the store.

  2. Check the badge and adjusted pricing on an eligible product card.

  3. Compare another product card to verify consistent campaign treatment.

Resolved SAVE 20% campaign copy with no raw token in the Juniper & Trail storefront, marked with one focused verification callout.
Annotated Juniper & Trail example

  1. Confirm the campaign announcement and Shop call to action fit the mobile header.

  2. Check that the badge remains readable on the mobile product card.

  3. 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 Use banner content and variables.
  • 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 | | --- | --- | --- | | Literal copy | Message never changes | Lowest context risk | | Discount tokens | Show code/amount/percentage | Route-dependent | | Timing context | Countdown or urgency | Must agree with campaign window | | Localized copy | Locale-specific message | Merchant maintains equivalence |

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.

Was this guide helpful?