Home → General →

Google Analytics Connector

• Edit

birwin

19 May, 2016 02:46 PM

Hey there, I know Google Analytics is changing all the time, so in all likely hood, this is likely due to a change they made, however, I am trying to setup a Google analytics connector. I put in the Profile ID, I click the verification link, get the verification code, paste the verification code, and then get a message " Authorized user does not have access to the Google Analytics profile with id: UA-XXXX"

I checked the logs, and there doesnt appear to be any error logs, and my account has full access.

Is there a work around or anything you can suggest?

Many thanks!

Brendon

1. Support Staff 1 Posted by Tim on 19 May, 2016 03:19 PM

   

   Hey Brendon,

   Based on the message you received:
   

   Authorized user does not have access to the Google Analytics profile with id: UA-XXXX
   

   I'm wondering if you may be using the account ID as opposed to the profile ID. When you have a moment, check out this page and see if obtaining the profile ID through those steps helps you to resolve this error.

   Let us know how things go.

   Thanks!

   • Edit

2. 2 Posted by birwin on 19 May, 2016 04:20 PM

   

   Thanks Tim, you nailed it.

   50$ follow up – I tried doing the manual import, it sits there for a second, and then gives me an error ‘An error occurred: null’

   I don’t see anything in the logs. I’m going to reboot Cascade because it’s been a while and see if that helps – but any suggestions?

   Thanks

   • Edit

3. Support Staff 3 Posted by Tim on 19 May, 2016 05:35 PM

   

   Glad to hear we got past that first issue. As for the NPE you're seeing, those can be tricky to track down. I have seen this error displayed when the Connector is unable to find any data within the date range it's looking for. Is the site you're working with one that has a bunch of data available already (in Google Analytics)?

   One thing we can try is enabling some additional logging in your instance to see if we can get some more context. When you have a moment, try this:

   • Click System Menu -> Utilities -> Logging
   • In the Configure by Category drop down, select Google Analytics Connector
   • Verify that the drop down menu next to it says DEBUG
   • Click Add/Update Category
   • Attempt your GA Connector sync
   • After it fails, grab your latest cascade.log file and attach it here

   Thanks!

   • Edit

4. 4 Posted by birwin on 19 May, 2016 05:58 PM

   

   Hmm, well there definitely should be data! Lots and lots of it haha.

   It appears our cascade stopped logging to the cascade.log file last July unfortunately hmmm. I copied some of the data out of the tomcat terminal log. Hopefully it is of use.

   Cheers,

   Brendon

   • log_info.txt 18.7 KB
   • Edit

5. Support Staff 5 Posted by Tim on 19 May, 2016 06:08 PM

   

   Thanks for including that. I'm going to look into some of the logging shown here and I'll let you know if I have any ideas.

   • Edit

6. Support Staff 6 Posted by Tim on 19 May, 2016 06:21 PM

   

   Hey Brendon,

   Based on where this logging ends, it seems to me that you're running into the known issue I mentioned. Specifically, I'm guessing that there isn't any data between 2014-05-18 and 2015-05-18 for the profile in question. Can you verify when you have a chance?

   Thanks

   • Edit

7. 7 Posted by birwin on 19 May, 2016 07:16 PM

   

   From what I can see – I do have the data for that time frame.

   [cid:[email blocked]]

   • image001.png 114 KB
   • Edit

8. 8 Posted by Bradley Wagner on 19 May, 2016 08:46 PM

   

   hi, can you confirm that what you're looking at above is using the same Profile/Webview as what the connector is using ga:109647133? It's possible though unlikely that we experienced a temporary interruptiion.

   • Edit

9. 9 Posted by birwin on 02 Jun, 2016 01:53 PM

   

   Hi Bradley, you can close this. Its working now. Many thanks!

   • Edit

10. Support Staff 10 Posted by Tim on 02 Jun, 2016 01:54 PM

    

    Thanks for the update, Brendon. Glad to hear you were able to get things working!

    • Edit

11. Tim closed this discussion on 02 Jun, 2016 01:54 PM.