Doing step 2 and 3 sounds fairly easy and we could do that one for now and ignore step 1. For step 3 indeed the guide would need to be changed and it';s generally also a bit more work. We could get away though maybe by mentioning PWA and linking to the offline tracking guide.

@mattab did you maybe want to create a separate issue for these 3 different things or at least for step 1 as that's a bit more work and we won't be doing that one anytime soon likely vs step 2 and 3 is quite quick to do and we might work on it. Or we don't create a new issue and just ignore it for now.

Re step 2) be aware we're also sending instructions for these different tracking techniques by email in plugins/SitesManager/templates/_trackingCodeEmail.twig and on the tracking code page we could mention it as part of the introduction in the JavaScript tracking card.

Sounds good to keep this one issue and ignore step 1 👌

Goal:

Once completed this work should help prevent feedback like the one we just received today: utterly useless for the world of SPAs and PWAs 🙈

To be done in this step:

1. Improve this guide at https://developer.matomo.org/guides/spa-tracking to make it clear it also caters to PWA. If the guide cannot be reused, we need to create a new page. For example PWA seem to require service workers, and are interested in offline availability, so maybe we could cross link to https://matomo.org/faq/how-to/how-do-i-set-up-matomo-offline-tracking/ or cover this in a new page. To be looked also how else they differ.

2. Add a new section "Single Page App (SPA) and Progressive Web App (PWA) to the "Other ways" tab in the "No data screen".

The same content also needs to be added to: The email that we send for "tracking code".
The same content also needs to be shown on the "SitesManager -> Tracking code" page.
It may also be needed in the installation where we show tracking code?

Still need this docs to review matomo-org/developer-documentation#614