Learn how to create and edit a trigger, and define the evaluation point and rules for firing the trigger.

For hands-on examples of creating different types of triggers, see Trigger examples.

Creating a trigger

To create a trigger:

1. In the Frosmo Control Panel, in the sidebar, select More > Triggers.
2. Click Create trigger.

3. Define the trigger settings.

   

4. When you're done, click Save.

Editing a trigger

To edit a trigger:

1. In the Frosmo Control Panel, in the sidebar, select More > Triggers.
2. In the triggers list, find the trigger you want to edit, and click the trigger name.

3. Edit the trigger settings.

   Before editing the trigger settings, check whether the trigger is in use. In the Edit trigger view, you can view the conversion definitions, placements, and shared code in which the trigger is being used.

4. When you're done, click Save.

Trigger settings

The following table describes the settings you can define for a trigger in the Frosmo Control Panel.

Table: Trigger settings

Figure: Defining the trigger settings

Evaluation point

An evaluation point determines the event on a web page that causes the Frosmo Platform to check whether to fire the trigger. The following table lists the evaluation points supported by the platform.

Table: Supported trigger evaluation points

Rules

Define the rules for firing the trigger. If you define no rules, the trigger is fired every time the trigger event, as defined by the evaluation point, occurs.

The Frosmo Platform supports the following rules:

Cookie

The trigger is fired based on the value stored in a cookie. You can get the value by cookie name.

DOM element

The trigger is fired if there is a specific DOM element on the page. To define the element, add a CSS selector and an attribute or property identifying the element:

• If the value in the field has the prefix prop:, the element node property must match.
• If the value in the field has the prefix attr:, the element node attribute must match.
• If there is no prefix, the system first tries to match properties and then attributes.

Event data

The trigger is fired based on data passed by a predefined event. Specifically, the rule checks whether the value of an event data property matches a value you provide.

This rule is available only for the following evaluation points:

• Core event
• Data layer event
• DOM element ready
• DOM event
• URL change

The available properties on which to base the rule depend on the selected evaluation point and, in some cases, the selected event type. Depending on your selection, you either select the property from a list of predefined properties or manually define the property name.

The following table lists the available properties based on the selected evaluation point and, if relevant, event type.

Table: Available event data properties based on evaluation point and event type

{"foo":{"foo.bar":"1"}}

JavaScript code

The trigger is fired based on your own JavaScript code. The code must return a value to be matched.

JavaScript variable

The trigger is fired based on a JavaScript variable value on the page. The variable must be available on the window object.

If you need to check the value of a nested object property on the page, use dot notation to reference the property, for example, object.object.property.

Local storage

The trigger is fired based on data stored in local storage. You can get the data by the key name.

Page referrer

The trigger is fired when the visitor arrives from a specific page.

You can define the page based on:

• URL: Matches the exact URL of the page. For example: http://www.example.com/index.html
• Protocol: Matches the HTTP or HTTPS part of the URL.
• Domain: Matches the part after the protocol. For example, in the URL http://www.example.com/index.html, the domain is www.example.com.
• Path: Matches the URL path after the domain. For example, in the URL http://www.example.com/index.html, the path is /index.html.
• Anchor: Matches any part of the URL that comes after the "#" character.
• Query selector: Matches any part or the URL that comes after the "?" character. If the query parameter is defined, it will only match a single parameter. For example, in the URL http://example.com/?search=word&count=10, the complete query parameters are search=word&count=10, and the query key for search is word.

Page URL

The trigger is fired on a specific page.

You can define the page based on:

• URL: Matches the exact URL of the page. For example: http://www.example.com/index.html
• Protocol: Matches the HTTP or HTTPS part of the URL.
• Domain: Matches the part after the protocol. For example, in the URL http://www.example.com/index.html, the domain is www.example.com.
• Path: Matches the URL path after the domain. For example, in the URL http://www.example.com/index.html, the path is /index.html.
• Anchor: Matches any part of the URL that comes after the "#" character.
• Query selector: Matches any part or the URL that comes after the "?" character. If the query parameter is defined, it will only match a single parameter. For example, in the URL http://example.com/?search=word&count=10, the complete query parameters are search=word&count=10, and the query key for search is word.

Alias

You can define an alias for a trigger. You can use the alias to bind a JavaScript function to the trigger. For example, use the following code to bind an alias named "myTriggerAlias" to a trigger:

frosmo.easy.events.on('myTriggerAlias', function (trigger) {...});

The bound function will be called every time the trigger fires. The function receives the trigger object as an argument. If you want to call the bound function once, use the frosmo.easy.events.once() function.