Site Analytics (Microsoft Clarity)
What the district websites record about visits, what they never record, and how to read form activity.
What it is
The district websites use Microsoft Clarity alongside Google Analytics. Google Analytics counts visits. Clarity shows how a page is used: where people click, how far they scroll, and where they get stuck. It does this with heatmaps and short screen recordings of a visit.
Clarity runs on:
- rotary9660.org.au, including the RYPEN pages
- help.rotary9660.org.au (this site)
- support.rotary9660.org.au, the district's online forms and tools
All three report into one Clarity project, so recordings and heatmaps are filtered by page address.
What is never recorded
Clarity hides what you type into form fields everywhere. On the support portal it goes further and hides every word on the page, including anything the page shows about you, such as your name on a consent or signing form.
On support.rotary9660.org.au a recording shows only the shape of the page, plus where the mouse moved, what was clicked and how far the page was scrolled. The text appears as blank blocks.
Some links are personal to one person, such as a signing link, a referee or witness link, a consent form link or a newsletter unsubscribe link. Those links carry a private code in the web address, so pages opened from them do not load Clarity at all.
Staff screens are not recorded at all either: the Compliance Register, the YEP portal and roster, and every admin page. They list people's records and documents, and some of them change their own web address as you use them.
How a page decides
flowchart TD
A["A district page loads"] --> B{"Personal link?
(a private code in the address)"}
B -- "Yes" --> C["Clarity is not loaded"]
B -- "No" --> S{"Staff screen?
(admin, register, roster)"}
S -- "Yes" --> C
S -- "No" --> D{"Which site?"}
D -- "support portal" --> E["Recorded with ALL text hidden,
plus form activity events"]
D -- "district site or help site" --> F["Recorded with typed input hidden"]
Reading form activity (support portal)
Each support portal form reports a handful of named events, so you can see when people use a form and where they drop off without seeing anything they entered.
| Event or tag | What it tells you |
|---|---|
| form_start | Someone clicked into the first field of a form. |
| form_invalid | The form refused a field (left empty, or in the wrong format). The form_invalid_fields tag names which fields. |
| form_submit_ok | The form was sent successfully. |
| form_submit_fail | The person pressed submit but the form could not be sent. Worth checking: this is usually a fault on our side. |
| form_abandon | The person started the form and left without sending it. |
| form_name tag | Which form it was, for example wwcc-submit or ryvid-form. |
| form_fields tag | The names of the fields the person used, in order. Names only, never what was typed. |
| form_last_field tag | The last field used before sending or leaving. On abandoned forms, this is usually where people give up. |
| form_time tag | How long the form took, in bands from 0-30s up to 10m+. |
To find drop-off on a form
- Open the district project at clarity.microsoft.com.
- Go to Recordings, then Filters.
- Under Custom tags, choose form_name and pick the form.
- Under Smart events, choose form_abandon.
- Look at form_last_field across those sessions. If one field keeps coming up, that field is the problem.
That event means a page put a private code into its own web address after it loaded. Tell support@rotary9660.org.au which page it was, so it can be excluded.
Email support@rotary9660.org.au.