http://forums.visokio.com/discussions/tagged/Connectors/p1/feed.rss Mon, 30 Oct 17 13:15:54 -0400 Tagged with Connectors - Visokio Forums en-CA http://forums.visokio.com/discussion/3212/flashtalking-connector-issues Fri, 03 Feb 2017 06:03:23 -0500 chris 3212@/discussions
The Flashtalking block is currently not working. This is due to an upgrade to the Flashtalking API. We have discussed this issue with Flashtalking and have implemented a fix. The fix is currently being tested in a private release, and will be integrated shortly.

Appologies for the inconvenience.

Chris]]> http://forums.visokio.com/discussion/3211/moat-connection Tue, 31 Jan 2017 11:05:24 -0500 JamesPC 3211@/discussions https://moat.com/) connection (like Integral) would be something I would be interested in. I have a contact who might be able to provide details on API connection]]> http://forums.visokio.com/discussion/2810/connector-integral-ad-science Mon, 12 Jan 2015 08:29:09 -0500 tjbate 2810@/discussions
We now have received some additional client interest in a Connector for Integral Ad Science ( http://integralads.com )

Please indicate your own interest, and post any specific requirements for the API Connector you may have.]]> http://forums.visokio.com/discussion/3189/omniscope-tls-1.1-support-for-https-salesforce-api-connections Thu, 17 Nov 2016 08:38:53 -0500 guillem 3189@/discussions
For old versions of Omniscope, Salesforce Input and Output blocks may show the following warning message:

Salesforce API error
TLS 1.0 has been disabled in this organization. Please use TLS 1.1 or higher when connecting to Salesforce using https.

In order to comply with this update, Omniscope has to be updated to the latest version available (b1835) from the downloads page.

For more information, please visit Salesforce Update Documentation.]]> http://forums.visokio.com/discussion/3175/data-sources-new-doubleclick-connector Fri, 23 Sep 2016 06:09:28 -0400 chris 3175@/discussions
At the moment this will be a straight port of the DFA DoubleClick connector in DataManager1. Please let us know if you would like us to add any additional features/reports in the new connector. Also, let us know if you would like a demonstration of the new connector once it is complete.

Chris]]> http://forums.visokio.com/discussion/3122/idea-connectors-microsoft-dynamics-crm Tue, 26 Apr 2016 08:08:41 -0400 tjbate 3122@/discussions http://forums.visokio.com/discussion/3153/flash-talking-connector-not-working Thu, 21 Jul 2016 12:05:49 -0400 JohnMR 3153@/discussions
I'm trying to access the Flash Talking Connector but every time I try to connect I get this error: "va6l: script_error".

The message states: "An unknown error occurred. va6l: script_error This may be a fault with Omniscope, or an unanticipated external error. Please submit an error report.".

I've search and can't seem to find anything wrong. What could it be?

Your help is much appreciated.]]> http://forums.visokio.com/discussion/2900/connectors-facebook-atlas-transition-from-microsoft-platform Wed, 01 Apr 2015 07:38:54 -0400 tjbate 2900@/discussions
We understand this will be temporary until the Facebook version of the API is fully enabled. Please post here to let us know who you are and what you have been told by Facebook Atlas to do by way of workaround.]]> http://forums.visokio.com/discussion/3081/connectors-doubleclick-deprecations Fri, 22 Jan 2016 07:45:04 -0500 daniel 3081@/discussions
https://developers.google.com/doubleclick-advertisers/reporting/deprecation?hl=en


The email that was sent:

Hello,

You’re receiving this email because our records show that your DoubleClick Campaign Manager user profile has accessed version 2.1 or earlier of the DCM/DFA Reporting and Trafficking API within the last 30 days. If you do not manage this API for your DCM advertiser, please forward this email to the appropriate users for your organization.

As we announced in November with the release of v2.3 of the DCM/DFA Reporting and Trafficking API, we will be sunsetting versions 2.1 and earlier of the API on February 29, 2016. You can read our announcement
here:
http://googleadsdeveloper.blogspot.com/2015/11/announcing-v23-of-dcmdfa-reporting-and.html.
Please note that all API requests to versions 2.1 and earlier will no longer work after this date, preventing you from updating and accessing information in DCM.

