Colquhoun.AI
← All guides

Reporting workflows

Export a Traffic CSV Someone Else Can Interpret

· Colquhoun.shop editorial

A CSV is easy to open and easy to misunderstand. When you export a traffic view from Colquhoun.shop, the useful task is not simply downloading rows. It is giving the next person enough context to know what those rows represent.

Know what this export contains

The dashboard’s analytics CSV export contains the selected traffic series, with columns for domain, provenance, date, visits, granularity and source. It is not a complete backup of every imported field. Bounce rate, pages per visit, keyword details and country breakdowns are not included in that traffic-series file.

Keep the original import separately if you need the full dataset. A compact export is useful for a chart or a focused discussion, but it should not become the only surviving copy of your source measurements.

Set the view before downloading

Confirm the active domain, reporting period, time granularity and traffic-source filter. The export follows those selections. A file created with a source filter should not later be described as total website traffic.

For the clearest handoff of imported monthly measurements, choose the monthly view and all sources. The date column uses the first day of each month as its label. A row dated October 1 represents the monthly total in that view, not a measurement of visits on October 1 alone.

Here is a fictional example of the meaning of one row:

FieldExample
Domainexample.com
ProvenanceUSER IMPORTED
Date2026-10-01
Visits12,500 for the month
Granularitymonth
Sourceall

Keep derived views separate from measurements

The current dashboard derives daily and weekly displays from monthly totals. Exporting those displays does not turn them into actual daily or weekly analytics. They should not be used to identify the day a campaign succeeded or the week an outage reduced visits.

Similarly, a source-filtered series applies the imported source share to monthly visits. It is a calculation using that share, not an independently collected channel history for every month. Explain this if you send a filtered file.

If the recipient needs true daily events or monthly channel measurements, obtain those records from the original analytics system instead. Do not imply that changing a display setting creates a finer-grained measurement.

Read the provenance column

The file distinguishes user-imported analytics from fictional demo data. “USER IMPORTED” identifies how the data entered the dashboard; it does not mean the application independently verified the numbers. “FICTIONAL DEMO” should never be removed to make a sample look like competitor evidence.

Keep your original source, reporting method and collection dates with the file. Those details may not be carried in the normalized import or CSV. If a teammate is combining several exports, check that the definitions and periods match before summing anything.

Send a short note with the file

A useful handoff note might say: “This contains imported monthly visits for example.com, all sources, for the available quarter. Dates label months. It excludes other analytics fields. The original measurement report is retained separately.”

Open the CSV before sharing it. Verify the domain, row count, first and last month, totals and source label. Make sure your spreadsheet has not interpreted a monthly date as evidence for a single day. Share only information you are authorized to disclose.

Use the right output for the question

If no analytics dataset is selected but a public scan has completed, the dashboard’s export can instead produce a website-scan JSON file. That is a different kind of evidence, not a traffic CSV. Check the actual downloaded filename and contents.

For preparing measurements, read the import guide. For repeat navigation rather than a data handoff, use saved views.

Return to the Colquhoun.shop dashboard with the recipient’s question in mind. Export the smallest truthful dataset that answers it, and preserve the context that makes it useful.

This guide describes the built-in Web Reader and Keyword Density behavior verified for this publication. Available data depends on the page response; these tools do not measure visits or search rankings.