campaign fundamentals

Choose what a campaign changes

Learn how to choose what a campaign changes with a safe Juniper & Trail example, shopper impact, options, and recovery checks. Campaign capabilities decide which wizard configuration and activation phases apply. Enable only the discount, badge, banner, or related storefront behavior required by the promotion brief.

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

Open full size ↗

1. 1

   Name and describe the campaign so teammates can identify its purpose.

2. 2

   Choose whether the campaign runs once or repeats on a schedule.

3. 3

   Set when the campaign should begin.

4. 4

   Choose whether the campaign ends automatically or stays open.

5. 5

   Save the basics and continue to the next wizard step.

1. Write the promotion outcome before opening the wizard.
2. Enable discount capability only when price or cart behavior must change.
3. Enable badge capability for product-media labels and banner capability for page-level messaging.
4. Remove capabilities that have no shopper requirement so their steps do not add configuration risk.
5. Continue through Review and confirm every enabled capability has a valid preview.

Campaign capabilities decide which wizard configuration and activation phases apply. Enable only the discount, badge, banner, or related storefront behavior required by the promotion brief.

Juniper & Trail example

Juniper & Trail prepares a Weekend Trail Kit campaign for packs, drinkware, and camp accessories. The team uses choose what a campaign changes 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 Choose what a campaign changes.
• 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

• Understand the campaign wizard

Options reference

| Option | Use it when | Consequence | | --- | --- | --- | | Discount | Change price or cart calculation | Requires product eligibility and revert planning | | Badge | Overlay product media | Requires theme rendering and slot choice | | Banner | Show page-level campaign messaging | Requires embed, targeting, and mobile review | | Combined | Coordinate offer and messaging | Every enabled phase must activate |

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.