To avoid an interruption in service, all DoubleClick users are required to upgrade their application to use version 2.2 or later of the API by February 29, 2016. If you haven’t yet started upgrading, we strongly encourage you to do so.

You can get started by using our updated client libraries, available at https://developers.google.com/doubleclick-advertisers/reporting/libraries,
to get up and running quickly. You can also learn more information about the new, regular deprecation schedule for older versions of the API here:
https://developers.google.com/doubleclick-advertisers/reporting/deprecation.

If you have questions, please post on the developer forum at https://groups.google.com/forum/#!forum/google-doubleclick-for-advertisers-api,
or contact DCM API support at dcmapi-support@google.com.

Sincerely,

The DoubleClick Campaign Manager API Team

Google Inc. 1600 Amphitheatre Parkway, Mountain View, CA 94043
]]> http://forums.visokio.com/discussion/3010/idea-new-connector-adform Tue, 06 Oct 2015 06:31:39 -0400 alexandervolk 3010@/discussions
We ourselves are using AdForm, as well as GroupM all across Scandinavia and Germany and other big agency networks. They’re currently moving into the US market as well.

Would anyone else be interested in having an AdForm connector in Omniscope?]]> 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/2519/idea-kenshoo-api-connector Tue, 15 Apr 2014 05:42:56 -0400 chris 2519@/discussions
If a Kenshoo connector is of interest we would be interested in identifying the key requirements. How do you see the connector working? What options would you like? Please provide us with as much detail as possible. It might be useful to describe the connector functionality int terms of which options you would like to see, for example if I was describing the Atlas connector I might say:

- An option to select the Agency/Branch/Client/Advertiser.
- Optional filtering by Action tag/Media plan/Buy/Cost package/Placement.
- An option to select the date range.
- Dimension/metric selection.

Any information you provide will be forwarded to Kenshoo and will also be used when the connector is developed.

Please let us know if you have any questions.

Chris]]> http://forums.visokio.com/discussion/2865/feeds-yahoo-financial-data-not-feeding-data-as-normals Wed, 11 Mar 2015 05:08:17 -0400 naruemon 2865@/discussions
Omniscope 2.9 build 1597]]> http://forums.visokio.com/discussion/2868/idea-connector-for-infegy Wed, 11 Mar 2015 07:31:41 -0400 tjbate 2868@/discussions http://forums.visokio.com/discussion/1551/idea-connector-for-appnexuss Wed, 16 May 2012 12:00:41 -0400 tbobker 1551@/discussions http://forums.visokio.com/discussion/2788/new-connector-celtra-mobile-adserver Mon, 15 Dec 2014 12:38:31 -0500 Paolo 2788@/discussions We would like to use Omniscope with Celtra mobile adserver (http://www.celtra.com/)
Is it possible to set up a connector for this?

Thank you very much
Paolo]]> http://forums.visokio.com/discussion/2221/idea-sources-json-filess Tue, 02 Jul 2013 08:04:43 -0400 ChloeWalton 2221@/discussions http://forums.visokio.com/discussion/2819/idea-connector-amazon-simple-storage-service-s3- Fri, 16 Jan 2015 06:26:05 -0500 tjbate 2819@/discussions
More detail on S3 is here: http://aws.amazon.com/s3

Please vote to register your interest in integrating Omniscope more closely with S3 and provide your use case, e.g. "we want to upload millions of rows to Redshift, but Amazon says the best way to do this is via copy from S3"...]]> http://forums.visokio.com/discussion/2809/google-analytics-feed-user-id-web-tracking-function Fri, 09 Jan 2015 10:34:34 -0500 DominicChan 2809@/discussions
We have been using the Google feed for some high-level MI on our web traffic via Google Analytics.

We have recently enabled UserID Web Tracking function in GA ( https://support.google.com/analytics/answer/3123666?hl=en-GB )

I had a quick play around in the Omni Google feed block and couldn't find this functionality. First question is if this is something already available in Omniscope? Do you know of this function in GA and how Omniscope can be set up to utilise this UserID function?

I am getting a tech demo from our developers on Monday, so will get more info and functional understanding of the UserID functions/data extraction method in GA.

Thanks
Dom ]]> http://forums.visokio.com/discussion/1568/connectors-facebook-api-ads-feeds Mon, 28 May 2012 11:51:36 -0400 renzo 1568@/discussions What about you?

