Free Data Tools for Product Analysts: Event Exports, Funnels and Cohorts

Product analytics tools answer the standard questions. The rest, such as an odd funnel, a one-off cohort or a raw export that needs checking, ends up as a CSV on a product analyst's laptop. This guide shows how to work with event exports using free browser tools, including SQL for funnels and retention.

Open the SQL on Your Files

Start by profiling the export

Event exports have predictable problems: duplicated events, missing user IDs, timestamps in mixed time zones and test accounts. Open the file in the data profiler first. Check the user ID column for blanks and the event column for typos such as `signup` and `sign_up`.

Funnel with SQL

Load the export in SQL on your files. A basic two-step funnel counts users who did step one and then step two:

select count(distinct a.user_id) as signed_up,
       count(distinct b.user_id) as activated
from events a
left join events b on b.user_id = a.user_id and b.event = 'activated'
where a.event = 'signed_up';

Adapt it to the SQL dialect and add time conditions, such as activation within seven days.

Retention by cohort

Group users by the week of their first event, then count how many return in later weeks. Keep the query in a file so it can be rerun on next month's export.

Compare two periods or releases

Use data comparison to compare two exports by a key, for example the list of users on a plan before and after a pricing change.

Mask users before sharing

Before a file goes to a vendor or a wider team, hide emails and names with data masking. Keep the user ID if joins are needed, but check whether the ID itself is personal in your context.

Realistic data for prototypes

Building a dashboard prototype? Generate events and users with the test data generator instead of using real behaviour.

Limits

This works on exports, not live event streams. Very large event logs may exceed browser memory; filter or sample first. Your product analytics tool is still the right place for standing dashboards.

Open the SQL on Your Files

Related tool pages

  • Query a Large CSV with SQL: Run SQL on a CSV of 500 MB or more without a database. Filter, group and export the result. Runs in your browser.
  • Query a CSV File with SQL: Query a CSV file with SQL online. Filter, group, sort and join with DuckDB in your browser. No database, no install and no upload.
  • Run SQL on an Excel File: Run SQL queries on an Excel file without importing it into a database. Join sheets from different files and download the result.
  • Query Parquet Files Online: Open and query Parquet files with SQL in your browser. Preview, filter, aggregate and export to CSV without installing anything.
  • Join CSV Files with SQL: Join two or more CSV files with SQL JOIN: inner, left, right or full. Runs in your browser with DuckDB and nothing is uploaded.
  • DuckDB in Your Browser: Use DuckDB in your browser with no setup. Drop in CSV, Excel, JSON or Parquet files and run analytical SQL on your own computer.

Also try

How to use the SQL on Your Files: step by step

  1. Export events as CSV.
  2. Profile for blanks and duplicates.
  3. Run funnel and cohort SQL.
  4. Mask and share results.

When to use the SQL on Your Files

  • Funnels and cohorts from raw exports
  • Cleaning duplicated events
  • Comparing plan membership across periods
  • Masking users before sharing

Example

Input: sales.csv + customers.xlsx

Output: SQL query result

Frequently asked questions

Can I do funnel analysis from a CSV export?

Yes. Load the event export in SQL on your files and count distinct users at each step, adding time conditions as needed.

How do I calculate retention from event data?

Group users by the week of their first event and count how many have events in each later week, using SQL on the exported file.

How do I clean duplicate events in an export?

Profile the file to find duplicates, then remove duplicate rows with the data transformation tool.

Is user data uploaded?

No. Files are processed in your browser and not uploaded to our servers.

Tip: Always filter out internal and test accounts before computing any funnel. They are the most common reason a conversion rate looks too good.