Welcome
Working with the System
The section provides comprehensive instructions for creating, configuring, and managing marketing events. It covers topics such as defining audience conditions, setting up triggers, deploying events, and tracking their performance. Additionally, this section includes explanations of key terminology and offers advanced options to optimize event management.
Pipelines overview
A pipeline is the core runtime workflow in Detect that evaluates streaming feed data, applies business rules, and sends qualified events to configured destinations.
Action-based pipelines
An action sets a transaction goal that a customer must reach after receiving a pipeline message, and Detect sends reminders and a fulfillment message based on the customer's progress.

Getting Started
Welcome to the documentation for HCL Detect, where you can find information about how to install, maintain, and use this service.
Installation
Learn more about HCL Detect installation and deploying core components of the product.
Administration
Learn about how to configure, manage, and maintain HCL Detect environments. It includes details on system setup, user management, and permissions, ensuring seamless operation and efficient deployment of your continuous delivery processes.
Working with the System
The section provides comprehensive instructions for creating, configuring, and managing marketing events. It covers topics such as defining audience conditions, setting up triggers, deploying events, and tracking their performance. Additionally, this section includes explanations of key terminology and offers advanced options to optimize event management.
- About Unica Detect
- Dashboards and Monitoring
  Detect dashboards give you visibility into system performance and active feeds so that you can monitor event and transaction activity as it happens.
- Pipelines overview
  A pipeline is the core runtime workflow in Detect that evaluates streaming feed data, applies business rules, and sends qualified events to configured destinations.
  - Creating a Pipeline
  - Action-based pipelines
    An action sets a transaction goal that a customer must reach after receiving a pipeline message, and Detect sends reminders and a fulfillment message based on the customer's progress.
    - Adding action to pipeline message
      Add an action to a data destination message to track whether customers reach a transaction goal and to send a fulfillment message when they do.
    - Adding reminders to action
      Add time reminders and milestone reminders to an action to send messages while a customer progresses toward the action goal.
  - Saving, Approving, and Deploying
  - Monitoring Pipeline Reports
- Audience Segments
- Feed Management Overview
  This section explains how Feed Applications, Aggregates, and Enrichments in HCL Unica Detect work together to define event sources, aggregate data, and enrich event information for improved event processing and decision-making.
System Data Model
This section provides detailed information about the internal tables used within the Detect module. It includes descriptions of each table's structure, purpose, and relationships, aiding administrators and developers in understanding and managing the underlying database schema effectively.

Action-based pipelines

An action sets a transaction goal that a customer must reach after receiving a pipeline message, and Detect sends reminders and a fulfillment message based on the customer's progress.

Note:

This feature will be available starting with version 26.1.0.IF02

An action sets a goal that a customer must reach after they receive a pipeline message, for example, recharging a total of 1000 within 30 days. Detect tracks each customer's progress separately. It can send reminders while the customer progresses, and it sends a fulfillment message when the customer reaches the goal.

Action types

An action is either cumulative or non-cumulative. A cumulative action is fulfilled when the total of the customer's qualifying transactions within the duration reaches or exceeds the amount. For example, if the target is 1000, transactions of 200, 300, and 500 fulfill the action. A non-cumulative action is fulfilled when a single qualifying transaction reaches or exceeds the amount; amounts from separate transactions aren't added together. For example, if the target is 1000, transactions of 600 and 400 don't fulfill the action.

Action messages

An action can send three kinds of messages. Detect sends a fulfillment message when the customer reaches the action goal and meets the eligibility conditions. Detect sends a time reminder when the time that you specify passes and the action is still incomplete. Detect sends a milestone reminder when the customer's cumulative total reaches or exceeds the milestone amount.