Items installed with Commerce Connect

Current version: 9.0

This topic describes the items installed in Sitecore with the Commerce Connect package.

Note

The Storefront Abandoned Cart marketing automation campaign is available from Commerce Connect 9.0.2. The New Order Placed marketing automation campaign is available from Commerce Connect 9.2. To use them, you must have installed the Connect Marketing Automation package. For more information, see the Installation Guide.

Finding Commerce Connect items in the Content Editor

Commerce Connect items are installed in the following folders in the Content Editor:

Item type

Item path

Page events

/sitecore/System/Settings/Analytics/Page Events/CommerceConnect

Goals

/sitecore/System/Marketing Control Panel/Goals/CommerceConnect

Outcomes

/sitecore/System/Marketing Control Panel/Outcomes

Conditional renderings

/sitecore/System/Settings/Rules/Definitions/Elements/CommerceConnect Conditional Renderings

Marketing automation plan folder

/sitecore/system/Marketing Control Panel/Automation Plans

Experience Analytics Dimensions

/sitecore/system/Marketing Control Panel/Experience Analytics/Dimensions/Connect

Marketing automation conditions

/sitecore/system/Settings/Rules/Definitions/Elements/Commerce - Cart

/sitecore/system/Settings/Rules/Definitions/Elements/Commerce - Email

Templates

/sitecore/Templates/CommerceConnect

Page events, goals, and outcomes

To access page events, goals, and outcomes included with Commerce Connect, you need to use the API provided with Commerce Connect. For more information, see the Commerce Connect Developer's Guide.

The table below details the Commerce Connect page events, goals and outcomes.

Note

When Sitecore saves events, goals and outcomes, Sitecore stores the related personal data in contact facets and assigns the facets a PIISensitive attribute (Personally Identifiable Information) so that the facets can be deleted if the customer exercises their right to be forgotten. For more information, see the Privacy Guide.

Service layer the item belongs to

Item Type

Item Name

Data Stored with the Item

Cart

Page event

Cart Created

ExternalId, UserId, CartName, CartStatus

Cart

Page event

Cart Deleted

ExternalId (Cart ID), UserId, CartName, CartStatus

Cart

Page event

Cart Locked

ExternalId, UserId, CartName, CartStatus

Cart

Page event

Cart Resumed

ExternalId, UserId, CartName, CartStatus, PreviousState

Cart

Page event

Cart Unlocked

ExternalId, UserId, CartName, CartStatus

Cart

Page event

Cart Updated

CustomerId, CartName, ShopName

Cart

Page event

Lines Added To Cart

ListOfCartLines (ProductId, Quantity, Price)

Cart

Page event

Lines Removed From Cart

ListOfCartLines (ProductId, Quantity, Price)

Cart

Page event

Lines Updated On Cart

ListOfCartLines (ProductId, Quantity, Price)

Cart

Outcome

Abandoned Cart

Shopname, Cart ID, Cart and Cart Total

Catalog

Page event

Visited Category Page

Catalog Name, Category Name

Catalog

Page event

Facet Applied

Facet name, Applied (boolean)

Catalog

Page event

Product Sorting

Sort key, Sort direction (ASC/DSC)

Catalog

Page event

Visited Product Details Page

Product ID, ProductName, ParentCategoryName, ShopName, ParentCategoryID

Customers and Users

Page event

Customer Account Deleted

CustomerName, ShopName

Customers and Users

Page event

Customer Account Disabled

CustomerName, ShopName

Customers and Users

Page event

Customer Account Enabled

CustomerName, ShopName

Customers and Users

Page event

Customer Account Updated

CustomerName, ShopName

Customers and Users

Page event

User Account Deleted

UserName, ShopName

Customers and Users

Page event

User Account Disabled

UserName, ShopName

Customers and Users

Page event

User Account Enabled

UserName, ShopName

Customers and Users

Page event

User Account Updated

UserName, ShopName

Customers and Users

Goal

Customer Account Created

CustomerName, ShopName

Customers and Users

Goal

User Account Created

UserName, ShopName

Globalization

Page event

Culture chosen

ShopName, Culture ID

Inventory

Page event

Add To Cart Stock Status

CartId, UserId, ShopName, ListOfCartLines(ProductId, StockStatus, InStockDate, ShippingDate)

Inventory

Page event

Back In Stock Subscription

Product, Email, Location, InterestDate, ShopName

Inventory

Page event

Back In Stock Unsubscription

Product, Location, ShopName, VisitorId

Inventory

Page event

Products Are Back In Stock

ShopName, ListOfProducts

Inventory

Page event

Visited Product Stock Status

ShopName, Product, Location, StockStatus, AvailabilityDate, StockCount

LoyaltyProgram

Goal

Loyalty Program Joined

ExternalId, UserId, ShopName, CardNumber

Orders

Page event

Gift Card Purchase

Order ID, Gift CardI ID, the order total, the amount used on the gift card and the remaining amount

Orders

Page event

Loyalty cart Purchase

Order ID, Order Total, Loyalty CardID, Loyalty program ID (if available), Loyalty points used and the total amount that the loyalty points equals

Orders

Page event

Order Status Changed

Order ID, Status (string)

Orders

Page event

Ordered Product Stock Status

