What is Rules
Launch is a rule-based system. It looks for user interaction and associated data. When the criteria outlined in your rules are met, the rule triggers the extension, script, or client-side code you identified.
Rules is the core part of Launch. Its role is to control trigger conditions and execute actions, and when and where to send data.
Principles of Rules
Rules are composed of if … then …, and the action is executed when the previous trigger conditions are met. If is understood as the trigger condition of Rules, then is the action.
If contains two configuration options, EVENTS and CONDITIONS.
EVENTS
EVENTS: The Chinese name is an event, but here should be understood as a trigger condition or trigger, that is, when, for example, EVENTS here can be click, submit, pull down and other actions.
The setting interface of EVENTS is as follows:
- Extensions: plug-ins, which indicate which extensions Rules is based on, generally using Core. If you want to track based on third-party plug-ins, you need to choose a third-party plug-in.
- Event Type: The event type is the kind of trigger behavior. The Event Type here is based on the previous Extensions. Different Extensions will have different Event Types built in.
- Name: The name is a combination of Extensions-Event Type, which is automatically generated and generally does not need to be changed.
- Order: Sequence, which controls the trigger priority. The lower the value, the higher the trigger priority. Adobe highly recommends that you order your rules with positive numbers between 1 and 100 (default is 50). Simpler is better.
The specific configuration on the right is based on the Event Type. Different Event Types are different, and some are not.
There are many built-in Event Types in Core, as shown in the following table:
|
Category |
Event Type |
Definition |
|
BROWERS |
Event is triggered when the content loses focus. | |
| Event is triggered when the content gains focus. | ||
|
FORM |
Blur |
An element lost focus (does not bubble). |
|
Change |
An element loses focus and its value changed since gaining focus. | |
|
Focus |
An element received focus (does not bubble). | |
|
Submit |
A form is submitted. | |
|
KEYBOARD |
Key Press |
A key is pressed and that key normally produces a character value (use input instead). |
|
MEDIA |
Media Ended |
Playback stopped because the end of the media was reached. |
|
Media Loaded Data |
The first frame of the media finished loading. | |
|
Media Pause |
Playback is paused. | |
|
Media Play |
Playback began | |
|
Media Stalled |
The user agent is trying to fetch media data, but data is unexpectedly not forthcoming. | |
|
Media Time Played |
Trigger the event if the media is played for a specified length of time. | |
|
Media Volume Change |
The volume has changed. | |
|
MOBILE |
Orientation Change |
The orientation of the device (portrait/landscape) has changed. |
|
Zoom Change |
When a pinch or spread gesture is performed on a mobile device. | |
|
MOUSE |
Click |
A pointing device button is pressed and released on an element |
|
Hover |
Trigger the event if the user hovers over a specified element. | |
|
Mousedown |
A pointing device is moved onto the element that has the listener attached or onto one of its children. | |
|
OTHERS |
Custom Code |
Inside your code, call trigger() whenever you would like the rule to fire. |
|
Custom Event |
Trigger the event if a custom event type occurs. | |
|
Data Element Change |
A date element changed. This event lets you select a specific data element to use as a trigger. | |
|
Direct Call |
Designed to bypass event detection and lookup systems. | |
|
Element Exists |
Trigger the event if a specified element exists. | |
|
Enters Viewport |
Trigger the event if the user enters a specified viewport. | |
|
History Change |
Trigger the event if a pushState or hashchange occurs. | |
|
Time On Page |
Trigger the event if the user remains on the page for a specified number of second | |
|
PAGE LOAD |
DOM Ready |
Trigger when the DOM is ready and the user can interact with the page |
|
Library Loaded (Page Top) |
Trigger the event as soon as the Launch library is loaded. | |
|
Page Bottom |
Trigger the event once _satellite.pageBottom(); has been called. When loading the Launch library asynchronously, this event type should not be used. | |
|
Window Loaded |
Trigger the event when onLoad is called by the browser and the page has finished loading. |
Click ➕ on the right side of EVENTS to create one more EVENTS. Multiple EVENTS is a relationship representing OR. As long as one of them is triggered, it will be triggered.
CONDITIONS
CONDITIONS: This is the condition. Limit the previous trigger conditions, such as certain pages, certain types of users, which are triggered only by these pages or users.
The setting interface of CONDITIONS is as follows:
- Logic Type: Logic type, one is Regular, which satisfies the rules, which can be understood as including, and the other is Reception, which is exclusion.
- Extensions: plugins, this must be consistent with EVENTS.
- Condition Type: Match type, which field is used to match.
- Name is a combination of Extensions-Condition Type, which is automatically generated and generally does not need to be changed.
The specific configuration on the right is based on the Condition Type. Different Condition Types are different and must not be empty.
Among them, there are many Condition types built into Core, as shown in the following table:
|
Category |
Event Type |
Definition |
|
DATA |
Cookie |
Specify the cookie name and value that must exist for an event to trigger an action. |
|
Custom Code |
Specify any custom code that must exist as a condition of the event. | |
|
Value Comparison |
Compares two values to determine whether this condition returns true. | |
|
Variable |
Specify the JavaScript variable name and value that must exist for an event to trigger an action. | |
|
ENGAGEMENT |
Landing Page |
Specify the page the user must land on to trigger the event. |
|
New/Returning Visitor |
Specify whether the visitor should be a new visitor or a returning visitor for an event to trigger an action. | |
|
Page Views |
Configure the number of times the visitor must view the page before the action is triggered. | |
|
Sessions |
Trigger the action if the user’s number of sessions meets the specified criteria. | |
|
Time On Site |
Trigger the action if the user’s number of sessions meets the specified criteria. | |
|
Traffic Source |
Trigger the action if the user’s number of sessions meets the specified criteria. | |
|
OTHER |
Date Range |
Specify a date range. Choose the date and time the event occurs after, the date it occurs before, and the time zone. |
|
Max Frequency |
Specify the maximum number of times the condition returns true. | |
|
Sampling |
Specify the percentage of the time the condition returns true. | |
|
TECHNOLOGY |
Browser |
Select the browser the visitor must use for the action to be triggered. |
|
Device Type |
Select the device type the visitor must use for the action to be triggered. | |
|
Operating System |
Select the operating system the visitor must use for the action to be triggered. | |
|
Screen Resolution |
Select the screen resolution visitors must use on their devices for the action to be triggered. | |
|
Window Size |
Select the window size visitors must use on their devices for the action to be triggered. | |
|
URL |
Domain |
Specify the visitor’s domain. |
|
Hash |
Specify one or more hash patterns that must exist in the URL. | |
|
Path And Query String |
Path And Query String | |
|
Path Without Query String |
Path Without Query String | |
|
Protocol |
Specify the protocol used in the URL. | |
|
Query String Parameter |
Specify the Query String Parameter used in the URL. | |
|
Subdomain |
Specify one or more subdomains that must exist in the URL. |
Click ➕ on the right side of CONDITIONS directly to create one more CONDITIONS. Multiple CONDITIONS is the relationship between AND, which indicates that multiple conditions are restricted at the same time, which will be triggered when all conditions are met.
ACTIONS
ACTIONS: There are only ACTIONS in Then, which is what is executed after Rules trigger. There can be multiple ACTIONS in a Then, but the order between different ACTIONS is required.
The setting interface of ACTIONS is as follows:
- Extensions: plug-ins. Here is what is triggered. What is sent is where to send data and control the sending of data, such as Adobe Analytics, Adobe Target, Adobe Audience Manager … It depends on which extensions are installed in your Extensions.
- Action Type: This Extensions has those sending forms, which depends on Extensions.
- Name, a combination of the name Extensions-Action Type, is automatically generated and can be modified.
The specific configuration on the right is based on the Action Type, which is different for different Action Types.
