> For the complete documentation index, see [llms.txt](https://docs.abtasty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abtasty.com/feature-experimentation-and-rollout/managing-campaigns-in-fe-and-r/campaign-scheduler.md).
# Campaign Scheduler
The Campaign Scheduler on Feature Experimentation & Rollout allows you to **automatically play or pause a campaign at a specific date and time**.
This feature helps you schedule activations or deactivations in advance, especially when working across different time zones or outside business hours. It ensures campaigns launch exactly when planned.
This feature is available for all campaign types.
### Campaign Scheduler activation
You can schedule campaigns to launch and/or pause at future dates from two areas:
#### 1. From the Campaign dashboard
On the **Feature Experimentation campaign dashboard**:
1. Click the **Campaign Status Button**.
2. Select **Schedule** **campaign** from the dropdown menu.
#### 2. From the Campaign creation flow
During campaign setups:
1. Click the **Campaign Status button** available in the top sidebar
2. Select **Schedule** **campaign** from the dropdown menu.
### Campaign Scheduler configuration
You can define a **start date**, a **stop date**, or both.
1. Enable the **Start date** and/or **Stop date** toggle.
2. Select the desired date and time.
3. Choose the appropriate **timezone**.
4. Click **Save**.
{% hint style="info" %}
If you only need to schedule a launch or pause (not both), enable only the relevant toggle.
{% endhint %}
Once configured, scheduled campaigns are identified in the dashboard with a **schedule icon** next to their status.
### Manual override
You can manually launch or pause a scheduled campaign anytime using the **Campaign Status Button.** This automatically removes the existing schedule.
### Notifications
If you want to be notified when a scheduled campaign starts or stops, you can configure:
* **Zapier integrations**
* **Webhooks**
These allow you to trigger automated workflows or internal notifications based on campaign status changes.
#### Example Use case
You are working in California and want to launch a campaign for Paris visitors on **December 24th at 10:00 PM (Paris time)**.
To schedule it:
1. From the dashboard, click the **Schedule** icon on your campaign.
2. Enable the **Start date** toggle.
3. Select **December 24th**.
4. Set the time to **10:00 PM**.
5. Choose the **Europe/Paris** timezone.
6. Click **Save**.
Your campaign will automatically activate at the selected time. No stop date is required unless you want to schedule one.
---
# 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://docs.abtasty.com/feature-experimentation-and-rollout/managing-campaigns-in-fe-and-r/campaign-scheduler.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.
