> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/what-would-you-like-to-learn-about/advocate-program/advocate-program-settings/date-based-actions-in-advocate-program-rules-explained.md).

# Date-Based Actions in Advocate Program Rules Explained

Date-based actions let a single program rule apply different actions depending on when referral activity happens. For example, you can reward purchases made during a promotional period with a different action than purchases made at any other time.

To enable date-based actions while you create a rule, or when you edit an existing rule, see [Set Up Program Rules in Advocate](https://help.impact.com/brand/what-would-you-like-to-learn-about/advocate-program/getting-started-with-advocate/advocate-program-rules-explained.md).

## How date-based actions work

A rule's trigger and conditions determine whether the rule fires. Date-based actions don't schedule the rule or change its trigger.

When the rule fires, impact.com compares a selected referral or activity date with the date range of each action on the rule:

* If the selected date falls within an action's date range, that action applies.
* When you enable date-based actions, the rule's existing actions without a date range become default actions. If the selected date doesn't fall within any action's date range, the default action applies.

{% hint style="success" %}
**Note:** An action's date range limits when the action applies, not when the rule can trigger. A rule still fires whenever its trigger and conditions are met.
{% endhint %}

Date-based actions are different from the *Time* rule condition. A *Time* condition decides whether the rule triggers at all. Date-based actions determine which action applies after the rule triggers.

## Which date can I evaluate?

The dates you can choose when configuring date-based actions depend on the rule's trigger.

| Rule trigger                          | Dates you can evaluate                                                         |
| ------------------------------------- | ------------------------------------------------------------------------------ |
| Referral starts                       | Referral start date                                                            |
| Friend makes a purchase               | Referral start date, referral conversion date, or purchase date                |
| Friend performs an action             | Referral start date, referral conversion date, or action date                  |
| Friend's segment and/or field changes | Referral start date, referral conversion date, or field or segment change date |

{% hint style="warning" %}
**Important:** A rule can have only one default action for the advocate and one for the friend. If a rule ends up with more than one default action for the same side, remove or change the extras. The *Review* screen shows a validation error until you do.
{% endhint %}

## Example

A rule has the trigger *Friend makes a purchase*, with *Purchase date* as the date-based trigger. The dates and action names are for illustration only.

| Action                                                 | Date range                | Applies when the friend's purchase date is… |
| ------------------------------------------------------ | ------------------------- | ------------------------------------------- |
| Holiday promotion (Reward and Email)                   | December 1 to December 31 | Between December 1 and December 31          |
| Standard reward (Reward and Email), the default action | None                      | Any other date                              |

Purchases made during the promotional period use the promotional action. Purchases made at any other time use the default action. This applies to both new and existing rules:

* **New rule:** You add the promotional action, with its date range, and the default action when you create the rule.
* **Existing rule:** The rule's original action, which has no date range, becomes the default action when you enable date-based actions. You then add the promotional action with its date range.


---

# 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.impact.com/brand/what-would-you-like-to-learn-about/advocate-program/advocate-program-settings/date-based-actions-in-advocate-program-rules-explained.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.
