Pirsch Documentation

Appearance

Troubleshooting ​

This is a collection of methods to test if your Pirsch integration is working properly. If you are missing something, please don't hesitate to contact our support.

Make Sure the Snippet Is Installed ​

Before trying other troubleshooting methods, make sure that the snippet is installed on your website if you are using the website integration.

  1. Visit your website.
  2. View your website's source code. You can do this by pressing Cmd + U' on a Mac or Ctrl + U' on Windows and Linux. Alternatively, you can right-click anywhere and select View Source from the context menu.
  3. Search for pirsch.js (using Cmd + F on Mac or Ctrl + F on Windows and Linux). You should be able to find the snippet as shown in the screenshot below. The data-code attribute must match the integration code from the Settings page.

Pirsch Snippet

Test the Snippet Integration ​

To test the script, navigate to your website and open the network tab of the developer tools in your browser (usually F12 or Ctrl/Command + Shift + I). Search for 'hit' and make sure you get a 200 response code in the status column.

Developer Tools

If not, check the identification code and domain you've configured. Also make sure you haven't sent the Do Not Track (DNT) HTTP header, set the disable_pirsch option in your localStorage, or added the script to your site more than once.

Test the Servers-side Integration ​

To test the server-side integration, log any errors returned by the Pirsch API that don't have the HTTP status codes 200 (ok) or 401 (unauthorised). The body of the response will include error and validation messages.

{
    "validation": {
        "field": "error message"
    },
    "error": [
        "error message"
    ]
}
{
    "validation": {
        "field": "error message"
    },
    "error": [
        "error message"
    ]
}

You can simply log the whole body, or parse it and log only parts of it. Here is an example from our JavaScript SDK.

js
client.hit(client.hitFromRequest(request)).catch(error => {
    // Something went wrong, check the error output.
    console.error(error);
});
client.hit(client.hitFromRequest(request)).catch(error => {
    // Something went wrong, check the error output.
    console.error(error);
});

If you don't see any errors and you still don't see any statistics on your dashboard. Make sure all fields in the request are correct.

We block certain IP addresses, so if your service is behind a load balancer or proxy, make sure it's forwarded to your server correctly, otherwise we'll get your server's IP address instead of the visitor's IP address. For example, most reverse proxies will return the visitor's real IP address in the X-Forwarded-For header. Our SDKs help you deal with these situations.

Visits Are Not Appearing on the Dashboard ​

If you don't see your visits on your dashboard immediately, don't worry. There is usually a small delay of a few seconds as we cache page visits before writing them to the database.

In case you don't see your visits appearing after a small delay, make sure you didn't disable Pirsch, have an ad blocker active, a VPN, or modified your DNT or User-Agent headers. In rare cases, your page views might be blocked by our bot filter. Try a different device on a different network in that case.

When running the pirsch-extended.js or pirsch-events.js script in combination with a Single Page Application (SPA) built with frameworks like React, Vue, Angular, Svelte, etc. to track outbound link clicks, file downloads, or custom events, you may run into the problem that certain features do not work.

Page views usually work fine, but tracking custom events or clicks (on an outbound link, for example) may not work. This is because the script may be loaded before the SPA has finished rendering the HTML of your web application. As the script scans the HTML for links and attributes to add events to, it will find nothing, and so will not add any event handlers.

To fix this, you can either delay loading the script, or better yet, use the JavaScript SDK. The SDK gives you full control over when an event is fired from your SPA code.

I Cannot Sign In ​

If you have trouble signing in, try deleting your temporary browser files (cookies and local storage) and clear your cache. This can usually be done from the history settings in most browser. The cache can be cleared by reloading the page using Ctrl/Cmd + Shift + R or Ctrl/Cmd + F5.

To clean up cookies and the local storage, open the developer console (Ctrl/Cmd + Shift + I, F12 or right click - inspect) and navigate to Web Storage (or similar). Select everything in the cookies and local storage tab and delete it.