Outbrain to Redshift

This page provides you with instructions on how to extract data from Outbrain and load it into Redshift. (If this manual process sounds onerous, check out Stitch, which can do all the heavy lifting for you in just a few clicks.)

Pulling Data Out of Outbrain

The first step of getting all that beautiful Outbrain data into Redshift is actually pulling that data off of Outbrain’s servers. You can do this using the Outbrain REST API, which is available to all Outbrain customers. Full API documentation can be accessed here.

There are several API’s provided by Outbrain. For data and reporting purposes, the Amplify API is what we’ll be using here. Data from the Outbrain Amplify API can be retrieved programmatically. You will be able to access endpoints like campaigns, and campaign_preformance. Carefully consider the methods in the documentation, and you’ll be able to retrieve the data you’d like to load into Redshift.

Sample Outbrain Data

Once you successfully query the Outbrain Amplify API, it will return JSON formatted data. Take a look at an example response from the campaigns endpoint:


Preparing Outbrain Data for Redshift

With the JSON in hand, you now need to map all those data fields into a schema that can be inserted into your Redshift database. This means that, for each value in the response, you need to identify a predefined data type (i.e. INTEGER, DATETIME, etc.) and build a table that can receive them.

Check out the Stitch Outbrain Documentation to get a good sense of what fields and data types will be provided by each endpoint. Once you have identified all of the columns you will want to insert, use the CREATE TABLE statement in Redshift to build a table that will receive all of this data.

Inserting Outbrain Data into Redshift

It may seem like the easiest way to add your data is to build tried-and-true INSERT statements that add data to your Redshift table row-by-row. If you have any experience with SQL, this will be your gut reaction.  It will work, but isn’t the most efficient way to get the job done.

Here is some good documentation from Redshift for how to best bulk insert data into new tables. The COPY command is particularly useful for this task, as it allows you to insert multiple rows without needing to build individual INSERT statements for each row.

If you cannot use COPY, it might help to use PREPARE to create a prepared INSERT statement, and then use EXECUTE as many times as required. This avoids some of the overhead of repeatedly parsing and planning INSERT.

Keeping Data Up-To-Date

So what next? You’ve built a script that pulls data from Outbrain and moves it into Redshift, but what happens on Monday when you have new and updated data from new campaigns?

The key is to build your script in such a way that it can also identify incremental updates to your data. Some API’s include fields like created_at that allow you to quickly identify records that are new since your last update (or since the newest record you’ve copied into Redshift). You can set your script up as a cron job or continuous loop to keep pulling down new data as it appears.

Other Data Warehouse Options

Redshift is totally awesome, but sometimes you need to start smaller or optimize for different things. In this case, many people choose to get started with Postgres, which is an open source RDBMS that uses nearly identical SQL syntax to Redshift. If you’re interested in seeing the relevant steps for loading this data into Postgres, check out Outbrain to Postgres

Easier and Faster Alternatives

If you have all the skills necessary to go through this process, chances are building and maintaining a script like this isn’t a very high-leverage use of your time.

Thankfully, products like Stitch were built to solve this problem automatically. With just a few clicks, Stitch starts extracting your Outbrain data via the API, structuring it in a way that is optimized for analysis, and inserting that data into your Redshift data warehouse.