Mailshake to Google Data Studio

This page provides you with instructions on how to extract data from Mailshake and analyze it in Google Data Studio. (If the mechanics of extracting data from Mailshake seem too complex or difficult to maintain, check out Stitch, which can do all the heavy lifting for you in just a few clicks.)

What is Mailshake?

Mailshake lets sales teams build cold outreach cadences via email, phone, and social media from a single dashboard. It offers mail merge personalization, includes an integrated phone dialer, and supports automatic follow-ups.

What is Google Data Studio?

Google Data Studio is a simple dashboard and reporting tool. It's free and easy to use, but it lacks the sophisticated features of higher-end reporting software. Many of the connectors it supports are for Google products, but third parties have written partner connectors to a wide variety of data sources. Its drag-and-drop report editor lets users create about 15 types of charts.

Getting data out of Mailshake

Mailshake provides a REST API that lets developers fetch information about campaigns, recipients, leads, and other data stored in the platform. For example, to retrieve a list of all of a team's campaigns, you would call GET https://api.mailshake.com/2017-04-01/campaigns/list.

Sample Mailshake data

Here's an example of the kind of response you might see with a query to retrieve campaign information.

{
  "object": "campaign",
  "id": 1,
  "title": "My campaign",
  "created": "2017-08-19T02:31:22.218Z",
  "archived": null,
  "isPaused": false,
  "messages": [
    {
      "object": "message",
      "id": 1,
      "type": "initial",
      "subject": "My subject",
      "replyToID": null,
      "isPaused": false
    },
    {
      "object": "message",
      "id": 2,
      "type": "follow-up",
      "subject": "null",
      "replyToID": 1,
      "isPaused": false
    },
    {
      "object": "message",
      "id": 3,
      "type": "follow-up",
      "subject": "null",
      "replyToID": 1,
      "isPaused": false
    },
    {
      "object": "message",
      "id": 4,
      "type": "drip",
      "subject": "Here's a drip email",
      "replyToID": null,
      "isPaused": false
    },
    {
      "object": "message",
      "id": 5,
      "type": "on-click",
      "subject": "You clicked my link",
      "replyToID": null,
      "isPaused": false
    }
  ],
  "sender": {
    "object": "sender",
    "id": "abc",
    "emailAddress": "mysender@company.com",
    "fromName": "Firm ABC",
    "created": "2017-08-19T02:31:22.218Z"
  },
  "url": "https://mailshake.com/app/#/..."
}

Preparing Mailshake data

If you don't already have a data structure in which to store the data you retrieve, you'll have to create a schema for your data tables. Then, for each value in the response, you'll need to identify a predefined datatype (INTEGER, DATETIME, etc.) and build a table that can receive them. The Mailshake documentation should tell you what fields are provided by each endpoint, along with their corresponding datatypes.

Complicating things is the fact that the records retrieved from the source may not always be "flat" — some of the objects may actually be lists. In these cases you'll likely have to create additional tables to capture the unpredictable cardinality in each record.

Loading data into Google Data Studio

Google Data Studio uses what it calls "connectors" to gain access to data. Data Studio comes bundled with 17 connectors, mostly to pull in data from other Google products. It also supports connectors to MySQL and PostgreSQL databases, and offers 200 connectors to other data sources built and supported by partners.

Using data in Google Data Studio

Google Data Studio provides a graphical canvas onto which users drag and drop datasets. Users can set dimensions and metrics, specify sorting and filtering, and tailor the way reports and charts are displayed.

Keeping Mailshake data up to date

At this point you've coded up a script or written a program to get the data you want and successfully moved it into your data warehouse. But how will you load new or updated data? It's not a good idea to replicate all of your data each time you have updated records. That process would be painfully slow and resource-intensive.

The key is to build your script in such a way that it can identify incremental updates to your data. Thankfully, Mailshake's API results include date fields like created that allow you to identify records that are new since your last update (or since the newest record you've copied). Once you've taken new data into account, you can set your script up as a cron job or continuous loop to keep pulling down new data as it appears.

From Mailshake to your data warehouse: An easier solution

As mentioned earlier, the best practice for analyzing Mailshake data in Google Data Studio is to store that data inside a data warehousing platform alongside data from your other databases and third-party sources. You can find instructions for doing these extractions for leading warehouses on our sister sites Mailshake to Redshift, Mailshake to BigQuery, Mailshake to Azure Synapse Analytics, Mailshake to PostgreSQL, Mailshake to Panoply, and Mailshake to Snowflake.

Easier yet, however, is using a solution that does all that work for you. Products like Stitch were built to move data automatically, making it easy to integrate Mailshake with Google Data Studio. With just a few clicks, Stitch starts extracting your Mailshake data, structuring it in a way that's optimized for analysis, and inserting that data into a data warehouse that can be easily accessed and analyzed by Google Data Studio.