Order Schema

An order interaction is a commerce action that captures actions performed by a user to manage new, in progress, or completed orders.

Source Event PropertyTarget Schema Developer NameField TypeDescriptionCustomer 360 Data Model Object / Attribute
<Automatically Assigned>eventIdtextRequired. Typically the primary key for the engagement events.Engagement / Engagement Id
<Automatically Assigned>dateTimedatetimeRequired. Used for data partitioning for engagement events. ISO8601 supported format.Engagement / Engagement Date Time
<Automatically Assigned>eventType = "order"textRequired. The developerName of an event defined in the Web Connector schema.-
<Automatically Assigned>sessionIdtextRequired. The identifier of the session.-
<Automatically Assigned>deviceIdtextRequired. Typically the primary key for profile events.Product Order Engagement / Individual
<Automatically Assigned>category = "Engagement"textRequired. Possible values are:
  • Engagement
  • Profile
-
<Automatically Assigned>interactionName = "Cancel | Deliver | Exchange | Preorder | Purchase | Return | Ship"textRequired. A descriptive name for the event.Product Order Engagement / Product Order Event Type
<Automatically Assigned>channel = "mobile"textThe SDK event channel. For Engagement Mobile SDK the value is mobile.Engagement / Engagement Channel Type
<Automatically Assigned if Location Tracking is allowed>longitudenumberThe longitudinal coordinate in decimal degrees reported by the device at the time the event was captured.Engagement / Device Longitude
<Automatically Assigned if Location Tracking is allowed>latitudenumberThe latitudinal coordinate in decimal degrees reported by the device at the time the event was captured.Engagement / Device Latitude
order.idorderIdtextA unique identifier representing the order.Engagement / Sales Order Product Engagement Action / Order Product Number
order.totalValueorderTotalValuenumberThe total value of the order.Product Order Engagement / Sales Order Product Engagement Action / Net Order Amount
order.currencyorderCurrencytextThe currency of the total value for the order.Product Order Engagement / Currency
order.attributesRefer to Schema Field Naming RulesnumberA dictionary of user-supplied values.-

Each Line Item Attribute contained in the Order Event gets mapped to a child event where order EventId is set to the eventId of the parent order event:

Source Event PropertyTarget Schema Developer NameData TypeDescriptionCustomer 360 Data Model Object / Attribute
<Automatically Assigned>eventIdtextRequired. Typically the primary key for the engagement events.-
<Automatically Assigned>dateTimedatetimeRequired. Used for data partitioning for engagement events. ISO8601 supported format.-
<Automatically Assigned>eventType = "orderItem"textRequired. The developerName of an event defined in the Web Connector schema.-
<Automatically Assigned>sessionIdtextRequired. An identifier for a session.-
<Automatically Assigned>deviceIdtextRequired. Typically the primary key for profile events.-
<Automatically Assigned>category = "Engagement"textRequired. Possible values are:
  • Engagement
  • Profile
-
<Automatically Assigned>orderEventIdtextRequired. The eventId of the order event containing this Line Item.Product Order Engagement
lineItem.catalogObjectTypecatalogObjectTypetextRequired. A type name of the catalog object referenced in the line item.-
lineItem.catalogObjectIdcatalogObjectIdtextRequired. A unique identifier representing the catalog object referenced in the line item.-
lineItem.quantityquantitynumberThe number of catalog objects in the line item.Product Order Engagement / Currency
lineItem.pricepricenumberThe price of the catalog object referenced in the line item.Product Order Engagement / Currency
lineItem.currencycurrencytextThe currency for the price field.Product Order Engagement / Currency
lineItem.attributes.customField0attributeCustomField0anyA user-supplied value.-
lineItem.attributes.customFieldNattributeCustomFieldNanyA user-supplied value.-

Properties added to lineItem.attributes aren’t automatically defined in the recommended schema. They’re shown to demonstrate how the source properties are mapped to the target schema. Manually add the properties to the schema.