25 Various Rule Event Types and Condition Types

In this session, we will explain the EVENTS and CONDITIONS in the Rule. EVENTS and CONDITIONS (if) Events with any conditions are the If  portion of a rule.

• Events——Specify one or more events that must take place to trigger the rule. Multiple events are joined by an OR. Any of the specified events will trigger the rule.
• Conditions——Narrow the event by configuring any conditions that must be true for an event to trigger the rule. An exception is defined as a NOT condition. Multiple conditions are joined by an AND.

Event Types

Browser Events

Browser Events has two, Tab Blur and Tab Focus

Tab Blur

Trigger the action when a tab loses the focus. Fired when the user clicks on a browser tab to jump to another page, When the page I am on is https://www.bbccss.com:

Then I clicked the second page to jump to https://www.bbccss.com/contact-me:

For the first page, it was Tab Blur.

There are no settings for this event type. E.g:

Tab Focus

Trigger the action when a tab gains the focus.  Click or open the current page, or follow the example above. For the second page, it is Tab Focus.

There are no settings for this event type. Eg：

Form Events

Blur

Trigger the action when a form loses the focus. Mouse away from form, click elsewhere

Eg：（Positioning via CSS）

Change

Enter information after clicking on the form， We enter the information and this is the change：

Eg：

Compared with Blur, there is more setting information, but it is basically not checked.

Focus

Trigger the action when a form gains the focus. Clicking on a form is Focus. After clicking, the cursor is here:

Eg：

Submit

Trigger the action when a form is submitted. Confirm that the form is successfully submitted. Note that this means successful. Only successful ones will be tracked. Unsuccessful will not be triggered.

Please note that the confirmation button must be type = submit, which is the same as GTM, otherwise it cannot be triggered.

Eg：

Keyboard Events

Key Press

Trigger the event if a key is pressed.  Monitor the operation of keyboard keys.

Eg：

It is still positioned by CSS. In fact, The position of each key corresponds to the keycode, you can check it through https://keycode.info/, but it seems that it is not recommended in Launch.

Media Events

Media Ended

Trigger the event when the media ends. Play ends.

Media Loaded Data

Trigger the event when the media loads data.

Media Pause

Trigger the event when the media is paused.

Media Play

Trigger the even when the media is played.

Media Stalled

Trigger the event if the media stalls.

Media Time Played

Trigger the event if the media is played for a specified length of time. Play duration or playback ratio

Eg：

Media Volume Changed

Mobile Events

Mouse Events

Click

Mousedown

Custom Event

Trigger the event if a custom event type occurs.

To be able to listen to an event, you have to first trigger one. Events are defined in the site’s code by your developers. This code is triggered on the page and actively sends data:

<span style="font-size: 12pt;">var addToCart = new CustomEvent('addToCart', 'detail': {'product_id': data.product.sku, 'quantity': data.product.quantity, 'price': data.product.price.fullPrice});
document.getElementById('minicart').dispatchEvent(addToCart);
</span>

Then you can use Custom Event to listen and receive it, this mode is the same as GTM DataLayer.  Specify the name of the custom event type, then configure the other settings as described in Options , below.

Direct Call

Designed to bypass event detection and lookup systems.

Direct call rules are ideal for situations where you want to tell Launch exactly what is happening. Also, they are ideal when Launch cannot detect an event in the DOM, such as with Adobe Flash.

Specify the _satellite.track string.  Proactive triggering is more accurate, but requires development to add code where it needs to be tracked. The format of the added code is: _satellite.track (‘haran’)

Do the following configuration in Launch:

Element Exists

Trigger the event if a specified element exists.

Enters Viewport

Trigger the event if the user enters a specified viewport.

In addition, configure whether the rule is triggered immediately or after a specified number of milliseconds.

History Change

Trigger the event if a pushState or hash change occurs.

There are no settings for this event type.

Page Load Events

Condition Types

This section describes the condition types available in the Core extension. Condition is a restriction on the event, making it more accurate.

Data

Cookie

Specify the cookie name and value that must exist for an event to trigger an action.

This restriction is very strong and is rarely used in general.

Engagement

Other

URL