Blog

Export a revised CSV file from web analytics

Edit a web analytics CSV, check headers, dates, IDs and delimiters, then export a clean revised copy while keeping the original untouched.

Emily ParkerTools and utilities Tools 4 min read

You have cleaned up a web analytics export and need to send the corrected data to a teammate or upload it to another system. Before you export, check that the columns still line up and important values, such as dates and IDs, have not changed.

Use the CSV Editor to open the file in your browser, make changes, and export a revised CSV. Keep the original file so you can compare it or start over if the result is not right.

Export a revised CSV file

  1. Open a copy of the export. Open the CSV Editor and select your analytics CSV file. The editor can open files with up to 10 million rows. For important data, duplicate the source file first and work on the copy.
  2. Check the columns before editing. Look at the header row and several rows of data. Confirm that fields such as page, date, campaign, source, sessions, and conversions appear under the expected headings. If the data is already misaligned, resolve that before making edits.
  3. Make the required changes. Find or edit values, sort rows, or remove duplicates as needed. Be cautious when removing duplicate rows: two rows with the same page or campaign may represent separate dates or traffic sources, not duplicate records.
  4. Review the edited data. Check the first and last rows, a few rows you changed, and any totals or counts that matter to your report. Compare the number of rows before and after removing duplicates.
  5. Export the revised CSV. Use the editor's export or download action to save the edited data as a new CSV file. Give the file a clear name, such as analytics-revised.csv, and keep the original export unchanged.

Before sending the new file, open it again in the editor or inspect it in a plain-text editor. Confirm that the header row is present, fields remain in the right order, and the file has the expected number of records.

What the result means

Each value appears under the right heading

The CSV structure is likely intact. Check a few rows with commas, quotation marks, or line breaks in the values, because these can make a file look unusual even when it is formatted correctly.

Values appear in the wrong columns

The; not match the file, or a quoted field; have been interpreted incorrectly. A; columns, commonly a comma, but some exports use a semicolon or tab. Check how the original file is structured before changing the; exp; ting again.

Some IDs; dates look different

Check the actual CSV text, not only how another app displays it. Spreadsheet software can interpret values when it opens a CSV. An ID such as 00127 may be displayed as 127,; a date may be ref; matted, even if the text in the exp; ted file is unchanged.

The row count is lower than bef; e

This may be expected if you removed duplicates, but confirm which fields you used to decide that rows were duplicates. A page name alone may repeat across many dates. If the count changed unexpectedly, reopen the; iginal copy and repeat the edit m; e carefully.

The file is not where you expected

The browser may have saved it to its default downloads folder; asked where to save it. Check the browser's downloads list and confirm the file name and time before exporting again.

How to fix common export problems

  1. Check the downloaded file first. Look in your browser's downloads list f; the newest CSV and confirm its name and file size. A second exp; t may have a different name if the browser added a number to avoid replacing the first.
  2. Reopen the; iginal if the edits look wrong. Do not continue changing a file with shifted columns; missing rows. Start from the unchanged source, check how its fields are separated, then make and review the edits again.
  3. Check the; quoted fields. A value can contain a comma when the field is enclosed in quotation marks. Do not treat that comma as a column break. If the file uses semicolons or tabs between fields, preserve that structure when preparing the revised version.
  4. Verify IDs; dates in plain text. If a value matters exactly, inspect the exported CSV as text. This helps distinguish a changed value from a display format applied by a spreadsheet or analytics platform.
  5. Check the header; row count again. Compare the revised file with the original. Confirm that no header was removed, no extra blank rows were added,; the number of removed records matches the changes you intended.
  6. Export in smaller sections if the browser struggles. A file with millions of rows can use substantial memory. If the editor becomes slow or the export does not finish, split the work into smaller files where possible,; check each exported part before combining or uploading it.

Keep the analytics data interpretable

A CSV stores rows; columns as text separated by delimiters. It does not preserve spreadsheet formatting, formulas, colors, or multiple worksheets. If your analytics workflow depends on those features, keep a separate spreadsheet copy for presentation; use the CSV for data exchange.

Before uploading a revised export, check the receiving system's expected column names, date format, delimiter, and required fields. A file can be valid CSV and still be rejected if the destination expects a different layout.

The CSV Editor runs in your browser, and files you open stay on your device.

More articles