Trackline calls, typed on arrival.
Add Basalt as a destination in Trackline. Track, identify and page calls become typed rows you can join with the rest of your data.
How it works.
Trackline delivers events to a Basalt ingest endpoint over HTTPS. Basalt deduplicates by messageId, types each event by its name and properties, and keeps one table per event so schemas stay narrow.
Set it up in three steps.
Add the source
Create a write key in Basalt, then add Basalt from the Trackline destination catalog and paste the key. Events start flowing on the next call.
# create an ingest key for the Trackline destination basalt source add web --segment --workspace acme-prod ✓ write key created · paste into Trackline ✓ first events received · track, identify, page
Shape it with a view
Write plain SQL over the source. Basalt keeps the view current with every record and tracks lineage back to the topic, partition and offset.
CREATE MATERIALIZED VIEW revenue_by_min AS SELECT date_trunc('minute', ts) AS minute, currency, sum(amount) AS revenue, count(*) AS payments FROM payments WHERE status = 'captured' GROUP BY 1, 2;
Read it from anywhere
Every view is an endpoint the moment it exists. Call it over REST, connect with any Postgres client, or use the SDK from your app.
curl https://api.basalt.dev/v1/views/revenue_by_min?limit=5 \ -H "Authorization: Bearer $BASALT_TOKEN"
What you get.
Per-event tables
Each track event gets its own typed table, built from the properties it sends.
Identity stitching
Identify calls link anonymousId to userId, so views can resolve sessions to people.
Message dedup
Trackline retries are dropped by messageId within a 24-hour window.
Tracking plans
Rows that break a Protocols plan are tagged, not dropped, so you can find them.
Set your data in stone.
Free up to 10M events a month. No card, no sales call. Your first pipeline is live in about four minutes.