settings
Configure campaign notifications
Learn how to configure campaign notifications with a safe Juniper & Trail example, shopper impact, options, and recovery checks. Choose which campaign lifecycle notices are useful and keep destinations current. Notifications report operations; they do not replace History as the authoritative execution record.
Before you begin
- Shop-owner or authorized staff access
- A record of the current setting
- A plan for how the change affects scheduled campaigns
Confirm the shop, current status, and intended consequence before changing anything. Use read-only status, preview, or history evidence first.
Step-by-step setup
Check the current plan before configuring plan-dependent settings.
Set and save the default timezone used when creating campaigns.
Review Shopify Markets synchronization availability and its plan requirement.
Name and upload an approved custom font for storefront campaign components.
- Open Settings → Notifications for the intended shop and confirm the current record and status.
- Set the effective recipient override, then enable/disable Failures, Lifecycle, and Reminders; turning Failures off requires the warning confirmation.
- Read the inline summary, warning, or preflight before submitting; do not repeat a command while background work is running.
- Save the recipient and confirm the success state; notification email does not replace History as execution evidence.
- Confirm the resulting status and History/audit evidence, then spot-check Shopify or the storefront when the action has external effects.
Choose which campaign lifecycle notices are useful and keep destinations current. Notifications report operations; they do not replace History as the authoritative execution record.
Juniper & Trail example
Juniper & Trail records the current value, applies configure campaign notifications, and verifies a draft preview before relying on the change for its next campaign. 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
Some settings affect only admin presentation; storefront-facing settings should be checked in every supported locale and market. 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 Configure campaign notifications.
- 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 | | --- | --- | --- | | Failures | Operational problems/parked recovery | Opt-out requires confirmation | | Lifecycle | Campaign state changes | Immediate toggle save | | Reminders | Upcoming campaign reminders | Immediate toggle save | | Recipient override | Send somewhere other than owner email | Blank follows captured owner |
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.