An event is generated by a trigger. You can take the customer login as an example. In general, an event is a notification that something has happened in a computer program.

NOTE

A particular date or the given ones can initiate actions in a campaign.

The Event Service creates an event object to encapsulate information about the event. If a customer triggers the event, the event object includes the customer ID.
A notification is sent on every event detected. An event can be of the following types:

Session: The start time, end time, and if executed, the login time of the customer’s session.
Registration: The customer registers on the e-commerce site.
Special Offer/Coupon: The customer is presented with a special offer or coupon through a link on which he/she clicks.
Content: The customer is presented some content, such as an ad, or clicks the presented content.
Cart: An item is added, removed, or updated to the customer’s shopping cart.
Buy: The customer completes the purchase of one or more items.
Campaign: The events generated within the context of a campaign.

If the event is one of the types described in the above step, it notifies.
For each active campaign, it tries to match the event based on conditions.
For any condition that matches the event, it initiates an action.

Query

You can use this query to see the buckets in Automation:

Select * FROM ‘type_status_master’ where status_type=1

Important

Red Mark: If a campaign did not run accordingly and get stuck somewhere, as soon as you open the dashboard you get that particular section in red mark. L1 and L2 gets the notification that the campaign is stuck somewhere and solve the issue and make the status change.