Перейти к содержимому

Custom events in scenarios 

Custom events allow you to track non-standard customer behavior in your online store. These unique actions may result from, e.g., the nature of your offer, the way your online store is built or your marketing strategy. 

How to create a custom event?

You can do this in two places: 

  • Directly in the scenario, in the Custom event starting point. 
  • In the List of events, by clicking the Create new event button.

When creating an event in a scenario: 

  1. Click the Event field. A drop-down list will appear. If this is your first time using the Custom event starting point, the list will be empty. 
  1. Click Create new to create a custom event. 

When creating an event in the List of events: 

  1. Click the Create new event button above the event table, on the right-hand side.

Next steps are the same for both methods: 

  1. In the newly opened window, add: 
    • Event name 
    • Description 
    • Check the Enable logging option if you want to track actions related to this event. You can find them in the List of events > Log table (eye icon in the last column) 
  1. Click Save. 

The saved custom event appears in the List of events. You will need to provide the event ID in your API, so that you can track the custom event in your system. 

Event log – preview of triggered actions 

You can track the triggering of custom events by clicking the Log option (eye icon), located in the List of events table, in the last column. 

A new window will display a list of triggers for a given event, with details grouped in columns: 

  • ID – trigger ID number. 
  • Created – date and time of registration of a given trigger. 
  • Customer email – email address assigned to the customer whose action on the website triggered the event. 
  • Scenario – ID and name of the scenario in which the event was used. If the event triggered several scenarios, each of such occurrences is recorded in the log separately. 
  • Details – icon in the last column opening a window with details of a given trigger. 

In the detail preview, you can see two tabs: 

  • Information – containing a summary of information from the table described above. 
  • Data fields – containing technical details of a given trigger, e.g., the URL where the event occurred, or the amount concerned. 
Privacy policy