We have just released a new version of AdWords Extractor. It works with AdWords API v201710 (see the Release notes) and you no longer need your own developer token to use it.
The previous version of the extractor is deprecated and you can use our migration tool which will migrate your AWQL queries. However, you have to reauthorize the extractor and give it access to your AdWords data again. The previous version uses AdWords API v201705 which will be switched off on 28 March 2018.
We have been experiencing temporary technical difficulties today around 9:15 AM CET and 9:20 AM CET.
Some component jobs may have failed as a result. We're investigating the issue and post an update when the root cause is found.
UPDATE 11:35 AM CET Jobs storage was temporarily unavailable for about two minutes. Jobs scheduling wasn't affected and running jobs were waiting until storage came up again so these jobs weren't affected. Unfortunately few orchestrations have failed, we'll do step to prevent this in the future.
Recently we have been hitting quota limits of the Google Analytics API with our extractor. As these limits are shared between all users of the extractor, we decided to add a new authorization option - Custom Authorization.
With Custom Authorization, you can provide your own API keys for the Google Analytics extractor, so you will have your own quota limits. This way you can monitor these limits as you need, and other users won't be affected.
Please check out our step-by-step guide on how to set up Custom Authorization in the Google Analytics Extactor.
In case of any problems or questions, please contact us on support@keboola.com.
As part of our effort to make Keboola Connection an open platform we would like to announce the availability of the Keboola Developer Portal - https://apps.keboola.com/. Some of you may already be aware that it is possible to modify applications in KBC through the Developer Portal API. Now we are adding an application to the API so that you can get things done more easily.
The Keboola Developer Portal is a completely separate application from Keboola Connection. It is region-less because it has no access to customer projects. The Developer Portal provides an authoritative list of KBC applications for each region. Each Keboola Connection stack reads this list regularly. As usual in Keboola, the Developer Portal is done in an API first approach, so everything that the application does can be done programmatically too.
What does the Developer Portal do?
Anyone can
sign up for the Developer Portal. However until you join a vendor or create a new
one, you will not be able to do anything. Both creating and joining a vendor
must be approved. Joining a vendor must be approved by the vendor
administrator, and creating a vendor must be approved by Keboola Tech. Once a
member of a vendor, you can modify and add new applications to that vendor. There's no need to fill a checklist and go through our support. When
you create an application, it becomes immediately available for you to use.
Using the Developer Portal, you can also set up automated
deployment for your application.
Keboola Tech still has some things to do:
Next steps:
Support for MySQL in Keboola Connection is coming to its end. Here's what will happen.
Effective immediately
MySQL Storage Backend (supported until January 2018)
MySQL Transformations (supported until April 2018)
These steps will allow us to deprecate a piece of the legacy infrastructure and focus on the state of the art technologies. The Snowflake storage backend and transformations have significant performance and scaling benefits, so your projects will run faster than on MySQL without any extra charge.
6.7.1. Permitted Use of Client Data. Keboola will only use and will cause all Affiliates and Keboola
employees, agents, subcontractors and representatives to only use Client Data for purposes of performing the
Services. Keboola shall follow Client instructions when processing Client Data and will not use Client Data
other than as authorized by this Agreement.
6.7.1. Permitted Use of Client Data. Keboola will only use and will cause all Affiliates and Keboola
employees, agents, subcontractors and representatives to only use Client Data for purposes of performing the
Services. Keboola shall follow Client instructions when processing Client Data and will not use Client Data
other than as authorized by this Agreement. Client Data which Keboola downloads (with permission granted by
Client during component configuration) from Google, Facebook, Twitter or other third party APIs ("Third Party
Data") are stored and handled the same as Client Data under this Agreement. Third Party Data will not be shared
anywhere (it remains stored securely on Keboola systems) until Client decides to share that data (for example,
by configuring Data writer to Client or third party systems). Client can delete all Third Party Data and data
source configurations from Keboola storage anytime. This section shall be read along side with and be subject to
the provisions of sections 6.9 (Retention and Deletion) and 6.10 (Compliance with Law) of this Agreement.
We're very pleased to announce the arrival of simplified database extractors. (Available for MySQL, MSSQL, PGSQL, Redshift, Snowflake, Oracle and IBM DB2)
Configuring the new extractors can not be any easier. All you need to do is select the tables you want to import and ... that's it!
Facebook is deprecating Marketing API v2.9 on Monday, November 13, 2017 thus any api call to v2.9 will fail with error.
The latest version is now v2.10.
The migration should only require changing the api-version parameter in all existing configurations of our Facebook Ads Extractor. However, since there may be some breaking changes, we strongly recommend to change the api-version in your configurations manually, review any possible changes and take the appropriate actions. For more details on the new version, please read Marketing API Changes in v2.10 in the Facebook API Changelog.
Possible breaking change might be renaming of action_link_click_destination breakdown types as follows:
app_store_clicks => click_to_app_store deeplink_clicks => click_to_app_deeplink website_clicks => click_to_website In other Facebook news, they have announced version v2.11 of Facebook Graph API and Facebook Marketing API, for more info read changelog here.