Marketing Cloud Personalization Bundle Mappings

Event and attribute mappings that aren’t included in the starter data bundle data streams must be defined manually after bundle creation:

• Shopping cart and order line item events
• Custom events
• Custom user attributes

Attributes for standard and custom events are fixed. Event data ingested from Marketing Cloud Personalization into Data 360 is limited to the standard attributes for both standard events and custom events. If you add, delete, or rename attributes in Marketing Cloud Personalization after creating and deploying a Marketing Cloud Personalization data stream, these changes won't be reflected in your data stream.

When ingesting data from Marketing Cloud Personalization, Data 360 creates data lake objects (DLOs) for each starter bundle along with schemas and mappings to Data Model Objects (DMOs). Use these tables to identify how the data is ingested from the DLO and how it’s mapped to the DMO within Data 360.

Data for users and four engagement events is ingested. Each is mapped to a separate data stream, and each populates a separate DLO. Events are immutable and appended. Shopping cart and order events both have an event CSV and a line items CSV, which creates two data streams for each event. A total of seven data streams are created, one for users and six for engagement events.