A useful resource receives interest, but the reporting sources describe different actions and units.
What happened?
What comes next?
Collect a few useful signals. Understand what they can tell you. Choose the next improvement with a clear reason.
THE CLEARWEFT CASE
How we label evidence The first review starts with a baseline.
No live Clearweft results have been published in this edition. The programme and practice examples below are ready to use while the operating case develops.
ILLUSTRATIVE PRACTICE / NOT CLEARWEFT RESULTS
Choose a journey and practise making a useful next decision.
People arrive. What helps them progress?
Website sessions120Sessions
Resource clicks18Click events
Confirmed subscriptions2Email-provider records
Paid referrals1Partner-reported outcome
Fictional practice counts for a seven-day window. Different units and sources are shown separately; these are not person-level conversion rates.
These totals do not identify one linked group of people. Referral reporting may also arrive later.
Test the resource journey with a reader, inspect signup delivery and check the referral reporting window.
Change one unclear instruction only after observing the problem. Review successful completion and specific reader feedback.
A calendar is open. Is the appointment useful?
Offer-page sessions80Sessions
Booking-page opens24Click events
Confirmed appointments6Booking-provider records
Recorded attendances4Attendance records
Fictional practice counts for a seven-day window. Different units and sources are shown separately; these are not person-level conversion rates.
Some appointments are recorded, and two booked sessions have not yet been recorded as attended.
They may be future appointments, cancellations or missing attendance records. A raw subtraction does not establish no-shows.
Match the relevant booking cohort and check appointment dates, availability, expectations and reminders.
Make one justified change, such as a clearer appointment description. Compare equivalent periods and record what else changed.
A sale happened. Did the result arrive?
Product-page sessions90Sessions
Checkout starts20Checkout-provider events
Completed purchases7Paid-order records
Confirmed deliveries6Delivery records
Fictional practice counts for a seven-day window. Different units and sources are shown separately; these are not person-level conversion rates.
The example contains a gap between completed purchases and recorded deliveries.
The missing delivery could be delayed, failed or unrecorded. Payment alone does not confirm usable access.
Reconcile the seven order IDs with delivery status. Resolve the specific exception before increasing promotion.
Verify recovery with the affected order and a fresh test purchase. Check that retries do not duplicate the delivery.
USE YOUR OWN AGGREGATE REPORTRead the evidence
Read the evidence
you already have.
Open a report produced by the Clearweft reporting script. This viewer reads the selected JSON file in this browser. It does not upload or publish its contents.
Use an aggregate report. Keep customer-level records in your own operating system.
KNOW WHAT THE NUMBER MEANSA few definitions
A few definitions
make a big difference.
A click is an action
A resource click does not prove that a reader used the resource. A booking-link click does not confirm an appointment. Name each event after what the source can verify.
Missing is different from zero
A disconnected source cannot report zero outcomes. Record its coverage and keep the value unknown until a complete, relevant report is available.
A period needs boundaries
State the reporting window and time zone. Separate future bookings, reporting delays and late reversals from the period you are trying to understand.
A decision needs a reason
Combine counts with reader questions, usability checks, costs and working time. State the next change and what evidence would support keeping it.