> For the complete documentation index, see [llms.txt](https://help.openloyalty.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.openloyalty.io/campaigns/campaigns/automation-campaigns.md).

# Automation Campaigns

In this section, you will learn about Automation Campaigns.

## What are Automation Campaigns?

**Automation Campaigns** (formerly known as time-based campaigns) let you schedule loyalty initiatives to run automatically - triggered by a date or a recurring schedule - without manual intervention.

{% hint style="info" %}
**Automation Campaigns** run after midnight according to the timezone configured for the tenant.
{% endhint %}

{% hint style="info" %}
**Built for scale**

* Each run prepares and dispatches its audience in parallel, so an automation can reach a member base of millions in a single nightly run.
* Only **active** automation campaigns count towards your tenant's limit of automation campaigns, and the limit is checked when you activate one. Inactive automation campaigns don't count.
  {% endhint %}

***

### 🚀 What Automation Campaigns Do

They’re designed to automatically reward members at key times:

* **Triggers** include recurring schedules (daily, weekly, monthly), birthdays, and membership anniversaries.
* **Rules** specify conditions (member segment, tier, custom attributes, **days since registration**) and effects (awarding points, coupons, balance adjustments).
* **Limits & Budgets** control how many rewards can be issued overall or per member.
* **Visibility & Status** settings decide who sees the campaign and when it becomes active.

***

### 🎯 Summary Table

<figure><img src="https://2658975168-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNVX03KZzmrGwJihLiEx%2Fuploads%2Fgit-blob-fc0df752e8a962d0ce0dc5ab587e6f536e12cfde%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

| Trigger Type    | Fires On                            | Audience Options                                       | Common Use Cases                                            |
| --------------- | ----------------------------------- | ------------------------------------------------------ | ----------------------------------------------------------- |
| **Daily**       | Every day at 00:00                  | <p>Everyone / Segment / Tier<br>Rule-based filters</p> | Streak rewards; tenure milestones (30/60/90 days, 365 days) |
| **Weekly**      | Chosen weekday(s) at 00:00          | Same as above                                          | Weekend promotions, weekly gifts                            |
| **Monthly**     | Chosen date(s) or last day at 00:00 | Same as above                                          | Subscription reminders, updates                             |
| **Birthday**    | Member birth date                   | Same as above                                          | Birthday bonuses, celebratory perks                         |
| **Anniversary** | Membership signup date              | Same as above                                          | Loyalty anniversary bonuses                                 |

Additional filters can be applied in Rule Conditions—even if not selectable at the audience level.

***

### ✅ Best Practices

* **Schedule thoughtfully**: Use appropriate frequency and timing (e.g. birthdays vs monthly).
* **Segment wisely**: Target specific audiences to increase relevance.
* **Rate-control your rewards**: Set sensible per-member and total limits before launching.
* **Monitor engagement**: Use dashboard analytics to identify spikes or drops.
* **Iterate using duplicates**: Copy campaigns for A/B testing.
* **Clean responsibly**: Deactivate and export before deleting, ensuring historical reward data remains accurate.

***

## Learn more about

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Creating Automations</strong></td><td><a href="/campaigns/campaigns/automation-campaigns/creating-automations.md">Creating Automations</a></td></tr><tr><td><strong>Managing Automations</strong></td><td><a href="/campaigns/campaigns/automation-campaigns/managing-automations.md">Managing Automations</a></td></tr><tr><td><strong>Deleting Automations</strong></td><td><a href="/campaigns/campaigns/automation-campaigns/deleting-automations.md">Deleting Automations</a></td></tr></tbody></table>


---

# 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://help.openloyalty.io/campaigns/campaigns/automation-campaigns.md?ask=<question>&goal=<user_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.