Creating an Amazon S3 Connector to Ingest Marketing Cloud Personalization Data into Data 360

To take advantage of what Salesforce Personalization has to offer, you need to transfer some Marketing Cloud Personalization metadata and catalog data into Data 360. You can do that with an Amazon S3 connector.

In Marketing Cloud Personalization, catalog updates are performed using the Marketing Cloud Personalization ETL system or updates through the WebSDK. In Data 360, you can use a dedicated Amazon S3 connection to transfer catalog metadata and item data to Data 360.

Important If your catalog is already defined in Data 360, you don’t need to set up data ingestion using an S3 connector. You need only create a dedicated Amazon S3 connector if you haven’t ingested Marketing Cloud Personalization data into Data 360 and plan to use the convergence tools discussed here.

An Amazon S3 Storage Connector, enables you to retrieve data objects from an AWS S3 bucket. Data 360 reads from the S3 bucket and automatically retrieves future data sets from the directory according to a defined schedule. For unstructured data, records are imported through file notifications.

The data streams that are automatically created while uploading Marketing Cloud Personalization metadata are hard-coded to use a specifically-named connector. When configuring the S3 connector, make sure to use these settings.

For information about how to configure an Amazon S3 connection, see Set Up Amazon S3 Connection in the Data 360 Integration Guide.