There are three ways to see if your website tracking is working correctly: with tracker debugger, debug mode in Tag Manager or an inspector tool in the browser.
In this article, we’ll explain how to work with each of these methods.
Using tracker debugger in Analytics
To check website tracking with the tracker debugger, follow these steps:
- Open the website you want to track with Piwik PRO.
- Consent to all tracking purposes.
- Add a random parameter to your page URL and reload it. Example:
https://example/?test
.Note: Another way to find your session is to search for visitor ID. Read more
- Copy the URL with the parameter.
- Log in to Piwik PRO.
- Go to Menu > Analytics.
- Navigate to Settings.
- On the left, click Tracker debugger.
- Paste the URL with the parameter into the session filter.
- If website tracking is working correctly, you’ll see your current session and all the events performed.
- Done!
Using debug mode in Tag Manager
To check website tracking in debug mode, follow these steps:
- Go to Menu > Tag Manager.
- Choose the site/app you want to work with. Use the site/app picker in the upper right corner.
- Click Debug.
Tip: To open debug mode, you can also add
?_stg_debug
at the end of your website’s URL. - Your website will open in a new tab with debug mode running.
- Check to see if the container is installed on the page.
- Sync: on or off. It should be on if you use the container for synchronous tags.
- Async: on. It should always be on. It shows the status of the container for asynchronous tags.
Note: Synchronous containers and tags will be discontinued by January, 2025. We recommend removing them and adjusting your setups accordingly. Read more
- Check to see if the tag named
Piwik PRO
was fired. - Click the tag name to see tag details like HTML tag content, tag type, and trigger.
- If the tag wasn’t fired, check to see if the trigger is set as
All page views
. You may also need to check the trigger’s conditions. - Navigate to Events log.
- Find a
stg.pageView
element on the event list and click on it. - Here you’ll see all tags that were fired. If the Piwik PRO tag is among them, the website tracking is working correctly.
- Done!
Using an inspector tool in the browser
To check website tracking using an inspector tool in the browser, follow these steps:
- Open your website.
- Right-click on any element on the website and click Inspect or Inspect Element, depending on the browser you’re using.
- Navigate to Network.
- Refresh the browser.
- Find the
ppms.php
element on the network list.Tip: You may see two types of
ppms.php
elements:ppms.php?action-name=
andppms.php?ping=
.Action-name
is a page view request.Ping
is a request to see if the visitor’s session is still active. The frequency of the ping is set in Piwik PRO tag settings. - Click
ppms.php
and check the following items:- Status code: 202. This means that tracking is working correctly.
- Request URL: This is your Piwik PRO account address.
- Navigate to Payload and check the site ID. It should match the site/app ID you’ve got in Piwik PRO (Where to find it?).
- If you need further information, navigate to Console.
- If the tracking code is broken, you’ll see an error message in the console.
- In Console, you can also use the following calls:
_paq
: if the call returns_paq.push
tracking is working correctly._paq.push(['trackPageView']);
: if it returns undefined tracking is working correctly.
Tip: You can also use an inspector tool to check cookies set by Piwik PRO in your browser. Navigate to Application > Cookies and look for cookies listed here.
- Done!
Reasons for broken tracking codes
If you find a broken tracking code on your website, it’ll be because of one of the following issues:
- Piwik PRO tag, which is responsible for tracking, is turned off.
- Trigger for the Piwik PRO tag is incorrect. It should be set as
All page views
with no additional conditions. - Tracking code has not been installed properly. For more on installing tracking codes, read this article.