From a4eebbf66f048d9f8d99c14994ff62dac9ac47b6 Mon Sep 17 00:00:00 2001 From: Conductor Adriaan Date: Sat, 7 Nov 2026 16:48:16 +0000 Subject: [PATCH 1/7] Give AI agents a guide to collect events The install guide for agents ends at pageviews. To add events, agents had to piece them together from the human pages, and often missed the placeholder function, a namespace or the robots in their own tests. events.md is short and links the event pages instead of repeating them: check the existing setup, pick automated, inline, sa_event or server-side events, name them, keep personal data out, and check them with the feedback header and the MCP tools. install.md links to it. Co-Authored-By: Claude Opus 5.5 --- events.txt | 60 +++++++++++++++++++++++++++++++++++++++++++++++++++++ install.txt | 1 + 2 files changed, 61 insertions(+) create mode 100644 events.txt diff --git a/events.txt b/events.txt new file mode 100644 index 0000000..977096e --- /dev/null +++ b/events.txt @@ -0,0 +1,60 @@ +--- +layout: null +permalink: /events.md +sitemap: false +--- +# Collect events with Simple Analytics + +How to collect events, like signups and button clicks, with Simple Analytics and check that they work. Written for AI agents, like Claude Code, Codex and Cursor, and for developers. + +Came here from the Simple Analytics dashboard or its MCP tools? They gave you the hostname and the script host of the website, use those. + +## 1. Before you start + +- Events need the Simple Analytics script on every page. Not there yet? Follow [the install guide]({{ site.url }}/install.md) first. +- Load event scripts the same way as the main script: from the same custom domain or proxy, and with the same [`data-namespace`]({{ site.url }}/events#the-variable-sa_event-is-already-used) (`ba_event` instead of `sa_event`). +- Look for events the website already sends, like `sa_event` calls and `data-simple-event` attributes, so you don't send them twice. + +## 2. Send events + +Use the first option that covers the event: + +1. **Outbound links, downloads, email and phone links:** add the [automated events script]({{ site.url }}/automated-events) next to the main script. No code needed: + + ```html + + ``` + + With a custom domain or the proxy, load it from that domain. With `data-namespace`, add `data-sa-global` to it. + +2. **Clicks and form submissions:** add `data-simple-event="signup_form"` to the element, from script version 12. See [inline events]({{ site.url }}/events/inline). +3. **Everything else,** like a signup that succeeded: call `sa_event` in JavaScript. + + ```js + sa_event("signup_completed", { plan: "starter" }); + ``` + + Events that can happen right after the page loads need the [placeholder function]({{ site.url }}/events#placeholder-event-function) in ``, before other scripts. + +4. **From a server or app:** send them to our endpoint, see [server-side events]({{ site.url }}/events/server-side). Use a user agent that isn't marked as a robot. + +## 3. Name events and add metadata + +- **Names:** letters, numbers and underscores, like `signup_completed`. Names are case-sensitive. The script replaces other characters with `_`, server-side names are stored as you send them. See [valid event names]({{ site.url }}/events#valid-event-names). +- **When:** send an event when something happened, like a signup that succeeded, not when someone clicks a button that might fail. +- **Metadata:** add details to an event as [metadata]({{ site.url }}/metadata), like `{ plan: "starter" }`. Values are text, numbers, booleans or dates. +- **No personal data:** never put email addresses, names, user IDs, what visitors type or other personal data in events or metadata. It's not allowed, and the account might be suspended. + +## 4. Check that it works + +1. Trigger the event in a browser and find its `simple.gif` request. Its `simple-analytics-feedback` response header says `Thanks for sending this event!` when it works. Never replay the request with curl or other tools, it adds fake events. +2. With access to Simple Analytics, through its MCP tools or a token the user approved, `get_recent_hits` with `type: "events"` shows the latest events, including robots. Headless browsers, like the ones AI agents use, count as robots, so a test event by an agent only shows up there. +3. `get_events` counts the events of real visitors per name, and `get_metadata` shows their metadata. New events can take a few minutes to show up. + +## 5. Use events + +- **[Goals]({{ site.url }}/goals)** count events or funnels of events and pages: `create_goal` with the MCP tools, then `get_goal_results`. +- **The [Events Explorer]({{ site.url }}/events-explorer)** shows events with their metadata, and the [export]({{ site.url }}/export-data) has the raw events: `export_data` with the MCP tools. +- **Event counts are how often an event happened,** not how many people did it. + +Need help? See [our support channels](https://simpleanalytics.com/contact). diff --git a/install.txt b/install.txt index 39312db..e756c4f 100644 --- a/install.txt +++ b/install.txt @@ -69,6 +69,7 @@ If the recent hits show nothing, that doesn't mean the installation failed. A pa ## 4. Collect the right data +- **Events,** like signups and button clicks: follow [the events guide]({{ site.url }}/events.md). - **URL parameters:** we only keep UTM codes and `ref`. To collect another parameter, like `product-id`, add it to [`data-allow-params`]({{ site.url }}/allow-params) first. It's only collected from then on. - **No personal data:** never put email addresses, names, user IDs or other personal data in paths, URL parameters, [events]({{ site.url }}/events) or [metadata]({{ site.url }}/metadata). It's not allowed, and the account might be suspended. - **Missing data,** for example because of ad blockers? Set up a [custom domain]({{ site.url }}/bypass-ad-blockers), or even better the [proxy]({{ site.url }}/proxy). From 6b154e2d67687c036ebce49fdc8f2c698f98910f Mon Sep 17 00:00:00 2001 From: Conductor Adriaan Date: Sat, 7 Nov 2026 17:33:43 +0000 Subject: [PATCH 2/7] Tell agents what differs for server events and namespaces Review found steps an agent could follow the wrong way: - Installing the script and the simple.gif header are for events in the browser. Server and app events don't need the script and are checked by the endpoint's answer. - data-namespace="ba" makes the function ba_event, and auto-events.js needs data-sa-global="ba_event". - Server user agents with bot, spider, crawl or agent are stored as robots, with the ServerSide/1.0 example of the server-side page. - New events of a new website can take over an hour, like page views. - Automated events store the address or number on the website's link, and a visitor's email, name or ID never goes in an event, metadata, button label or link title. Co-Authored-By: Claude Opus 5.5 --- events.txt | 19 ++++++++++--------- 1 file changed, 10 insertions(+), 9 deletions(-) diff --git a/events.txt b/events.txt index 977096e..0aeb78f 100644 --- a/events.txt +++ b/events.txt @@ -11,21 +11,21 @@ Came here from the Simple Analytics dashboard or its MCP tools? They gave you th ## 1. Before you start -- Events need the Simple Analytics script on every page. Not there yet? Follow [the install guide]({{ site.url }}/install.md) first. -- Load event scripts the same way as the main script: from the same custom domain or proxy, and with the same [`data-namespace`]({{ site.url }}/events#the-variable-sa_event-is-already-used) (`ba_event` instead of `sa_event`). +- Events in the browser need the Simple Analytics script on every page. Not there yet? Follow [the install guide]({{ site.url }}/install.md) first. Events from a server or app don't need the script, see option 4 below. +- Load event scripts the same way as the main script: from the same custom domain or proxy. Does the script have a [`data-namespace`]({{ site.url }}/events#the-variable-sa_event-is-already-used), like `data-namespace="ba"`? Then the function is `ba_event` instead of `sa_event`. - Look for events the website already sends, like `sa_event` calls and `data-simple-event` attributes, so you don't send them twice. ## 2. Send events Use the first option that covers the event: -1. **Outbound links, downloads, email and phone links:** add the [automated events script]({{ site.url }}/automated-events) next to the main script. No code needed: +1. **Outbound links, downloads, email and phone links:** add the [automated events script]({{ site.url }}/automated-events) next to the main script. No code needed. It stores the address or number that's already on the website's link, not what visitors type: ```html ``` - With a custom domain or the proxy, load it from that domain. With `data-namespace`, add `data-sa-global` to it. + With a custom domain or the proxy, load it from that domain. With `data-namespace="ba"`, add `data-sa-global="ba_event"` to it. 2. **Clicks and form submissions:** add `data-simple-event="signup_form"` to the element, from script version 12. See [inline events]({{ site.url }}/events/inline). 3. **Everything else,** like a signup that succeeded: call `sa_event` in JavaScript. @@ -36,20 +36,21 @@ Use the first option that covers the event: Events that can happen right after the page loads need the [placeholder function]({{ site.url }}/events#placeholder-event-function) in ``, before other scripts. -4. **From a server or app:** send them to our endpoint, see [server-side events]({{ site.url }}/events/server-side). Use a user agent that isn't marked as a robot. +4. **From a server or app:** send them to our endpoint, see [server-side events]({{ site.url }}/events/server-side). User agents with `bot`, `spider`, `crawl` or `agent` in them are stored as robots, so use one like `ServerSide/1.0 (+https://www.example.com/)`. ## 3. Name events and add metadata - **Names:** letters, numbers and underscores, like `signup_completed`. Names are case-sensitive. The script replaces other characters with `_`, server-side names are stored as you send them. See [valid event names]({{ site.url }}/events#valid-event-names). - **When:** send an event when something happened, like a signup that succeeded, not when someone clicks a button that might fail. - **Metadata:** add details to an event as [metadata]({{ site.url }}/metadata), like `{ plan: "starter" }`. Values are text, numbers, booleans or dates. -- **No personal data:** never put email addresses, names, user IDs, what visitors type or other personal data in events or metadata. It's not allowed, and the account might be suspended. +- **No personal data:** never put a visitor's email address, name, ID, what they type or other personal data in an event, metadata, button label or link title. It's not allowed, and the account might be suspended. ## 4. Check that it works -1. Trigger the event in a browser and find its `simple.gif` request. Its `simple-analytics-feedback` response header says `Thanks for sending this event!` when it works. Never replay the request with curl or other tools, it adds fake events. -2. With access to Simple Analytics, through its MCP tools or a token the user approved, `get_recent_hits` with `type: "events"` shows the latest events, including robots. Headless browsers, like the ones AI agents use, count as robots, so a test event by an agent only shows up there. -3. `get_events` counts the events of real visitors per name, and `get_metadata` shows their metadata. New events can take a few minutes to show up. +1. **In the browser:** trigger the event and find its `simple.gif` request. Its `simple-analytics-feedback` response header says `Thanks for sending this event!` when it works. Never replay the request with curl or other tools, it adds fake events. +2. **From a server or app:** our endpoint answers `201` with `"ok": true` when it stores the event. Otherwise `message` says what's wrong. +3. With access to Simple Analytics, through its MCP tools or a token the user approved, `get_recent_hits` with `type: "events"` shows the latest events, including robots. Headless browsers, like the ones AI agents use, count as robots, so a test event by an agent only shows up there. +4. `get_events` counts the events that aren't robots per name, and `get_metadata` shows their metadata. On an existing website, new events show up within minutes. On a new website, it can take over an hour. ## 5. Use events From 605fb7861f99b1399d56ecfcd9c799c4a912664e Mon Sep 17 00:00:00 2001 From: Conductor Adriaan Date: Sat, 7 Nov 2026 17:46:16 +0000 Subject: [PATCH 3/7] Cover links added later, link URLs, the placeholder and user agents From CodeRabbit, checked against auto-events.js: - The automated script only finds the links on the page when it loads, so links a single-page app adds later need inline or manual events. - Outbound and download links send their full URL as url metadata. Links with personal data or a token in the URL get a data-simple-event name, which the automated script skips. - The placeholder function also keeps sa_event defined when an ad blocker blocks the script, so recommend it for every manual event. - Server events from a visitor's request send the visitor's user agent, so robots stay robots. ServerSide/1.0 is for the rest. Co-Authored-By: Claude Opus 5.5 --- events.txt | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/events.txt b/events.txt index 0aeb78f..fb83973 100644 --- a/events.txt +++ b/events.txt @@ -27,6 +27,8 @@ Use the first option that covers the event: With a custom domain or the proxy, load it from that domain. With `data-namespace="ba"`, add `data-sa-global="ba_event"` to it. + It only sees the links that are on the page when it loads, so links a single-page app adds later need option 2 or 3. Outbound and download links send their full URL as `url` metadata. Does a URL have personal data or a token in it, like a download link per customer? Give that link a `data-simple-event` name instead, the automated script then skips it. + 2. **Clicks and form submissions:** add `data-simple-event="signup_form"` to the element, from script version 12. See [inline events]({{ site.url }}/events/inline). 3. **Everything else,** like a signup that succeeded: call `sa_event` in JavaScript. @@ -34,9 +36,9 @@ Use the first option that covers the event: sa_event("signup_completed", { plan: "starter" }); ``` - Events that can happen right after the page loads need the [placeholder function]({{ site.url }}/events#placeholder-event-function) in ``, before other scripts. + Add the [placeholder function]({{ site.url }}/events#placeholder-event-function) to ``, before other scripts. It queues events that happen before the script loads, and keeps `sa_event` defined when an ad blocker blocks the script, so the call doesn't throw. -4. **From a server or app:** send them to our endpoint, see [server-side events]({{ site.url }}/events/server-side). User agents with `bot`, `spider`, `crawl` or `agent` in them are stored as robots, so use one like `ServerSide/1.0 (+https://www.example.com/)`. +4. **From a server or app:** send them to our endpoint, see [server-side events]({{ site.url }}/events/server-side). Send the visitor's user agent when the event comes from their request, so robots stay robots. Otherwise use one like `ServerSide/1.0 (+https://www.example.com/)`: user agents with `bot`, `spider`, `crawl` or `agent` in them are stored as robots. ## 3. Name events and add metadata From c3e79354c47e2064691b2546b1c3502c38b1532d Mon Sep 17 00:00:00 2001 From: Conductor Adriaan Date: Sat, 7 Nov 2026 17:48:36 +0000 Subject: [PATCH 4/7] Use the namespaced function in the placeholder too With data-namespace="ba", the placeholder has to define ba_event, or a blocked script still leaves it undefined. Co-Authored-By: Claude Opus 5.5 --- events.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/events.txt b/events.txt index fb83973..438d6b9 100644 --- a/events.txt +++ b/events.txt @@ -36,7 +36,7 @@ Use the first option that covers the event: sa_event("signup_completed", { plan: "starter" }); ``` - Add the [placeholder function]({{ site.url }}/events#placeholder-event-function) to ``, before other scripts. It queues events that happen before the script loads, and keeps `sa_event` defined when an ad blocker blocks the script, so the call doesn't throw. + Add the [placeholder function]({{ site.url }}/events#placeholder-event-function) to ``, before other scripts. It queues events that happen before the script loads, and keeps `sa_event` defined when an ad blocker blocks the script, so the call doesn't throw. With `data-namespace="ba"`, replace every `sa_event` in it with `ba_event`, like [the namespace example]({{ site.url }}/events#the-variable-sa_event-is-already-used). 4. **From a server or app:** send them to our endpoint, see [server-side events]({{ site.url }}/events/server-side). Send the visitor's user agent when the event comes from their request, so robots stay robots. Otherwise use one like `ServerSide/1.0 (+https://www.example.com/)`: user agents with `bot`, `spider`, `crawl` or `agent` in them are stored as robots. From 0182181da646e6af13580d4f1436c3b95eb9c2b4 Mon Sep 17 00:00:00 2001 From: Conductor Adriaan Date: Sat, 7 Nov 2026 17:50:44 +0000 Subject: [PATCH 5/7] Say links with a title don't send their URL Co-Authored-By: Claude Opus 5.5 --- events.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/events.txt b/events.txt index 438d6b9..01f68c3 100644 --- a/events.txt +++ b/events.txt @@ -27,7 +27,7 @@ Use the first option that covers the event: With a custom domain or the proxy, load it from that domain. With `data-namespace="ba"`, add `data-sa-global="ba_event"` to it. - It only sees the links that are on the page when it loads, so links a single-page app adds later need option 2 or 3. Outbound and download links send their full URL as `url` metadata. Does a URL have personal data or a token in it, like a download link per customer? Give that link a `data-simple-event` name instead, the automated script then skips it. + It only sees the links that are on the page when it loads, so links a single-page app adds later need option 2 or 3. Outbound and download links can send their full URL as `url` metadata. Does a URL have personal data or a token in it, like a download link per customer? Give that link a `data-simple-event` name instead, the automated script then skips it. 2. **Clicks and form submissions:** add `data-simple-event="signup_form"` to the element, from script version 12. See [inline events]({{ site.url }}/events/inline). 3. **Everything else,** like a signup that succeeded: call `sa_event` in JavaScript. From 29d6ffdfcf9e26e7e88ad068b89e3b8b963e7a6c Mon Sep 17 00:00:00 2001 From: Conductor Adriaan Date: Sun, 8 Nov 2026 07:52:12 +0000 Subject: [PATCH 6/7] Apply review suggestions to the events and install guides Mention namespaces as the rare case they are, show metadata on inline events, allow replaying a request only when nothing else works, and say robots and new websites can show up later. Links added after the page loaded are collected once scripts#155 is released. Co-Authored-By: Claude Opus 5.5 --- events.txt | 14 +++++++------- install.txt | 6 +++--- 2 files changed, 10 insertions(+), 10 deletions(-) diff --git a/events.txt b/events.txt index 01f68c3..22d86c3 100644 --- a/events.txt +++ b/events.txt @@ -12,7 +12,7 @@ Came here from the Simple Analytics dashboard or its MCP tools? They gave you th ## 1. Before you start - Events in the browser need the Simple Analytics script on every page. Not there yet? Follow [the install guide]({{ site.url }}/install.md) first. Events from a server or app don't need the script, see option 4 below. -- Load event scripts the same way as the main script: from the same custom domain or proxy. Does the script have a [`data-namespace`]({{ site.url }}/events#the-variable-sa_event-is-already-used), like `data-namespace="ba"`? Then the function is `ba_event` instead of `sa_event`. +- Load event scripts the same way as the main script: from the same custom domain or proxy. Does the script have an uncommon [`data-namespace`]({{ site.url }}/events#the-variable-sa_event-is-already-used), like `data-namespace="ba"`? Then the function is `ba_event` instead of `sa_event`. - Look for events the website already sends, like `sa_event` calls and `data-simple-event` attributes, so you don't send them twice. ## 2. Send events @@ -25,11 +25,11 @@ Use the first option that covers the event: ``` - With a custom domain or the proxy, load it from that domain. With `data-namespace="ba"`, add `data-sa-global="ba_event"` to it. + With a custom domain or the proxy, load it from that domain. In the rare case that `data-namespace="ba"` is used, add `data-sa-global="ba_event"` to it. - It only sees the links that are on the page when it loads, so links a single-page app adds later need option 2 or 3. Outbound and download links can send their full URL as `url` metadata. Does a URL have personal data or a token in it, like a download link per customer? Give that link a `data-simple-event` name instead, the automated script then skips it. + Outbound and download links can send their full URL as `url` metadata. Does a URL have personal data or a token in it, like a download link per customer? Give that link a `data-simple-event` name instead, the automated script then skips it. -2. **Clicks and form submissions:** add `data-simple-event="signup_form"` to the element, from script version 12. See [inline events]({{ site.url }}/events/inline). +2. **Clicks and form submissions:** add `data-simple-event="signup_form"` to the element, from script version 12. Add metadata with `data-simple-event-` attributes, like `data-simple-event-logged-in="true"` for `logged_in` metadata. See [inline events]({{ site.url }}/events/inline). 3. **Everything else,** like a signup that succeeded: call `sa_event` in JavaScript. ```js @@ -49,10 +49,10 @@ Use the first option that covers the event: ## 4. Check that it works -1. **In the browser:** trigger the event and find its `simple.gif` request. Its `simple-analytics-feedback` response header says `Thanks for sending this event!` when it works. Never replay the request with curl or other tools, it adds fake events. +1. **In the browser:** trigger the event and find its `simple.gif` request. Its `simple-analytics-feedback` response header says `Thanks for sending this event!` when it works. Avoid replaying the request with curl or other tools, because it adds fake events. Only do that when nothing else works, and tell the user. 2. **From a server or app:** our endpoint answers `201` with `"ok": true` when it stores the event. Otherwise `message` says what's wrong. -3. With access to Simple Analytics, through its MCP tools or a token the user approved, `get_recent_hits` with `type: "events"` shows the latest events, including robots. Headless browsers, like the ones AI agents use, count as robots, so a test event by an agent only shows up there. -4. `get_events` counts the events that aren't robots per name, and `get_metadata` shows their metadata. On an existing website, new events show up within minutes. On a new website, it can take over an hour. +3. With access to Simple Analytics, through its MCP tools or a token the user approved, `get_recent_hits` with `type: "events"` shows the latest events, including robots. Headless browsers, like the ones AI agents use, can count as robots, so a test event by an agent might only show up there. +4. `get_events` counts the events that aren't robots per name, and `get_metadata` shows their metadata. On an existing website, new events show up within minutes. On a new website, it can take longer because of caching or DNS changes. ## 5. Use events diff --git a/install.txt b/install.txt index e756c4f..cc14a07 100644 --- a/install.txt +++ b/install.txt @@ -57,15 +57,15 @@ With a custom domain, allow that domain instead of both. The Free plan badge als - `IP in excluded IP list for website`: the website settings exclude this IP address. - Anything else explains what is wrong. 2. No `simple.gif` request? Check the console for `Simple Analytics:` warnings and Content Security Policy errors. -3. Never replay the `simple.gif` request with curl or other tools, it adds fake page views. +3. Avoid replaying the `simple.gif` request with curl or other tools, because it adds fake page views. Only do that when nothing else works, and tell the user. JavaScript on the page can't read this header. Server-side page views, like `trackPageview` in Next.js middleware, don't show up in the browser at all. With access to Simple Analytics, through its MCP tools or a token the user approved, `check_installation` checks the live website and `get_recent_hits` shows the latest page views and events. -Headless browsers, like the ones AI agents use, count as robots. Simple Analytics stores robots but doesn't show them in the dashboard, so a test visit by an agent only shows up in the recent hits, marked as a robot. +Headless browsers, like the ones AI agents use, can count as robots. Simple Analytics stores robots but doesn't show them in the dashboard, so a test visit by an agent might only show up in the recent hits, marked as a robot. -If the recent hits show nothing, that doesn't mean the installation failed. A page view that got `Thanks for sending this page view!` is almost always stored, also when the website isn't added yet. Hits of new websites can take over an hour to show up. +If the recent hits show nothing, that doesn't mean the installation failed. A page view that got `Thanks for sending this page view!` is almost always stored, also when the website isn't added yet. Hits of new websites can take longer to show up because of caching or DNS changes. ## 4. Collect the right data From 38559a09b288437760cba5c2a9a3385cdda85970 Mon Sep 17 00:00:00 2001 From: Conductor Adriaan Date: Sun, 8 Nov 2026 07:59:45 +0000 Subject: [PATCH 7/7] Say light.js sends no events, which downloads count and which links can hold personal data Co-Authored-By: Claude Opus 5.5 --- events.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/events.txt b/events.txt index 22d86c3..2c5d907 100644 --- a/events.txt +++ b/events.txt @@ -11,7 +11,7 @@ Came here from the Simple Analytics dashboard or its MCP tools? They gave you th ## 1. Before you start -- Events in the browser need the Simple Analytics script on every page. Not there yet? Follow [the install guide]({{ site.url }}/install.md) first. Events from a server or app don't need the script, see option 4 below. +- Events in the browser need the Simple Analytics script on every page, `latest.js` and not [`light.js`]({{ site.url }}/light), which doesn't send events. Not there yet? Follow [the install guide]({{ site.url }}/install.md) first. Events from a server or app don't need the script, see option 4 below. - Load event scripts the same way as the main script: from the same custom domain or proxy. Does the script have an uncommon [`data-namespace`]({{ site.url }}/events#the-variable-sa_event-is-already-used), like `data-namespace="ba"`? Then the function is `ba_event` instead of `sa_event`. - Look for events the website already sends, like `sa_event` calls and `data-simple-event` attributes, so you don't send them twice. @@ -27,7 +27,7 @@ Use the first option that covers the event: With a custom domain or the proxy, load it from that domain. In the rare case that `data-namespace="ba"` is used, add `data-sa-global="ba_event"` to it. - Outbound and download links can send their full URL as `url` metadata. Does a URL have personal data or a token in it, like a download link per customer? Give that link a `data-simple-event` name instead, the automated script then skips it. + Downloads are links to pdf, csv, docx, xlsx, zip, doc and xls files, set `data-extensions` for other files. Outbound and download links can send their full URL as `url` metadata, email and phone links their address or number. Does a link have personal data or a token in it, like a download link per customer or the visitor's own email address? Give that link a `data-simple-event` name instead, the automated script then skips it. 2. **Clicks and form submissions:** add `data-simple-event="signup_form"` to the element, from script version 12. Add metadata with `data-simple-event-` attributes, like `data-simple-event-logged-in="true"` for `logged_in` metadata. See [inline events]({{ site.url }}/events/inline). 3. **Everything else,** like a signup that succeeded: call `sa_event` in JavaScript.