campaign fundamentals
Review and launch a campaign
Learn how to review and launch a campaign with a safe Juniper & Trail example, shopper impact, options, and recovery checks. Review checks completeness, resolved products, offer calculations, shopper-facing previews, and token compatibility. Resolve every blocking issue and understand warnings before using Launch.
Before you begin
- Decide the offer goal and the storefront components it needs
- Know which products may change
- Confirm who may launch or delete campaigns
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
Review campaign identity, timing, and timezone; use Edit to correct them.
Confirm the product rule and matching product count.
Check the final banner and badge customer preview.
Verify the selected badge appearance on product cards.
- Open Review after every preceding step is saved.
- Check Basics timing in the shop timezone and the chosen end behavior.
- Check the discount calculation and resolved product/variant count.
- Check badge and banner previews plus token compatibility warnings.
- Resolve every blocker, acknowledge relevant warnings, choose Launch once, and monitor phases.
Review checks completeness, resolved products, offer calculations, shopper-facing previews, and token compatibility. Resolve every blocking issue and understand warnings before using Launch.
Juniper & Trail example
Juniper & Trail prepares a Weekend Trail Kit campaign for packs, drinkware, and camp accessories. The team uses review and launch a campaign while keeping the campaign in Draft until review is complete. 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
Shoppers see only the capabilities you enabled, and only after activation completes for those phases. 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 Review and launch a campaign.
- 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.
- Skipping the consequence check. Confirm what changes for shoppers and what the end or restore path will do.
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.
Related guides
Options reference
| Option | Use it when | Consequence | | --- | --- | --- | | Blocking issue | Required data is missing or invalid | Return to the named step | | Warning | Configuration is valid but risky or surprising | Understand before launch | | Save draft | Defer storefront changes | Safe for review | | Launch | Queue activation | Do not click repeatedly |
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.