Export visit results
Use Export CSV in the results toolbar to save every visit result to a file you choose. Completed runs also produce an Excel report, opened with the Open Excel button on the run summary.
Export to CSV
In the results toolbar, click Export CSV. You will be asked where to save, with a default filename of overrider_results.csv.
The export contains every visit result currently in the table, not just the visible rows.
Open the Excel report
When a run completes, the summary offers Open Excel, which opens the generated report from that run’s output folder. This is a formatted report rather than a raw dump — useful for sharing with someone who does not have OverRider.
What to do with the data
The most common uses:
- Calculate the real success rate over a long run, rather than reading the live card.
- Group failures by error to see whether they are proxy failures, site blocks or timeouts. This changes what you fix.
- Check target URL distribution — with random selection, each URL should get a roughly equal share over a large run.
- Correlate with your analytics by comparing visit timestamps against your GA4 Realtime figures.
The gap between OverRider’s success count and what your analytics recorded is the single most informative number you can produce. A large gap almost always means bot filtering or a tag that is not firing, not a traffic problem.
Keeping records across runs
Export at the end of each run and name the file with the date and project, for example 2026-08-27-site-a.csv. Comparing exports over weeks makes proxy quality trends obvious in a way the live dashboard never does.
Opening CSV in Excel
If Excel mangles long numbers or misreads columns, use Data → From Text/CSV rather than double-clicking the file. That opens the import dialog where you can set each column’s type explicitly.
Where run output is stored
Each completed run writes to its own output folder, which the Open Excel button opens. Your projects and settings live separately:
- Projects:
%APPDATA%OverRiderprojects - Global settings:
%APPDATA%OverRiderglobal_settings.json - Device profiles and proxies:
%APPDATA%OverRideror.db
Those files are worth including in a backup if you have spent time building up a project set.
Last updated: