Apps: Web Data Collection: Building Blocks: Triggers

When AJAX is used on your website an ordinary page load trigger is not adequate to use as the page is not loading. Most of the time only a portion of the page will be updated and this trigger allow you to select the portion of the page that is updating with the on-site widget. When you have selected the element that changes on the page, the trigger will be looking for any update on this specific location and when it sense any content update the execution will take place.

Please be aware that if the content change on your page takes unusual long time the trigger will not execute (generally more than 1 second). If this is the case there are other solutions to this. Please contact Clientcare.

In-page interaction trigger is used when you would like to trigger an Event when a user interacts with a page. A visitor will interact with your web page by the cursor, keyboard or touchscreen. This trigger will let you select an element or an area and a specific action.

Further reading:

How to use the widget

This trigger is very similar to page load, except that it is designed for personalisation. This trigger will display the personalisation as early as possible and will trigger all others applications as a regular page load trigger. For performances reasons, we recommend you to use Page load trigger if you are not using personalisation.

This is the most used web data collection-trigger as it is triggered when a page has been loaded (on a page view). This trigger will assure that all data and tags on the page will be executed before it is triggered.

Just before the visitor switch from one page to another, closes a tab or the whole browser, APSIS web data collection is able to execute an event.

Using the Scroll to element trigger in your Event means that the Event will be triggered when an element is visible in the screen.

This trigger will let you choose an element from the site by using the On-site widget.

You can also specify whether it should be entirely visible or not by switching to Advanced mode. The default is that it doesn't have to entirely visible. 

You can however select "entirely visible", it means that your Event will be triggered only when the whole element is visible in the user's window.

An Event using the scroll to element trigger is actually triggered as soon as the element is visible, which means that it can sometimes be triggered when the page loads, if the user has a high screen resolution and doesn't need to actually scroll to see the element.

The scroll to element trigger is almost always used with the Restrict per visitor or session condition. If it is not used with that condition, the Event may be triggered very often, since it will be triggered on every scroll action.

Further reading:

How to install the onsite widget?

A set of triggers for social actions is available when building Events. These can be used to capture your visitor’s activity on your site connected to social media sites.

In order to use these triggers, you will have to have the Facebook and Twitter widgets included on your site.

Currently, the following actions are available for use inside APSIS Profile Cloud:


  • Comment
  • Share
  • Like
  • Unlike


  • Tweet

One caveat with the social triggers is that they in some cases require recent versions of the social plugins to be installed on your website (in technical terms: javascript and not iframed plugins).

Using the Trigger after X seconds on page trigger in your Event means that the Event will be triggered when the visitor has spent a specific time on the current page.

Double click on the building block after you have dropped it in the Trigger area to enter a threshold in seconds.

Further reading:

Creating your first events