Replies: 1 comment
-
I can only assume I am missing something here, but the docs are not much help to me. When I track an event , why is everything separated?? If I send umami.track('viewDoc', {sessionId, projected, userId}) I was expecting to be able to find a single event with that information in, instead it seems to create separate entries for each property I am sending... using eventsDataEvents: {eventName : "viewDoc", fieldName: "sessionId", dataType 1, total 1} using eventsDataFields {fieldName: :"sessionId", dataType:1, fieldValue: "123", total 1} Why would I want that? How am I supposed to relate them so I can see they all occurred at the same time? I was expecting to be able to get a single object back with all the information like this... {eventName : "viewDoc", sessionId:"123", projectId:"123",userId:"123"} Is there any further docs about actually using events in a meaningful way? |
Beta Was this translation helpful? Give feedback.
-
Every time someone visits a particular page I am sending a custom event...
umami.track('viewDoc', {sessionId, projected, userId});
where sessionId is a unique identifier to track the visit, projectId is an internal ID to track the project, and userId is the user whose project it is.
I now want to be able to get all events that relate to a particular user but can't figure out which API call will do this. I was looking at the following...
getEventDataEvents(id, data)
getEventDataFields(id, data)
getEventDataStats(id, data)
None of them give the data back how I would expect.
Ultimately I want to be able to build a dashboard for the document creator so they can see how many times a document is opened, where it was opened from(location) and other stats like on the default dashboard, but obviously just for them, they shouldn't be able to see anyone else's metrics.
How can I just return the data for a particular userId? Thanks!
Beta Was this translation helpful? Give feedback.
All reactions