What Bloopbot measures on its public pages

What is measured, and where

The person running this Bloopbot can turn on Google Analytics for the public pages only: the homepage, these guides and the “Account linked” pages you see after connecting Twitch. When it is on, Bloopbot counts:

Page views, including which guides are read and for how long.
Searches in the guides, so unanswered questions show up as guides worth writing.
Clicks on Sign in with Twitch, Open dashboard and the homepage flow demos.
Whether a channel finished linking, counted once per browser session without any channel or account identifier.
Your answer to Was this guide helpful? at the end of a guide.

What is never tracked

Nothing in the dashboard: flows, channels, settings, links and editors are private pages and load no analytics tag.
Nothing in widgets, alerts or OBS Browser Sources. Overlays are streaming surfaces and stay tag-free.
No chat messages, viewer names, Twitch data, tokens or keys.
No Twitch sign-in codes or channel IDs. Those are removed from the page address before it is reported, even though they can appear in your browser’s address bar.
No advertising storage or personalisation. The tag starts in a measurement-only consent state.

Opt out

Turn on Global Privacy Control or Do Not Track in your browser. When either signal is present, Bloopbot does not load the analytics script at all, and the feedback buttons do nothing. A content blocker that blocks Google Analytics has the same effect.

Not sure how to switch this on? Search your browser’s settings for “Global Privacy Control” or “Do Not Track”. Some browsers offer it under Privacy, others through an extension.

The “Was this guide helpful?” buttons

Each guide can end with a quick yes/no question. It appears only when analytics is on, because that is the only place the answer goes: one event with the guide’s name and your yes or no. There is no text box and nothing you type is sent. Use the troubleshooting guide to collect a proper problem report when something is wrong.

Turn analytics on for your own Bloopbot

Running Bloopbot yourself and want to see traffic to your homepage and guides? You need a Google Analytics 4 property and its Measurement ID.

In Google Analytics, create a property (or open an existing GA4 property) and add a Web data stream for your Bloopbot address, such as https://bot.example.com.
Copy the stream’s Measurement ID. It starts with G-.
Set GA_MEASUREMENT_ID to that value in your Bloopbot environment and restart the app. Leave it unset to keep analytics off.
Open your homepage in a browser without Do Not Track and check the Realtime report in Google Analytics. Your visit should appear within a minute.

An ID that does not look like a GA4 Measurement ID stops the app at startup with a clear message, so a typo never runs silently as “analytics on” with nothing recorded.

These events arrive alongside the standard page views, ready for reports or conversions:

Event	When it fires	Parameters
`sign_in_click`	A Sign in with Twitch button is pressed.	`placement`: nav, hero or closing
`open_dashboard_click`	A signed-in visitor opens the dashboard from the homepage.	`placement`
`channel_linked`	A channel finished linking. Once per browser session.	`source`: oauth_callback or homepage
`demo_select`, `demo_run`	Someone tries the homepage flow demos.	`example`, `placement`
`search`	A guide search is submitted.	`search_term`
`guide_feedback`	A reader answers the helpful question.	`guide`, `helpful`: yes or no

Was this guide helpful?