https://developers.facebook.com/docs/reference/ads-api/]]> http://forums.visokio.com/discussion/2650/idea-connectors-doubleclick-dcm-reach-report Thu, 17 Jul 2014 07:14:56 -0400 daniel 2650@/discussions
https://developers.google.com/doubleclick-advertisers/reporting/v1.3/dimensions#reach-metrics
]]> http://forums.visokio.com/discussion/2663/connectors-omniscope-appnexuss Wed, 30 Jul 2014 12:37:02 -0400 beck 2663@/discussions 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/2659/connectors-querying-apiss Tue, 29 Jul 2014 02:28:57 -0400 acdewinter 2659@/discussions
I have a random question, is there perhaps a way for Omniscope to connect to public/private API's and pull data that way, or is the complexity of how API's operate in general out of scope?

Regards
Adrian]]> http://forums.visokio.com/discussion/2552/connectors-google-analytics-api-definitions-updates Thu, 08 May 2014 10:03:03 -0400 panost 2552@/discussions
I was trying to get the DeviceCategory dimension, which was added on 12/12/2013, but definitions have not been updated from the depricated columns.

The one I have been looking at is this

"These dimensions and metrics have been deprecated.

Dimension - ga:isMobile - Use ga:deviceCategory instead (e.g., ga:deviceCategory==mobile).
Dimension - ga:isTablet - Use ga:deviceCategory instead (e.g., ga:deviceCategory==tablet).
Metric - ga:entranceBounceRate - Use ga:visitBounceRate instead.
"

...but there was another release last month, so if you could do a bigger update and incorporate those changes as well that'd be great!

https://developers.google.com/analytics/devguides/reporting/core/v2/changelog

Thanks
Panos]]> http://forums.visokio.com/discussion/2568/connectors-googleanalytics-updateschanges Fri, 23 May 2014 12:21:08 -0400 chris 2568@/discussions
In the next release of Omniscope 2.8 (b1248) and Omniscope 2.9 (1271) we have updated the GoogleAnalytics connector.

The following is a summary of the changes we have made:

• We have changed the section order/names, for example "Visitor" has now become "User".
• We have removed some deprecated metrics/dimensions, for example "Visitor type".
  
• We have added several new metrics/dimensions, for example "Goal conversions", "App Tracking", "Audience" etc.
  
• We have changed the names of some of the metrics/dimensions, for example "Search keyword" has been changed to "Search time". These changes have been made so that the names used inside the connector are now inline with the names used in the GoogleAnalytics website.
  

This has been a fairly substantial overhaul, and it may impact any pre-configured reports that use GoogleAnalytics as a source, particularly if you have specified any dimensions/metrics that have been removed/replaced.

Once the version listed above is available on the Visokio website please download and check your report output and if necessary re-configure any downstream blocks in your DataManager workflow to accommodate the changes.

If you have any questions or encounter any problems please let us know.

Chris]]> http://forums.visokio.com/discussion/2464/connectors-doubleclickdfa-api-versions Thu, 06 Feb 2014 06:12:12 -0500 ALC 2464@/discussions
Thanks
Anna
]]> http://forums.visokio.com/discussion/2537/connectors-google-analytics-client-id-login-errors Tue, 29 Apr 2014 06:08:12 -0400 Valentina 2537@/discussions
I have created a Google billing account but the client ID and Secret do not seem to work.

I receive the error: Please log-in to Google.

Any ideas how to sort this problem?]]> http://forums.visokio.com/discussion/2502/connectors-facebook-atlas-paid-search-report-2.9- Wed, 26 Mar 2014 12:33:07 -0400 chris 2502@/discussions
In tonight's Omniscope 2.9 release (b1053) we have added the ability to select the report type in the Facebook Atlas connector. You now can choose from "Web media report" and "Paid search report".

The "Web media report" is the default report that was supported in older versions of Omniscope.

The "Paid search report" is a new report that mirrors the paid search report in the web interface.

Please let us know if you have any questions about this, or if you have any ideas for improving the Atlas connector.

Chris]]> http://forums.visokio.com/discussion/2465/idea-connector-elastic-search-kibanas Fri, 07 Feb 2014 09:23:22 -0500 powellblyth 2465@/discussions
We pull a lot of real-time data into Elastic Search, it would be awesome to be able to connect visokio to this to pull the later stats. We total live search reports per day etc]]>