ARGOMENTI×

Core Extension

The Core extension is the default extension released with Launch.

Use this reference for information about the options available when using this extension to build a rule.

Launch Core extension

Core extension event types

This topic describes the event types available in the Core extension.

For information about options that can be set for several different event types, see Options .

Browser

Tab Blur

Trigger the action when a tab loses the focus.

There are no settings for this event type.

Tab Focus

Trigger the action when a tab gains the focus.

There are no settings for this event type.

Form

Blur

Trigger the action when a form loses the focus.

See Options , below.

Focus

Trigger the action when a form gains the focus.

See Options , below.

Submit

Trigger the action when a form is submitted.

See Options , below.

Keyboard

Key Press

Trigger the event if a key is pressed.

See Options , below.

Media

Media Ended

Trigger the event when the media ends.

See Options , below.

Media Loaded Data

Trigger the event when the media loads data.

See Options , below.

Media Pause

Trigger the event when the media is paused.

See Options , below.

Media Play

Trigger the even when the media is played.

See Options , below.

Media Stalled

Trigger the event if the media stalls.

See Options , below.

Media Time Played

Trigger the event if the media is played for a specified length of time.

See Options , below.

In addition, specify that the event is triggered after a specific amount of time.

Media Volume Changed

Trigger the event if the volume is raised or lowered.

See Options , below.

Mobile

Orientation Change

Trigger the event if the device’s orientation changes.

There are no settings for this event type.

In addition, specify that the event is triggered after a specific amount of time.

Zoom Change

Trigger the event if the user zooms in or out.

There are no settings for this event type.

Mouse

Click

Trigger the event if the specified element is clicked.

Optionally, you can specify property values that must be true for the element before the event is triggered.

You can also specify whether to delay navigation until the rule runs if the element is a link. When you click the check box, a field opens where you can enter the desired delay in milliseconds. This specifies how long Launch waits for tags to fire on clicked links before moving to the next page. The default value is 100 milliseconds. Longer delays improve tracking accuracy. Adobe recommends a delay of 500 milliseconds or less, which the user will not perceive. Launch will wait up to the time specified, but if the beacon fires sooner, the delay is cut short. (That is, user won’t always wait the full length of the delay.)

In addition, specify that the event is triggered after a specific amount of time.

For advanced options, see Options , below.

Hover

Trigger the event if the user hovers over a specified element.

See Options , below.

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

Other

Custom Event

Trigger the event if a custom event type occurs.

You can name a JavaScript function that you’ve defined elsewhere and use it for the event.

Specify the name of the custom event type, then configure the other settings as described in Options , below.

Data Element Changed

Trigger the event if a specified data element changes.

Enter the data element name. You can select the data element from a list by clicking the icon and then selecting the data element.

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.

Element Exists

Trigger the event if a specified element exists.

See Options , below.

Enters Viewport

Trigger the event if the user enters a specified viewport.

See Options , below.

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 hashchange occurs.

There are no settings for this event type.

Time Spent on Page

Trigger the event if the user remains on the page for a specified number of seconds.

Specify the number of seconds that must pass before the event is triggered.

Page load

DOM Ready

Trigger when the DOM is ready and the user can interact with the page

There are no settings for this event type.

Library Loaded (Page Top)

Trigger the event as soon as the Launch library is loaded.

There are no settings for this event type.

Page Bottom

Trigger the event once _satellite.pageBottom(); has been called. When loading the Launch library asynchronously, this event type should not be used.

There are no settings for this event type.

Window Loaded

Trigger the event when onLoad is called by the browser and the page has finished loading.

There are no settings for this event type.

Options

Each of the form event types uses the following settings:

Specific Elements \| Any Element

If you choose Specific Elements , the options to select the elements and property values appear.
If you choose Any Element , there are no further options required to narrow down the elements.

Elements matching the CSS selector

Enter the CSS selector that identifies the elements that trigger the event.

And having certain property values

If you select this option, the following parameters become available:

property=value
Specify the value for the property
Regex
Enable if the property=value is a regular expression.
Add
Add another property=value pair.

Advanced options (Bubbling)

Run this rule even when the event originates from a descendant element
Allow this rule to run even if the event already triggered a rule targeting a descendant element
After the rule runs, prevent the event from triggering rules targeting ancestor elements

