Eloqua to QuickSight

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

Oracle Eloqua is a marketing automation platform (MAP) that aims to help B2B marketers and organizations manage marketing campaigns and sales lead generation. Its capabilities include email marketing, lead nurturing, customer targeting and segmentation, and marketing measurement.

Getting data out of Eloqua

Eloqua provides a REST API that lets developers get at accounts, contacts, forms, and other information stored in the platform. For example, to retrieve a particular account using the Eloqua API, you would call GET /api/REST/1.0/data/account/{id}.

Sample Eloqua data

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

{
    "type":"Account",
    "id":"1",
    "createdAt":"1423758306",
    "depth":"complete",
    "description":"This is an example company.",
    "name":"Cyberdyne Systems",
    "updatedAt":"1423758306",
    "address1":"123 Industry Lane",
    "address2":"",
    "address3":"",
    "businessPhone":"5555555555",
    "city":"Los Angeles ",
    "country":"United States",
    "fieldValues":[],
    "postalCode":"",
    "province":"CA"
}

Preparing Eloqua 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. Eloqua'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 Eloqua 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, Eloqua's API results include fields like createdAt 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 Eloqua to your data warehouse: An easier solution

As mentioned earlier, the best practice for analyzing Eloqua data in Amazon QuickSight 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 Eloqua to Redshift, Eloqua to BigQuery, Eloqua to Azure SQL Data Warehouse, Eloqua to PostgreSQL, Eloqua to Panoply, and Eloqua 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 Eloqua to Amazon QuickSight automatically. With just a few clicks, Stitch starts extracting your Eloqua 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 Amazon QuickSight.