> For the complete documentation index, see [llms.txt](https://help.citrusad.com/retail-media-interface/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.citrusad.com/retail-media-interface/platform-navigation/platform-notifications/email-notifications.md).

# Email notifications

Email notifications send campaign and wallet alerts to your inbox so your team stays informed when you're not in the platform. Each notification type has its own trigger, audience, and settings.

This page explains what each email covers. For the full overview of in-UI and email alerts, see [Platform Notifications](/retail-media-interface/platform-navigation/platform-notifications.md). For step-by-step setup, see [Managing email notifications](/retail-media-interface/advertiser-team-and-user-management/managing-email-notifications.md).

{% hint style="info" %}
Which notification types appear for your team depends on what your retailer has enabled. You may not see every type listed here.
{% endhint %}

### Overview

Email notifications are managed at the team level. You enable the types your team needs, set any thresholds or reminder frequencies, and choose who receives each alert.

There are two audiences:

* **Supplier / advertiser teams** can receive campaign approval, campaign rejection, and low wallet balance emails.
* **Master Retailer Teams** can receive campaigns pending review emails.

Emails include a link to the relevant page in the platform so you can act without hunting for the campaign or wallet.

### Prerequisites & availability

* **Where available:** **Settings → Teams → your team → Email Notifications**, when email notifications are enabled for your retailer.
* **Limitations:** Available notification types and options depend on your retailer's configuration.
* **Language:** Notification emails are sent in your namespace's default language — the same language rule used for user invite emails.

{% hint style="info" %}

## Retailers wanting to enable any email notifications can contact support.

{% endhint %}

### How to access email notifications

1. Go to **Settings → Teams**.
2. Select your team.
3. Open **Email Notifications**.
4. Enable the notification types you need, set any thresholds or frequencies, and manage recipients.

{% embed url="<https://epsilon.storylane.io/share/ykk73sz84jgy>" %}

### Email notification types

| Notification                 | Who receives it                       | When it sends                           | Configurable settings                              |
| ---------------------------- | ------------------------------------- | --------------------------------------- | -------------------------------------------------- |
| **Campaign approval**        | Supplier / advertiser team recipients | Once, when a campaign is approved       | On / off per team and per recipient                |
| **Campaign rejection**       | Supplier / advertiser team recipients | Once, when a campaign is rejected       | On / off per team and per recipient                |
| **Low wallet balance**       | Supplier / advertiser team recipients | When a wallet falls below the threshold | Threshold, reminder frequency, recipients          |
| **Campaigns pending review** | Master Retailer Team reviewer email   | When campaigns are pending review       | Reviewer email; frequency is configured by support |

#### **Campaign approval**

Sends when a retailer approves one of your team's campaigns.

* **Who it's for:** Supplier / advertiser teams.
* **When it sends:** Once per campaign approval. Approval and rejection emails are not sent for campaigns in archive or draft.
* **What to do next:** Use the link in the email to open the campaign in the platform.
* **Settings:** Turn the type on for the team, then choose which recipients get **Campaign approval**.

You will receive a notification each time a campaign is approved.

<figure><img src="https://19206235-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmxYbXHcdDvQ7toxAu8ql%2Fuploads%2FvWkAcBQNJQI4GvovRIXZ%2FCampaign%20approval%20-%20green.png?alt=media&amp;token=c4fa407d-a44b-43c1-9835-9e3a2373eb78" alt=""><figcaption></figcaption></figure>

#### **Campaign rejection**

Sends when a retailer rejects one of your team's campaigns, including the rejection reason where provided.

* **Who it's for:** Supplier / advertiser teams.
* **When it sends:** Once per campaign rejection. Approval and rejection emails are not sent for campaigns in archive or draft.
* **What to do next:** Use the link in the email to open the rejected campaign, review the reason, and update or resubmit as needed.
* **Settings:** Turn the type on for the team, then choose which recipients get **Campaign rejection**.

You will receive a notification each time a campaign is rejected.

{% hint style="info" %}
In the UI, rejected campaigns also appear from the notification bell as **Campaigns rejected**, linking to your campaigns filtered to rejected.
{% endhint %}

<figure><img src="https://19206235-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmxYbXHcdDvQ7toxAu8ql%2Fuploads%2FS7iYrUhl3F4UW40gyk5Q%2FCampaign%20rejection%20-%20green.png?alt=media&amp;token=5e7be83f-17fc-4ca1-9a76-2b0fd51f5801" alt=""><figcaption></figcaption></figure>

#### **Low wallet balance**

Sends when any wallet on the team falls below a balance you set, so you can top up before campaigns are disrupted.

* **Who it's for:** Supplier / advertiser teams.
* **When it sends:** When a wallet's available balance drops below the **Wallet balance threshold**. Reminders follow the **Notification frequency** you set (days or hours), based on when you first received the alert for that threshold breach.
* **What to do next:** Use the link in the email to open **Wallets**, then top up or ask your retailer to add funds.
* **Settings:**
  * **Wallet balance threshold** — amount below which the alert sends (currency is your retailer's default currency).
  * **Notification frequency** — how often to remind you while the wallet stays below the threshold (1–29 days, or 4–24 hours).
  * Recipients — team members or custom email addresses (for example a finance contact). If no recipients are set, notifications may fall back to the team's billing contact email where one exists.

{% hint style="info" %}
Low wallet balance alerts are based on available wallet balance. They do not use campaign or wallet daily budgets.
{% endhint %}

This email is separate from the in-UI **Wallet running low** and **Wallet out of balance** alerts on the bell, which show live counts while you're in the platform.

<figure><img src="https://19206235-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmxYbXHcdDvQ7toxAu8ql%2Fuploads%2F9QsCCk1RJBUI6pBy3HfH%2FLow%20wallet%20--%20green.png?alt=media&amp;token=d08018c5-7bf4-410c-b804-9bec39eab240" alt=""><figcaption></figcaption></figure>

#### **Campaigns pending review**

Sends when campaigns are pending retailer review, so reviewers can respond promptly.

* **Who it's for:** The Primary Retailer Team.
* **When it sends:** When campaigns are pending review. Support configures the notification frequency.
* **What to do next:** Use the link in the email to open **Reviews** and approve or reject pending campaigns.
* **Settings:** Contact support or your account manager to setup.

<figure><img src="https://19206235-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmxYbXHcdDvQ7toxAu8ql%2Fuploads%2Fv09tbZHvUwbFUb31MzQG%2FCampaigns%20pending%20-%20green.png?alt=media&amp;token=688955c0-bac6-488e-976a-dd1394f5c549" alt=""><figcaption></figcaption></figure>

#### Tips for success

* Turn on email for the alerts your team can't miss — especially campaign rejection and low wallet balance.
* Add a shared mailbox or finance contact for wallet alerts so the right people see them even if individuals change teams.
* Set a wallet threshold and reminder frequency that give you time to top up before spend stops.
* Open the link in the email to go straight to the campaign, wallet, or reviews screen.
* If a notification type is missing from **Email Notifications**, ask your retailer administrator — options match what they have enabled.

#### Troubleshooting & support

* **I'm not receiving emails I expect:** Confirm the notification type is enabled for the team, the recipient is listed with that type selected, and check spam or junk folders. Emails are sent from the platform notification address.
* **A notification type isn't shown:** Your retailer may not have enabled it. Ask your retailer administrator or account manager.
* **Low wallet emails keep repeating:** Check the **Notification frequency** on the team. Reminders continue while the wallet stays below the threshold.
* **Campaign approval or rejection didn't send:** Confirm the campaign wasn't in archive or draft, and that recipients are subscribed to that type.
* **Pending review emails aren't arriving:** Confirm the Master Retailer Team has an address in **Reviewer email**. If the field is blank, no email is sent.
* Still need help? Contact your account manager or <support@citrusad.com>

```
```


---

# 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 dynamically by asking a question.

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

```
GET https://help.citrusad.com/retail-media-interface/platform-navigation/platform-notifications/email-notifications.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.