Export your analytics data

You own your data. Elido has three ways to get it out of our system, depending on how much of it there is and how often you need it.

Quick CSV export#

For a single link or a date range up to 90 days:

1. Open the link's Analytics tab (or the workspace-level analytics page for a multi-link export).
2. Click Export → CSV.
3. We background the job — it lands in your notifications inbox within 30 seconds for under 100K events, or up to a few minutes for larger ranges.

The CSV columns match the click event schema. The file is UTF-8 with a BOM so Excel doesn't mangle non-ASCII characters in country names or UTM values.

Scheduled exports#

On Pro+, you can schedule a recurring export to your own email or an S3-compatible bucket. The cron lives in notification and supports daily / weekly / monthly cadences with timezone-aware scheduling (so "every Monday 09:00 in Europe/Berlin" stays correct across DST).

Configure it under Settings → Reports → Scheduled exports. Each schedule emits the previous period's events on the cadence you pick.

ClickHouse export (Business)#

If you want to land click events directly in your own ClickHouse cluster, the analytics-export worker can stream events to your clickhouse:// DSN as they arrive. Setup:

1. Settings → Integrations → ClickHouse export.
2. Paste your DSN. We test the connection before saving.
3. Pick which tables you want populated — clicks_raw, clicks_hourly, or both.

Once enabled, your cluster receives a copy of every click event within ~5 seconds. We never delete from your cluster — retention there is your concern.

Programmatic export (API)#

For lighter integrations, the /v1/clicks endpoint returns click events as JSON, paginated with cursor-based pagination. The SDKs wrap this with helpers like client.clicks.recent() and client.clicks.range(from, to).

This is the right tool for syncing into a customer-data warehouse on a daily-batch cadence (Fivetran, Airbyte, custom Python). For higher-volume real-time use cases, the ClickHouse export above is the better fit.

GDPR-friendly export#

When you export, we redact any field that you've opted out of via retention controls. Re-running an old export against a since-shrunk retention window is safe — the missing rows are simply not in the file.