In short: Google has shut down v2.3 of the reporting API. The stable branch of this module is being updated to use v2.4 URLs.

Original report by scott_earnest:

When trying to set up a Google account for authorization, I get to the "Grant Access" page on Google. However, when I click the grant access button it returns me to the admin settings screen without any google analytics account information.

I see the following information in the watchdog, which appears to be coming from Google.
Code: 404 - Error: Not Found - Message: Error 404 (Not Found)!!1 *{margin:0;padding:0}html,code{font:15px/22px arial,sans-serif}html{background:#fff;color:#222;padding:15px}body{margin:7% auto 0;max-width:390px;min-height:180px;padding:30px 0 15px}* > body{background:url(// 100% 5px no-repeat;padding-right:205px}p{margin:11px 0 22px;overflow:hidden}ins{color:#777;text-decoration:none}a img{border:0}@media screen and (max-width:772px){body{background:none;margin-top:0;max-width:none;padding-right:0}} 404. That’s an error. The requested URL /analytics/feeds/accounts/default?max-results=1000&oauth_consumer_key=anonymous&oauth_nonce=****************&oauth_signature=****************%3D&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1345752101&oauth_token=****************&oauth_version=1.0&start-index=1&v=2 was not found on this server. That’s all we know.
(I *'d out some info above)

I am also seeing the issue on sites that already have had the Google Analytics Reports set up and authorized. On these sites the reports still run but the admin settings page acts as if the site has not yet authenticated, and the above message appears.

Maybe this url is no longer valid?

Maybe some updates need to be made to ? I can see in version 7 some of the paths have changed for getting the account list.

Please let me know if any more information is needed.


kloewer’s picture

Same, same ind Drupal 7... :(

Dinesh Kumar Sarangapani’s picture

Same here, any update on this issue?

Ilmar’s picture

Same in 7.x-1.2 version.

oturpin’s picture


Just downloaded and installed the Reports module.
This error happens on 7.X v1.2 version. leads to 404 error ...

thameemul.m’s picture

Version: 6.x-1.2 » 7.x-1.1

Modifying to 7.x Version , to get more attention!

scott_earnest’s picture

I am guessing that something along these lines needs to be implemented into the module:

"Management API v2.3 has been shutdown."

oturpin’s picture

Hi Guys,

In the "google_analytics_reports 7.x-3.x-dev" release notes, one can read:

-> Integration with v3 of the Google Analytics API.

That was Posted by raspberryman on April 20, 2012 at 10:46pm

Have to wait a little for release....

Dinesh Kumar Sarangapani’s picture

Agreed with #7, i tried "7.x-3.x-dev" the basic is working fine.

scott_earnest’s picture

Hoping something will happen for 6.x as well.

jakemac53’s picture

Version: 7.x-1.1 » 6.x-1.1

I am also experiencing this issue. I am trying to hack it to work in the meantime, got the accounts request working with the management API (the only one you can use now). The core data api looks like it also needs to be upgraded to 2.4 though sigh.

benschwabe’s picture

So would it be worth working towards getting this module to work with v3.x of so that users can migrate over to oAuth 2.0 in the short term for authentication, then once it's all working, start work on updating the core data api to 3.0.


According to the above, the v2.4 core data api returns v2.3 compatible responses... so it should just work no?

grendzy’s picture

Title: Authentication Issue » Update to v2.4 core reporting API
Version: 6.x-1.1 » 6.x-1.x-dev
Status: Active » Patch (to be ported)

I updated the URLs to point at the v2.4 API: ab045580

Marking for backport. (BTW this is for the 7.x-1.x and 6.x-1.x branches. The experimental 7.x-3.x will provide support for v3.0 of the API).

grendzy’s picture

Status: Patch (to be ported) » Fixed


Version Downloads Date Links
7.x-1.3 tar.gz (18.94 KB) | zip (26.1 KB) 2012-Sep-10 Notes
6.x-1.3 tar.gz (19.48 KB) | zip (26.77 KB) 2012-Sep-10 Notes

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Anonymous’s picture

Issue summary: View changes

summarize current state