Once Nomni POS is connected, each customer with a valid email arrives in Liven Engage as a contact on the All Contacts list, with the details below. You can use any of them in segments, automations and personalisation. Fields are created for you on the first sync, so don't create fields with the same names yourself.
Contact details
Field | What it contains |
The customer's email. Required for the customer to sync, and used to match them | |
First name, Last name | From the customer profile |
Phone | Mobile number from the profile |
Customer and loyalty fields (update within minutes)
Field | What it contains |
Company Id | Your business ID in Nomni POS |
Member Code | The customer's member code, the same code that's scanned at the POS or kiosk |
Date of Birth | Birthday from the profile (date field) |
Registered On | When the customer joined (date field) |
Status | Active or InActive (archived) |
Reward Points | Current Nomni Loyalty points balance |
Membership Level | Current tier name |
Status Points | Not in use yet. Always shows 0 |
Points Earned In Last 5 Transactions | For example |
Points Earned In Last 5 Transactions With Date | For example |
Tags | The customer's POS tags, separated by commas |
Spend, visit and product fields (update daily)
Field | What it contains |
Initial Sale Date / Last Sale Activity | First and most recent purchase (date fields) |
Visit Count | Number of invoices |
Spend in Last 12 Months | Total spend in the past year |
Total Life Time Spend | Total spend ever |
Average Spend Amount | Total spend divided by number of invoices |
Current Month Spend / Current Quarter Spend | Spend so far this month or quarter |
Monthly Rolling Average | Average monthly spend since January, reset each January |
Quarterly Rolling Average | Average quarterly spend since Q1, reset each year |
Store Name / Store Id | Every store the customer has bought from |
Store Id With Most Visits | Stores with visit counts, for example |
Product Name, Product Id | Every product the customer has bought |
Product Variants Name, Product Variants Id | Every size or option bought |
Product Category Name, Product Category Id | Every category bought from |
Top Products | Everything the customer has bought, most bought first |
The daily update runs early each morning (Sydney time) and covers customers who were active in the previous two days. A purchase made today shows in these fields tomorrow. Run month-end or quarter-end campaigns after the period has closed.
Brandollars fields (if you sell Brandollars)
These fill in once we connect your Brandollars data. They update each time a customer buys, earns or uses Brandollars.
Field | What it contains |
Current Wallet Balance | Brandollars balance (purchased plus earned, minus used). It should match what the customer sees in the app |
Total Brand Dollars Bought | Lifetime Brandollars credited from purchases, including any bonus |
Total Brand Dollars Purchased Value | Lifetime amount paid for Brandollars |
Total Brand Dollars Earned | Lifetime Brandollars earned as rewards |
Total Brand Dollars Claimed | Lifetime Brandollars used |
Total Transactions | Visits where Brandollars were bought, earned or used (counted once per day) |
Last Earned / Last Redeemed / Last Package Purchased Timestamp | Most recent of each |
Last sync Timestamp | When this customer's Brandollars data last updated |
Brandollars customers are matched by email too. A Brandollars customer who isn't already a contact is added as a contact, but isn't added to a list.
Venue app consent (if you have a Nomni venue app)
Field | What it contains |
Consent |
|
What doesn't sync
POS email and SMS marketing checkboxes. Every customer with a valid email is added to All Contacts.
Postcode and address.
POS tags as Liven Engage tags. They arrive in the Tags field instead.
Order-by-order history. You get totals, dates and product lists rather than each receipt.
Want a field that isn't here? Let us know.
Tips for segmenting
Most of these fields are text, not numbers. Use is, contains or is not empty conditions, for example Tags contains VIP or Membership Level is Gold. "Greater than" conditions on text fields such as Reward Points or Visit Count won't behave like numbers.
Use the date fields (Last Sale Activity, Registered On, Date of Birth) for "in the last X days" and birthday conditions.
Segment POS tags with the Tags field: Tags contains …, not the "has tag" condition.
Product, store and category fields list everything bought, so Product Category Name contains Coffee finds anyone who has ever bought coffee.