Overview

The Keyword Performance Email Notification automates the process of monitoring keyword performance, eliminating the need for manual report creation. With this feature, you can proactively identify underperforming or improving keywords based on key performance metrics in Conversion Tracking Summaryreport. By setting up automated alerts, you can respond quickly to changes, optimize performance, and ensure your search experience remains effective.

Notification Details

Trigger

Email notifications are triggered when the system evaluates keyword performance based on user-defined conditions at scheduled intervals. If any keyword meets or exceeds the defined condition, a notification is sent.

Configuration

1. Name / Subject: Define the email notification's name or subject line for easy identification.
2. Notification Type: Keyword Performance
3. Recipients: Enter the email addresses of individuals who should receive the notification.
4. Target Keywords: Keywords that you want to montior for performance change. You can monitor mulitple keywords under one notification configuration. The system evaluates each keyword independently if it meets the trigger conditions.
   1. Note: The default limit for Target Keywords is 50 to ensure optimal system performance; for additional keywords, please contact our CSD team for assistance.
5. Performance Metrics: Choose the metric you would like to monitor for the target keywords.
   1. Count - the number of times the keyword was used
   2. /# of Orders - the number of orders placed in the same session as the keyword was searched
   3. Total [$] - total amount of all the orders placed in sessions when the keyword was searched
   4. Avg. Order [$] - Total[$] divided by # of Orders - reflects the average order amount assigned to the keyword
   5. Conversion [%] - # of Orders divided by Count - reflects the percent of sessions that resulted in a sale when searching the keyword
6. Trigger Conditions: Set the condition that will trigger the notification. Each trigger condition type defines how the system evaluates keyword performance changes.
   1. Absolute Change: Triggers when the performance metric changes by a specified absolute value or more. Use this when you want to track a specific numeric increase or decrease. Example:
      1. Condition: "Avg. Order [$] increases by $50".
      2. If Avg. Order Value increases from $200 to $260 → Triggered.
   2. Percentage Change: Triggers when the performance metric changes by a specified percentage or more. Use this to identify relative performance changes in percentage terms. Example:
      1. Condition: "Avg. Order [$] decreases by 10%".
      2. If Avg. Order Value drops from $200 to $170 → Triggered.
   3. Threshold: Triggers when the performance metric is above, below, or at a specified value. Use this to set specific thresholds for performance benchmarks. Example:
      1. Condition: "Avg. Order [$] is below or at $150".
      2. If Avg. Order Value is $140 → Triggered.
7. Analysis Window: Specifies the historical period to analyze for keyword performance changes. This is to ensure accurate comparisons between timeframes to evaluate changes in performance.
   1. For Absolute Change and Percentage Change trigger condition type:
      1. The system compares the current analysis window against the previous equivalent window to detect changes. Example:
         1. Condition: "Avg. Order [$] increases by $50".
         2. Analysis Window: 2 months.
         3. Current Period: March–April → Avg. Order: $250
         4. Previous Period: January–February → Avg. Order: $190
         5. Result: Increase of $60 → Triggered.
   2. For Threshold trigger condition type:
      1. The system evaluates keyword performance within the current analysis window only to check if it meets the specified threshold. Example:
         1. Condition: "Avg. Order [$] is below or at $200".
         2. Analysis Window: 2 months.
         3. Current Period: March–April → Avg. Order: $180
         4. Result: Metric is below $200 → Triggered.
   3. Note:
      1. Weekly: Minimum of 1 week, maximum of 26 weeks.
      2. Monthly: Minimum of 1 month, maximum of 6 months.
      3. Note: The default limit for Analysis Window is 26 weeks/6 months to ensure optimal system performance; for additional keywords, please contact our CSD team for assistance.
8. Is Active? Toggle to enable or disable the notification.

Schedule

Specify how often the system should check whether the condition for triggering the Keyword Performance notification has been met.

For example: If the schedule is set to check weekly on Monday at 8:00 AM, the system will evaluate the selected keywords and performance metrics against your configured conditions. If any keyword meets the trigger condition, a notification will be sent at that time.

Recommendation: Choose a schedule that aligns with your business needs, such as weekly or monthly checks, to identify trends and respond proactively.

Validation

When you click “Save” or “Save and Preview”, the system checks if there is enough historical data to analyze performance based on your selected Analysis Window.

1. If there is enough data: The system saves the notification, and it will be triggered when conditions are met.
2. If there is not enough data: The system will inform you that there isn’t enough historical data to perform the comparison. You can still choose to save the notification, and it will activate automatically once sufficient data becomes available.

Email Notification Content

Email for Absolute Change

Content

1. Engine name: [engine name]
2. Environment: [DEV/TEST/PROD]
3. Metric: [Count/# of Orders/Total [$]/Avg. Order [$]/Conversion [%]]
4. Trigger Condition: [Increase/Decrease value]
5. Keyword/Value: [keyword: value increase/decrease]
6. Analysis Window:
   1. window 1: [start date] to [end date]
   2. window 2: [start date] to [end date]

Example

Engine Name: Elastic Demo
Environment: DEV
Metric: Avg. Order [$]
Trigger Condition: Decrease $50
Keyword/Value: jacket: $60 decrease
Analysis window:

1. window 1: 12/17/2023 to 6/16/2024
2. window 2: 6/17/2024 to 12/17/2024

Email for Percentage Change

Content

1. Engine name: [engine name]
2. Environment: [DEV/TEST/PROD]
3. Metric: [Count/# of Orders/Total [$]/Avg. Order [$]/Conversion [%]]
4. Trigger Condition: [Increase/Decrease value%]
5. Keyword/Value: [keyword: value increase/decrease]
6. Analysis Window:
   1. window 1: [start date] to [end date]
   2. window 2: [start date] to [end date]

Example

Engine Name: Elastic Demo
Environment: DEV
Metric: Conversion [%]
Trigger Condition: Increase 20%
Keyword/Value: jacket: 22% increase
Analysis window:

1. window 1: 12/17/2023 to 6/16/2024
2. window 2: 6/17/2024 to 12/17/2024

Email for Threshold Change

Content

1. Engine name: [engine name]
2. Environment: [DEV/TEST/PROD]
3. Metric: [Count/# of Orders/Total [$]/Avg. Order [$]/Conversion [%]]
4. Trigger Condition: [Above/Below] or at [value]
5. Keyword/Value: [keyword: value]
6. Analysis Window: [date range]

Example

Engine Name: Elastic Demo
Environment: DEV
Metric: Conversion [%]
Trigger Condition: Above or at 10%
Keyword/Value:

1. jacket: 67%
2. skirt: 100%

Analysis window: 11/1/2024 - 12/1/2024