Pure360 Personalisation can load transaction data from a file which you place on an sFTP server.
For example, the following file could be used:
order_id,product_id,item_name,item_price,qty,cart_price,cart_price_including_tax,cart_price_excluding_tax,order_date,email,Currency 4056046,861838,Drawer Lock 19 x 22mm Chrome Plated Keyed Alike Differ 1,8.1,2,122.9,147.48,122.9,08/04/2015 09:51,peter.duck@domain1.com,GBP 4056046,651826,Legge 5 Lever Sashlock Stainless Steel Case Size 64mm Backset 44mm,22.5,1,122.9,147.48,122.9,08/04/2015 09:51,peter.duck@domain1.com,GBP 4056047,969754,Exidor 305 Panic Mortice Actuator,72.5,1,72.5,87,72.5,08/04/2015 09:52,nancy.blackett@domain2.com,GBP
The filename must contain ‘transaction’ to be recognized as a transaction file.
Please also ensure that the order_id field contents are sequential as per the above example.
File formats supported: TSV, CSV. We recommend that data should be encoded as utf-8, however ucs-2 can also be used. If all the characters in your data can be represented in the first 127 characters, then you can use US-ASCII (sometimes called ANSI)
Note that:
- All files in the ftp directory which match the ‘allowed files pattern’ will be retrieved, processed and deleted from the ftp server. Therefore, the FTP account used will require read, write and delete permissions.
- You must set a wildcard such as transaction*.csv to avoid confusion with other import processes which are reading from the same FTP server.
- At present, only ’email’ and ‘eid’ need to be specified in the field mapping.
- Only the field names below are used for transaction files. By default, you should use exactly the field names specified. However, you can also specify other field names for the FTP file using the field mapping JSON.
- If you do not have a suitable customer ID, use email address. For example:
{"email":{"ftp_field_name":"email"},
"eid":{"ftp_field_name":"email"}}
- order_date must be in a recognized format. Currently, the following formats are supported:
25/04/2012 14:14 5/4/2012 14:14 8/Apr/2015 09:59 25/04/2012 25/04/2012 14:14 Thu, 19 Apr 2012 11:20:33 GMT +01:00 4 Oct 2012 08:45:35 2012-02-22T11:47:34.874Z 2012-02-22T11:47:34Z 2012-02-22T11:47:34.874 2017-06-30 14:16:02.997 2012-02-22
* Note: All transaction import records must contain either an Email Address (email) or Customer ID (customer_id), but may contain both.
| Field | Description |
|---|---|
| order_id | If omitted for a record, the record will be treated as being part of the same cart as the previous record |
| email* | Email address. Required if a customer_id is not provided. |
| customer_id* | Customer Identification. Required if a email address is not provided. |
| product_id | using same coded values as will be used by Pure360 Personalisation to capture data from the website. |
| order_date | |
| order_id | cart_price |
Optional Fields but are required for the transaction data to be used in recommendations
| Field | Description |
|---|---|
| item_price | Item price |
Optional Fields
| Field | Description |
|---|---|
| item_name | |
| qty | |
| cart_price_including_tax | |
| cart_price_excluding_tax | |
| curr | Currency |
| sbr | Site Brand / product Set |
| cat | Category Array. You should use a list_separator for this field if more than one category will be supplied |
| lang | Language |
| opt | Product Options |
| ex | Cart Extra Data |
| return_reason | If a return_reason is specified then this transaction will be treated as a return. This means a “Return Purchase” signal will be raised instead of a “Purchase”. |