Score or data-change triggers
Score or data-change triggers start condition
Score or data-change triggers start from a meaningful change in the dashboard.
Use this carefully. A small metric move can be noise. A repeated change with clear evidence is more useful.
Trigger setup
Write the condition in plain language.
Examples:
If mention rate drops this week, inspect the related prompts and sources. Send a card only if the drop is tied to a clear page or source issue.
If a new competitor appears in more than one important prompt, review the source evidence and return one next action.
CLEA context
These workflows need Analytics, Sources, Competitors, and the related prompt answers.
For Search Console or Google Analytics checks, CLEA should only use the data when the integration is connected.
Detect the change
Notice a score, prompt, source, or analytics movement.
Check repeat proof
Look for a pattern before acting.
Ask for one result
Return a card, note, or review task.
Avoid noise
Watch thin signals instead of creating busy work.
Noise control
Set a high bar for action.
A good rule is: no repeated pattern, no card. If the change happened once and the evidence is thin, ask CLEA to watch it instead of acting.