# 6am Analytics — monthly report sample

**Illustrative data. Not client results, a benchmark or a forecast.**
Example period: 30 days. Service business, one website.

## 1. Measurement context

This model distinguishes website sessions, form starts and a confirmed success event. Events must be configured and validated for the website. A button click does not confirm an inquiry or a sale. Counts below represent sessions reaching each step, not total repeated clicks.

| Metric                              |        Example |
| ----------------------------------- | -------------: |
| Website sessions                    |          1,200 |
| Sessions starting the form          |            120 |
| Sessions reaching confirmed success |             36 |
| Start-to-submit completion          | 30% (36 / 120) |

## 2. Device comparison

| Device  | Form starts | Confirmed submissions | Completion |
| ------- | ----------: | --------------------: | ---------: |
| Mobile  |          80 |                    16 |        20% |
| Desktop |          40 |                    20 |        50% |
| Total   |         120 |                    36 |        30% |

The difference is a signal to investigate. It does not prove that mobile design caused the drop-off. Compare traffic sources, user intent, time periods and browser behaviour.

## 3. Attention model — mobile service page

| Section          | Share reaching the section |
| ---------------- | -------------------------: |
| First screen     |                       100% |
| Service details  |                        64% |
| Customer stories |                        28% |
| Contact form     |                        18% |

These reach percentages describe the separate page-view sample used for the illustrative scroll map. They are not funnel conversions and must not be compared directly with all-site session counts.

## 4. Up to three priorities

### 01 — Investigate the mobile form

- Evidence: 80 form starts and 16 confirmed submissions; 20% completion.
- Working hypothesis: unclear fields or mobile validation could be interrupting progress.
- Next step: review matching sessions and reproduce any validation problem before proposing a change.
- Check: completion rate and confirmed submissions for comparable traffic after an approved change.

### 02 — Bring proof into view

- Evidence: 28% reach customer stories in the scroll-map example.
- Working hypothesis: relevant proof may be too far from the service explanation.
- Next step: propose a test moving a relevant story closer to that explanation.
- Check: section reach and contact events, segmented by device and source.

### 03 — Review the service page in search

- Example query: “boiler repair near me”. 4,800 impressions, 96 clicks, 2% CTR.
- Working hypothesis: the search result may not clearly explain the area served.
- Next step: inspect query intent, rankings, title, description and page content. Define a separate SEO scope if an opportunity is supported.
- Check: query-level clicks, impressions and CTR in comparable periods, with ranking and seasonality context. No ranking gain is guaranteed.

## 5. Limits and delivery

This is an example of the report structure, not a live analytics product or customer dashboard. The service includes setup or cleanup for one site, up to five agreed events and one advertising pixel; monthly tracking checks, reporting and up to three priorities. Available views depend on consent, traffic and the agreed measurement setup. Low traffic may require more observation time.

Website changes, experiments, SEO execution, CRM integrations and custom tracking are scoped separately. Accounts remain owned by the client. Access is requested through platform invitations, not shared passwords.

US$399 setup + US$149/month. Scope and billing timing are confirmed before payment. Submitting the brief does not charge the customer.