Custom triggers let you:
- send custom events to your tracking tools (e.g. when someone visits a product page from a specific ad campaign)
- measure the quality of your traffic sources (with visitor scoring)
- trigger changes to your website (with reactions module)
How to set up custom triggers
Setting up custom triggers is pretty straightforward.
When you enable the “Custom triggers” module, you will be able to set up triggers in sections that look like the one below.
A complete trigger consists of:
- a name
- an initiating action (e.g. click, form submission, page load, etc.)
- conditions that need to be met
- and optionally, point value of the action that this trigger tracks (used in visitor scoring)
“Conditions” section can look like this:
In the first field, you can add paths to JavaScript values on the front-end of your website. We recommend you use values from the fpdata object, but these can be any other JavaScript variables that can be accessed through the “window” object.
The fpdata object contains many variables that you will find useful when setting up a trigger.
When you write the data path, you only need to remember to use the “>” symbol to indicate that some value is inside another one., for example, data located at window.fpdata.page_id should be entered as fpdata > page_id.
How to test triggers
To test triggers, you simply need to:
- turn on the “debug this trigger” option of a trigger you want to test
- save the changes on the page
- open your website in a new tab
- take actions should trigger… the trigger
When your trigger fires, you will see a new entry in the browsers console.
