The format of a valid css selector is defined by the W3C standards. To put it short you have to follow this syntax for the tsuiseki tracking module: element.classname

Examples

All links that have the class foo:

a.foo

All input fields (e.g. buttons) having the class bar:

input.bar

All links that have the class foo plus all links that have the class bar:

a.foo, a.bar

We provide several ready made solutions (e.g. plugins for Drupal and Wordpress). In addition to that we provide a general PHP based solution that can easily be adapted to an existing PHP website. If you use other technologies do not hesitate to contact us. We are willing to provide your developers with any assistance or may develop the needed functionality for you. Please see our Tsuiseki® integration guide for further informations.

Currently, we provide the following paper.

If you don't want to track a specific path on your website, you need to prevent only that the Tsuiseki tracking is invoked on this path. These paths can be specified in the different integration options (such as Drupal, Wordpress, PHP, etc.).

A request is a recieved query on the tracking server. Thus every tracked view and click is a request.

In short: No, they don't. As we use ajax and javascript to track views and clicks the regular search engine crawler does not generate any requests. If we notice that crawlers are capable of generating requests we will filter these out and you won't be charged for them.

You have to register each subdomain separately (e.g. example.com is not the same as www.example.com).

Please email our technical support team at support@tsuiseki.com