Sending Custom Events to Piskes Analytics
How to send your own event data to Piskes Analytics from inside an authenticated app — and why this isn't a public embeddable tracking snippet.
Piskes Analytics has a working endpoint for recording events beyond the default pageview tracking — useful if your team wants to track something specific to how you use the platform. Before using it, though, there's one thing to get straight: this is not a public tracking snippet you drop into an external site.
What kind of event tracking this is
The track endpoint requires an authenticated Piskes session and workspace access — the request needs to come from inside the platform, identified as a specific user in a specific workspace. That makes it fundamentally different from a public analytics pixel like Google Analytics' or Plausible's script tag, which you embed on any page and which accepts anonymous traffic. If you're picturing dropping a snippet onto your own marketing site to track visitors there, that's not what this does.
What you send
An event consists of an event type, a set of properties you define, the URL and referrer it's associated with, a session identifier, and an event ID. That event ID matters more than it might look: it's used for deduplication. If the same event ID is sent twice, the second attempt is silently ignored rather than double-counted, and the response tells you whether that happened. That makes retries safe — you can resend an event you're not sure went through without worrying about inflating your numbers.
What happens to what you send
Whatever properties you attach go through the same filtering every event goes through before storage: any property key matching a known sensitive pattern gets dropped, and string values over 2,000 characters get truncated. Build your event payloads with that in mind — don't rely on a property surviving if its name looks like it could hold something sensitive, and don't send long free-text values expecting them to arrive intact.
Where this is actually useful
The realistic use case is tracking something specific to your own workflow inside Piskes — a custom action your team cares about that isn't covered by default pageview tracking. Because it requires an authenticated session, it's suited to instrumenting your own use of the platform, not to standing up analytics for an external audience or an unauthenticated public page.