Core extension condition types

This section describes the condition types available in the Core extension. These condition types can be used with either the regular or exception logic type.

Data

Custom Code

Specify any custom code that must exist as a condition of the event. Use the built-in code editor to enter the custom code.

Click Open Editor .
Type the custom code.
Click Save .

A variable named event will automatically be available, which you can reference from within your custom code. The event object will contain useful information about the event that triggered the rule. The easiest way to determine what event data is available is to log event to the console from within your custom code:

console.log(event);
return true;

Run the rule in a browser and inspect the logged event object in the browser’s console. Once you understand what information is available, you can use it for programmatic decisioning within your custom code.

Condition Sequencing

When the “Run rule components in sequence” option from property settings is enabled you can have subsequent rule components wait while your condition performs an asynchronous task.

When the condition returns a Promise , the next condition in the rule will not execute until the returned promise is resolved. If the promise is rejected, Launch considers that condition as failed and no further conditions or actions from that rule will be executed.

An example of a condition that returns a promise:

return new Promise(function(resolve, reject) {
  setTimeout(function() {
    if (new Date().getDay() === 5) {
      resolve();
    } else {
      reject();
    }
  }, 1000);
});

Value Comparison

Compares two values to determine whether this condition returns true.

If you have a rule with multiple conditions, it is possible that this condition will return true, but the rule will still not fire because the other conditions evaluate as false or one of the exceptions evaluates as true.

Provide a value.
Select the operator. Refer to the list of value comparison operators, below, for more details.
(Where required) Select whether the comparison should be case-insensitive.
Provide another value for the comparison.

The following value comparison operators are available:

Equal: The condition returns true if the two values are equal using a non-strict comparison (in JavaScript, the == operator). The values may be of any type. When typing a word like true , false , null , or undefined into a value field, the word is compared as a string and is not be converted to its JavaScript equivalent.

Does Not Equal: The condition returns true if the two values are not equalusing a non-strict comparison (in JavaScript, the != operator). The values may be of any type. When typing a word like true , false , null , or undefined into a value field, the word is compared as a string and is not be converted to its JavaScript equivalent.

Contains: The condition returns true if the first value contains the second value. Numbers are converted to strings. Any value other than a number or string results in the condition returning false.

Does Not Contain: The condition returns true if the first value does not contain the second value. Numbers are converted to strings. Any value other than a number or string will result in the condition returning true.

Starts With: The condition returns true if the first value starts with the second value. Numbers are converted to strings. Any value other than a number or string results in the condition returning false.

Does Not Start With: The condition returns true if the first value does not start with the second value. Numbers are converted to strings. Any value other than a number or string results in the condition returning true.

Ends With: The condition returns true if the first value ends with the second value. Numbers are converted to strings. Any value other than a number or string results in the condition returning false.

Does Not End With: The condition returns true if the first value does not end with the second value. Numbers are converted to strings. Any value other than a number or string results in the condition returning true.

Matches Regex: The condition returns true if the first value matches the regular expression. Numbers are converted to strings. Any value other than a number or string results in the condition returning false.

Does Not Match Regex: The condition returns true if the first value does not match the regular expression. Numbers are converted to strings. Any value other than a number or string results in the condition returning true.

Is Less Than: The condition returns true if the first value is less than the second value. Strings representing numbers are converted to numbers. Any value other than a number or a convertible string result in the condition returning false.

Is Less Than Or Equal To: The condition returns true if the first value is less than or equal to the second value. Strings representing numbers are converted to numbers. Any value other than a number or a convertible string result in the condition returning false.

Is Greater Than: The condition returns true if the first value is greater than the second value. Strings representing numbers are converted to numbers. Any value other than a number or a convertible string result in the condition returning false.

Is Greater Than Or Equal To: The condition returns true if the first value is greater than or equal to the second value. Strings representing numbers are converted to numbers. Any value other than a number or a convertible string result in the condition returning false.

Is True: The condition returns true if the value is a boolean with the value of true. The value you provide is not converted to a boolean if it is any other type. Any value other than a boolean with the value of true results in the condition returning false.

Is Truthy: The condition returns true if the value is true after being converted to a boolean. See MDN’s Truthy documentation for examples of truthy values.

