A traffic number becomes useful when it can be traced to a site, date range, goal, property, or dimension. Strawberry can query Plausible sites, aggregates, breakdowns, time series, realtime visitors, goals, custom properties, teams, and site configuration to explain what changed.
01
Start with the site and the question.
Analytics is less useful when the date range and target site are implicit.
Strawberry can retrieve site context first, then run the aggregate or query that actually answers the question.
02
Explain the movement beneath the total.
An aggregate may show that traffic moved; a breakdown and time series help reveal where it moved. Combine those views rather than turning one headline number into a story.
03
Keep goals and properties in the reporting loop.
A pageview is not always the metric the team cares about.
Plausible goals and custom properties can show whether the site is measuring the action behind a growth claim.
04
Keep the workflow ready for the next review.
Save the reporting definition as a Plausible skill, then use a routine to prepare a site-specific performance brief at the chosen cadence. It should retain the site and comparison range in every run.
Plausible Strawberry