[Alexander Dean (alexanderdean)]

What

Adds a row for the Snowplow Signals browser plugin (@snowplow/signals-browser-plugin) to the "All plugins" table on docs/sources/web-trackers/plugins/index.md, plus a short note explaining its independent release cadence.

The plugin is Snowplow-maintained and extends the browser tracker, but ships independently of the JavaScript tracker monorepo (like the Kantar Focal Meter row precedent). The new row sits alphabetically between "Screen views" and "Site search".

Cell rationale:

• Creates: Events and entities — tracks intervention_receive, intervention_handle, and intervention_handle_error events automatically, with the intervention payload attached as a custom entity.
• Tracked: Automatic
• sp.js / sp.lite.js: ❌ / ❌ — not bundled in either distribution.
• Full scoped package name used, since it's not in the monorepo and the browser-plugin-* shorthand would be misleading.

Minimum tracker version

3.x. Source: the package's peerDependencies on npm declare "@snowplow/browser-tracker": "3 - 4" (the published package is at v0.2.2, dependencies on @snowplow/browser-tracker-core and @snowplow/tracker-core are also "3 - 4"). This means it supports browser tracker v3 and v4, so the minimum is 3.x.

⚠️ Human confirmation suggested: the peer dependency gives a compatibility range (3–4) rather than a single "introduced in" version like the monorepo plugins have. "3.x" reflects the lowest supported tracker major, but a maintainer may prefer a more specific minor (e.g. the earliest version actually tested) if one exists.

Checks

• Ran prettier on the file — no formatting changes needed; the Markdown table columns line up (7 columns matching the header).

🤖 Generated with Claude Code

[claude]

Style review: I found nothing material to flag. The new row and note follow CLAUDE.md and the style guide. "Signals" is capitalized correctly, the internal links end in /index.md, and the #subscribe-with-the-browser-tracker-plugin anchor resolves to an existing H2. This PR doesn't add or change any external URLs.

One optional consistency point: every other row in the version column uses a full version number (for example, 3.0.0), and this row uses 3.x. If maintainers can confirm the minimum version, a specific number such as 3.0.0 would match the table's format.

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	documentation	8ed78fc	Commit Preview URL Branch Preview URL	Nov 01 2026, 06:05 PM

[Alexander Dean (alexanderdean)]

Peter Perlepes (@igneel64) - what is the compatibility version for the Signals browser plugin? That is being flagged in this PR as worth checking...

[Peter Perlepes (igneel64)]

Hey Alex, actually I am not sure this is a valid place for the change.
The mentioned component 'Signals interventions' is more of an SDK rather than a plugin. I am not sure that the expectation of the snowplow tracker being there technically makes it a plugin as a user would understand it. Also the name 'Signals interventions' probably should be avoided because even if it currently only includes interventions, I would consider it the "Signals browser" component.

Also the table itself is not a compatibility table but a table that shows what version the plugin is available from since plugins and the tracker are released together (plus a couple additional fields).

Certainly not have strong feelings if we want to merge this change but I would at least change it 'Signals browser' and keep it as a note at the end of the table. If we want to have it as a table row, a browser tracker after 3.0.0 can be used for the functionality.