Is False: The condition returns true if the value is a boolean with the value of false. The value you provide is not converted to a boolean if it is any other type. Any value other than a boolean with the value of false results in the condition returning false.

Is Falsy: The condition returns true if the value is false after being converted to a boolean. See MDN’s Falsy documentation for examples of falsy values.

Variable

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

Specify the JavaScript variable name.
Specify the variable value that must exist as a condition for the event.
(Optional) Enable Regex if this is a regular expression.

Engagement

Landing Page

Specify the page the user must land on to trigger the event.

Specify the landing page.
(Optional) Enable Regex if this is a regular expression.

New/Returning Visitor

Specify whether the visitor should be a new visitor or a returning visitor for an event to trigger an action.

Select one of the following:

New Visitor
Returning Visitor

Page Views

Configure the number of times the visitor must view the page before the action is triggered.

Select whether the number of page views must be greater than, equal to, or less than the specified value.
Specify the number of page views that determines whether the condition is met.
Configure when the page views are counted by selecting one of the following:
- Lifetime
- Current Session

Sessions

Trigger the action if the user’s number of sessions meets the specified criteria.

Select whether the number of sessions must be greater than, equal to, or less than the specified value.
Specify the number of sessions that determines whether the condition is met.

Time On Site

Trigger the action if the user’s number of sessions meets the specified criteria.

Configure how long the visitor must be on the site before the action is triggered.

Select whether the number of minutes the visitor is on the site must be greater than, equal to, or less than the specified value.
Specify the number of minutes that determines whether the condition is met.

Traffic Source

Trigger the action if the user’s number of sessions meets the specified criteria.

Specify the source of the visitor’s traffic that must be true for the action to be triggered.

Specify the traffic source.
(Optional) Enable Regex if this is a regular expression.

Technology

Browser

Select the browser the visitor must use for the action to be triggered.

Select one or more of the following browsers:

Chrome
Firefox
Internet Explorer/Edge
Internet Explorer Mobile
Mobile Safari
OmniWeb
Opera
Opera Mini
Opera Mobile
Safari

Device Type

Select the device type the visitor must use for the action to be triggered.

Select one or more of the following device types:

Android
Blackberry
Desktop
iPad
iPhone
iPod
Nokia
Windows Phone

Operating System

Select the operating system the visitor must use for the action to be triggered.

Select one or more of the following operating systems:

Android
Blackberry
iOS
Linux
MacOS
Maemo
Symbian OS
Unix
Windows

Screen Resolution

Select the screen resolution visitors must use on their devices for the action to be triggered.

Select whether the screen resolution width of the visitor’s device must be greater than, equal to, or less than the specified value.
Specify the number of pixels required for the screen resolution width.
Select whether the screen resolution height of the visitor’s device must be greater than, equal to, or less than the specified value.
Specify the number of pixels required for the screen resolution height.

Window Size

Select the window size visitors must use on their devices for the action to be triggered.

Select whether the window size width of the visitor’s device must be greater than, equal to, or less than the specified value.
Specify the number of pixels required for the window size width.
Select whether the window size height of the visitor’s device must be greater than, equal to, or less than the specified value.
Specify the number of pixels required for the window size height.

URL

Domain

Specify the visitor’s domain.

Hash

Specify one or more hash patterns that must exist in the URL.

Multiple hash patterns are joined by an OR.

Specify the hash pattern.
(Optional) Enable Regex if this is a regular expression.
Add any other hash patterns.

Path And Query String

Specify one or more paths that must exist in the URL. This includes the path and the query string.

Multiple paths are joined by an OR.

Specify the path.
(Optional) Enable Regex if this is a regular expression.
Add any other paths.

Path Without Query String

Specify one or more paths that must exist in the URL. This includes the path, but does not include the query string.

Multiple paths are joined by an OR.

Specify the path.
(Optional) Enable Regex if this is a regular expression.
Add any other paths.

Protocol

Specify the protocol used in the URL.

Select one of the following:

HTTP
HTTPS

Query String Parameter

Specify URL parameter used in the URL.

Specify a URL parameter name.
Specify the value used for the URL parameter.
(Optional) Enable Regex if this is a regular expression.

Subdomain

Specify one or more subdomains that must exist in the URL.

Multiple subdomains are joined by an OR.

Specify the subdomain.
(Optional) Enable Regex if this is a regular expression.
Add any other subdomains.

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. You can select from the following options:

