Skip to content

Customer Log History

Menu Location: Customers > Last Cust Viewed > Log History

Last Updated: 2026-07-26


Overview

The Customer Log History page shows the raw activity log for one customer account. Every row is a single timestamped text line pulled from the system's internal activity log (the syslog table): things like recurring item changes, order edits, logins/logouts, and other admin or automated actions get written here as they happen.

The log is not a curated, categorized audit trail. It is a running feed of whatever the code wrote at the time, so it also picks up page-view and browsing noise. Because of that, the page defaults to a filtered "Simple View" that hides the noisiest entries, and also offers a "Detailed View" that shows everything.

Primary Functions:

  • View recent activity on a customer's account (logins, order changes, recurring item changes, admin edits)
  • See which admin made a change, when one is recorded
  • Filter to a date range
  • Filter to customer-only activity, admin-only activity, or both
  • Switch between a plain chronological list ("Old View") and a grouped, icon/badge view ("New View", work in progress)
  • Do a client-side keyword search over whatever is currently on screen

Note: This menu item only appears after you've opened a customer account elsewhere in the admin (it works off "last customer viewed"). It is not a standalone searchable log across all customers.


Page Layout

Header Section

The same customer summary header used across the customer's other sub-pages: avatar, customer name/username, and subscription status coloring, with a "Log" tab active and a "Back" button that returns to the customer's main account page.

Main Content Area

Above the log, a filter form ("From" / "To" date pickers, a Simple/Detailed View dropdown, a Cust & Admin / Only Customer / Only Admin dropdown, and a New View / Old View dropdown) plus a "Set Filters" button, and a client-side "instant search" text box.

Old View (the classic layout) shows one row per log entry:

  • Date and Time - when the entry was written
  • Source - the admin's username if the entry was made by a logged-in admin/staff user, otherwise blank (or a plain "admin" badge if an admin ID is present without a username)
  • Entry - the raw log text. Most entries are shown as-is; a small number of specific entry types (currently, new-customer signup entries) are reformatted into a readable table instead of the raw string

