> For the complete documentation index, see [llms.txt](https://kbase.whitelabel-loyalty.com/product/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kbase.whitelabel-loyalty.com/product/loyalty-engine/campaigns/managing-campaigns.md). # Managing Campaigns Learn how to manage the lifecycle of your campaigns — including status changes, editing, cloning, and archiving. Every campaign has a status that determines its current state. Status is set at the campaign level and cascades to everything inside it — pausing or ending a campaign applies to all of its reactors and missions together. Individual reactors and missions don't have their own separate status. Campaigns follow this lifecycle: | Status | Meaning | | ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Draft** | Created but not active. You can configure reactors or missions, edit settings, and prepare the campaign before activation. | | **Active** | Live. Rule Based campaigns are processing events and firing reactions; Goal Based campaigns are tracking user progress. | | **Paused** | Temporarily suspended. No events are processed and no progress is tracked. Can be reactivated. Pausing stops execution only; it does not re-enable structural editing (adding or removing reactors and missions still requires a Draft campaign). | | **Ended** | The campaign has ended, either because you set it to Ended manually or because its end date has passed. Manual ending takes effect immediately; end-date ending is applied by a scheduled daily process (see End dates). An ended campaign no longer processes events or tracks progress, and cannot be reactivated. | | **Archived** | Permanently deactivated. Cannot be reactivated. Use for campaigns that have finished or are no longer needed. | ![](https://1999217057-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEFmrMvu6tg0ZiSX9SGEq%2Fuploads%2FiwyBPxGdS8JhNjkqJfhg%2FSCR-20260828-lklq.png?alt=media\&token=1034a544-3664-40b2-a68d-17b4ecb94575) **Status transitions** * You activate a campaign by changing its status to **Active** once you've finished configuring it. * You can change an active campaign's status to **Paused** (temporary) or **Archived** (permanent). * You can change a paused campaign's status back to **Active**, or to **Archived**. * A campaign becomes **Ended** when you end it manually, or automatically after its end date passes. Automatic ending runs on a daily schedule rather than the instant the date passes — see [End dates](#end-dates). An ended campaign can be archived or cloned, but not reactivated. * **Archived** campaigns cannot be reactivated — use the clone function if you need to recreate one. *** #### Editing a campaign **Campaign settings** You can edit a campaign's name, description, picture, start date, end date, and visibility criteria while it is in **Draft**, **Active**, or **Paused** status. * The **start date** can only be modified before the campaign becomes active. * The **end date** can be extended or shortened on an active campaign. * The **campaign type** can only be set while the campaign is in Draft. It cannot be changed once the campaign has been activated. **Adding or removing reactors and missions** Reactors and missions can only be added or deleted while a campaign is in **Draft** status. Once a campaign has been activated, its mission and reactor structure is locked — this is intentional, because campaigns and missions are live shared records rather than per-participant snapshots, so adding or removing them after activation could cascade through the mission hierarchy and affect progress already underway. Pausing a campaign stops execution, but it does **not** return the campaign to an editable Draft state. You cannot add or remove reactors or missions on a paused campaign. If you need to change the structure of a live campaign, clone it instead. The clone is created in Draft status, where you can freely modify its reactors and missions before activating. **Editing** [**reactors**](/product/loyalty-engine/campaigns/rule-based-campaigns/reactors.md) **(Rule Based campaigns)** Reactors follow the same model as missions. An existing reactor's configuration — its conditions, reaction, and reward — can be edited while the campaign is Active or Paused. You can't add, remove, or reorder reactors once the campaign is published; that's Draft-only. To change which reactors a live campaign contains, clone the campaign and publish the amended draft. **Editing** [**missions**](/product/loyalty-engine/campaigns/goal-based-campaigns/missions.md) **(Goal Based campaigns)** The logic inside an existing mission stays editable after a campaign goes live. You can change its completion condition, its conditions, and its reaction/reward while the campaign is Active or Paused, and existing missions remain editable even once the campaign has Ended. What you can't change once a campaign is published is its structure: you can't add missions, remove them, reorder them, or switch a group between parallel and sequential. Structure is fixed in Draft. The campaign type (Goal Based or Rule Based) is also fixed at creation and can't be switched later. For Goal Based campaigns, the campaign-level completion reaction can still be added or edited while the campaign is active. To restructure a live campaign, clone it, make the structural changes on the draft copy, and publish the clone. {% hint style="warning" %} **Editing a live campaign: what to check first** Editing a reactor or mission on a live campaign is allowed and non-destructive — it never deletes a user's history. It does change how that history is counted, so review the effect before you save. * **Reactors** — the participation list reflects historical events that match the reactor's current conditions. Tightening the conditions removes participants whose earlier events no longer qualify; loosening or reverting them brings those participants back. Their history isn't lost — it's re-filtered against the live configuration. * **Missions** — changing a completion condition re-evaluates each user's existing progress against the new target. Raising a target can return a completed user to "in progress" (a finished mission may re-show as, for example, 2/10); lowering it below a user's current progress can mark them complete, but will not report a `MISSION_COMPLETED` event. * **Missions with a cooldown** — if users have already completed the mission, take extra care: a qualifying event after your edit may begin a fresh cooldown cycle rather than continue the previous one. Check the completion and cooldown state of in-progress users first. When you want to protect members already in progress, make the change on a cloned draft and publish the clone instead of editing the live campaign. {% endhint %} *** #### Cloning a campaign You can clone any campaign to create a copy with the same configuration. The cloned campaign is created in **Draft** status, so you can modify it before activation. ![](https://1999217057-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEFmrMvu6tg0ZiSX9SGEq%2Fuploads%2FZlGwaxJGE8ii4dyTRAcu%2FSCR-20260828-mbwd.jpeg?alt=media\&token=25302478-1b44-44c8-b4e9-4374aa9689fc) Cloning is useful for: * Running a recurring promotion with updated dates * Creating variations of an existing campaign for different audiences * Recovering a previous configuration after editing *** #### Pausing a campaign Pausing a campaign temporarily suspends all activity across every reactor and mission it contains: * **Rule Based campaigns** — reactors stop processing events. Events reported while paused are not retroactively processed when the campaign is reactivated. * **Goal Based campaigns** — mission progress tracking is suspended. Events reported while paused do not count toward progress. When reactivated, the campaign resumes from its current state. *** #### Archiving a campaign Archiving permanently deactivates a campaign. Archived campaigns: * Cannot be reactivated * Remain visible in the campaign list for reference * Retain all historical data (activation history, mission progress) If you need to run a similar campaign in the future, use the clone function to create a new copy from the archived campaign. *** #### End dates A campaign stops running when you end it manually or when its configured end date passes. Once the end date passes, the campaign stops processing events and tracking progress straight away — even if its status still shows Active. Campaigns are automatically moved to the Ended status on a schedule. A background process runs once a day, in the early hours (around 1:00 AM in your tenant’s timezone), and sets every campaign whose end date has passed to Ended. So a campaign whose end date passes during the day keeps its Active label until that night’s run — but it has already stopped tracking events from the moment the end date passed. The status catches up overnight; event processing stops at the end date itself. The end date is evaluated against the timezone configured for your tenant. Ended campaigns cannot be reactivated. To run a similar campaign again, clone it — the copy is created in Draft status with a new schedule. You can archive an ended campaign to keep your campaign list clean, or leave it in place for historical reference. *** #### FAQs **Can I pause or archive a single mission or reactor without affecting the rest?** No. Status is managed at the campaign level and applies to all of its reactors and missions together. If you need a mission or rule to have its own lifecycle, put it in its own campaign. **Can I reactivate an archived or ended campaign?** No. Archived and ended campaigns cannot be reactivated. Clone the campaign to create a new copy if needed. **Can I add a reactor or mission to an active campaign?** No. Reactors and missions can only be added or removed while a campaign is in **Draft** status. Pausing an active campaign stops execution but does not unlock structural editing, so you can't use Pause as a way to add content. If you need a different structure, clone the campaign — the copy is created in Draft, where you can add or remove reactors and missions before activating it. **What happens to user progress when a Goal Based campaign is paused?** Progress is preserved but frozen. No new progress is recorded while paused. When reactivated, tracking resumes from where it left off. **What happens to events reported while a campaign is paused?** Events reported while a campaign is paused are not processed by that campaign and are not retroactively applied when the campaign is reactivated. **My campaign shows Active — is it tracking events?** Not necessarily. A campaign only processes events and tracks progress while the current time falls within its scheduled window — on or after its start date and before its end date. Outside that window it isn’t tracking, even if its status still shows Active: * Before the start date, a published campaign is waiting to begin. It won’t track events until its start date arrives. * After the end date, a campaign stops tracking straight away, but its status only changes to Ended overnight, when the daily process runs (around 1:00 AM in your tenant’s timezone). So it can show Active while no longer tracking anything. An Active status alone doesn’t confirm a campaign is live — check that today’s date sits between its start and end dates. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://kbase.whitelabel-loyalty.com/product/loyalty-engine/campaigns/managing-campaigns.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.