# 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="warning" %}
**Performance limitations**

* **Automation Campaigns** can be triggered for audiences equal to or lower than 200,000 (limit does not apply to Birthday Campaigns and Membership Anniversary Campaigns).&#x20;
* The maximum number of **Automation Campaigns** is 4 (active and inactive) in the loyalty program (in one tenant).
  {% 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) 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="/files/j4j7OCe7DadLovaShqPq" 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 for active members   |
| **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="/pages/X7y3Jfl1upf29W8EO08D">/pages/X7y3Jfl1upf29W8EO08D</a></td></tr><tr><td><strong>Managing Automations</strong></td><td><a href="/pages/FN9tYubBmM5jXCsKIrwx">/pages/FN9tYubBmM5jXCsKIrwx</a></td></tr><tr><td><strong>Deleting Automations</strong></td><td><a href="/pages/KGv5b5ZpUJfa5iKV31Ch">/pages/KGv5b5ZpUJfa5iKV31Ch</a></td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.openloyalty.io/main-features/campaigns/automation-campaigns.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
