campaign operations
Launch a campaign safely
Learn how to launch a campaign safely with a safe Juniper & Trail example, shopper impact, options, and recovery checks. Launch validates the draft, freezes the intended inputs, and queues background activation phases. One launch command is enough; monitor phase progress and do not create a duplicate campaign to work around a slow job.
Before you begin
- Review campaign completeness and product preview
- Confirm authorization and theme status
- Know the restore consequences of the chosen discount route
Confirm the shop, current status, and intended consequence before changing anything. Use read-only status, preview, or history evidence first.
Step-by-step setup

Use the summary cards to check live, scheduled, and sale-product totals.
Inspect the active campaign and use its view, edit, revert, or end actions.
Check theme embed, badge, banner, background-job, and countdown health.
Search and filter past campaigns before opening their records.
- Open the campaign Review page for the intended shop and confirm the current record and status.
- Resolve completeness, product-preview, token, entitlement, authorization, and overlap findings, then choose Launch once.
- Read the inline summary, warning, or preflight before submitting; do not repeat a command while background work is running.
- Watch activation phases until status is Active or a classified failure appears.
- Confirm the resulting status and History/audit evidence, then spot-check Shopify or the storefront when the action has external effects.
Launch validates the draft, freezes the intended inputs, and queues background activation phases. One launch command is enough; monitor phase progress and do not create a duplicate campaign to work around a slow job.
Juniper & Trail example
Juniper & Trail uses launch a campaign safely on its controlled Weekend Trail Kit campaign, then checks phase status, History, and two representative storefront products. 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

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.
During activation or revert, storefront components can settle at different moments; use status rather than repeated clicks to determine completion. 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 Launch a campaign safely.
- 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 | | --- | --- | --- | | Launch | Queue one activation | Background phases apply the campaign | | Blocking finding | Configuration is invalid | Return to named wizard step | | Warning | Valid but consequential setup | Understand before launch |
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.