Revinate to Metabase

This page provides you with instructions on how to extract data from Revinate and analyze it in Metabase. (If the mechanics of extracting data from Revinate 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 Revinate?

Revinate is a CRM and email marketing platform for the hotel industry. It aims to address online reputation by soliciting guest surveys and collecting reviews for TripAdvisor or Google.

Getting data out of Revinate

Revinate's API lets developers get at information stored in the platform about things like hotels and reviews. For example, to retrieve a particular review using the Revinate API, you would call GET /reviews/{reviewId}.

Sample Revinate data

Here's an example of the fields you might see in a response to a query like the one above.

{
  "title": "",
  "body": "",
  "author": "",
  "authorLocation": "",
  "dateReview": 0,
  "dateCollected": 0,
  "updatedAt": 0,
  "rating": 0,
  "nps": 0,
  "reviewSite": {
    "name": "",
    "mainUrl": "",
    "slug": "",
    "links": [
      {
        "rel": "",
        "href": "",
        "templated": false
      }
    ]
  },
  "language": {
    "name": "",
    "englishName": "",
    "slug": "",
    "links": [
      {
        "rel": "",
        "href": "",
        "templated": false
      }
    ]
  },
  "crawledUrl": "",
  "subratings": {},
  "tripType": "",
  "guestStay": {
    "checkinDate": "",
    "checkoutDate": "",
    "loyaltyId": "",
    "confirmationCode": "",
    "bookingChannel": "",
    "roomType": "",
    "roomNumber": "",
    "rate": "",
    "rateCurrency": "",
    "ratePlanCode": "",
    "checkedInBy": "",
    "checkedOutBy": "",
    "groupName": "",
    "guest": {
      "title": "",
      "firstName": "",
      "lastName": "",
      "phone": "",
      "email": "",
      "address": "",
      "address2": "",
      "city": "",
      "state": "",
      "country": "",
      "postalCode": "",
      "links": [
        {
          "rel": "",
          "href": "",
          "templated": false
        }
      ]
    },
    "links": [
      {
        "rel": "",
        "href": "",
        "templated": false
      }
    ]
  },
  "surveyTopics": [
    {
      "name": "",
      "questionAnswers": [
        {
          "question": {
            "name": "",
            "type": "",
            "rangeConfig": {
              "leftValue": 0,
              "rightValue": 0,
              "step": 0,
              "leftText": "",
              "rightText": ""
            },
            "multipleChoiceOptions": [
              {
                "position": 0,
                "text": ""
              }
            ]
          },
          "yesNoAnswer": "",
          "textAnswer": "",
          "ratingAnswer": 0,
          "rangeAnswer": 0,
          "multipleChoiceAnswers": [
            {
              "position": 0,
              "text": ""
            }
          ],
          "notApplicableAnswer": false
        }
      ]
    }
  ],
  "response": {
    "body": "",
    "author": "",
    "date": 0
  },
  "links": [
    {
      "rel": "",
      "href": "",
      "templated": false
    }
  ]
}

Preparing Revinate 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. Revinate's 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.

Keeping Revinate 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, Revinate's API results include fields like dateCollected and updatedAt that allow you to identify records that are new since your last update (or since the newest record you've copied). Once you've take 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 Revinate to your data warehouse: An easier solution

As mentioned earlier, the best practice for analyzing Revinate data in Metabase 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 Revinate to Redshift, Revinate to BigQuery, Revinate to Azure SQL Data Warehouse, Revinate to PostgreSQL, Revinate to Panoply, and Revinate to Snowflake.

Easier yet, however, is using a solution that does all that work for you. Products like Stitch were built to move data from Revinate to Metabase automatically. With just a few clicks, Stitch starts extracting your Revinate data via the API, 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 Metabase.