Advanced

  • 2 minute(s) read
Prev Next

This section describes the advanced configuration options.

Settings

Request limitation - Number

Specify the maximum number of requests, which may be sent within the specified period.

Incorrect implementation of the pixel or bot traffic can lead to false requests. To minimize this risk, you have the option of limiting the maximum number of permitted requests.

By default, the request limitation is activated: once the limit of 1000 requests (pages and actions) has been exceeded every 30 minutes, no requests are sent by the pixel for the remaining time.

Please note that you cannot deactivate this function.

Request limitation - Time Interval

Specify the time interval in seconds, in which the specified number of requests can be sent.

Validate Ever ID

The Ever ID is a unique visitor ID that is written in an ever cookie created by Mapp Intelligence. This cookie ID is unique per Mapp Intelligence account and (when using first-party cookies) per domain.

Activate the checkbox, to enable the check whether the generated EverID is valid (correct timestamp). If this is not the case, the EverID will be regenerated.

Request Obfuscation

To minimize the block quota of tracking blockers as far as possible, the recognition of tracking requests for ad blockers is made technically more difficult. This is achieved by

  • A random string is appended to the tracking endpoint (wt) for each request.

  • The order of all tracking parameters (including "p") is randomly generated for each request.

Please note that default disables this feature.


Example

http://q3.webtrekk.net/999955867561122/wtc2l42m?cg3=home&cdbeid=c100fd2bbad6e4c107b39b7861c03060&tz=2&cs1=0&one=0&eid=2153140690100273509&pu=http%3A%2F%2Fdemoshop.webtrekk.com%2F&cg2=de&fns=0&cg1=home&p=507,de.home,1,1680x1050,24,1,1531491500231,0,1647x850,1

Filtering URL Fragments

To ensure a correct analysis, you should make sure that no page URL is recorded, which values differ for individual visitors, such as, a session ID. Should such values within the URL appear, or, as is usual for Java servers, attached with a ";" to a file name, you have the option to filter out these fragments from the page URL using a regular expression.

Example

  • Before filtering 
    A typical URL of a Java server may look as follows:

    http://www.webseite.com/teaser_a.htm;jsessionid=1CBE7F79EF7D681569A3BF30DD0C5D72.jp64?page_id=1

  • After filtering
    With the following configuration, the session ID is filtered out up to the first parameter and replaces it with a "?". The remaining parameters are appended to the file name.
    After the fragments are filtered out, you will get the following URL:

    http://www.webseite.com/teaser_a.htm?page_id=1

Specify a regular expression that locates, for example, the session including the parameters in the URL.

Replacing URL fragments that have been filtered

Replaces the URL fragments, which have been filtered, with the given text.

Pixel sampling factor

Here you can define whether only every n-th user should be tracked on your page.

Activate pre-rendering

Pre-rendering allows you to control whether pages loaded in the background, before a user actively views them, should be tracked. For more information on how it works and its impact on tracking, see here.

Activate tab browsing

Tab browsing allows you to define when a page is considered viewed when users open multiple tabs. For more information on how it works and its impact on tracking, see here.

Activate Web to App tracking

Enabling Web to App Tracking allows the Mapp Intelligence Pixel to recognize tracking requests that originate from a mobile SDK (e.g. Flutter, Android, iOS).

This ensures that user interactions within a WebView are linked to the correct app session and user identity (everId). All tracking data from the WebView is forwarded to the SDK and attributed accordingly.

This setting is required to maintain consistent tracking across app and web contexts, particularly when WebViews are embedded inside mobile apps.

Note

Enabling this feature involves controlled data exchange between the Pixel and the SDK. Make sure to evaluate this option in the context of your app’s privacy and security policies.