Skip to main content

How to edit a specific recommendation

Jonas Østergård Bæk avatar
Written by Jonas Østergård Bæk
Updated over a month ago

Each recommendation in Alvie comes with a set of default values - including severity, thresholds, and descriptive text - but you can fully customise these to better match your marketing strategy or preferences.

This flexibility means you’re not locked into our defaults. If something isn’t considered “critical” in your context, or if you want to adjust the logic behind a rule, you can easily change it.

How to edit a recommendation

  1. Go to the Recommendations page (/recommendations)

  2. Find the recommendation you want to edit

  3. Click the three dots (···) next to it

  4. Select “Edit this recommendation”

This will open the Edit recommendation popup, where you can modify the following:

  • Name
    You can rename the recommendation to use internal terminology or clarify the issue it detects.

  • Description
    Update the explanation of the recommendation to reflect what your team should look for or do when it appears.

  • Severity
    Choose between Critical, Moderate, or Low severity. This affects how the recommendation is prioritised in Alvie.

Customising rule parameters

You can also adjust how the rule is triggered by modifying its parameters.
For example if a recommendation monitors drops in impressions, you might want to adjust what "drop in impressions" means for your specific case:

  • Impression loss percentage
    Set the threshold at which the recommendation should trigger (e.g. less than 20%).

  • Interval
    Define the time period over which the condition is evaluated (e.g. the last 7 days).

This gives you full control over what “significant drop” or “underperformance” means to your team.

What happens after you edit?

  • The new configuration is saved immediately for your workspace.

  • Future runs of the recommendations will use your updated values.

  • All users in the workspace will see the updated name, description, and severity.

Did this answer your question?