Questions about Matomo versions (AI prompt)

General questions
1

Putting a pin in this AI prompt briefly in case someone wants to riff on it.

Prompt:
If I asked, could you ingest any linked pages from the changelog postings here: https://matomo.org/changelog. I only want you to ingest pages that are for “Matomo 5.X.Y”.

For example, ingest the information on this page: https://matomo.org/changelog/matomo-5-3-0/
But not this: https://matomo.org/changelog/matomo-4-16-0/ My goal is for you to learn them and then I will ask you questions going forward about them. there are about 50 individual pages you would need to ingest. Doable?

Response:

I can absolutely ingest and analyze all of the Matomo 5.x changelog pages in a single conversation session. Looking at the archive, there are roughly 20-25 public Matomo 5.x release pages today (5.0.0 through 5.11.x), not 50, unless you’re also including release candidates, betas, GitHub changelogs, or plugin release notes. (Analytics Platform - Matomo)

What I can do:

  • Crawl all Matomo 5.x changelog pages from the archive.

  • Build a structured knowledge base of:

    • New features

    • UI changes

    • Tracking changes

    • Tag Manager changes

    • API changes

    • Breaking changes

    • Security updates

    • Deprecations

    • Plugin-specific enhancements

  • Answer questions such as:

    • “When was AI referrer detection introduced?”

    • “Which releases changed Tag Manager?”

    • “What improvements were made to ecommerce tracking in Matomo 5?”

    • “What changed between 5.2 and 5.7?”

    • “Which releases would matter to a Product Analytics customer?”

    • “What features should I highlight to a customer upgrading from 4.16?”

What I cannot do:

  • Permanently “learn” those pages across future unrelated conversations.

  • Store 20+ release notes in my long-term memory automatically.

The practical workaround is, in a prompt, ask me to ingest all Matomo 5.x changelog pages.

CAVEAT:

If I try to ingest all releases and simultaneously hold every detail while generating the final document, I may hit context limits depending on how verbose the releases are.

A more reliable approach would be:

  1. Crawl all Matomo 5.x release pages.

  2. Generate the markdown incrementally.

  3. Save the completed .md file.

  4. Give you the file.

  5. You can upload that file later when asking me a question about the matomo changelog. The final reference document would likely be: 8,000-20,000 words, 12,000-30,000 tokens, fetching and reading all pages: ~2-5 minutes, condensing and assembling: ~1-3 minutes, generating the markdown file: <1 minute. So I would expect 3-8 minutes total.

That avoids trying to keep the entire changelog history in active context at once.

1 Like
2

And of course:
we will do this internally and share when done.
I just am sharing this hack openly in the meantime.

1 Like