June 2020

June 2020

Google Adwords June 2020 (v1.51)

Panoply is always working to improve our service and our data sources. This update to the Google Adwords data source brings it current with recent changes in the underlying API, including changes to the Search Query Report which affected the Primary Key of the report and the addition of greater historical data ranges. Some of these changes will require action by those clients using the Adwords API data source.

That action includes the following steps:

  1. Delete the table with Search Query Report data. Unless renamed by user it will be called “adwords_search_query_performance_report“.

  2. Verify that the Search Query Report is checked in your Adwords data source.

  3. Manually collect from the Adwords data source. This will recreate the table and will pull in the data.

  4. All data will be historical up to the attribution window

In addition, the changes to this data source affected the primary key. In response we have updated the ID pattern on the Search Query Performance Report by adding a hashed value of the Search term field. The new ID pattern is {campaign_id}*{ad_group_id}*{ad_id}*{keyword ID}*{customer_id}*{Search term hashed}*{Day}

Lastly, we have added options for longer date ranges greater than the last 30-days. These ranges include 30-days, 90-days, 1-year, and 2-years. We have also added the option to choose the attribution window on succeeding data collects with durations of 30-days or 90-days.

Intercom June 2020 (v 1.1)

Revisions in the API for a data source often drive the changes that Panoply makes to allow our users to take advantage of new or changing fields. Changes to the Intercom API have caused Panoply to revise the Intercom data source, and the current version will be deprecated. Any existing connections to the current version of Intercom will continue to function and collect data for 90 days following the release of version 2. All new connections will use version two.

Intercom has merged the two columns “Users” and “Leads” into a single column called “Contacts”. Intercom has also altered their IDs, requiring us to make alterations in order to use {workspace_id}-{id} as the primary key. The default destination of this key is intercom_{workspace_name}_{__resource}.

Additionally, two new columns were added, workspace_id and workspace name, to help users differentiate between workspaces.

Note: every Intercom data source collects one Workspace today. Nevertheless, users should be mindful if they plan to query across tables created by different workspaces.

Getting started is easy! Get all your data in one place in minutes.
Try Free