It seems that there are a lot of advantages to having a single goal per automation.
- If you use the “Jump to goal” (from elsewhere in the automation) then the JUMP logic is easier to keep track of (b/c there is only one place they can jump to.
- Stats are easier to track. Automation stats are listed for performing any goal , there does not seem to be a way to filter it down
Does this seem correct?
1 Like
Using one goal per automation is often the best approach for measuring performance of an automation. However, there may be times where you will need to use a goal just for the jump function. In those cases your automation may have more than one goal.
Regarding your screenshot above I recommend logging performance in a spreadsheet. It’s safe to compare your overall completion rate to the last 30 days but you should also be tracking every 30 days separately (preferably in a spreadsheet) to get the full view of your performance over the year. I would log the overall completion rate along with it.
