@Aftabnack opened this Issue on May 31st 2018

Hi,

We are using matomo to track our SPA. Kudos on creating this amazing tool!!
I'm running into a issue off late.
On every client side route navigation I'm setting a bunch of data and calling trackPageView.

    window._paq.push(['setUserId', username]);
    window._paq.push(['setTrackerUrl', url + 'piwik.php']);
    window._paq.push(['setSiteId', '13']);
    window._paq.push(['setCustomUrl', window.location.href]);
    window._paq.push(['trackPageView']);

It tracks couple of actions as soon as I enter the application. But post that every route navigation it makes a request which returns with a status of 307 Internal Redirect and that action doesn't get tracked!

Any idea about what the problem is?

My Setup:

screenshot from 2018-05-31 12-40-14

@Aftabnack commented on May 31st 2018

Sorry to bother. But this is since I had a chrome extension blocking third party trackers!

@Aftabnack commented on May 31st 2018

Should this be documented somewhere on the matomo website?
I searched all over the internet why 307 is happening.
There should be a note somewhere mentioning that ad blockers could mess with tracking!

@mattab commented on May 31st 2018 Member

Never heard before of a 307 request, not sure where this comes from. Adblockers already mentioned in our faq: https://piwik.org/faq/troubleshooting/faq_58/

@Aftabnack commented on May 31st 2018

I'm using Ghostry chrome extension. This somehow intercepts all my outgoing requests to piwik, and responds with a 307.

This is a screenshot of how it looks.
screenshot from 2018-05-31 18-03-01

@Aftabnack commented on May 31st 2018

Maybe I should have just searched for Matomo and Ghostery which would have redirected me to that FAQ.
I was looking for "307 Internal Redirect" with "Piwik/Matomo" which obviously took me nowhere.

Thought this can also be mentioned somewhere accessible. The probability of people looking into their network tab to see what the error is will be small. But devs like me can't resist to dig in. :smile:

This Issue was closed on May 31st 2018
Powered by GitHub Issue Mirror