How to exclude traffic from specific URL - matomo

I want to disable tracking traffic data for https://www.example.com/something?utm_source=something
How can I achieve this? I only found a way to exclude parameters, but this is not what I need. (https://piwik.org/faq/how-to/faq_81/)

For example when you have a website with a URL of “example.com”, by default Matomo (Piwik) will track all requests for this website, even those requests for Page URLs that do not belong to “example.com”. If you add the JavaScript tracking code on pages of “another-website.com”, these requests will be tracked in your website “example.com” in Matomo.
It is possible to configure your website in Matomo (Piwik) so that only requests to “example.com” will be tracked, and all other requests ignored. Go to Administration > Websites > click “Edit”. Below the “URLs” field for your website, there is a checkbox “Only track visits and actions when the action URL starts with one of the above URLs.”. If you click this checkbox, and click “Save”, Matomo will then only track requests where the domain and the path is an exact match of one of the URLs you specified for this website. This means each valid subdomain has to be specified separately. For example when the known URLs are ‘http://example.com/path’ and ‘http://good.example.com’, tracking requests for ‘http://example.com/otherpath’ and ‘http://bad.example.com’ are ignored.
from: https://matomo.org/faq/how-to/faq_21077/

Related

Tracking visitors who visited website with a code in url with Google Analytics

I have a React website, I want to build a system that first a code is created for example its "my-special-code-100". I want to track website visitors who entered the website from a url like https://mywebsite.com/../?code=my-special-code-100 and need to track if or if not X 'not signed in' visitor do a successful payment - a button click on specific page - also need to store an account id of the wallet, payment that happened, and need to see trackings of how many visitors of website came with "my-special-code-100"(and other codes) and how many of them made a payment and stored wallet id should be visible for that visited user.
I couldn't be sure how to and is Google Analytics correct tool for this and could you give example what can I use to achieve something like this ? Thanks

How to remove URL Queries in Google Tag Manager for any tag (not only Google Analytics)?

I found a few articles and answers how to strip queries from URLs sent to Google Analytics. How about other services, like Facebook or Hotjar? Is there any way to send them clean URLs?
I aim to maximize the website visitors' privacy and to avoid accidental data leaks.
That does not depend on Google Tag Manager, but on the respective tracking tags.
It works for Google Analytics because the "location" field is explicitly set and can be overridden. Other tags might not offer this as a feature - e.g. many marketing tags infer the page location from the referrer instead of having an option to set the value. Since the referrer is sent in a http header as part of the request for the marketing pixels, it is outside the domain of GTM to manipulate.

How not to log URLs with recovery token using Matomo

We are integrating Matomo (formerly Piwik) to monitor our application visits.
We have a page for users to recover their password, the URL looks like :
https://example.com/pwdRecovery?token=ABCDEFGHIJKLMNOPQRST
Could you confirm that it is unsecure to log the URL containing the recovery token with Piwik ?
It is interesting to gets statistics on this page, that is why I do not want to remove my Matomo Tracking code here, how can I remove the confidential part of the URL in my Matomo's stats ?
Matomo (formerly Piwik) handles this for you, you just need to configure the parameters' name you want to exclude.
Login as the Super User, go to Administration > Manage Websites > Global list of Query URL parameters to exclude field.
Documented on their FAQ :
How do I exclude URL query parameters from the URLs tracked, and from Pages reports?

Piwik Tracking - How to exclude a Single Page from tracking?

is it possible to exclude a Single Page from Piwik Tracking?
We want to get the Statistics without the tracking of some Subpages on the Website.
You can either not execute javascript code on such site (trackPageView) or exclude it (if it is possible to identify this unique site for example using a query parameter). Excluded parameters can be configured in the websites settings in Piwik.

How to add the user name in the url for a Chrome extension?

I am working on a chrome bookmarking extension with google app engine as the backend. I am the only user now but I thought that if in the future there are other users the url needs to include the user name for the extension to interact with the backend. So I was thinking to change
http://ting-1.appspot.com/useradminpage
to
http://ting-1.appspot.com/user_name/useradminpage
where "user_name" is the gmail user id.
But I looked at twitter url and I see that they have
http://twitter.com/#!/user_name/
What is the purpose of "#!"? Is my scheme good enough in this case?
The # in a URL signifies the 'fragment identifier'. Historically this has been used to identify a part of a document identified by an 'anchor' tag, but recently webapp developers have begun to use it to pass information about the page state to Javascript code running in the page. This is used because it's possible for Javascript code to modify the fragment of the current page without causing the page to reload - meaning it can update as you browse through the webapp, and go right back to where you were when you reload the page.
The fragment is not sent to the server when the browser loads a page, so Twitter's server just sees a request for twitter.com; it's up to the Javascript code in the page to examine the fragment and determine what to do after that.
In your particular case, assuming you're using the App Engine User service to authenticate users, you have a number of options for how to distinguish users in your URLs:
Use their email address. In theory this can change, and users may not want their address in a URL they will share. If the URLs are private, this is more or less a moot point.
Use their user_id. This is opaque and reveals no useful information about the user, so it's safe, but it's also meaningless and hard to remember.
Let users pick a nickname for their URLs, like Facebook and other services do, on a first-in, first-served basis.

Resources