Under Reports, the Audit Log is the account’s diary. It is one list in time order, newest first, and it answers the question you actually have when something looks odd: what happened, and when.
What is in it
- Stamps, including the joining stamp and the birthday stamp, with whoever was signed in at the time.
- Rewards: Reward Earned when a customer finished a card and kept the reward for later, and Reward Spent when you handed one over.
- Wallet updates: the copy of a card in Apple Wallet or Google Wallet catching up, or failing to.
- Messages: anything you said to a customer’s wallet, and what that card actually got.
- Changes to your locations: a place added, edited or deleted, and every event in your trading week added, edited or deleted, with the name of whoever saved it.
Narrowing it down
The Event filter is the quickest way in. Stamp, Reward Spent and Reward Earned show the counter activity on its own; Wallet updates and Messages show the two things that happen without anybody pressing a button; Locations and Daily events show what has been changed about where and when you trade. Search finds a customer by name, email or card code, and the date boxes take a range.
The User and Location filters skip the wallet and message rows, because neither has a person or a place behind it: a wallet update is us keeping a promise about a stamp somebody already made, so it is recorded as System. Everything else has both. Picking a place gives you its whole history, the stamps taken there and the changes made to it, including places you have since deleted.
The wallet words
- Wallet update failed: a card’s copy in a wallet did not get the change. The line underneath says which wallet and what it told us.
- Retry queued, then Retry succeeded or Retry failed: we try again on our own, a few times over about an hour and a half.
- Retries given up: we stopped trying. This is the one worth telling us about.
- Wallet back in sync: a card that was behind has caught up.
Most cards never produce any of these. A wallet update that works writes nothing, on purpose: a line for every stamp saying the wallet copy updated as usual would bury the handful of lines that matter.
The message words
Message sent is one you typed; Birthday message, Reward message and Progress message are ones a Program sent on your behalf. The line underneath says what that one card got, including when our daily limit turned a notification into a quiet update. Message failed means every wallet holding that card refused it.
The location words
Location Added, Location Edited and Location Deleted are the places themselves. Daily Event Added, Edited and Deleted are the events in your trading week. The line underneath says what actually changed: the day and the times on a new one, and on an edit the value it had before, so "Tuesday: start time changed from 09:00 to 09:30" tells the whole story without opening anything.
Saving a page you have not changed records nothing, so pressing Save twice does not fill your log up. Deleting a place writes its own line and one for each event in your trading week that went with it, which is what you need if you take the same pitch again next season.
Take it away as a spreadsheet
Export CSV, under the filters, downloads what you are looking at. It is the events your filters, your date range and your search select, all of them, not just the page on screen, in whatever order you have the table sorted into. So set the log up the way you want it first, then press Export CSV: filter to one Program, one place, one person or one kind of event, search for a customer, put the dates around the month you are interested in, and the file matches.
The file opens in Excel, Numbers, Google Sheets or anything else that reads a CSV. It has a column for the date and time (UK time, in a form a spreadsheet sorts properly), the event, the line of detail under it, the customer’s name and email, the Program and its code, the user who did it, the location, and one more called Source that says which part of LoyalPack the row came from: Card activity, Wallet update, Message or Settings change.
A cell is left empty where the column does not apply, rather than saying so in words: a settings change has no customer and no Program, and a Program that collects no names has no name to give. That keeps the file countable. On screen those same cells show a dash or "Not collected", because a person reading a table wants telling.
One file carries up to 10,000 events. If your filters select more than that, the count under the table says so and the file gives you the first 10,000 in the order shown; narrow the dates and take it in a couple of goes.
We can ask a wallet to show a message; we cannot see whether the customer read it. Nothing here ever claims a message was delivered, because neither Apple nor Google tells us.