v1.5.1

List of Events

Event is a certain action of a visitor to your site (e.g., login, registration, placing an order) or an action of a system (e.g., change order status, cron job execution).

Events are used in the notifications as a signal for the extension to start sending messages.

Each event has a set of related variables - which can be used in the template and conditions - that are used in the rules and allow you to set up a notification in such a way as to receive only the messages that interest you.

  • App Events

    • Error

      This event is triggered when a new error is occurred in your site and allows you to be aware of all critical errors.

      When a new error is occurred by using this event, you can immediately inform your developer on the need to investigate it. In addition, you can send a message to the support team of a company that developed the extension, which thrown an error.

      • Related Conditions for Notifications: Error
      • Related Variables for Templates:

      Note

      The Error event has multiple levels, the low-level errors (Debug, Info, Notice, Warning) generate too many records that are registered by our extension and stored in the DB table mst_event_event. Therefore in order to avoid the fast overflow of this table, we recommend you observe only high priority error levels. You can select observed error levels at the global settings of the extension: System > Event Watcher and Notification > Settings

  • Admin Events

    • Admin Logged In

      This event is triggered whenever Admin User is logged in to the backend.

      You can configure notifications to be sent when admin users use new devices to log in to your store, or even possible password stealing.

      • Related Conditions for Notifications: Admin (User)
      • Related Variables for Templates:

    • Admin Login Failed

      This event is triggered whenever Admin User tries to log in to the backend but failed.

      You can configure notifications to be sent when login failures reach a certain limit, so you can detect a brute-force hacker attack.

      • Related Conditions for Notifications: Admin (User)
      • Related Variables for Templates:

  • Cron Events

    • Cron job

      The event is triggered whenever a new cron job is added to a schedule.

      With this event, you can always be aware of failed and long-running cron jobs or be notified when the cron schedule has stuck and can send notifications to your server admin to handle problems with cron. Or, you can also automatically contact the support of a company that developed the extension whose cron job got failed.

      • Related Conditions for Notifications: Schedule
      • Related Variables for Templates:

  • Admin Notification Events

    • New Notification

      The event is triggered whenever your site receives a new Admin Notification. These messages feature in Magento is used for notifying an admin user about variability issues, security patches, updates, and other news. Read more about them.

      With this event, you can configure the extension to receive only the notifications of a selected severity, therefore, notifying different staff members about respective problems.

  • Product Events

    • Decreased QTY

      The event is triggered whenever a product quantity is decreased. This event allows you to be aware, when product stock quantity falls below the threshold, and to notify responsible staff on the need to replenish the warehouse.

      • Related Conditions for Notifications: Product
      • Related Variables for Templates:

    • Product View

      The event is triggered when a product is viewed by a registered customer. This rule can be used for tracking down the interest in specially promoted products, or some experimental goods.

      • Related Conditions for Notifications: Product, Customer, Store.
      • Related Variables for Templates:  

  • Customer Events

    • Customer Logged In

      The event is triggered whenever a customer logs in to the store.

      • Related Conditions for Notifications: Customer, Store.
      • Related Variables for Templates:

    • Customer Logged out

      The event is triggered whenever a customer logs out of the store.

      • Related Conditions for Notifications: Customer, Store.
      • Related Variables for Templates:

    • New Customer Sign up

      The event is triggered when a customer is registered in your store.

      • Related Conditions for Notifications: Customer, Store.
      • Related Variables for Templates:

    • Customer Birthday

      The event is triggered whenever a customer has a birthday.

      Note

      This event is fired at 00:00 of the day of the customer's birth.
      • Related Conditions for Notifications: Customer, Store.
      • Related Variables for Templates:

  • Newsletter Events

    • Newsletter subscription

      The event is triggered when a customer subscribes to the newsletter.

      • Related Conditions for Notifications: Customer.
      • Related Variables for Templates:

    • Newsletter unsubscription

      The event is triggered when a customer cancels the subscription to the newsletter.

      • Related Conditions for Notifications: Customer.
      • Related Variables for Templates:

    • Subscription status change

      The event is triggered when a customer enables or cancels the subscription to the newsletter.

      • Related Conditions for Notifications: Customer.
      • Related Variables for Templates:

  • Shopping Cart

    • Abandoned Shopping Cart

      The event is triggered when the shopping cart was not updated in a reasonable period, or customer logged off but did not place an order. Criteria for such a cart can be configured at Stores -> Settings -> Configuration -> Dotmailer -> Abandoned Carts.

  • Order Events

    • Order status was changed

      The event is triggered whenever the order is saved to apply some changes (it includes placing an Invoice or Shipping documents).

    • Order obtained 'XXX' status

      Our extension features a set of generic Events, which act as a shortcut to Order was changed event with a check of Order status. These events have similar names as shown in the header (Order obtained 'Complete' status, for example), and trigger, whenever Order receives particular status.

  • Review Events

    • New review was added

      This event is triggered whenever a new Review is added (but before Approvement).

    • Review has been approved

      This event is triggered whenever a new Review is approved and displayed in the store.

  • Wishlist Events

    • Product was added to wishlist

      This event is triggered whenever a new product is added to the customer's wishlist.

    • Wishlist was shared

Note

Did you not find an event for your needs? Contact our support team, and we will be glad to help you.