This article covers the Backoffice setup guide for the mParticle Interface with Bepoz.

Prerequisites

For an Operator to be able to setup the mParticle Interface, the following Operator privileges must be enabled:

mParticle Transaction Queue Device Setup

A Transaction Queue Device is required to support sending Account Sales information from Bepoz to mParticle

This will only send the Transactions when the Account Parent Group name start with “*TSG” or “*TGIF”

After logging into BackOffice, complete the following steps to create & configure a mParticle Transaction Queue Device:

Navigate to the System Setup component in the sidebar, expand, and select Venue, Stores & Tills to open the Venue & Till List Tab
Highlight the desired Till and click on the Add New Device button in the header; when prompted select 'Blank Device' and a New Device and Interfaces Maintenance window will open
Enter a relevant Device Name, set the Device Type to 'Transaction Queue', set the External DLL Name to 'Transqmparticle.Dll', and the Class Name to 'M Particle Device'
Within the Device Options, configure as follows:

ON: When the flag is enabled, separate log files are generated in the local directory c:\Bepoz\Data\mParticle.log
OFF: When the flag is disabled, no log files are generated and stored

ON: When the flag is enabled, the information payload sent to mParticle is also logged locally in the SmartControllerLog file

OFF: When the flag is disabled, the information payload sent to mParticle is NOT logged