Wire up missing ol-data-track events

[mekarpeles]

Wire up missing ol-data-track events

• PatronImports Goodreads
• CTAClick YearlyReadingGoals
• CTAClick Read & CTAClick Borrow
• CTAClick ReadSearchInside
• search_inside
• list_create
• follow
  • https://github.com/internetarchive/openlibrary/tasks/b464b502-396e-48d2-8b5e-92a0a6bcf426
• CTAClick Edit or CTAClick StickyEdit
• readlog_completion
• CTAClick StarRating
• readlog_currently_reading
• readlog_want_to_read
• CheckInForm SubmitCheckIn
• MainNav Explore
• MainNav MyBooks
• search /search
• book_view /books/* + /works/*
• author_view /authors/*

PageViews come directly from matomo

[mekarpeles]

⚠️ Contributors, this issue will be ready to work on once:

• Triage — maintainers will add Priority: * and Lead: @* to replace Needs: Triage and Needs: Lead
• Needs: Detail — the issue body is empty; all context lives in a Google Spreadsheet that is not publicly accessible to community contributors
• Needs: Breakdown — no implementation steps, no list of templates or components that need ol-data-track attributes wired up

---

Context

• ol-data-track does not currently appear anywhere in the openlibrary codebase. It is distinct from the established data-ol-link-track click-event attribute handled by openlibrary/plugins/openlibrary/js/ol.analytics.js. The Retention Score epic (Retention Score #11956) references "set custom tag for ol-data-track" as a completed sub-item, implying a Matomo Tag Manager trigger for this attribute may already exist, but the corresponding HTML attributes have not been added to templates.

• Related analytics infrastructure: Migrate Plausible Event Types to Matomo Tags #12313 (Migrate Plausible Event Types to Matomo Tags, closed) documents how data-ol-link-track was wired to Matomo via a CSS selector trigger [data-ol-link-track]. An analogous trigger for [ol-data-track] (or [data-ol-track]) would follow the same pattern but requires confirming the exact attribute name and Matomo variable setup already in place.

---

Issue Assessment

Open questions

1. What is the exact attribute name and expected value format for ol-data-track? Is it data-ol-track, ol-data-track, or another variant? The Matomo trigger CSS selector must match.
2. Is the Matomo Tag Manager trigger for ol-data-track already deployed, or does it still need to be created alongside the template changes?
3. Which specific templates, macros, or components are listed in the spreadsheet as missing events? These need to be enumerated in the issue body for contributors to act on.

Action items

• Add issue body describing what ol-data-track is, how it differs from data-ol-link-track, and what value format it uses
• Enumerate the list of missing event locations from the spreadsheet directly in the issue (or as sub-tasks), so contributors do not require spreadsheet access
• Confirm whether the Matomo Tag Manager trigger is already live or needs to be created first

---

Full triage checklist (maintainers / Pam)

• Triage — correct labels applied or removed: Needs: Breakdown, Needs: Investigation, Needs: Design, Needs: Staff Decision, Needs: Staff / Admin, Good First Issue, Blocked, Blocker
• Problem / opportunity — problem is clear, audience identified, actionable
• Scope — issue is well-scoped; does not try to do too many things; split suggested if needed
• Justification — reasoning and impact stated; sufficient for leads to prioritize (note: does it include urgency / why now?)
• Success & testing criteria — defines what "done" looks like, verifiable by a contributor without asking; what must be tested
• Proposal & breakdown — concrete plan present; checklist or sub-issues actionable for a contributor
• If bug: environment & repro steps — N/A (feature / analytics instrumentation)
• Risks, concerns, open questions — identified and surfaced (note: any security or privacy implications? if so, apply Blocker)
• Pam context — ol.analytics.js reviewed; Retention Score #11956, Migrate Plausible Event Types to Matomo Tags #12313 checked; ol-data-track not found in codebase
• References — screenshots, designs, docs, and links present where needed; current spreadsheet link is not publicly accessible

Note

This comment was automatically generated by Pam, Open Library's Project AI Manager, on behalf of @mekarpeles. Pam is designed to provide status visibility, perform basic project management functions and relevant codebase research, and provide actionable feedback so contributors aren't left waiting.