403 Forbidden - Analytics Report

Search Home

Home

Support

Analytics Repor...

403 Forbidden

3/11/2013 6:31 AM

John Toennies

Joined: 8/29/2012

Posts: 1

403 Forbidden (United States)

I purchased your module this past Friday. I have created a page and added the module to it. I put in my email address and password for my Google Analytics account and the tracking code from Google. I keep getting a 403 - Forbidden error. I am running on DNN 7.03. I have copied and pasted all three things in to the setup screen so I do not know what I am doing wrong. I am running 45.6.6 of the module

Thanks

3/11/2013 9:45 AM

DNN Module Support

Joined: 8/28/2006

Posts: 2065

Re: 403 Forbidden (Australia)

It could be that you have the wrong code.

The number you should use is the reference number to the account in Google Analytics. Ours looks like this: UA-2072522-2

Also ensure that the login has access to that data.

http://www.interactivewebs.com/blog/index.php/dotnetnuke-modules/analytics-report-support/invalid-data-reportedanalytics-report/

If after all of this, you have no joy. Please use the support tab on this page to contact us and provide the details so we can test.

11/14/2014 11:15 PM

Dave Colbeck

Joined: 7/15/2010

Posts: 3

Re: 403 Forbidden (Canada)

This is an old post, however someone may be interested in this. It is probably because of the 2-step verification (I was having the same problem). If you go into your Google account, under Security, you will dig a bit more to find an option for an App sepecific password. Generate a new App specific password and paste that into the password field. It should connect then.

11/14/2014 11:25 PM

DNN Module Support

Joined: 8/28/2006

Posts: 2065

Re: 403 Forbidden (Australia)

Thanks for the feedback Dave.

1/29/2015 9:33 AM

Jesus Camarillo

Joined: 1/29/2015

Posts: 1

Re: 403 Forbidden (Mexico)

Hi guys! I can't find the place to have a password for apps in Google Analytics (or my account) in order to have it working.

I have an error that is The remote server returned an error: (403) Forbidden

Page 1 of 1

Connect to us