Count what matters: events

Bearing already counts every page view. An event counts one precise thing: open your site's Events tab, click Count something new, and choose how. Each event then shows its status (never received, active, silent for some days) and how to install it again.

1. A page reached (nothing to install)

The simplest: when an action leads to its own page, count that page. A form that shows /thank-you after sending, a purchase that ends on /confirmation. Give the page's address, that's all: visits to it count as your event, past visits included.

2. A click on a button or a link (no JavaScript)

1. Create the event with the name you want, for example “Newsletter sign-up”. Bearing gives you a label such as bearing-event-newsletter-sign-up.
2. Add this label as a class on your button or link. In WordPress's block editor: select the button, then Advanced → Additional CSS class(es). In Webflow: the button's settings, Custom attributes, name data-bearing, value the event's name.
3. Click the button on your site: within seconds the event shows Active.

<a href="/brochure.pdf" class="bearing-event-download-brochure">Download</a>
<button data-bearing="newsletter-sign-up">Sign up</button>

Wix, Squarespace and some editors don't let you add a class to a button. Count the page shown after the click instead (way 1).

3. From your own code (for a developer)

Once Bearing is installed, call bearing with the name of what happened, optionally with properties:

bearing("signup");
bearing("download", { props: { file: "guide.pdf" } });

Because the script loads with defer, bearing may not exist yet when your own code runs. Add this line once, before your scripts: calls are kept and sent as soon as Bearing loads.

<script>window.bearing=window.bearing||function(){(window.bearing.q=window.bearing.q||[]).push(arguments)}</script>

Rules

• Names: up to 64 characters, letters, digits, spaces and _ . : - /. Bearing makes the name from what you call the event (Newsletter sign-up → newsletter-sign-up, landing_view stays landing_view). For an event your code already sends, give its exact name in Name your code already sends.
• Properties: up to 30 per event; text up to 256 characters, numbers or true/false. Their most frequent values show under the event in the Events tab, your AI can read them, and all of them are in your exports.
• Each click or code event counts toward your plan, like a pageview. A page reached is already a pageview: it costs nothing more.
• Never put personal data in an event (an email, a name, an order number tied to a person). Bearing is built to count, not to identify.
• Events your site sends without being created show as Detected: add them to your list to give them a readable name.
• An event that is what your site is for (a sale, a sign-up) can be marked as a goal: see Goals.