Importing transactional data
By importing transactions to Synerise, you can prepare analyses of transactions. The output of the import is transaction.charge events generated on the profile cards of customers indicated in the imported file.
- You need user permissions that grants you access to Simple Imports or/and Automation
- Prepare a
.csvfile that contains the following data (the list contains recommended column names, if you use different names you will be able to map/transform data during the process):
clientcolumn - a column with profile identifiers, you can use one of the following identifiers: email, uuid, clientId, or customID.WARNING: If you choose an email as an identifier, pay attention to the correct format of emails. Otherwise, your import will fail.
orderIdcolumn which contains IDs of the transactions
paymentInfo.methodcolumn which describes how the transaction was paid (for example, cash, online, and so on)
products.finalUnitPrice.amountcolumn which contains the final price of items
products.finalUnitPrice.currencycolumn which contains the currency of the final price
products.namecolumn which contains the name of the purchased item
products.quantitycolumn which contains the number or quantity of purchased items
products.skucolumn which contains the SKU of purchased items
revenue.currencycolumn which contains the currency of the transaction
value.currencycolumn which contains the currency of the transaction value before taxation
sourcecolumn which contains the source of transaction (for example, POS, WEB_MOBILE, WEB_DESKTOP, MOBILE_APP, MOBILE, DESKTOP)
- Spaces and special characters in the column headers are not allowed.
.csvfiles must be UTF-8 encoded
- The file cannot contain empty fields. If you want to leave empty fields, enter the