== Background
- Now that the A/B test bucketing is finished, we need to fire events based of the instrumentation spec T378103 and work investigating the session tick schema in T380926 https://docs.google.com/spreadsheets/d/1tYYRsxICotHT_uAt0gfZckHNZBmqZTKuykeUEwQSCvs/edit?gid=0#gid=0
Explanation of the session tick instrument: https://docs.google.com/document/d/1lNqNlQQqIM-ZNC5kJ_o1eSQ2IqecNWzBXJ7wkjc8aEc/edit?tab=t.0
TL;DR Tracks active browsing sessions by sending “tick” events every minute to measure engagement and session length.How it works:
• Self-contained: Each feature handles its own events (no messy cross-code dependencies).
• Ticks: Logs an event every minute during active sessions. Sends an instant tick to capture short sessions (e.g., mobile lookups).
Setup:
1. Define your instrument: Name it, connect to a schema in Wikimedia Events.
2. Attach listeners:
```
$('#search-overlay')
.on('open', () => sessionTick.recordEvent('search_open'))
.on('searchStart', () => sessionTick.recordEvent('search_start'));
```
3. Start ticking:
```
const sessionTick = new SessionTickMixIn(STREAM_NAME, SCHEMA_ID);
sessionTick.start();
```
== User story
- As the web team, we need data from our A/B test to make the most informed decision
== Requirements
- Events are fired for session length and click thru rate based off [the spec](https://docs.google.com/spreadsheets/d/1tYYRsxICotHT_uAt0gfZckHNZBmqZTKuykeUEwQSCvs/edit?gid=0#gid=0)
== Design
- none
== Acceptance criteria
- Instrumentation fires for each item in the spec and with the correct fields
== Communication criteria - does this need an announcement or discussion?
- no