Google Analytics not displaying any metrics
This topic contains 15 replies, has 4 voices, and was last updated by Paolo 8 years, 1 month ago.
We have moved to a support ticketing system and our forums are now closed.
Open Support Ticket-
AuthorPosts
-
September 12, 2016 at 8:07 am #264610
Pretty sure we have it set up correctly, proper OAuth, project, tracking code, etc., however we can’t seem to get any stats to display for listings. We can see the “Analytics” title and the “Active users” area (even though none show when we’re on) but there are no charts or message that says there are no metrics.
Any idea what we’re missing?
Thanks!
September 12, 2016 at 8:55 am #264625This reply has been marked as private.September 13, 2016 at 9:14 am #265280This reply has been marked as private.September 13, 2016 at 5:51 pm #265606Hi,
I’d say that deactivating momentarily all non GD plugins in this case is strictly necessary. If you simply disabled them, refresh the page if the error is gone and then reactivate them, there will be no problem.
Thanks
September 19, 2016 at 8:13 am #268565Okay, it looks like the complete lack of display was related to the order in which plugins were loading. Now that is resolved, selecting the “Analytics” button returns an error of “{“error”:{“errors”:[{“domain”:”global”,”reason”:”insufficientPermissions”,”message”:”User does not have sufficient permissions for this profile.”}],”code”:403,”message”:”User does not have sufficient permissions for this profile.”}} – See more at: http://www.inmaricopa.com/listing/real-estate-1/pat-lairson/#sthash.CExQYg7I.dpuf”
Checked through all other forum posts with the “does not have sufficient permissions for this profile” reference and tried everything suggested. I was hoping that you could review the screenshots captured from the developer page where API was created and Analytics page where it’s applied. Maybe you will see something obvious that we’re missing? Tried http vs. https and both, added permissions for service account email addresses, had no trouble with the OAuth Client process, etc. Maybe we’re using an incorrect callback URL?
Any ideas would be appreciated.
September 19, 2016 at 8:14 am #268566This reply has been marked as private.September 19, 2016 at 6:04 pm #268897This reply has been marked as private.September 20, 2016 at 12:28 am #269161This reply has been marked as private.September 20, 2016 at 11:27 am #269385What Google email are u logged in with when you are clicking authorize on the GD backend? Does that EMAIL have google analytics permission?
Stiofan
September 20, 2016 at 2:40 pm #269579This reply has been marked as private.September 24, 2016 at 5:15 pm #272652It should be the one account that creates everything, i have never seen the need to add another email. If the one account did not create everything it will not work.
Stiofan
September 26, 2016 at 7:24 am #273033Hi – Sorry, but I’m not sure what that means. We don’t have anything unique about the Google Analytics account and set all parameters per the process outlined in the forum post. It was not working with the primary email so I tried troubleshooting via StackOverflow. One suggestion included:
“Did you give permissions to the service account on your actual GA profile? Admin > View > User Management > “Add permissions for:”
“The service@myapp.com account has full permissions. However, your comment did prompt me to add the actual service account email as well (i.e. XXXXX@developer.gserviceaccount.com), which seems to resolve the problem.”
It didn’t work for us. I can delete the “Service Account” email but then will be back to original. We have both http and https JavaScript origins and Authorized Redirect URLs entered, with screenshots above. Do those look correct to you?
Thanks!
September 26, 2016 at 5:31 pm #273276Hi,
you must use 1 google account to create the Google Analytics account to get the code to track statistic on your website and the same account to create the API keys and connect the application.
If your website uses https you should authorize it ONLY with https, if your site doesn’t use https you should authorize it ONLY with http.
Your website is not using SSL so you should only authorize HTTP. When you’ll move to https, you will need to remove HTTP and add HHTPS to the API authorized referrers.
I just tried on a blank install of WordPress and GeoDirectory following step by step the documentation and it worked like a charm.
We cannot access your Google accounts to check (they’d be blocked), so I’m not really sure how we can better assist you…
Thanks
September 26, 2016 at 11:26 pm #273563Appreciate the extra detail. Will try what you clarified above and if we still have trouble we’ll start over…
Thanks for the great effort, as always!
September 27, 2016 at 7:06 am #273718Okay, it looks like we’ve got it resolved. Back to Stiofan’s comment:
“What Google email are u logged in with when you are clicking authorize on the GD backend? Does that EMAIL have google analytics permission?”
I originally read that to mean “Were we authorizing the API while logged in with the proper Google email?” So finally I logged out of Google altogether and logged in using the main Google account, then logged into the website, navigated to GD and re-authorized, and it works.
Also deleted the https references in the API for now. Thank you again for your patience on this one!
-
AuthorPosts
We have moved to a support ticketing system and our forums are now closed.
Open Support Ticket