ProductID, ProductName, StockStatus, InStockDate, ShippingDate, PreOrderable (true/false)

Orders

Page event

Visitor Cancel Order

CustomerId, ShopName, OrderId, Total

Orders

Page event

Visitor Viewed Order Details

CustomerId, ShopName, OrderId, Total amount

Orders

Page event

Visitor Viewed Order History

CustomerId, ShopName

Orders

Page event

Offline Orders Synchronized

UserId, ShopName, LastOrderSynchronizedDate, ExternalSystem, NumberOfOrdersSynchronized, SynchronizedOrderIDsList

Orders

Goal

Visitor Order Created

ExternalId (Order ID), ShopName, Totals, Order

Orders

Outcome

Product Purchase (Visitor Order Created)

Shopname, Order ID (External ID), a cut down order (order header + order lines with product ids and names, line total, subtotal and total)

Note

This is not enabled from Sitecore 9.0.2 to Sitecore 9.2. You can use the Visitor Order Created goal instead.

Pricing

Page event

Currency chosen

ShopName, Currency ID

WishLists

Page event

Lines Added To WishList

ExternalId, UserId, WishListName, ShopName, ListOfCartLines(ProductId, Quantity, Price)

WishLists

Page event

Lines Removed From WishList

ExternalId, UserId, WishListName, ShopName, ListOfCartLines(ProductId, Quantity, Price)

WishLists

Page event

Lines Updated On WishList

ExternalId, UserId, WishListName, ShopName, ListOfCartLines(ProductId, Quantity, Price)

WishLists

Page event

WishList Created

ExternalId, UserId, WishListName, ShopName

WishLists

Page event

WishList Deleted

ExternalId, UserId, WishListName, ShopName

WishLists

Page event

WishList Emailed

ListOfWishLists(ExternalId, UserId, WishListName, ShopName)

WishLists

Page event

WishList Printed

ExternalId, UserId, WishListName, ShopName

[Part of Platform]

Page event

Search

ShopName, SearchTerm, NumberOfHits

Personalization rules

The table below shows details of the personalization rule conditions that come with Commerce Connect.

Service layer

Item name

Description

Rule parameters

Cart

Total Product Quantity Condition

Tests the current quantity of items in the cart against a specified value.

TotalProductQuantity, compares-to operator

Cart

Cart Total Condition

Tests the current cart total against a specified amount.

CartTotal, compares-to operator

Cart

Specific Product Quantity Condition

Tests the current cart content for the quantity of a specified product against a specified value.

ProductId, ProductQuantity, compares-to operator

Inventory

Current Product Stock Count

Tests the stock count of a product given by the Commerce Context implementation against a specified value. Requires Commerce Context. The default implementation alone throws Not Implemented exceptions.

StockCount, compares-to operator

Inventory

Current Product Stock Count By Location

Tests the stock count of a product provided by Commerce Context against a specified value. Also tests for the product being in a specified location. Requires Commerce Context. The default implementation alone throws Not Implemented exceptions.

StockCount, Location, compares-to operator

Inventory

Current Product Stock Status

Tests the stock status of a product provided by Commerce Context against a specified status. Requires Commerce Context. The default implementation alone throws Not Implemented exceptions.

StockStatus, compares-to operator

Inventory

Current Product Stock Status By Location

Tests the stock status of a product provided by Commerce Context against a specified status. Also tests for the product being in a specified location. Requires Commerce Context. The default implementation alone throws Not Implemented exceptions.

StockStatus, Location, compares-to operator

Inventory

Specific Product Stock Count

Tests the stock count of a specified product against a specified value.

ProductId, StockCount, compares-to operator

Inventory

Specific Product Stock Count By Location

Tests the stock count of a specified product against a specified value. The condition also tests for the product being in a specified location.

ProductId, StockCount, Location, compares-to operator

Rules

Has Triggered Page Events

Tests the number of occurrences of a specified page event within a specified time range against a specified value. Not recommended for use in production systems; not optimized as it does not use KeyBehaviorCache, which was introduced with 8.1.

PageEventName, MinimalNumberOfTimes, TimeRange

Marketing automation campaigns

Commerce Connect contains default marketing automation campaigns including the Storefront Abandoned Cart marketing automation campaign and the New Order Placed marketing automation campaign. The following table describes items installed for marketing automation campaign.

Service layer the item belongs to

Item type

Item name

Description

Cart

New Order Placed campaign template

New Order Placed

Sends an order confirmation email to contacts who have completed a purchase.

Cart

Marketing Automation campaign template

Abandoned Cart

Follows up on contacts who visit the storefront and leave a shopping cart with products in it. If a contact has a known email address, Sitecore sends a notification email to encourage the contact to finalize the purchase. The marketing automation campaign stores the cart ID in custom values.

Cart

Marketing Automation campaign template

Where Cart Has Been Manipulated

Checks if any actions have been performed on the cart since the contact was enrolled into the campaign or since last checked.

Cart

Marketing Automation campaign template

Where Contact Has Email

Checks if an email exists for the contact.

Cart

Marketing Automation campaign template

Where Contact Cart Is Empty

Checks whether the cart with the specified ID is empty.

Do you have some feedback for us?

If you have suggestions for improving this article,