Each unique order Id can only be sent once. Orders reusing an orderid will be dropped.
- If accid is sent, then userid will be ignored – as all subsequent events will be tracked against the account.
- If userid is sent, then this will be taken as an identifier for the user across the site. Use this same identifier when the user logs in; makes an order; or in any offline orders that are submitted.
- If neither accid or userid is sent, then email will be used as the unique identifier for the user. This should be used whenever the user logs in; makes an order; or in any offline orders that are submitted.
- If accid or userid is set – and email is set as well – then the email address will just be stored against the user. It will be used if any Triggered Emails are sent.
- Best practice is to send the userid (or accid if using accounts). This is because it will remain unique to that user – email addresses may well be changed over time.
- The Id should match the Id sent in the user feed.
If you are passing groupid, then this must match one of the groups sent in the GroupPricing field in the Product Feed.
Properties
Unique order number of this order
Total order value in base currency.NOTE: Values should have no currency symbol or comma separators. This value can either be ex-VAT or VAT depending on the site. Decimal separator must be a . and NOT a ,
The customer title or salutation. For example Mr, Mrs, Miss, Ms, Dr
First name of the customer
Last name of the customer
The zipcode of the delivery address
The postcode of the delivery address
Date of Birth of the Customer (Format YYYY-MM-DD)
The customers unique user id
The customers email address
The business account id of the customer
Optional user group. Used to support price banding (prices per user group)
Array of items in the order
