Oracle Responsys, a component of Oracle Marketing Cloud, lets organizations manage and orchestrate marketing campaigns and interactions with customers across email, mobile, social, display, and the web. Responsys provides cross-channel orchestration of customer touchpoints using the medium(s) customers prefer.

Amazon S3 (Simple Storage Service) provides cloud-based object storage through a web service interface. You can use S3 to store and retrieve any amount of data, at any time, from anywhere on the web. S3 objects, which may be structured in any way, are stored in resources called buckets.

Responsys has a REST API that you can use to get at information stored in the platform. For example, to retrieve an email or push campaign schedule, you would call GET /rest/api/v1.3/campaigns/{campaignName}/schedule/{scheduleId}.

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

{
    "id": 1491,
    "scheduleType": "ONCE",
    "scheduledTime": "2019-01-25 06:00 AM",
    "launchOptions": {
        "proofLaunch": true,
        "proofLaunchEmail": "someemail@a.com",
        "proofLaunchType": "LAUNCH_TO_ADDRESS",
        "recipientLimit": 3,
        "samplingNthSelection": 1,
        "samplingNthOffset": 1,
        "samplingNthInterval": 1,
        "progressEmailAddresses": [
            "email1@a.com",
            "email2@a.com"
        ],
        "progressChunk": "CHUNK_10K",
        "links": [
            {
                "rel": "self",
                "href": "/rest/api/v1.3/campaigns/test/schedule/1491",
                "method": "POST"
            },
            {
                "rel": "createSchedule",
                "href": "/rest/api/v1.3/campaigns/test/schedule",
                "method": "GET"
            },
            {
                "rel": "updateSchedule",
                "href": "rest/api/v1.3/campaigns/test/schedule/1491",
                "method": "PUT"
            },
            {
                "rel": "deleteSchedule",
                "href": "rest/api/v1.3/campaigns/test/schedule/1491",
                "method": "DELETE"
            }
        ]
    }
}

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. Responsys'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.

To upload files you must first create an S3 bucket. Once you have a bucket you can add an object to it. An object can be any kind of file: a text file, data file, photo, or anything else. You can optionally compress or encrypt the files before you load them.

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.

Responsys lacks key fields that a script could use to bookmark its progression as it looks for updated data. However, you can create .csv or .txt files as part of a Responsys Connect data export job and use a date/time prefix or suffix in the file names. You could then set up your script as a cron job or continuous loop to get new data as it's exported from Responsys.

S3 is great, but sometimes you want a more structured repository that can serve as a basis for BI reports and data analytics — in short, a data warehouse. Some folks choose to go with Amazon Redshift, Google BigQuery, PostgreSQL, Snowflake, Microsoft Azure Synapse Analytics, or Panoply, which are RDBMSes that use similar SQL syntax. 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 Synapse Analytics, and To Panoply.