Define Cart
Carts overview
Right-click the cart in the list to access a pop-up menu with following options:
- Pin component — adds the cart to the dashboard
- Copy cart as a new cart — duplicates the selected cart, displays the properties in Edit mode.
- Edit cart — access to the properties in Read mode. You still need to select the Edit button to make modifications
- View report — graphs and tables with details on cart items
Cart Details
To create a new cart, press the
'New cart' button 
. A new tab is added and the following
configuration page allows defining the cart:
- Name & Description of the cart. Make it explicit, especially when working with multiple carts (eg. for multiple websites)
- Public name— used in scripts. Name must be unique and cannot contain spaces.
- Currency — this is used for reporting purposes. Currently there is no calculation based on the currency. Prices need to be provided in the currency specified for the cart.
- Cart is abandoned after (optional) — set a time frame after which the cart is considered as abandoned. (eg. after 2 days of no changes to the cart it is an abandoned cart). If this option is set, you can define actions that should be executed when a cart is abandoned. The information can also be used in the constraint editor to create segments.
- Cart is cleared after — set a time frame after which items should be removed from the cart. This option allows imitating the behavior of the real cart.
First, we recommend to set use this option and clear automatically the cart in Site in the same time frame as it is handled on the website. The website administrator could send calls to Site whenever the cart is cleared on the website. However using the option is target is easier to implement.
What? Define your actions
The two following options set the actions to be taken when a profile abandons his cart or completes it. The action itself is defined in a Campaign Journey of type 'Abandon/checkout cart'. This type of Journey requires an Input component through which the profiles can enter the Journey and receive for instance an email.
Trigger Journey after cart abandonment:
From the drop down, select the Campaign Journey and its input component that must be triggered. The reason why an Input component must be selected is that a Journey may contain multiple Input components and that you need to decide through which Input component the visitor enters the Journey. (Note: only journeys linked to the current universe and configured as 'Abandon/Checkout cart' Journey, are listed.)
If the Journey input component has custom input parameters, you can
pass Site values to the Journey.
Two values are always passed on by default and are therefore not listed
here: the cart's public name (for Journey parameter CART) and the list
of products in the cart (PRODUCTS).
Use the ... button to the right of the field to set the values for the
Journey’s custom input parameters. Click
the ‘Edit’ icon to the right
of the custom parameter to select the value. A dialog is displayed where
a choice can be made between profile data (hits, visits, visit durations…),
tag values (Site tag values) and offer data (if the user visitor is in
an offer or not, and when he was in or out of the offer). Identification
data, Do not Track option and Reporting segments can equally be used to
set the values for the parameters.
Trigger Journey upon cart completion: select the input component of the Journey where the profile must be sent to when he completed his cart. The fact that a profile has completed his cart is communicated from the website to target through the API at the moment the profile completes his purchase. Setting the parameters is done in the same way as for the above option.
For more information on how to set up these journeys,
check out the topic Create
Abandon/Checkout cart journeys.
For the step by step setup of the integration with Campaign, Check out
the section on Campaign integration setup. in the Table of content
Create a new abandon cart offer: this takes you straight to the Offer section where you can start defining an offer for the predefined audience 'Has abandoned cart <current cart>'.
What? Product catalog
Product catalog allows using
an XML that maps the items in the cart with actual product names. When
items in the cart are sent back to Marigold Site, the item ID, value
and amount is passed. Often, these item ids don't say much. The XML file
is then used to map these item ids to actual product names. The mapping
can even depend on the language.
The product mapping is used for instance in the constraint editor when
creating segments. Instead of being shown the product ids, the user will
see the actual product names.
Now this XML file can be created manually or automatically. You can also choose to apply no mapping at all.
From XML: the user browses for the XML file to use for the mapping.
This XML has to have the structure as in the following example
example of XML file:
<PRODUCTMAPPING>
<PRODUCT PRODUCTID="1">Product 1</PRODUCT>
<PRODUCT PRODUCTID="1" LANG="FR">Produit 1</PRODUCT>
<PRODUCT PRODUCTID="1" LANG="NL">Produkt 1</PRODUCT>
<PRODUCT PRODUCTID="2">Product 2</PRODUCT>
<PRODUCT PRODUCTID="3">Product 3</PRODUCT>
<PRODUCT PRODUCTID="4">Product 4</PRODUCT>
<PRODUCT PRODUCTID="5">Product 5</PRODUCT>
</PRODUCTMAPPING>
From Engage Data list: in this case the XML file is generated automatically based on the information retrieved from the article list in Campaign. For this to be possible following needs to be set:
Select the name of the article table. The list contains all article tables in the Campaign environment configured on Universe level.
Select the field in the article list that will be used as Article ID to match the item in the basket with.
Select the field that will be used for the name of the item in the basket.
Last sync and next sync date and time tells you when the mapping was last performed and when the next one will happen.
