http://forums.visokio.com/discussions/tagged/Google_Adwords/feed.rss Mon, 30 Oct 17 14:41:03 -0400 Tagged with Google_Adwords - Visokio Forums en-CA http://forums.visokio.com/discussion/2281/testing-new-google-adwords-connector Mon, 12 Aug 2013 08:49:20 -0400 chris 2281@/discussions
We are now in a position to test a new Omniscope Google AdWords connector.

The Google AdWords API is quite large, and unfortunately we are not Google AdWords users ourselves, so before we start development we need to gather requirements and prioritise key functionality.

If a Google AdWords connector is something you would be interested in, and if you would be prepared to help us develop this connector, please tell us:

• What would you like the connector to do? What types of reports do you want to download?
• What options would you like to see? Please base this on other connectors such as GoogleAnalytics. The more specific the better, for example "A dropdown to select campaign", "A dropdown to select keywords" etc. We would like you to tell us how the Google AdWords connector should work.
• Would you be able to help us out with development by arranging a short screen-sharing session and demonstrating how you use the Google AdWords online application? This will help us get a better understanding of the types of queries being undertaken on the Google AdWords platform and how these might translate to an Omniscope connector.
• Are you able to provide us with a test account that we can use to develop the connector?

Once we have gathered enough requirements we will develop and deploy the connector. This will initially be made available only to users who have registered interest on this forum or who have contacted us privately. Once the connector has been sufficiently tested we will make it available to all Omniscope users.

Chris]]> http://forums.visokio.com/discussion/2576/connectors-google-adwords-and-bing-ads-datas Fri, 30 May 2014 03:48:33 -0400 WassimChammaa 2576@/discussions http://forums.visokio.com/discussion/2951/google-adwords-importing-their-csv-output-into-omniscope Mon, 08 Jun 2015 06:50:51 -0400 daniel 2951@/discussions
The csvs won't load just by dragging and loading in the DataManager space and results in the data coming out with weird symbols. This is because the csvs follow a different set of encoding, you will have to amend this by selecting "UTF-16LE" and change the separator value to "\t". Also make sure to set the Header row accordingly (should be 6, this may vary).

See image below for what the configuration looks like, you can use the "Batch Append File" too but do check to make sure that the header rows are always on the same row number for each file.



]]> 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.]]>