New View (work in progress, toggled per-admin-user) groups entries by day/hour block and adds:

  • An admin column showing a wizard-hat icon and username (linked to that admin's user page), only shown when the entry has an admin recorded
  • A badge for entries matched by keyword: SUBSC (recurring item added/removed/updated), LOGOUT, ORDER (subbed-out items, items added/removed from an order, or any entry tied to an order), LOGIN
  • An order # column (linked to the order) with its delivery date, when the entry is tied to a specific order; shows "deleted" if that order no longer exists
  • A small icon for specific recognized event text: login, logout, recurring item added/removed/updated, item subbed out, item added to an order, order item quantity changed, item deleted, "could not add" system errors, QR code, and label downloaded

New View also collapses repeated identical entries that land within a couple of minutes of each other, so a single underlying action doesn't show up as several rows.


Search & Filtering

Date Range: "From" and "To" date pickers. Defaults to the last 30 days through today.

Simple View vs. Detailed View: Simple View (the default) hides internal noise: page-view/browsing entries, background debug queries, Intercom and ActiveCampaign sync triggers, guest-session entries, permanent-auto-sub notices, and a few other internal-only messages. Detailed View shows all of it.

Cust & Admin / Only Customer / Only Admin: Filters rows by whether the entry has an admin ID attached, i.e. whether it was written by staff action or not.

Instant search box: Filters the rows already loaded on the page by keyword, client-side, as you type. It does not query the database or go outside the current date range.

There is no export, no admin-specific dropdown, and no "action type" category filter beyond the two dropdowns above.


Common Use Cases

Use Case 1: Investigate a Disputed Change

Goal: Customer claims their address, box type, or another account detail was changed without their knowledge.

Steps:

  1. Open Customer Log History for the customer
  2. Set the date range to cover when the change would have happened
  3. Switch to Detailed View if Simple View doesn't show it
  4. Use the instant search box to narrow by keyword (e.g. part of an address or item name)
  5. Check the Source/admin column to see who made the change, if it was staff
  6. Check the timestamp against the customer's account of events

Use Case 2: Review Recurring Item / Subscription Changes

Goal: Understand why a recurring item was added, removed, or changed.

Steps:

  1. Open Customer Log History
  2. In New View, look for the SUBSC badge, or search for "recurring" in Detailed View
  3. Check the timestamp and admin column for who made the change and when

Use Case 3: Trace Changes to a Specific Order

Goal: See what was added, removed, or changed on one order.

Steps:

  1. Open Customer Log History
  2. Search for the order number, or look for the ORDER badge / order # column in New View
  3. Click the linked order number to jump to that order's detail page
  4. Read the entries in chronological order to see the sequence of changes

Use Case 4: Check Login Activity

Goal: Confirm whether the customer (or an admin acting on their account) logged in around a given time.

Steps:

  1. Open Customer Log History
  2. In New View, look for LOGIN / LOGOUT badges, or search "logged in" / "logged out" in Detailed View
  3. Cross-reference the timestamp with the customer's report

Troubleshooting

Cannot Find a Specific Change in the Log

Check:

  1. Widen the From/To date range - the default window is only the last 30 days
  2. Switch from Simple View to Detailed View - the change may be one of the entries Simple View hides
  3. Try different keywords in the instant search box - it matches whatever text was written into the log, not a fixed vocabulary
  4. Confirm you're looking at the correct customer account

Log Shows Too Many Entries

Solutions:

  1. Narrow the date range
  2. Stay in Simple View to hide page-view/browsing noise
  3. Use the instant search box to filter to a keyword
  4. Switch to New View, which groups entries and collapses near-duplicate rows

Cannot Identify Who Made a Change

Understanding:

  • A username in the Source/admin column means a logged-in admin made the change
  • A blank Source means no admin was recorded on that row (often a customer-initiated or automated action)
  • The log does not record an IP address, so there is nothing else to check for attribution beyond the admin column and the surrounding entries

These live in the same "Last Cust Viewed" menu group as Log History, and only appear once you've opened a customer account:

  • Current Customer - the customer's main account page
  • Email History - the customer's email log
  • Order Viewed - the last order viewed for this customer
  • SMS Messages - SMS history, if SMS is enabled for the tenant
  • Cancelled - the customer's cancellation record, if applicable

Quick Reference Card

Task Action/Location
View customer log Customers > Last Cust Viewed > Log History
Narrow to a time period Set the From/To date pickers, then "Set Filters"
Hide noise Leave "Simple View" selected
See everything Switch to "Detailed View"
Filter to staff-only or customer-only activity Use the Cust & Admin / Only Customer / Only Admin dropdown
Search current results Type in the instant search box
Try the grouped layout Switch the New View / Old View dropdown to "New View"
Jump to an order from the log Click the linked order number (New View)
Return to the customer Click "Back"

FAQs

How far back does the log go?

The date filter defaults to the last 30 days, but you can set an earlier "From" date to look further back, as long as entries exist for that customer.

Can I edit or delete log entries?

No, there is no edit or delete option on this page.

Why do some entries show no admin name?

The admin column is only populated when the action was taken by a logged-in admin/staff session. Customer-initiated actions and some automated/background actions do not have an admin attached.

Can customers see this log?

No, this page is admin-only.

Does the log track IP addresses or before/after values?

No. Each log row is a single free-text description plus a timestamp and (optionally) the admin who triggered it. There is no IP address field and no separate "old value" / "new value" columns.

Why are there so many similar-looking entries?

The underlying log is written by many different parts of the system as things happen, not by a single curated event list, so related actions can produce several entries close together. New View collapses immediate duplicates; Simple View hides the most common noise.


End of Documentation

For additional help, contact your system administrator or Kiva Logic support.