Each event family maps to specific Data Model Objects (DMOs) in Data 360. When B2C Commerce captures engagement events, it transforms that data into standardized DMO fields that Data 360 can process. Each event family has distinct mappings based on the type of customer interaction.
Each family mapping reference includes:
- Source fields from B2C Commerce
- Target DMO fields in Data 360
- Field requirements (required or optional)
- Data transformations applied during mapping
- Cart Management Family DMO Mappings
Cart Management interactions capture when B2C Commerce customers add products to their shopping cart (cart-add), remove products from their cart (cart-remove), or modify quantities and product options (cart-update). These interactions map to two DMOs: ShoppingCartEngagement for the cart-level event and ShoppingCartProductEngagement for individual product line items. - Checkout Process Family
Checkout Process interactions capture when B2C Commerce customers initiate checkout (checkout-begin), progress through checkout stages (checkout-step), provide contact information (checkout-contact-info, deprecated), create accounts during checkout (checkout-user-register), and submit final orders (checkout-submit). These interactions map to WebsiteEngagement DMO for checkout events, plus Individual, ContactPointEmail, ContactPointPhone, and ContactPointAddress DMOs for customer data capture. - Customer Profile Management Family
Customer Profile Management interactions capture new B2C Commerce customer account creation (user-register) and profile modifications (update-user-profile). These interactions map to five DMOs: Individual for core customer identity, ContactPointEmail for email addresses, ContactPointPhone for phone numbers, ContactPointAddress for physical addresses, and PartyIdentification for cross-system identity linking. - Order Processing Family
Order Processing interactions capture when B2C Commerce orders are successfully processed and accepted (order-accepted). This interaction maps to ProductOrderEngagement DMO for order completion events, and can also update customer profile data through Individual and ContactPoint objects. - Product Discovery Family
Product Discovery interactions capture when B2C Commerce customers perform product searches (search), view product detail pages (catalog-object-view-start), and see product impressions (catalog-object-impression). These interactions map to two DMOs: WebSearchEngagement for search activities, and ProductBrowseEngagement for product viewing and browsing. - Content Engagement Family
Content Engagement captures a single interaction,page-view, recorded each time a shopper loads a B2C Commerce storefront page. This browser-side interaction maps to the WebsiteEngagement DMO using the Browser2Server integration type. - Wishlist Management Family
Wishlist Management interactions capture when B2C Commerce customers save products for later (wish-list-add) and remove items from their wishlist (wish-list-remove). These interactions map to WebsiteEngagement DMO for wishlist interactions.