Drip is an eCommerce Customer Relationship Management platform that gathers and organizes customer data, then enables online retailers to craft personalized omnichannel buying experiences.

The Panoply Smart Cloud Data Warehouse platform can spin up an Amazon Redshift instance in just a few clicks, and import data with no schema, no modeling, and no configuration. It uses machine learning and natural language processing (NLP) to learn, model, and automate data management activities from source to analysis. You can then work with analysis, SQL, and visualization tools to gain business insights from your data.

You can collect data from Drip’s servers using webhooks and user-defined HTTP callbacks. Set up the webhook in your Drip account, and define a URL that your script listens to and from which it can collect the data.

Once you've set up webhooks and HTTP endpoints, Drip will begin sending data via the POST request method. Data will be enclosed in the body of the request in JSON format. Here's a sample of what that data might look like.

{
  "id": "z1togz2hcjrkpp5treip",
  "status": "active",
  "email": "john@acme.com",
  "custom_fields": {
    "name": "John Doe"
  },
  "tags": ["Customer", "SEO"],
  "time_zone": "America/Los_Angeles",
  "utc_offset": -440,
  "created_at": "2017-06-21T10:31:58Z"
  "ip_address": "123.123.123.123",
  "user_agent": "Mozilla/5.0",
  "lifetime_value": 2000,
  "original_referrer": "https://google.com/search",
  "landing_url": "https://www.drip.co/landing",
  "prospect": true,
  "base_lead_score": 30,
  "lead_score": 65,
  "user_id": "123"
}

You need to map all the data fields in the JSON data from your webhook into a schema that can be inserted into your database. For each value in the response, you need to identify a predefined datatype (i.e. INTEGER, DATETIME, etc.) and build a table that can receive them.

Once you've identified the columns you want to insert, you can use Redshift's CREATE TABLE statement to define a table to receive all of the data.

With a table built, you might be tempted to migrate your data (especially if there isn't much of it) by using INSERT statements to add data to your Redshift table row by row. Not so fast! Redshift isn't optimized for inserting data one row at a time. If you have a high volume of data to be inserted, you should load the data into Amazon S3 and use the COPY command to load it into Redshift.

Once you’ve coded up a script or written a program to get the data you want and move it into your data warehouse, you’re going to have to maintain it. If Drip modifies its webhook implementation, or 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.

Panoply is great, but sometimes you need to optimize for different things when you're choosing a data warehouse. Some folks choose to go with Amazon Redshift, Google BigQuery, PostgreSQL, Snowflake, or Microsoft Azure Synapse Analytics, which are RDBMSes that use similar SQL syntax. Others choose a data lake, like Amazon S3 or Delta Lake on Databricks. If you're interested in seeing the relevant steps for loading data into one of these platforms, check out To Redshift, To BigQuery, To Postgres, To Snowflake, To Azure SQL Data Warehouse, To S3, and To Delta Lake.