Trigger types – overview
January 29, 2018
There are two settings that can be used for every trigger type, firing when specific conditions are met and firing on the specific audience.
All Visitors vs when conditions are met
Every trigger in PPTM can either fire whenever it’s able to (its main condition is met) or it can have additional conditions (or set of conditions) added that have to be met before triggering a tag.
The conditions can be chosen from the dropdown list, some of them are trigger-specific (ex. Click ID for the Click trigger or form ID for the form submission trigger) and the rest are common for all trigger (ex. Page URL, Piwik Campaign, Traffic source etc.) Every variable set in PPTM can also be used as a triggering condition.
To use additional conditions just check the radio button „Fire tag when conditions are met” You can choose multiple conditions that all need to be met to fire the tag (AND type connection).
Trigger on audience member visit
Another option that can be added for each trigger is to fire it only when the visitor is part of a particular audience. The audiences are part of the Piwik PRO Data Management Platform and you can define them inside the DMP platform. To learn more about Audiences, go here:
There are seven types of triggers:
The Page View trigger is the first and most basic type of trigger. It fires the tag with each newly opened page. It has a couple of additional options that additionally adjust the trigger:
First of all, you can decide at which exact moment of the page loading the tag should be triggered, there are three possibilities:
Next option lets you choose how many times the tag should be fired for the same visitor:
Click trigger simply fires the tag whenever the left mouse button is pressed by the visitor. While there may be few use cases requiring firing tag with every click, this feature is super useful when combined with additional conditions (especially click ID and click Classes) allowing tracking clicks to various buttons on our website that does not cause the page reload. It can be combined with the Virtual Page views to allow tracking of Single Page Applications. You can read more on this here:
This trigger will fire a tag whenever a form on a page is submitted (usually by clicking on submit Button) It can either fire with every submission or it can be set to work with only particular forms (selected by the form ID or other means available in the condition selector)
The event trigger can be used to fire a tag whenever a particular data layer event happens.
To create a data layer trigger you’ll need to provide a name (or part of the name) of the event. You can use the debug tool, to check the event’s happening on your website:
This trigger allows you to serve a tag whenever your visitor scrolling will reach a particular point on the page. The scrolled amount can either be set corresponding to the % of the whole page or simply a number of pixels (px).
The Page scroll can be fired every time the set amount is scrolled, only once per page view or only once per the whole visit. In the last case, the visit length has to be set in a similar way as for the page view triggers.
This trigger is often the last thing that you can serve before a visitor leaves your website. It will fire whenever the mouse cursor will leave the browser area.
It can be set to either fire on exit intent (cursor leaving via the top bar – suggesting that the visitor wants to close the tab or the whole browser) or whenever cursor leaves through any side of the browser. A simple use case here is the last resort when you can try to change the mind of the visitor and make him stay, for example with a pop-up window.
This tag has the same additional option as the Page Scroll allowing to choose if it should be fired fire multiple times, once per page view or once per session.
The last type of trigger is a timer which will fire a tag whenever a visitor spends the set amount of time on page, the times can be chosen from the dropdown list and can vary between 3 seconds and 5 minutes.