New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Still errors from https://www.google-analytics.com/collect? using v2 #50

Closed
hazenet opened this Issue Dec 24, 2017 · 8 comments

Comments

Projects
None yet
2 participants
@jehna

This comment has been minimized.

Show comment
Hide comment
@jehna

jehna Dec 25, 2017

Owner

@hazenet are you sure you don't have any ad blockers on your browser? When I visit hazenet.dk, I don't get any errors and the call to Google Analytics API completes succesfully.

Owner

jehna commented Dec 25, 2017

@hazenet are you sure you don't have any ad blockers on your browser? When I visit hazenet.dk, I don't get any errors and the call to Google Analytics API completes succesfully.

@jehna

This comment has been minimized.

Show comment
Hide comment
@jehna

jehna Dec 25, 2017

Owner

What is this tool that you're using? Pingdom website speed test?

Owner

jehna commented Dec 25, 2017

What is this tool that you're using? Pingdom website speed test?

@hazenet

This comment has been minimized.

Show comment
Hide comment
@hazenet

hazenet Dec 25, 2017

Yeah, the tool is https://tools.pingdom.com where I am testing "https://hazenet.dk" in.

hazenet commented Dec 25, 2017

Yeah, the tool is https://tools.pingdom.com where I am testing "https://hazenet.dk" in.

@jehna

This comment has been minimized.

Show comment
Hide comment
@jehna

jehna Dec 25, 2017

Owner

It's possible that Google Analytics is blocking the Pingdom bot by default (which sounds reasonable), and that could result into 4xx response for the API request. Could this be the reason?

Owner

jehna commented Dec 25, 2017

It's possible that Google Analytics is blocking the Pingdom bot by default (which sounds reasonable), and that could result into 4xx response for the API request. Could this be the reason?

@hazenet

This comment has been minimized.

Show comment
Hide comment
@hazenet

hazenet Dec 25, 2017

Could be. I don't seem to get these errors (or I may not understand completely how to read the information) I my own browser developer view / web inspector / debugger.

hazenet commented Dec 25, 2017

Could be. I don't seem to get these errors (or I may not understand completely how to read the information) I my own browser developer view / web inspector / debugger.

@jehna

This comment has been minimized.

Show comment
Hide comment
@jehna

jehna Dec 25, 2017

Owner

Yep, I can confirm that there's no connection error present when I tested on real Firefox and Chrome on your site.

I checked that Pingdom is using a rather regular user-agent to check sites, so it can be that Google Analytics has just blocked their IP addresses.

Owner

jehna commented Dec 25, 2017

Yep, I can confirm that there's no connection error present when I tested on real Firefox and Chrome on your site.

I checked that Pingdom is using a rather regular user-agent to check sites, so it can be that Google Analytics has just blocked their IP addresses.

@hazenet

This comment has been minimized.

Show comment
Hide comment
@hazenet

hazenet Dec 25, 2017

Okay, thanks for taking the time to test this.
Then the "problem" is purely cosmetic on the tools.pingdom.com website.
Please disregard this issue-thread then.
Merry Christmas

hazenet commented Dec 25, 2017

Okay, thanks for taking the time to test this.
Then the "problem" is purely cosmetic on the tools.pingdom.com website.
Please disregard this issue-thread then.
Merry Christmas

@jehna

This comment has been minimized.

Show comment
Hide comment
@jehna

jehna Dec 25, 2017

Owner

Merry christmas to you too :)

Owner

jehna commented Dec 25, 2017

Merry christmas to you too :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment