Colquhoun.AI
← All guides

Working with your analytics

Bring Your Own Analytics Without Losing Their Meaning

· Colquhoun.shop editorial

A dashboard becomes useful when you know where its numbers came from. Colquhoun.shop accepts a structured monthly analytics import so you can review your own measurements instead of confusing a demonstration or public website scan with real visitor data.

Start with a monthly question

Choose something the available data can answer: “Did monthly visits rise over the last quarter?” or “Which traffic sources account for the largest shares in this report?” Keep the same website, reporting method and time zone across the periods you compare.

The import is a normalized JSON file, not an automatic connection to every analytics platform. Export your measurements from a source you are authorized to use, then arrange them to match the sample schema in Colquhoun.shop’s Data setup area. Do not assume an arbitrary CSV or vendor export will work unchanged.

Prepare the required fields

The current importer expects schema version 1, a domain, and between one and 120 monthly records. Each month needs a unique YYYY-MM label, visits, bounce rate and pages per visit. Source and country breakdowns are also required, with each set of percentage shares adding to 100%.

Use numbers rather than formatted strings: write 12500, not “12,500 visits.” Bounce rate is a percentage from 0 to 100, not a decimal fraction unless you have converted it to that scale. Visits should represent the same metric in every month; do not silently mix users, sessions and pageviews.

Keyword, AI-provider and technology fields are additional inputs, not evidence the app independently discovered those facts. Only include values you can support. If your source does not provide a particular optional measure, do not invent it to make the dashboard look complete.

Validate before importing

Check for duplicate months, negative values, inconsistent domains and percentage totals. The app validates structure and numeric ranges, but a technically valid file can still contain incorrect measurements. A bounce rate of 25 is accepted as a number; only your source report can establish whether it is the right number.

Keep an untouched copy of the original export and a short note explaining any normalization. Record whether you combined small countries into an “Other” category or changed channel names. This makes a later comparison easier to reproduce.

The file must be smaller than 2 MB. Open Data setup, review the displayed sample and choose your JSON file. If validation fails, use the error message to correct the input rather than replacing unknown values with convenient guesses.

Keep the monthly view as your evidence

The monthly records are the measurements you supplied. The current dashboard also offers day and week views derived from those monthly totals. Those finer-grained displays do not reconstruct the actual dates on which visits occurred.

Do not use a derived daily spike to claim a campaign performed well on a particular Tuesday. To investigate that question, return to the source analytics system and its actual daily records. Likewise, applying an imported traffic-source share to a monthly total is a calculation, not new independently measured channel history.

This distinction matters when exporting charts or discussing results with a client. Keep “imported monthly measurements” separate from “derived presentation” in your explanation.

Know where the data lives

The dashboard’s import flow stores normalized analytics in the current browser. Do not assume signing in creates a synchronized cloud backup of those imports or makes them available on a second device. Clearing browser storage or using a different browser can remove access to that local workspace.

Keep your source files somewhere appropriate for your business. Avoid importing unnecessary personal information. The import flow also starts a separate public homepage check for the domain; that check is not a verification of your private traffic measurements.

Turn the review into one next action

Compare the available monthly periods, note missing months, and write one observation that the evidence supports. For example: “Imported visits increased from June to July; we need source-level reporting to understand why.” That is more useful than assigning a cause the file cannot establish.

If you want to explore potential advertising revenue, use the RPM scenario guide and keep its assumptions visible. For technical homepage signals, use the website-check workflow. These are complementary tools, not interchangeable sources of truth.

Open the Colquhoun.shop dashboard with a clean file, a clear question and the original report nearby. The goal is a better decision, not merely a fuller screen.

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.