You can use advanced triggers to track when visitors take very specific actions in a specific context. Learn how to set up your own advanced triggers.
You can mix and match the provided examples and modify them as you please.
The examples below also include suggested setup for visitor scoring, which lets you measure the quality of your traffic sources. You can learn more about them from this article.
The data below, should be entered in the fields in the Advanced Triggers module.
These rules set up a trigger on every view of a product page that is not a landing page in the current session.
Action:
page loaded
Rule 1
– fpdata > page_type
– equals
– Woo Product
Rule 2:
– fpdata > current_session > page_views
– does not equal
– 1
Suggested visitor scoring:
– First action
– Point value: 1
This trigger fires when a visitor is on a product page for longer than 10 seconds and has scrolled at least to the middle of the page.
Attention! When you use this trigger in a complex event, remember to set it, to fire once on a page. Otherwise, it will trigger every second (if the conditions are met).
Actions
– do every second
Rule 1:
– fpdata > page_type
– equals
– Woo Product
Rule 2:
– fpdata > scrolled > max
– greater then
– 49
Rule 3:
– fpdata > activity > total
– greater then
– 10
Suggested visitor scoring:
– First action
– Point value: 5
This trigger fires when a visitor views 5 product pages in one session.
Action:
page loaded
Rule 1:
– fpdata > page_type
– equals
– Woo Product
Rule 2:
– fpdata > current_session > page_types > Woo product
– equals
– 5
Suggested visitor scoring:
– Point value: 3
This trigger fires when a visitor is on a specific page for longer than 15 seconds and has scrolled at least to the middle of the page.
Attention! When you use this trigger in a complex event, remember to set it, to fire once on a page. Otherwise, it will trigger every second (if the conditions are met).
Action:
– do every second
Rule 1:
– fpdata > page_id
– equals
– 111111
Rule 2:
– fpdata > scrolled > max
– greater then
– 49
Rule 3:
– fpdata > activity > total
– greater then
– 10
Suggested visitor scoring:
– First action
– Point value: 5
This trigger fires on the first page that a visitor landed on after clicking a link in a newsletter with campaign name 2025_deal. It will trigger only once in a session.
The URL in this example is https://yoursite.com/?utm_source=newsletter&utm_medium=email&utm_campaign=2025_deal&utm_id=somecampaign
Action:
page loaded
Rule:
– fpdata > current_session > landing_page > url_params > utm_campaign
– contains text
– 2025_deal
Rule 2:
– fpdata > current_session > landing_page > url_params > utm_medium
– contains text
– email
Rule 3:
– fpdata > current_session > landing_page > url_params > utm_source
– contains text
– newsletter
Rule 4:
– fpdata > current_session > page_views
– equals
– 1
Suggested visitor scoring:
– First action
– Point value: between 2 and 5
This trigger fires when a visitor entered the website from Catalunya region in Spain. It will only fire on the first visited page in a session.
Attention. You need to use the geolocation module. In this example we assume that we are using a geolocation provider that tracks country and region of the visitor.
Action:
page loaded
Rule 1:
– fpdata > current_session > page_views
– equals
– 1
Rule 2:
– fpdata > country
– equals
– ES
Rule 3:
– fpdata > region
– equals
– CT
This trigger fires every time the visitor enters the checkout page with the value of products in cart above 500. Currency is not important in this example.
Action:
page loaded
Rule 1:
– fpdata > page_type
– equals
– Woo Checkout
Rule 2:
– fpdata > woo > cart > subtotal
– greater than
– 499
This trigger fires on the checkout page if the customer had previously 3 completed orders with average value over 200 (currency is not important). The current order is not counted since it is not completed yet.
Attention. The data on previous orders is only available the first time the user visits the order confirmation page (and no other page). It will be changed in v 9.3, when the data will be available on all pages.
Action:
page loaded
Rule 1:
– fpdata > page_type
– equals
– “Woo Order Received”
Rule 2:
– fpdata > user > completed_orders_number
– greater than
– 2
Rule 3:
– fpdata > user > completed_orders_average_value
– greater than
– 199