Page view
Sessions
Visitor
Seconds
Minutes
Days
Weeks
Months

Sampling

Specify the percentage of the time the condition returns true.

Core extension action types

This section describes the action types available in the Core extension.

Custom Code

Provide the code that runs after the event is triggered and conditions are evaluated.

Name the action code.
Select the language used to define the action:
- JavaScript
- HTML
Select whether to execute the action code globally.
Click Open Editor.
Edit the code, then click Save.

When JavaScript is selected as the language, a variable named event will automatically be available, which you can reference from within your custom code. The event object will contain useful information about the event that triggered the rule. The easiest way to determine what event data is available is to log event to the console from within your custom code:

console.log(event);

Run the rule in a browser and inspect the logged event object in the browser’s console. After you understand what information is available, you can use it for programmatic decisioning within your custom code, send a piece of the event object to a server, and so on.

Custom Code action processing

The Core extension, available to all Launch users, contains a Custom Code action for executing user-provided JavaScript or HTML. It is often helpful for users to understand how rules with Custom Code actions are processed.

Rules using the page top or page bottom events

Code from custom actions is embedded in the main Launch library. The code is written to the document using document.write. If a rule has multiple Custom Code actions, the code is written in the order configured in the rule.

Rules using any event other than page top or page bottom

Code from custom actions is loaded from the server and written to the document using Postscribe . If a rule has multiple Custom Code actions, the code is loaded in parallel from the server, but written in the order configured in the rule.

While using document.write after a page has loaded would typically present problems, this is not an issue for code provided through Custom Code actions. You may use document.write within Custom Code actions regardless of when the code will be executed.

Custom Code Validation

The validator used in the Launch code editor is designed to identify issues with developer-written code. Code that has gone through a minification process—such as the AppMeasurement.js code downloaded from the Code Manager—might be falsely flagged as having issues by the Launch validator, which can usually be ignored.

Action sequencing

When the “Run rule components in sequence” option from property settings is enabled you can have subsequent rule components wait while your action performs an asynchronous task. This works differently for JavaScript and HTML custom code.

JavaScript

When creating a JavaScript custom code action, you may return a Promise from your action. The next action in the rule will be executed only when the returned promise is resolved. If the promise is rejected, the next actions from the rule will not be executed.

Note : This only works when your JavaScript is not set to execute globally. If you are executing your custom code action in the global scope, Launch will treat the promise as immediatly resolved and move on to the next item in the processing queue.

An example of a JavaScript custom code action that returns a promise:

return new Promise(function(resolve, reject) {
  setTimeout(function() {
    if (new Date().getDay() === 5) {
      resolve();
    } else {
      reject();
    }
  }, 1000);
});

HTML

When creating an HTML custom code action, a function named onCustomCodeSuccess() will be available to use within your custom code. You may call this function to indicate that your custom code has completed and that Launch may move on to executing subsequent actions. On the other hand, if your custom code failed in some way, you may call onCustomCodeFailure() . That will inform Launch to not execute the subsequent actions from that rule.

An example of an HTML custom code action that uses the new callbacks:

<script>
setTimeout(function() {
  if (new Date().getDay() === 5) {
    onCustomCodeSuccess();
  } else {
    onCustomCodeFailure();
  }
}, 1000);
</script>

Core extension data element types

Data Element types are determined by the extension. There is no limit to the types that can be created.

The following sections describe the types of data elements available in the Core extension. Other extensions use other types of data elements.

Constant

Any constant string value that can be then referenced in actions or conditions.

Example:

string

Custom code

Custom JavaScript can be entered into the UI by clicking Open Editor and inserting code into the editor window.

A return statement is necessary in the editor window in order to indicate what value should be used as the data element value. If a return statement is not included or the value null or undefined is returned, the data element’s default value will be used as the data element value.

Example:

var pageType = $('div.page-wrapper').attr('class').split('')[1];
if (window.location.pathname == '/') {
  return 'homepage';
} else {
  return pageType;
}

If the custom code data element is being retrieved as part of a rule execution, a variable named event automatically becomes available, which you can reference from within your custom code. The event object will contain useful information about the event that triggered the rule. The easiest way to determine what event data is available is to log event to the console from within your custom code:

console.log(event);
return true;

