calendar history

Use the campaign calendar

Learn how to use the campaign calendar with a safe Juniper & Trail example, shopper impact, options, and recovery checks. Calendar shows campaign timing in the shop context. Use it to find collisions and open the underlying campaign; do not infer successful activation from a calendar block alone.

Before you begin

• Open the correct shop and campaign
• Know the campaign's discount route
• Do not overwrite a legitimate newer merchant edit without review

Confirm the shop, current status, and intended consequence before changing anything. Use read-only status, preview, or history evidence first.

Step-by-step setup

Open full size ↗

1. 1

   Move between dates or return to today.

2. 2

   Switch between month and week views or create a campaign.

3. 3

   Select a calendar occurrence to inspect its campaign timing.

4. 4

   Use the legend to distinguish active, scheduled, completed, failed, and projected occurrences.

1. Open Campaign calendar for the intended shop and confirm the current record and status.
2. Switch month/week view, inspect campaign blocks and conflicts, and open the underlying campaign for operational status.
3. Read the inline summary, warning, or preflight before submitting; do not repeat a command while background work is running.
4. Check shop-local dates and do not treat calendar placement as proof of successful activation.
5. Confirm the resulting status and History/audit evidence, then spot-check Shopify or the storefront when the action has external effects.

Calendar shows campaign timing in the shop context. Use it to find collisions and open the underlying campaign; do not infer successful activation from a calendar block alone.

Juniper & Trail example

Juniper & Trail uses use the campaign calendar to inspect the Weekend Trail Kit occurrence and compares the recorded snapshot with the current Shopify value before any recovery action. 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

History itself is not shopper-facing, but restore choices determine whether current storefront prices and campaign elements change. 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 the campaign calendar.
• 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

• Review campaign sessions

Options reference

| Option | Use it when | Consequence | | --- | --- | --- | | Month | Plan broad schedule | Compact campaign windows | | Week | Inspect timing detail | Better overlap resolution | | Campaign block | Open source record | Status remains authoritative |

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.