Get your Vexo data into your stack
Export to your warehouse, connect the tools you already use, wire up custom webhooks, and decide how long your data sticks around
August 20, 2026
Jump to section
Analytics you can't get out of is analytics you don't fully own. The most useful thing Vexo can do with your events, sessions, and errors is often to hand them off — to your data warehouse, to the tools your team already lives in, or to a bit of code you wrote yourself. This post is a tour of the ways Vexo lets your data leave: scheduled bulk export, prebuilt integrations, outbound webhooks, and the retention controls that decide how long everything lives.
The shape is simple. Get raw data into your warehouse with export, push signals into the tools you use with integrations, cover anything custom with webhooks, and use retention to control the lifespan of it all. Here's each piece.
Bulk export to your data warehouse
Scheduled exports take your event data out of Vexo and drop it in cloud storage (S3) as flat files you can load anywhere — Snowflake, BigQuery, Redshift, DuckDB, or a plain script. You set up an export job per app, pick a format and a cadence, optionally narrow it to the events you care about, and Vexo does the rest on schedule. Every run is recorded, so you can see exactly what was written and when.
You choose two things: the file format and how often it runs.
| Setting | Options |
|---|---|
| Format | CSV for spreadsheets and quick loads, or NDJSON (newline-delimited JSON — one event object per line) for the shape most warehouses ingest directly. |
| Cadence | Hourly, daily, or weekly on a schedule — or keep it manual and fire a one-off run whenever you need a fresh pull. |
| Scope | Export everything, or filter to specific event types or a single named event so a job only carries the slice a downstream table expects. |
Scheduled jobs run in the background — a daily job wakes up once a day, renders the new window of events to a file, and uploads it. Need last night's data right now instead of waiting for the next tick? Trigger a run on demand and pull the file as soon as it lands.
Integrations for the tools you already use
Not everything belongs in a warehouse. Sometimes you just want an event to show up where your team already works. Vexo connects to a growing set of tools from each app's settings — here are the ones live today.
Segment
Forward Vexo's custom events into Segment and fan them out to every downstream destination Segment already feeds. Paste your Segment source Write Key, and Vexo starts forwarding. Want only a subset? Give it a comma-separated allow-list of event names; leave it blank to forward every custom event. There's a single toggle to pause forwarding without deleting your key, so you can stop the flow during a migration and turn it right back on.
Microsoft Teams
Send Vexo alerts straight into a Microsoft Teams channel using a Teams Incoming Webhook URL. Pick which alert types you want delivered, or leave them all unchecked to receive every alert. It's the fastest way to make sure the right channel hears about what's happening in your app without anyone having to keep a dashboard open. Delivery has its own enable toggle, so you can mute it without losing the configuration.
Jira
Connect your Jira site with its URL and an API token, and turn what Vexo catches into tracked work. Instead of copy-pasting an error into a ticket by hand, you can push it into Jira with the context attached — so the bug that showed up in your sessions becomes a real item in your backlog, not a note someone loses.
These sit alongside integrations we've shipped before, including GitHub and Slack. If the tool you want isn't on the list yet, the next section has you covered.
Outbound webhooks for anything custom
When there isn't a prebuilt integration for what you need, outbound webhooks are the escape hatch. Point Vexo at any HTTPS endpoint you control and it will POST a JSON payload there as events happen — feed a Lambda, a queue, an internal service, or a workflow tool like Zapier or n8n. It's the same “data out” idea as export, but real-time and event-by-event instead of batched into files.
You choose which events a hook fires on: subscribe to custom events, errors, or use a wildcard to receive everything. And because networks are flaky, delivery isn't fire-and-forget — if your endpoint is briefly down or returns an error, Vexo retries the delivery rather than dropping it on the floor. You get an at-least-once handoff you can build on.
Control how long your data is kept
Getting data out is half the story; deciding how long Vexo holds onto it is the other half. Under Settings → Data retention, you can see and manage the window Vexo keeps your sessions, replays, and events before they're automatically deleted. Free workspaces keep roughly the last 60 days; paid plans keep about two years by default. Aggregated metrics — the rolled-up numbers behind your charts — are always kept longer than raw sessions, so your long-term trends stay intact even after the underlying replays age out.
Need to hold raw data longer for compliance or historical analysis? Extended retention is a paid add-on that stretches the window for sessions, replays, and events up to several years. You pick the length, confirm the change, and it bills from your next cycle — and you can dial it back down whenever you want. Retention is a lever you control, not a fixed policy you're stuck with.
How the pieces fit together
Reach for export when you want raw events in a warehouse for BI, modeling, or joining against other data. Reach for an integration when you want a signal to appear in a tool your team already uses — analytics routing through Segment, alerts in Teams, bugs in Jira. Reach for a webhook when you want real-time, per-event data flowing into something you built yourself. And use retention to make sure everything lives exactly as long as you need — no more, no less.
Frequently Asked Questions
What formats can I export?
CSV and NDJSON. CSV is handy for spreadsheets and quick loads; NDJSON (one event object per line) is the shape most data warehouses ingest directly, so it's the better default for a warehouse pipeline.
How often do exports run?
You choose: hourly, daily, or weekly on a schedule, or leave a job manual and trigger a one-off run whenever you need fresh data. Every run is recorded so you can confirm what was written.
Can I forward only some events to Segment?
Yes. Provide a comma-separated allow-list of event names and Vexo forwards only those. Leave it blank to forward every custom event.
What happens if a webhook delivery fails?
Vexo retries it. A brief outage or an error response from your endpoint won't silently drop the event — delivery is retried so you get an at-least-once handoff.
How long is my data kept?
Free workspaces keep about the last 60 days of sessions, replays, and events; paid plans keep roughly two years by default, with aggregated metrics kept longer. If you need more, extended retention is a paid add-on that stretches the window up to several years. You manage all of this under Settings → Data retention.
Want to put your Vexo data to work in the rest of your stack? Start free, or tell us what you'd like to connect next at hello@vexo.co — we're listening.
