> For the complete documentation index, see [llms.txt](https://docs.avada.io/cookie-help-center/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avada.io/cookie-help-center/settings/customize-notification-email-to-store-owner.md).
# Customize notification email to Store owner
**Requires:** Advanced plan
***
### Step 1: Navigate to Email Content Settings
Open the Avada Cookie Consent app. Go to **Settings** page and scroll to the **Email content** section.
### Step 2: Select "Send to store owner"
In the **Email content** card, locate the dropdown filter at the top-right corner. By default, it shows **Send to customer**.
* Click the dropdown
* Select **Send to store owner**
The email list updates to show 5 store owner notification templates.
### Step 3: Choose an Email Template to Customize
The 5 available store owner emails are:
| Email | When it is sent |
| ----------------------------- | ------------------------------------------------------- |
| **Export customer's profile** | A customer requests to export their account information |
| **Edit customer's profile** | A customer requests to edit their account information |
| **Delete customer's profile** | A customer requests to delete their account information |
| **Data sales opt-out** | A customer opts out of data sales |
| **Manage customer's request** | A customer requests to export all of their data |
* Click on the email template you want to customize
### Step 4: Edit Email Content
On the email detail page, you can customize the email body using the rich text editor.
* Edit the greeting, body text, button text, or footer as needed
* The **Preview** section below the editor updates automatically as you type
* Supported variables: `{{email_name}}` (customer's email), `{{shop_name}}` (your store name)
By default, each email includes a **Review request** button that links directly to your **Data requests** log in the app.
### Step 5: Send a Test Email
Before saving, you can send a test email to verify how it looks.
* Click **Send test** in the top-right corner of the page
* A confirmation modal appears showing the recipient (your shop email)
* Click **Send** to deliver the test email
### Step 6: Save Your Changes
* Click **Save** on the save bar at the top of the page
* A "Setting updated" confirmation appears
To undo your edits, click **Discard** instead.
> **Note:** If you navigate away without saving, a confirmation dialog will ask you to save or discard your changes.
***
### How It Works
Store owner emails are triggered **after** a customer completes their data request:
1. The customer submits a request on your Privacy/Compliance page
2. The customer receives a confirmation email and clicks the verification link
3. The request is processed by Avada Cookie Consent
4. You receive a notification email with a **Review request** button
The **Review request** button takes you directly to **Consent Activities > Data Requests** in the app.
***
And there you have it! You've successfully set up store owner email notifications. From now on, you'll receive an automatic email whenever a customer's data request is processed.
If you have any questions or run into any issues, don't hesitate to reach out. We're here to help!
---
# 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://docs.avada.io/cookie-help-center/settings/customize-notification-email-to-store-owner.md?ask=&goal=
```
`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.