Skip to main content

Transactions XML import

The API is the preferred way of creating and updating contacts in Engage. However, sometimes file-based imports are more suitable, for example when another system is the master and immediate updates are not crucial.

Engage connects all purchases to the contact who made them and this can later be used for segmentation and analysis. The transaction object has some flexibility in order to fulfill a client’s specific needs. In addition to the standard fields, you can add up to 10 extra string fields and up to 5 extra date fields which can be used for segmentation. Only include fields that are necessary since every additional field can affect the overall performance. Read more about transactions here.

Please read about file based integration before going any further!

Naming the files

Files sent to the FTP server should follow this naming convention:

[Timestamp]_[sequence number OR store id] _transactions.xml

[Timestamp] should be formatted as: YYYYMMDDHHmmss.

The sequence or store id is only needed if there's a risk that several applications might send XML files at the same time, although it is never wrong to include it.

A correct filename has this form: 20220808134729_471_transactions.xml

FTP location

The XML files should be placed here:


Scheme and field definitions

You can download the basic XSD scheme used for the XML import on the example files page.

Find the complete list of Field definitions here.

Register a purchase

Read more about registering a purchase here.

<?xml version="1.0" encoding="utf-8"?>
<transactions xmlns="http://voyado.Schemas.ImportReceipts">
        <description>25kr bonuscheck</description>
          <item name="cardNumber">489456*</item>
          <item name="cardIssuer">ICA Banken</item>
        <articleName>Stickad tröja V-neck</articleName>
            <description>50% rabatt nedsatt vara</description>

Register a return

Read about registering a return here.