http://forums.visokio.com/discussions/tagged/Google/feed.rss Mon, 30 Oct 17 16:35:25 -0400 Tagged with Google - Visokio Forums en-CA http://forums.visokio.com/discussion/2748/connectors-google-analytics-api-definitions Tue, 21 Oct 2014 11:37:57 -0400 panost 2748@/discussions
I have a minor bug to bring to your attention, the "In-market Segment" in the Google Analytics API is declared as "ga:interestMarketCategory" (see attached screenshot), when the correct definition is "ga:interestInMarketCategory"

https://developers.google.com/analytics/devguides/reporting/core/dimsmets#cats=audience

This is quite insignificant as I barely ever need it, but it would be nice if it could be corrected.
I am using the latest 2.9 b1474 (15/10/2014).


On another note, you might be interested in Google's MetadataAPI which provides always up-to-date definitions of columns:
https://developers.google.com/analytics/devguides/reporting/metadata/v3/
not sure if you can build it into Omniscope but it might make things easier between versions!


Also lastly I was wondering if in cases such as this it is possible to build manual patches into connectors, perhaps by editing config files or is there/will there be such developer functionality for connectors?

Many thanks in advance,
Panos
]]> http://forums.visokio.com/discussion/2661/connectors-google-logins-invalid-grant-error Tue, 29 Jul 2014 09:18:33 -0400 chris 2661@/discussions
"error" : "invalid_grant"

This error effects the following connectors:

• Google Analytics
• Google Drive
• Google Spreadsheets
• Google BigQuery
• DoubleClick

This error is generated by the Google server and not Omniscope.

The following link outlines why this error occurs:

https://developers.google.com/analytics/devguides/config/mgmt/v3/mgmtAuthorization?hl=fi#helpme

As described in the link above, the cause of this error is either due to your server clock or the refresh limit being reached. In most cases it is because the refresh limit is being reached.

The refresh limit is controlled by Google and is beyond our control. Here is a summary of how it works:

Every time you enter your client ID/secret and click on the "connect" button in a Google block a refresh-token is generated behind the scenes. This refresh token is saved and used to download data from the Google server. Google have hard-coded a limit of 25 refresh tokens per client ID/secret. What this means is that if you have 26 Google blocks and you connect on each one in order, once you connect on the 26th block the first block's refresh token becomes invalid. If you attempt to refresh the data the "invalid grant" error will be shown.

If you are using the same client ID/client token and are regularly creating and configuring Google blocks you are likely to run into this issue.

We have spoken to Google about this issue and there is no way to change this limit or to get notification when a refresh token becomes invalid.

We will be improving the error message shown when this error occurs. We will also investigate ways that we can get around this issue, perhaps by storing refresh tokens on the server.

In the short term here are a few tips for getting around this issue:

• If you regularly use the Google connectors, create several client ID's/secrets. Maybe create one client ID/secret for production and one for testing.
• If you are using Google connectors in a production system, avoid using the client ID/secret elsewhere
• Keep track of the client ID/secret that you are using and the associated Omniscope files.

We apologise to all our users affected by issue, it appears that Google have recently introduced this restriction and we understand it has caused a great deal of frustration. We will endevour to create a better solution, but in the meantime if you have any further questions please get in touch.]]> http://forums.visokio.com/discussion/2514/sources-google-drive-spreadsheet-connection-error-version-2.9s Tue, 08 Apr 2014 04:16:57 -0400 nuriozlu 2514@/discussions for your information

]]> http://forums.visokio.com/discussion/2284/website-map-ga-integration-problem Tue, 13 Aug 2013 07:56:53 -0400 JfJf 2284@/discussions