This article describes how to configure alerts. If you want to learn more about the concept of Alerts and how they work in ContentKing, you can refer to this article.
When you add a website to ContentKing, it already comes with a default set of alerts that will ensure that you are notified about every important change that occurs on your website.
However, you can also customize these alerts and tailor them to your needs to make sure that you have the best possible setup for every monitored website. This article describes how to do that.
What can be configured in alerts
For each alert definition, you can configure the following parameters: Scope, Sensitivity, Recipients, and Slack.
Scope of the alert definition determines what part of the website you will be alerted about. You can set it to the entire website or a specific segment.
If none of the existing segments fit your needs for a certain alert definition, you can create a new segment based on any filter criteria that you want.
Sensitivity determines how many pages need to be affected by the change for the alert to open.
The Importance of the affected pages also influences the sensitivity, so if a change affects a number of very important pages, the alert will open sooner than if the same number of less important pages was affected.
There are four sensitivity levels:
If you set the sensitivity level of an alert definition to
Always, you will be alerted about every single change on any page, regardless of the page’s Importance score.
If you set the sensitivity level of an alert definition to
Low, the change will need to affect a significant part of the website in order for the alert to open.
Below the sensitivity slider, you will always see exactly how many pages from the selected scope need to be affected for the alert to trigger with the given sensitivity level:
If you feel like you’re receiving a certain alert too often, lower the sensitivity level. If you want to be notified about every single change on any page, set the Sensitivity to
Let’s say you have a website with 200,000 pages and on 100 of these pages the page title changes. Would you want to be alerted about that?
Your answer to that question is probably “it depends”.
If these 100 pages are unimportant, somewhere deep down in the website and hardly getting any traffic, you probably don’t want to be alerted. However, if this change happens on the homepage and your main categories, you most likely would want to be alerted about it.
That’s why ContentKing’s alerting engine is smart and doesn’t just look at the number of pages affected, but also at the Importance of these pages.
And of course: every single change — no matter how unimportant — is always tracked with ContentKing’s Change Tracking feature.
Recipients are the team members who will receive the alert via email.
You can set multiple email recipients for one alert definition and also different recipients for different definitions (see also the Best practices described below).
You can also receive the alerts via Slack.
Similar to Recipients, you can set different Slack channels for different alert definitions. You can read more about the Slack integration here.
How to configure alerts
You can create new alert definitions from scratch or edit the existing definitions. All of this can also be done using bulk actions.
Creating new alert definitions
To create new alert definitions, follow these steps:
- On the Alerts definitions screen, click Create alert definitions
- Select the alert types for which you want to create definitions
- Set the scope of the definitions (whole website or specific segments)
- Set the sensitivity level, the recipients and/or the Slack channel
- Click Create alert definitions
Editing alert definitions
By default, ContentKing comes with one alert definition for each alert type. You can edit or remove these default alert definitions using the action buttons on the right side of the screen.
If you don’t care about a certain alert type and you don’t want to be alerted about the change at all, you can remove all recipients from the alert definition or remove the alert definition completely.
- If you remove all recipients from an alert definition, the alert will still open if the change happens and you will see the incident on the Alert incidents screen, but no email or Slack notification will be sent.
- If you remove the alert definition completely, the alert will not open at all.
You can also edit existing alert definitions in bulk.
When you select one or more alert definitions on the Alerts definitions screen (by ticking their checkbox on the left side of the screen), a blue toolbar will appear at the top, allowing you to perform the following bulk actions:
- Edit scope
- Edit sensitivity
- Edit recipients
- Edit Slack channel
Best practices for alert configuration
Higher sensitivity for important segments
For every website that you add to your account, ContentKing comes with a default set of alert definitions that are set for the whole website and have the
Medium sensitivity level.
We recommend keeping the default alert definitions as they are (or lowering their sensitivity if you are getting too many alerts) and creating new alert definitions with the
Always sensitivity level for your important segments (more about Segments here).
This means that when a change occurs on an important page, you are immediately alerted about it. However, when a change occurs on less important pages, a significant part of the website needs to be affected for the alert to open.
This setup ensures that you are alerted about every important change that cannot go unnoticed but at the same time you are not overwhelmed by alerts about every tiny and unimportant change.
Assigning alert recipients
ContentKing is fully collaborative and allows you to invite as many users as you want.
This means that you can invite your whole team to your account and assign alerts to them based on their roles or the websites they are taking care of.
Assigning recipients based on role
If you have multiple teams working together in ContentKing, make sure people only receive alerts that are relevant for their role.
So for example, the content team will only receive the content alerts, the technical team will only receive the platform alerts, and so on.
This will ensure that every team member will only receive alerts that are actionable for them and will not get overwhelmed by irrelevant alerts.
Assigning recipients based on assigned websites
If different team members are responsible for different websites, make sure they are only alerted about the websites they are responsible for.
There are two ways to manage this, from a user perspective and from a website perspective:
- Website perspective: in the Website settings, you can set which team members will receive alerts about the website:
- User perspective: in the Email settings tab of the User profile, you can set which websites the team member will be alerted about:
If you have any questions about the alert configuration or you need a hand setting it up, don’t hesitate to contact us and we will be happy to help.