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.
Requirements
- You need user permissions that grants you access to Simple Imports or/and Automation
- Prepare a
.csv
file 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):- a
client
column - 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. - an
orderId
column which contains IDs of the transactions - a
paymentInfo.method
column which describes how the transaction was paid (for example, cash, online, and so on) - a
products.finalUnitPrice.amount
column which contains the final price of items - a
products.finalUnitPrice.currency
column which contains the currency of the final price - a
products.name
column which contains the name of the purchased item - a
products.quantity
column which contains the number or quantity of purchased items - a
products.sku
column which contains the SKU of purchased items - a
revenue.currency
column which contains the currency of the transaction - a
value.currency
column which contains the currency of the transaction value before taxation - a
source
column 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.
.csv
files must be UTF-8 encoded- The file cannot contain empty fields. If you want to leave empty fields, enter the
null
value. - Maximum file size: 200 MB.
- a
Example