Apps: Web Data Collection

Events that do not trigger will not show up in the Log widget on your site. If you are experiencing this problem, make that you have checked the following things.


  1. Have you saved the event that you are working on? Events must be saved in the event editor before they can be tested in the development mode.
  2. Do you have a trigger for your event? All events need to be configured with one trigger in order to run on your site.
  3. Have you added a condition to restrict your event? Incorrectly configured conditions can prevent your event from triggering.
  4. Are you testing in development or live mode? You must push your event to live before it will be publicly available on your site. If you wish to test your event before that, use the Dev mode bookmarklet.

If you still have problems after completing the steps above, please contact APSIS Client Care for further investigation.


Further reading:

Creating your first Events


To validate the events created is working as expected before deploying to production it must be tested. APSIS provides a tracking widget which is reached by clicking on the “Dev mode (Apsis)” bookmarklets. The widget appears as a symbol in the right-hand corner. Click on the symbol and the widget will unfold. When browsing in dev mode the tracking widget will show all occurring APSIS events.


By browsing on the site and trigger the events that have been built in APSIS, it is possible to see if the event is triggered and working as expected. By clicking on the triggered event in the widget, the widget will visualize the plugins and data dimension used in the event. Hover over the data dimensions and see if the correct values are being used.

Set cookies on


  • Domain of N period
    Will set the cookies on the domain based on the number of periods. Defines the domain depth (domain periods) on which the cookie will be set. For instance if the APSIS script is executed on sub.domain.abc.com, then setting equal 2 will store cookie on domain .abc.com, 3 - on .domain.abc.com, etc. If the APSIS script is executed on sub.domain.abc.co.uk, then setting 2 will lead to an error (as .co.uk is a complex top level domain), 3 - on .abc.co.uk. and etc. Value equal 1 is forbidden to use in any case.
    If your website is using a second level registration, like abc.com, and you want all the subdomains and the domain to access the same data, the setting should be 2. If your website is using a third level registration, like abc.co.uk, and you want all the subdomains and the domain to access the same data, the setting should be 3. No setting will allow to share cookie information’s between abc.com and abc.co.uk, but APSIS cross-domain identification technology can share profile data between them.
    If you want to restrict data to a subdomain, recommended setting is 3 for a second level registration like sudomain.abc.com and 4 for a third level registration like subdomain.abc.co.uk . With 3 periods, yourblog.wordpress.com will not exchange data with anotherblogyoudontown.wordpress.com, or 4 for the .co.uk versions, which will lead to have two different profiles for each visiting browser. This behaviour is also interesting if you think that, depending on your website structure, this can be damageable or counterproductive to the analyse of created profiles, for example in case of domains like country1.company.com and country2.company.com or businessunit1.company.com and businessunit2.company.com.

  • Custom domain
    Will allow you to set the one you want on the dedicated field. This arbitrary setting will have to break any cookie domain settings of all the pages where the script will be executed.


  • Current domain
    will set all APSIS cookies on the current domain or subdomain of the actual page. 


Cookie ID name

Change the name of the cookie storing the APSIS ID. Should not be changed except in case of conflicts.

Sync profile with cloud

Whether the data is to be sent and stored in Profile Cloud. If "no", the Profile Cloud synchronisation will be disabled and absolutely no data will be stored, even if the events are enabled to store in Profile Cloud.


Profile: max local events

Define the maximal number of events stored in the browser in case of communication failure to Profile Cloud. Since data is always sent immediately, the storage is rarely used.


Profile: value max length

Some occasions require limiting the size of the data sent to profile cloud (network issues or old browsers). This setting limits the size of each event value. Every value larger than what´s defined in this setting will not be sent to the profile cloud.


Profile: event max length

Some occasions require limiting the size of the data sent to profile cloud (network issues or old browsers). This setting limits the total size of an event. Event larger than what´s defined in this setting will not be sent.


Bucket used in live

Defines the name of the bucket used in live. Modifying this setting have major implications and should only be modified by a technical admin. Default setting is empty. Contact client care for more info.


Bucket used in dev

Define the name of the bucket used in development mode, useful in case you want to keep your production bucket clean from testing data. Default setting is empty. Contact client care for more info.


Profile host

Defines the domain that is hosting profile cloud.


Cross domain identification

Is a functionality profile cloud is offering. Collect, enhance and share data across all your domains. If activated, the web collection will store the profile-ID independently of the domain. In order to use cross-domain identification, all intended domains must be created under the same bucket.


Force jQuery

Force APSIS to always download jQuery.


JQuery min version

If the version of jQuery already on the website is lower than this setting, APSIS will download a version of the library allowing proper execution. Insertion is made in order to not conflict with the existing library.


JQuery max version

If the version of jQuery already on the website is higher than this setting, APSIS will download a version of the library allowing proper execution. Insertion is made in order to not conflict with the existing library.


Charset

The charset of the web data collection script.


Build type

Defines whether the generated file will be hosted in APSIS production or development servers. This setting is unrelated to the dev/live bookmarklets that will work in all build types. Default is the recommended setting.



Web data collection triggers allow an event definition to be executed when all conditions are met. Conditions and segments control the logic behind the execution while the triggers define the final action the event will execute on, for example on a page load, mouse click, after a certain time etc. All events have to have a trigger. An event can contain several triggers if needed.


Further reading:

For more information about "Building blocks".



Web Data Collection is an APSIS app to access your website. This app allows you to create events, session data, profile attribution, segments and activations on your website.

  • Access the app by opening the collection-app options and click on “Web Data Collection”.