Every one is ready to run, and you can adjust it in plain language.
Start analysis from usable CSV rows and review source line errors.
Your analysts get CSVs from new text exports in a shared folder. A companion report points to source lines that need fixing.
Combine weekly extracts and count exact duplicates removed.
Get a downloadable CSV from your teams' weekly extracts when the files are usable. See what needs attention in a summary beside it.
Deliver checked data extracts to colleagues each month.
Get a dated CSV and row count in your shared folder every month, or an error note explaining why the export stopped.
Load new CSV data into a table and flag failed imports.
Keep your PostgreSQL table current as CSV files arrive, with a row count or a clear reason when an import needs attention.
Load valid activity rows and flag rejects for analysis.
Get fresh website activity in your analysis table, with an import tally and a report of rows that need fixing.
Export updated query results with the agreed column headings.
Your report preparer gets a fresh Excel workbook when the SQL reporting table changes. The rows follow your chosen query and headings.