Analytics interpretation
Read Traffic Changes in the Right Units
A dashboard can put a bounce-rate change beside a visits change, but the two numbers do not necessarily use the same unit. Colquhoun.shop’s imported-analytics overview displays bounce-rate changes in percentage points and visits and pages-per-visit changes as relative percentages. Reading those labels carefully prevents a small reporting mistake from becoming a misleading business claim.
This guide is about interpreting analytics you import. The public homepage scanner does not measure visits or bounce rate, and fictional demo data is not evidence about a real website.
Percentage points describe a difference between rates
Suppose the previous imported month has a bounce rate of 40%, and the latest has 35%. The difference is minus 5 percentage points. That is the unit shown as “pp” beside the bounce-rate change.
It is not the same as saying bounce rate fell by 5%. A relative calculation would be (35 / 40 − 1) × 100, which is a 12.5% decrease. Both calculations can be valid, but they answer different questions and must be labeled correctly.
For a concise report, write: “Bounce rate moved from 40% to 35%, down 5 percentage points.” Including the starting and ending values makes the result understandable without requiring the reader to reverse-engineer a percentage.
Relative percentages need a nonzero starting value
Visits and pages per visit use a relative-change calculation when the preceding imported value is nonzero. If visits move from 10,000 to 12,000, that is a 20% increase. If pages per visit move from 2.0 to 2.5, that is a 25% increase.
A zero starting value needs different treatment. You cannot divide by zero to calculate a meaningful relative percentage increase. The current display uses a zero fallback when the previous value is zero, so do not read that fallback as proof that nothing changed. State the actual values instead: “Visits rose from 0 to 500; a relative percentage comparison is not applicable.”
That caveat is especially important when a new analytics installation starts collecting data or when missing measurements have been incorrectly entered as zeros.
Check which records are being compared
The overview compares the latest imported monthly record with the previous available record. If there is no previous record, it displays “No prior month.”
Do not automatically call every comparison “month over month.” If your import contains September and November but no October, those are the two available records. Name the actual periods and investigate the missing month before presenting a continuous trend.
The overview cards are based on the latest imported records. A chart’s selected range is a separate display choice, so confirm the labels and source rather than assuming every number summarizes the whole selected range.
Direction is not the same as business value
The dashboard visually treats a higher bounce rate as negative and higher visits or pages per visit as positive. Those cues help you scan the display; they are not a diagnosis of business performance.
More visits can come from an audience that does not need your product. More pages per visit can reflect useful exploration or difficulty finding an answer. A rate can change because the measurement setup changed. Review the definition in your original analytics source and pair the numbers with the business outcome you actually care about.
Write a short, checkable conclusion
A useful summary names the source, periods, values and unit: “Our imported analytics show 12,000 visits in October versus 10,000 in September, a 20% increase. Bounce rate fell 5 percentage points. We have not attributed either change to a specific campaign.”
Use the Colquhoun.shop dashboard to organize those figures, then consult the analytics import guide before sharing them. Clear units and honest limits make the report more useful than an unexplained green arrow.