Tedooo Panel

Create a project

In the console, Analytics › Projects › New: a name and the platform. The project key is shown once created. Members with analytics.view see the project in Panel; analytics.manage edits boards and settings; analytics.query runs custom and SQL queries.

Send events

Panel’s collector accepts the event SDKs most teams already ship. Keep your code and point the SDK at Tedooo’s host with your project key:

// Any SDK that takes an api_host / host option:
init('<project key>', { api_host: 'https://ingest.tedooos.com' })

track('Order Completed', { revenue: 49, platform: 'web' })
identify('user_123', { plan: 'pro', country: 'NL' })

Events appear in Events › live tail within seconds. Name events in Title Case and properties in snake_case, and describe them in the Lexicon so the assistant and your team read them the same way.

The first board

1. Boards › New board. Give it a name; pin it as home if it is the one everyone should see.
2. Add a report: pick Insights, Funnels, Flows, Retention, Stickiness or Lifecycle. The report is built in place and re-runs 400 ms after every valid change.
3. Add metric cards for the numbers that matter (unique users, orders, revenue) with the change against the previous period.
4. Set the board’s range and filters; every card follows them.
5. Subscribe… sends a daily picture of the board to Slack or email through Tedooo OS.

Business data

• Custom queries: connect a MongoDB database under Credentials › Data sources in the console, then write find or aggregate queries with {{start}} and {{end}} placeholders. Save one and it becomes a preset in Insights.
• Stripe and Meta Ads: report sections that read the credentials the organisation already holds.
• SQL: one guarded, read-only SELECT with a cost estimate, for managers.

Ask AI

Off until an Admin switches it on in Panel’s settings. When on, the drawer answers questions by running real reports and can build or edit boards for managers. The model sees event and property names and aggregate results only.

Bringing your history

Imports walks a BigQuery export of your previous tool into the project and produces a parity report, so you can compare the numbers before you switch your SDKs.