Build an owned-site performance report from analytics

Why use this

1. A website owner may notice a traffic change without knowing whether it came from one channel, a different reporting window or a measurement change. Rebuilding comparisons manually can also leave inconsistent figures across successive reports.

2. This job could prepare a repeatable performance view with the underlying definitions and caveats attached. The owner can separate noteworthy changes from reporting artifacts before deciding what deserves further investigation.

Why an agent / simpler alternative

Useful judgment

Compare aligned periods, reconcile traffic and engagement definitions and identify plausible questions without asserting causation.

Simpler alternative

Use built-in analytics reports when one stable metric and period answer the question.

Unsuitable when

The report is expected to prove marketing causality or authorize autonomous website changes.

Proposed inputs

1. Name

   Analytics export

   Owner

   Site owner

   Minimum scope

   Approved aggregate channel and engagement metrics

   Quality check

   Record property, timezone, date range and definitions

2. Name

   Comparison brief

   Owner

   Owner or marketer

   Minimum scope

   Business questions and relevant known site changes

   Quality check

   Separate observations from suspected explanations

Access and setup — proposed or unknown

Proposed minimum

1. Read a limited export and create a private report; no website administration or tracking changes.

Compatibility unknowns

1. Current analytics access, metric compatibility, reporting delay and runtime support are unknown.

External actions requiring approval

1. Connecting accounts, sharing private analytics, scheduling distribution or altering site/tracking settings requires approval.

Expected deliverable and review checks

Proposed artifact

Period-comparison report with channel changes, metric definitions, coverage notes and investigation questions.

Critical checks

1. Align period lengths and filters; reconcile totals; mark partial data and avoid attributing outcomes without evidence.

Missing output evidence

This overlay adds no new output inspection, execution or validation; consult the referenced canonical source outcome limits.

Failure signals and proposed responses

1. Signal

   A partial week is compared with a full week

   Why it matters

   The apparent decline is a timing artifact

   Proposed response

   Use aligned completed periods or label the limitation.

2. Signal

   Channel definitions changed between exports

   Why it matters

   Category movement can resemble growth

   Proposed response

   Document the definition change and avoid direct comparison.

Effort and cost — unknown

Setup work

1. Define comparison windows and authoritative metrics.

Ongoing review

1. Review anomalies and reporting-definition changes.

Unknowns

1. Data latency, aggregation differences, report maintenance and service costs are unknown.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

Invent two channel summaries with one incomplete period and a renamed category; draft the comparison commentary only.

Acceptance checks

1. Flag both comparability issues; show usable totals; separate observations from causal hypotheses.

Stop conditions

1. Stop if sensitive user-level data is requested or the next step would change the site.

Limits

1. A traffic report does not establish conversion quality, incremental impact or the reason visitors behaved differently.