Listrak to Metabase

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

Listrak is a marketing automation platform for online and omnichannel retailers. It combines data from desktop and mobile platforms with online and offline data about purchases, and uses AI and predictive analytics to give businesses insights into their customers' behavior.

What is Metabase?

Metabase provides a visual query builder that lets users generate simple charts and dashboards, and supports SQL for gathering data for more complex business intelligence visualizations. It runs as a JAR file, and its developers make it available in a Docker container and on Heroku and AWS. Metabase is free of cost and open source, licensed under the AGPL.

Getting data out of Listrak

Listrak has three REST APIs – for email, SMS, and data input – that developers can use to get at information stored in the platform. For example, to get information about an email list, you would call GET /v1/List/{listId}.

Sample Listrak data

Here's an example of the kind of response you might see with a query like the one above.

"status": 200,
"data": {
"listId": 0,
"listName": null,
"folderId": 0,
"ipPoolId": 0,
"bounceDomainAlias": null,
"bounceHandling": null,
"bounceUnsubscribeCount": 0,
"createDate": "0001-01-01T00:00:00",
"enableBrowserLink": false,
"enableDoubleOptIn": false,
"enableDynamicContent": false,
"enableGoogleAnalytics": false,
"enableInternationalization": false,
"enableListHygiene": false,
"enableListRemovalHeader": false,
"enableListRemovalLink": false,
"enableListrakAnalytics": false,
"enableSpamScorePersonalization": false,
"enableToNamePersonalization": false,
"fromEmail": null,
"fromName": null,
"googleTrackingDomains": null,
"linkDomainAlias": null,
"mediaDomainAlias": null

Preparing Listrak 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. Listrak'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. This means you'll likely have to create additional tables to capture the unpredictable cardinality in each record.

Loading data into Metabase

Metabase works with data in databases; you can't use it as a front end for a SaaS application without replicating the data to a data warehouse first. Out of the box Metabase supports 15 database sources, and you can download 10 additional third-party database drivers, or write your own. Once you specify the source, you must specify a host name and port, database name, and username and password to get access to the data.

Using data in Metabase

Metabase supports three kinds of queries: simple, custom, and SQL. Users create simple queries entirely through a visual drag-and-drop interface. Custom queries use a notebook-style editor that lets users select, filter, summarize, and otherwise customize the presentation of the data. The SQL editor lets users type or paste in SQL queries.

Keeping Listrak 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.

Instead, identify key fields that your script can use to bookmark its progression through the data and use to pick up where it left off as it looks for updated data. Auto-incrementing fields such as updated_at or created_at work best for this. When you've built in this functionality, you can set up your script as a cron job or continuous loop to get new data as it appears in Listrak.

And remember, as with any code, once you write it, you have to maintain it. If Listrak modifies its API, or the API sends a field with a datatype your code doesn't recognize, you may have to modify the script. If your users want slightly different information, you definitely will have to.

From Listrak to your data warehouse: An easier solution

As mentioned earlier, the best practice for analyzing Listrak 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 Listrak to Redshift, Listrak to BigQuery, Listrak to Azure Synapse Analytics, Listrak to PostgreSQL, Listrak to Panoply, and Listrak 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 Listrak with Metabase. With just a few clicks, Stitch starts extracting your Listrak 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 Metabase.