Last post 6 hours 41 min ago

Posts last week 94

Average response time last week 34 min

All time posts 67911

All time tickets 10496

All time avg. posts per day 20

Helpdesk is open from Monday through Friday CET

Please create an (free) account to post any question in the support area.

Please check the development versions area. Look at the changelog, maybe your specific problem has been resolved already!

All tickets are private and they cannot be viewed by anyone. We have made public only a few tickets that we found helpful, after removing private information from them.

#1320 – Google Analytics

Posted in ‘sh404SEF’

This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Thursday, 05 November 2015 12:09 UTC

ifootpath

Hi

I have tried to connect to Google Analytics and get the following error message

Zendshl_Http_Response Object
(
[version:protected] => 1.1
[code:protected] => 400
[message:protected] => Bad Request
[headers:protected] => Array
(
[Vary] => Array
(
[0] => Origin
[1] => X-Origin
)

[Content-type] => application/json; charset=UTF-8
[Content-encoding] => gzip
[Date] => Thu, 05 Nov 2015 12:02:58 GMT
[Expires] => Thu, 05 Nov 2015 12:02:58 GMT
[Cache-control] => private, max-age=0
[X-content-type-options] => nosniff
[X-frame-options] => SAMEORIGIN
[X-xss-protection] => 1; mode=block
[Server] => GSE
[Alternate-protocol] => 443:quic,p=1
[Alt-svc] => quic=":443"; p="1"; ma=604800
[Connection] => close
)

[body:protected] => �5�1
�0н��z��G5��("�]�߻1"j�Dl~H1�k�w~ʊ��ݪm�
:��E6��I/��,AR

I have tried to set everything a couple of times and it all looks correct - including adding the code.
(I seem to recall somewhere that this may not work in the UK?)

Many thanks

Friday, 06 November 2015 09:12 UTC

wb_weeblr

(I seem to recall somewhere that this may not work in the UK?

I'd be surprised there are country limitations, this is just Google analytics API being used.

[message:protected] => Bad Request

That's pretty surprising erro, it hints more towards a problem on the server.

Adding the code is only the first part, for collecting data. To display reports (this is what you want to do, right?), you need to do the authorization procedure. Did that went well?

Rgds

Friday, 06 November 2015 09:35 UTC

ifootpath

Ok

I have tried authorisation again and still an error

I have another component that also calls Google through an API using the same authorisation - JSitemap Pro - when I try to authorise I get the following error

Warning
Error calling GET https://www.googleapis.com/analytics/v3/management/accounts/~all/webproperties/~all/profiles?key= (removed) : (403) This service is not available from your country

(I removed the key)

So my guess is that it may not work in the UK? Just wondered if any other users from the UK have the same issue?

- by the way - really like the latest version - excellent! I am just a novice with Joomla and but I enjoy using your sh404SEF

Friday, 06 November 2015 10:52 UTC

wb_weeblr

Hi

Well that's not the same error and no, you're the first to report anything like this, whether from the UK or elsewhere.

Again, the message is not the same, so I wouldn't infer at this stage the problem is identical.

What you have is:

[code:protected] => 400

[message:protected] => Bad Request

Bad request means that the request we sent is malformed, incorrect, etc

That may be a result of an earlier request (the https://www.googleapis.com/analytics/v3/management/accounts... being denied) and the second one failing for having a wrong account id (the first request is needed to fetch your internal analytics account id, we do the same as JSitemap).

I have not found any info on this feature not being available in the UK from Google.

Maybe you need to wait a few hours?

When you try again, and before trying, I'd suggest you clear the Joomla cache, as we store some data there. Go to Joomla System menu > Clear cache, and clear anything related to sh404SEF there.

Rgds

Rgds

This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.