Realtime TTS-2 is live. Built for realtime conversation that feels human. Read the Realtime TTS-2 announcement

Data integrations

Data integrations overview

Integrate with your analytics platforms to measure routing impact on your KPIs

Connect your analytics platform to export router data and import custom events. Exported data lets you analyze routing performance alongside product metrics. Imported events let you define KPI metrics in Portal and measure how routing decisions affect them.

How it works

Connect your analytics platform

Add your Mixpanel or BigQuery credentials in Portal — open Routers > Metrics and click Set up data integration. The same connection is used for both exporting and importing.

Export router exposure data

When users interact with your router, exposure data (which router, route, and variant was served to which user) is automatically sent to your analytics platform. You can use this data to build dashboards and segment users by their routing assignment. Exposure is recorded for requests to a saved router that carry a user ID, on chat completions, the Responses API, and the Messages API.

Import your product events

Tell Inworld which of your product events to pull in — purchases, signups, conversions, or any other events you track. Inworld syncs these events into Portal so you can use them as KPI signals.

Define custom metrics

Create metrics in Portal that aggregate your imported events (unique users, total events, property sums or averages). Associate metrics with routers to see how different routes and variants affect your business KPIs.

Supported platforms

PlatformExportImportGuide
Mixpanel✅✅Mixpanel integration
BigQuery✅✅BigQuery integration

Data sync

Both export and import sync automatically approximately every 8 hours. Data is aggregated into hourly buckets — each bucket captures the distinct users, routes, and variants observed during that hour.

What is not exported

Data integrations export routing exposure only. They do not export request logs, prompts, responses, token counts or costs. For usage and cost data, see Usage or query the Usage API.

Next steps