Notifications in Pertento

Notifications tell you when something happened that you would otherwise have to go looking for. They appear in the bell in the dashboard header, and each one links to the page where you can act on it.

Experiment lifecycle

• Started — an experiment went live and is collecting data.
• Ended — an experiment finished. Links to its results.
• Deployed — a winning variant was rolled out, naming the variant.

Results

• Is winning — a variant is significantly ahead, with the variant name and the lift.
• Is losing — a variant is significantly behind the control, with the same detail. This is the one to act on quickest: a losing experiment costs conversions every day it runs.

Health

These say an experiment cannot be trusted, or has stopped being an experiment, which is more urgent than any result it is currently reporting:

• Did not split as configured — the traffic split does not match the configured weights. Results are not trustworthy until this is explained.
• Has stopped receiving traffic — nothing recorded in the last day while still running. Usually broken targeting or a missing script.
• Past its end date — still running and still collecting traffic after its scheduled finish.

Workflow and account

• Marked as implemented — someone recorded a winning change as permanently built.
• A user was invited — a colleague was invited, and the role they are joining as.
• A website was added — a new website was added to the account.

How they relate to the attention list

Notifications and the attention list are driven by the same signals, and they are for different moments. A notification is a push, telling you something changed. The attention list is a pull: everything currently needing a person, in priority order.

If you are away from the dashboard, notifications reach you. If you are sitting down to work, the attention list is the better starting point because it is ranked and it does not include things that have since been resolved.

Notes

• Every notification carries structured detail rather than a frozen sentence, so the same event can also become an email later and its links stay correct when pages move.
• Health notifications are deduplicated: a persistent fault does not notify repeatedly.
• Pertento only defines notifications for things that actually happen, so there is nothing in the list that never fires.