Rich Event Data
Attach any JSON data to your events. Track user details, metadata, custom properties. Click any event to see the full context.
Events without context are just noise
Knowing that a signup happened is useful. Knowing who signed up, where they came from, what plan they chose, and whether they were referred by an existing customer is far more useful. The difference between a notification and actionable insight is context.
Most event tracking tools force you into rigid schemas or limit what you can attach. You end up with events that tell you something happened, but not enough to understand why it matters or what to do next.
When your co-founder asks "who was that signup?" you should not have to dig through your database or cross-reference three different tools. The answer should be one click away.
Attach anything, find everything
Every Quicklog event can carry a JSON metadata payload. User details, transaction amounts, error stacks, feature flags, A/B test variants, referral codes. If you can serialize it to JSON, you can attach it to an event.
When you click an event in your dashboard, you see everything: the event name, description, timestamp, channel, and the full metadata payload with syntax highlighting. No truncation, no "click here to see more in another tool."
We also support reserved keys that unlock automatic formatting and future insights. Use revenue for payment amounts and we will format it as currency. Use status with values like "success" or "error" and we will color-code your timeline. Use source to track attribution.
All metadata is indexed for full-text search. Looking for all events from a specific customer? Search their email. Need to find that error with a particular message? Search the error text. The context you attach becomes the context you can find.
What you get
- Free-form JSON metadata on every event with no schema requirements
- User object with dedicated fields for id, email, and name
- Reserved keys like revenue, status, and source for automatic formatting
- Full-text search across all event fields and metadata
- Syntax highlighting in the event detail view
- Export as JSON or CSV for analysis in other tools
What to include in your events
User context
Include user email, name, and ID on every event. When you see a signup or payment in your timeline, one click shows you exactly who it was. Search by email to see all events for a specific customer.
Transaction details
For payment events, include amount, currency, plan name, and whether it was an upgrade or new subscription. Use the revenue reserved key to get automatic currency formatting.
Attribution data
Track where users came from: UTM parameters, referral codes, landing page variants. When you want to know if that Twitter campaign actually converted, the data is already attached to each signup event.
Context on every event
Attach the data that matters. Find it when you need it.