Automation activity tracking

You can use two tools to track what happens in automation: events saved to individual customer profiles, and statistics of the entire workflow.

Events

In the Automation module, each activity (movement between steps in the workflow) of the customer is translated into events and listed on the customer card.

The Track datapoints option (disabled by default, except for triggers and end nodes) makes these events available for use in analyses in the Analytics module. The option can be enabled separately for each node.

Important:
  • The Track datapoints option doesn’t affect the visibility of the clientIsInPath events on the customer card. It only changes their availability in analytics.
  • Events are kept in the database for a retention period that differs between business profiles. To check the retention of a particular event type, contact your system administrator.
  • Activities connected with automation steps may appear with a slight delay due to overloads caused by increased traffic. This has no impact on workflow execution.

Switched off activity tracking option
Switched off activity tracking option

The Track datapoints option is available for most nodes. You can find it in the lower-left corner of the node configuration view.
When you switch the toggle on in a node, the clientIsInPath event generated for that node will be available in the Analytics module.

Important: The Track datapoints option doesn’t affect generating events of actions that are performed in accordance with the logic of the nodes, such as webhook.response.

Example

When a customer arrives at the Send email action node and the Track datapoints option is switched on in the node settings:

  1. An email is sent to a customer.
  2. A message.sent event is generated and it is visible on the customer card and in analytics (this happens regardless of the state of the Track datapoints option).
  3. An automation.clientPathStep event is generated and visible on the customer card (this event is generated regardless of the Track datapoints option).
  4. The same automation.clientPathStep event becomes available for use in analytics, for example in funnels.
  5. Triggers and End nodes only: The Open in Profiles option becomes available in the statistics of the node.

Statistics

Automation statistics let you examine how many customers reached and passed particular nodes. You can use this to evaluate the effectiveness of your workflow, but also for troubleshooting.

Note: Statistics are available only in workflows that were started at least once. Pausing, modifying, and resuming a workflow does not reset the statistics.

To access the statistics:

  1. Go Automation > Workflows.
  2. Open a workflow.
  3. In the upper-left corner above the canvas, click Analytics.
    The analytics may take a few seconds to load.
    Result: The view displays how many customers entered each of the nodes.
  4. To see detailed statistics of a node, double-click it.
    Result: A panel with the detailed statistics opens. Each node node contains information about how many customers entered and completed (executed) the node. Additional information depends on the type of node and may include data such as:
    • how long it takes to reach this node
    • how many customers who began the workflow reached this node
    • if there were any errors in processing the node
    • CTR
    • and more
  5. Triggers and End nodes only: To see a list of profiles who completed this node, in the upper-right corner click Open in Profiles.

Examples

Statistics of a Client Filter node
Example: statistics of a Client Filter node
Statistics of an Outgoing Integration node
Example: statistics of an Outgoing Integration node
😕

We are sorry to hear that

Thank you for helping improve out documentation. If you need help or have any questions, please consider contacting support.

😉

Awesome!

Thank you for helping improve out documentation. If you need help or have any questions, please consider contacting support.

Close modal icon Placeholder alt for modal to satisfy link checker