Pages

Versions Compared

Old Version 20

changes.mady.by.user Timo Lagus

Saved on

compared with

New Version Current

changes.mady.by.user Timo Lagus

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from this space and version 17.6

...

Evaluation pointOptionsDescription
Core eventEvent

A specific Frosmo Core event has occurred.

If you select this event, also define the event type. You can select from the following event types:

  • Conversion
  • Frosmo custom action
  • Modification display
  • Modification click
  • Modification true display
  • Session start
  • Other predefined event
  • Product purchase
  • Visitor location change
Note

By default, Visitor location change does not work on mobile devices. To enable the event for mobile devices, contact Frosmo support.


Info

Visitor location change is evaluated in the beginning of each visitor session. The Frosmo Platform does not detect location changes in real time.


Info

Other predefined event can be any event on the site. If you select Other predefined event, enter the name of the event.


Data layer event

Data has been pushed to the data layer.

Every dataLayer.push() call on a page triggers this event.

DOM element ready

Element

Timeout (seconds)

A specific DOM element has been loaded and parsed, and is ready to be manipulated.

If you select this event, also define the element whose readiness fires the trigger and, optionally, the timeout (in seconds) after which the Frosmo Platform stops trying to fire the trigger. Define the element using a CSS selector; jQuery selectors are not supported. If you define no timeout (or set it to "0"), the platform keeps trying indefinitely.

DOM event

Event

Element

A specific DOM event has occurred.

If you select this event, also define the event type and the element to which the event must happen. Define the element using a CSS selector; jQuery selectors are not supported. You can select from the following event types:

  • Click
  • Key down
  • Key press
  • Key up
  • Submit

For example, to fire the trigger on a link click, select Click as the event type, and define the element with the CSS selector "a".

DOM ready
All DOM elements have been loaded and parsed, and are ready to be manipulated.
Frosmo script loaded

Frosmo Core has been loaded and is ready to be initialized.

Note

At this point, some DOM elements may not yet be available.


Frosmo script ready

Frosmo Core has been initialized.

Frosmo context data (visitor data stored in frosmo.easy.context) has been loaded, segmentation has taken place, and the Frosmo custom script can now be initialized.

Note

At this point, some DOM elements may not yet be available.


JavaScript variable ready

Variable

Timeout (seconds)

A specific JavaScript variable defined in the window object has been loaded and is ready to be manipulated.

If you select this event, also define the variable name and, optionally, the timeout (in seconds) after which the Frosmo Platform stops trying to fire the trigger. If you define no timeout (or set it to "0"), the platform keeps trying indefinitely.

Tip

If you need to check the value of a nested object property, add a JavaScript variable rule to the trigger, and define the nested object property as the variable using dot notation (for example, object.object.property or object.object["property"]).


URL change

A URL change through the hashchange or popstate event has occurred.

Note

The URL change event is supported only for single-page applications and works only for as long as there is no new page load.

To use the URL change event, single-page application support must be enabled in the Frosmo custom script. To set up single-page application support, contact Frosmo support.

For more information about the hashchange and popstate events, see hashchange event and popstate event at MDN.

...

Evaluation pointEvent typeEvent data propertiesDescription
Core eventConversion
  • Conversion ID
  • Conversion type
The trigger is fired when a conversion event with the specified ID or type occurs.
Frosmo custom action
  • Custom action name
  • Custom action value
The trigger is fired when a custom action with the specified name or value occurs.
Modification display/click/true display
  • Modification ID
  • Variation ID
  • Variation type
  • Variation content
The trigger is fired when a modification with a matching ID or variation ID, type, or content receives a display, click, or true display.
Other predefined eventDepends on the event data.The trigger is fired when the specified event occurs. The event can be any event on the site.
Product purchase
  • Product ID
  • Product value
The trigger is fired when a transaction with the specified product ID or value occurs.
Visitor location change
  • Country
  • IP address
  • Internet service provider
  • Latitude
  • Longitude

The trigger is fired when the visitor's location data matches the specified rules in the beginning of a visitor session.

Note

The By default, the visitor location change event does not work on mobile devices. To enable the event for mobile devices, contact Frosmo support.


Data layer eventAnyDepends on the event data.

The trigger is fired when the specified data has been pushed to the data layer.

Tip

If you use the Event data rule with the Data layer event evaluation point, define both the name and value of the property. You can use either dot notation or bracket notation to access a nested property (for example, foo.bar or foo["bar"]).

Note the following:

  • If you define a property name that contains one or more periods (for example, foo.bar), the name is treated as a dot notation reference to an object property. If, instead, you want the name to be treated as a string that contains periods, use bracket notation and wrap the name in quotation marks (for example, ["foo.bar"]).
  • If you use an integer as a nested property name in dot notation (for example, foo.1), the integer is normalized into an array reference (for example, foo[1]).
  • When you save the trigger, the property name may get normalized or trimmed depending on the notation and syntax you've used, so don't be surprised if the name looks a little different when you open the trigger settings again.

Example of the expected event data object when the property is foo["foo.bar"] and the data value is "1":

Code Block
languagejs
themeRDark
{"foo":{"foo.bar":"1"}}



DOM element readyAny
  • Element ID
  • Element classes
  • Element HTML
  • Element text
  • Element property
The trigger is fired when a DOM element with the specified ID, class, HTML content, text content, or property has been loaded and rendered on the page.
DOM eventAny
  • Element ID
  • Element classes
  • Element HTML
  • Element text
  • Element property
The trigger is fired when a DOM event for an element with the specified ID, class, HTML content, text content, or property occurs.
URL changeAny
  • Current URL
  • Previous URL

The trigger is fired when a URL change through the hashchange or popstate event occurs.

Note

The URL change event is supported only for single-page applications and works only for as long as there is no new page load.

To use the URL change event, single-page application support must be enabled in the Frosmo custom script. To set up single-page application support, contact Frosmo support.


...