Question 1

What is TrackingKoala?

Accepted Answer

TrackingKoala is an event tracking and usage analytics platform for teams that need real-time visibility into API and AI workloads. It helps you track events, monitor spend, and share usage insights without stitching multiple tools together.

Question 2

Who should use TrackingKoala?

Accepted Answer

TrackingKoala is built for engineering, product, and finance teams that need trusted operational and cost data from the same event stream.

Question 3

Is TrackingKoala only for AI products?

Accepted Answer

No. It works for any event-driven product. AI teams use it for provider/model cost tracking, while SaaS teams use it for billing visibility, feature usage, and customer reporting.

Question 4

Can non-technical stakeholders use it?

Accepted Answer

Yes. Teams can share read-only usage links for customer or project scopes, so stakeholders can monitor metrics without full dashboard access.

Question 5

What makes TrackingKoala different from generic analytics tools?

Accepted Answer

TrackingKoala is optimized for operational event telemetry: cost, charge, provider, project, customer, action, tags, traces, and metadata in one schema. It is designed for decision-making, not vanity charts.

Question 6

How do I send my first event?

Accepted Answer

Create an API key, call the tracking endpoint, and send an event payload with fields like cost, currency, environment, application, action, tags, and metadata. Most teams see their first events in the dashboard within minutes.

Question 7

Do you provide an SDK?

Accepted Answer

Yes. TrackingKoala provides an official SDK package and API examples so teams can instrument quickly and keep payloads consistent.

Question 8

Can I track both cost and charge?

Accepted Answer

Yes. You can send both cost and charge values per event to monitor margins, provider impact, and project-level profitability.

Question 9

Can I segment by environment?

Accepted Answer

Yes. Events support development, staging, and production environments so your team can separate test traffic from business-critical production signals.

Question 10

Can I organize events by project or customer?

Accepted Answer

Yes. Use application and customer fields to group events, then filter, analyze, and share scoped usage views.

Question 11

What can I filter by in the dashboard?

Accepted Answer

You can filter by environment, cost, charge, currency, provider, application, action, customer ID, tags, traces, and metadata.

Question 12

Does TrackingKoala support saved queries?

Accepted Answer

Yes. Teams can save frequently used filters and reuse them during investigations, reporting, and weekly reviews.

Question 13

Do you support real-time updates?

Accepted Answer

Yes. Dashboard views can refresh with newly ingested events so teams can monitor behavior and spend continuously.

Question 14

Can I analyze usage per project?

Accepted Answer

Yes. The projects area includes distribution and growth views to compare how different providers and workloads contribute to total spend.

Question 15

Can I export or share usage views externally?

Accepted Answer

Yes. You can generate public usage links scoped to customer or project contexts for read-only sharing.

Question 16

How do budget alerts work?

Accepted Answer

Set a threshold for an organization or project. TrackingKoala continuously evaluates spend and triggers an alert when the threshold is crossed.

Question 17

Who receives alerts?

Accepted Answer

You can configure one or more phone recipients for each alert policy so the right on-call or owner is notified.

Question 18

Can I create multiple alerts?

Accepted Answer

Yes. Teams often create layered thresholds per project plus an organization-wide safety net.

Question 19

Can external users query my internal workspace?

Accepted Answer

No. Public share links provide scoped read-only visibility without exposing your full internal workspace.

Question 20

Can teams collaborate inside the same organization?

Accepted Answer

Yes. TrackingKoala supports organizations and members so teams can operate from a shared source of event truth.

Question 21

How is pricing calculated?

Accepted Answer

Pricing is volume-based and aligned to tracked event usage tiers. The first 1,000,000 tracked events per month are free. For Stripe integration invoices, we charge 2% of invoice volume.

Question 22

Can I switch plans as we scale?

Accepted Answer

Yes. You can move between plans as your monthly tracked volume changes.

Question 23

How do API keys work?

Accepted Answer

API keys are generated per workspace and used to authenticate ingestion requests. Keys can be created, reviewed, and revoked in the dashboard.

Question 24

Is data isolated per organization?

Accepted Answer

Yes. Event data, alerts, and integrations are scoped by organization boundaries.

Question 25

Do you publish your subprocessors?

Accepted Answer

Yes. We maintain an up-to-date subprocessor list in our legal section for transparency.

Questions about TrackingKoala?

Answers about setup, instrumentation, analytics, alerts, pricing, and how to run your event operations with confidence.

General

What is TrackingKoala?

Who should use TrackingKoala?

Is TrackingKoala only for AI products?

Can non-technical stakeholders use it?

What makes TrackingKoala different from generic analytics tools?

Setup & Instrumentation

How do I send my first event?

Do you provide an SDK?

Can I track both cost and charge?

Can I segment by environment?

Can I organize events by project or customer?

Dashboards & Analytics

What can I filter by in the dashboard?

Does TrackingKoala support saved queries?

Do you support real-time updates?

Can I analyze usage per project?

Can I export or share usage views externally?

Pricing & Security

How is pricing calculated?

Can I switch plans as we scale?

How do API keys work?

Is data isolated per organization?

Do you publish your subprocessors?

Questions about TrackingKoala?

Answers about setup, instrumentation, analytics, alerts, pricing, and how to run your event operations with confidence.

General

What is TrackingKoala?

What is TrackingKoala?

Who should use TrackingKoala?

Who should use TrackingKoala?

Is TrackingKoala only for AI products?

Is TrackingKoala only for AI products?

Can non-technical stakeholders use it?

Can non-technical stakeholders use it?

What makes TrackingKoala different from generic analytics tools?

What makes TrackingKoala different from generic analytics tools?

Setup & Instrumentation

How do I send my first event?

How do I send my first event?

Do you provide an SDK?

Do you provide an SDK?

Can I track both cost and charge?

Can I track both cost and charge?

Can I segment by environment?

Can I segment by environment?

Can I organize events by project or customer?

Can I organize events by project or customer?

Dashboards & Analytics

What can I filter by in the dashboard?

What can I filter by in the dashboard?

Does TrackingKoala support saved queries?

Does TrackingKoala support saved queries?

Do you support real-time updates?

Do you support real-time updates?

Can I analyze usage per project?

Can I analyze usage per project?

Can I export or share usage views externally?

Can I export or share usage views externally?

Alerts & Collaboration

How do budget alerts work?

How do budget alerts work?

Who receives alerts?

Who receives alerts?

Can I create multiple alerts?

Can I create multiple alerts?

Can external users query my internal workspace?

Can external users query my internal workspace?

Can teams collaborate inside the same organization?

Can teams collaborate inside the same organization?

Pricing & Security

How is pricing calculated?

How is pricing calculated?

Can I switch plans as we scale?

Can I switch plans as we scale?

How do API keys work?

How do API keys work?

Is data isolated per organization?

Is data isolated per organization?

Do you publish your subprocessors?

Do you publish your subprocessors?