Run the rule in a browser and inspect the logged event object in the browser’s console. Once you understand what information is available under the various rules that may use your data element, you can use it for programmatic decisioning within your custom code or return a piece of the event object as the data element’s value.

DOM attribute

Any element value can be retrieved, such as a div or H1 tag.

Example:

CSS Selector Chain:

id#dc logo img

Get the value of:

src

JavaScript variable

Any available JavaScript object or variable can be referenced using the path field.

When you have JavaScript variables, or object properties in your markup, and you want to collect those values in Launch to use with any of your extensions or rules, one way to capture those values is to use Data Elements in Launch. This way, you can refer to the Data Element throughout your Rules, and if the source of the data ever changes, you only need to change your reference to the source (the Data Element) in one place in Launch.

For example, let’s say your markup contains a JavaScript variable called Page_Name , like this:

<script>
  //data layer
  var Page_Name = "Homepage"
</script>

When you create the Data Element in Launch, simply provide the path to that variable.

If you use a data collector object as party of your data layer, simply use dot notation in the Path to reference the object and property you want to capture into the Data Element, like _myData.pageName , or digitalData.pageName , etc.

Example:

window.document.title

Local storage

Provide the name of your local storage item in the Local Storage Item Name field.

Local storage gives browsers a way to store information from page to page ( https://www.w3schools.com/html/html5\_webstorage.asp ). Local storage works a lot like cookies, but is much larger and more flexible.

Use the provided field to specify the value you created for a local storage item, such as lastProductViewed.

Page info

Use these data points to capture page info for use in your rule logic or to send information to Analytics or external tracking systems.

You can select one of the following page attributes to use in your data element:

URL
Hostname
Pathname
Protocol
Referrer
Title

Query string parameter

Specify a single URL parameter in the URL Parameter field.

Only the name section is necessary and any special designators like “?” or “=“ should be omitted

Example:

contentType

Random number

Use this data element to generate a random number. It’s often used for sampling data or creating IDs, such as a Hit ID. The random number can slso be used to obfuscate or salt sensitive data. Some examples might include:

Generate a Hit ID
Concatenate the number to a user token or timestamp to ensure uniqueness
Perform a one-way hash on PII data
Randomly decide when to show a survey request on the site

Specify the minimum and maximum values for your random number.

Defaults:

Minimum: 0

Maximum: 1000000000

Session storage

Provide the name of your session storage item in the Session Storage Item Name field.

Session storage is similar to local storage, except the data is discarded after the session ends, whereas local storage or a cookie might retain the data.

Visitor behavior

Similar to Page Info, this data element uses common behavior types to enrich logic within rules or data collection.

Select one of the following visitor behavior attributes:

Landing page
Traffic source
Minutes on site
Session count
Session page view count
Lifetime page view count
Is new visitor

Some common use cases include:

Show a survey after a visitor has been on the site for five minutes
If this is the landing page for the visit, populate an Analytics metric
Show a new offer to the visitor after X number of Session Counts
Display a newsletter sign up if this is a first time visitor

Core Extension

Core extension event types

Browser

Tab Blur

Tab Focus

Form

Blur

Focus

Submit

Keyboard

Key Press

Media

Media Ended

Media Loaded Data

Media Pause

Media Play

Media Stalled

Media Time Played

Media Volume Changed

Mobile

Orientation Change

Zoom Change

Mouse

Click

Hover

Other

Custom Event

Data Element Changed

Direct Call

Element Exists

Enters Viewport

History Change

Time Spent on Page

Page load

DOM Ready

Library Loaded (Page Top)

Page Bottom

Window Loaded

Options

Specific Elements \| Any Element

Elements matching the CSS selector

And having certain property values

Advanced options (Bubbling)

Core extension condition types

Data

Cookie

Custom Code

Value Comparison

Variable

Engagement

Landing Page

New/Returning Visitor

Page Views

Sessions

Time On Site

Traffic Source

Technology

Browser

Device Type

Operating System

Screen Resolution

Window Size

URL

Domain

Hash

Path And Query String

Path Without Query String

Protocol

Query String Parameter

Subdomain

Other

Date Range

Max Frequency

Sampling

Core extension action types

Custom Code

Custom Code action processing

Rules using the page top or page bottom events

Rules using any event other than page top or page bottom

Custom Code Validation