Nevect

Operations & troubleshooting

Triggers and automated actions

Test the condition, reporting window and action before enabling automation.

Checked for Nevect 1.0.6 · Updated

Understand the boundary

Triggers is marked beta in the panel. Use it for supported automated checks and actions only after the same decision has been verified manually. A delayed conversion feed or incorrect cost can make an automatic condition misleading.

Configure a trigger

  1. Open Triggers and create a definition.
  2. Choose the resource scope, metric and comparison.
  3. Set the evaluation period and scheduling controls exposed by the editor.
  4. Choose the supported action or notification target.
  5. Review whether the action can affect shared resources.
  6. Save with automation disabled until the configuration has been checked.

Test the decision

Use an isolated scope with known data. Compare the condition's input with a report using the same period and filters. Confirm what happens when it matches, when it does not match and when data is absent or delayed.

Enable and observe

Enable deliberately, inspect the first recorded run or resulting state and keep the previous configuration. A notification being delivered does not prove the intended campaign action occurred.

Stop unexpected behavior

Disable the trigger before adjusting several conditions. Check whether the action already ran and whether repetition has additional effects. Keep the condition, time, original resource state and observed outcome for support.