msgbyte / msgbyte/tianji

Event data not visible in UI

Open
#236 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
3.1k
Forks
194
Avg merge
18m
Merged PRs (30d)
3

Description

I am tracking custom events using the script tag method with data-tianji-event attributes. While the event counts appear correctly in the dashboard, the custom data properties are nowhere to be found. The rows are not clickable, and there is no drill-down view or separate "Events" tab to analyze the captured data keys (e.g., filtering by store).

Steps to Reproduce

  1. Add the tracking script to a website.

  2. Create an element with event data attributes:

<a href="..."
   data-tianji-event="redirect"
   data-tianji-event-store="MyStore">
   Click me
</a>
  1. Click the element to trigger the event.

  2. Verify in the browser developer tools that the payload is sent correctly. Mine looks something like this:

{
  "type": "event",
  "payload": {
    "website": "",
    "hostname": "127.0.0.1",
    "screen": "1680x1050",
    "language": "en-US",
    "title": "",
    "url": "/",
    "referrer": "",
    "name": "redirect",
    "data": {
      "store": "MyStore"
    }
  }
}
  1. Open the Tianji Dashboard.

Expected Behavior
I expect to be able to click the event name ("redirect") to see a breakdown of the custom properties sent with it (e.g., a breakdown of store: MyStore, AnotherStore, etc.), similar to how other analytics tools (like Umami) handle event properties.

Actual Behavior
The dashboard shows the event "redirect" and the count of times it occurred.

  • The row is not clickable.
  • There is no "Details" view.
  • The custom data is not displayed anywhere in the UI.
Image

Environment

  • Installation method: Docker (via Dokploy template)
  • Version: Latest
  • Browser: Chrome/Brave. Have also tried Safari.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named in the issue. Start by locating the dashboard event list and the existing event-data handling, then determine how a details or drill-down view could expose and filter captured properties. Done means event properties such as store values are visible and analyzable in the dashboard.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
analytics, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.