Bearing

Help · Guides: step by step

Sign-ups: know what brings you subscribers

Step by step: say that a sign-up is what your site is for, choose how Bearing knows one happened, check that it arrives, then read which sources and campaigns lead to it, and what one is worth to you.

A newsletter, an account, a seat at a workshop: when your site is there for people to sign up, the question is not how many visits you get, but which ones end in a sign-up. This guide sets that up: the goal, the way Bearing knows a sign-up happened, and where to read what leads there. About ten minutes, most often with nothing to install. If your site is there to sell, see the guide for sales; for contact requests and bookings, the one for contacts.

Nobody is followed: Bearing counts the visits during which someone signed up, never who signed up. What that leaves out of its sight is listed at the end.

1. Say that your site is for sign-ups

  1. Open your site's Statistics page. While the site has no goal, the first place invites you: What is your site for?, with the button Say what my site is for. With a goal already there, click Add a goal, under the table What leads there.
  2. Under What you expect from a visitor, choose That they sign up.
  3. The name of this goal, in your words: Bearing proposes Sign-up. Say which one if you have several: “Newsletter sign-up”, “Workshop registration”.
  4. Answer How do we know it happened? (the next section helps you choose), then click Save this goal.

A newsletter and a workshop are two different sign-ups: make two goals, one after the other. Each has its own numbers.

2. How Bearing knows someone signed up

Four ways, from the simplest to the surest. Take the first one that fits your site.

  • A page shows afterwards. If people land on a thank-you or confirmation page of your site once they have signed up, choose A page shows afterwards and give that page's address. Nothing to install, and past visits are counted: the numbers are there at once. The same page in several languages: one address per line. An address that ends with * counts every address that begins so (/thank-you/*).
  • A form counted by itself, on WordPress. With Bearing's plugin, the forms of Contact Form 7, WPForms, Gravity Forms, Elementor, Fluent Forms, SureForms and Kit are counted when they were sent successfully, never a refused one, and never what was typed in them. They show as Form sent in the Events tab, under Counted by themselves, from the first form sent. On the goal's screen, pick it under My site already sends it; or in the Events tab, open its Install and settings and click Make it a goal.
  • A button or a link is clicked. Choose A button or a link is clicked: after saving, the Events tab opens on the small label to add to your button, with the steps for the tool your site runs on. A click is not a sign-up completed: someone can click “Sign up” and leave the form empty. Use it when nothing else fits, and read its numbers as clicks.
  • Your site itself says so. For an app with accounts, whoever manages your site can have it send the event when the account is created (from its own code), or better, confirm it from its server: a sign-up is then counted even when the visitor's browser sent nothing. Once your site sends it, the event is listed under My site already sends it.

Form sent counts every form of your site together: with a contact form and a newsletter form, both are in it. The details under the event say which form each one was, but the goal does not separate them. To count sign-ups alone, use the page shown afterwards.

Your AI can do it for you: “Count the page /thank-you of my site as a goal named Newsletter sign-up.”

3. Newsletter forms: three cases to know

  • A Kit form on WordPress counts when Kit asks for the email address to be confirmed, so before it is. Compare Bearing's number with the sign-ups Kit receives, not with its confirmed subscribers. A Kit form set to send people to another page once they signed up is not seen by the plugin: count that page instead (a page shown afterwards).
  • A form on your newsletter tool's own page. Your site only has a link or a button that leads there: the sign-up happens on another site, where Bearing is not. What Bearing sees is the click that leaves your site, because links to other sites are counted by themselves. To make it your goal, open the Events tab, Count something new, choose A link to another site, give the address of your newsletter tool's page, tick This is a goal, then click Create. Past clicks are counted. Read it as the visits that left to sign up, not as sign-ups.
  • A form from your newsletter tool, placed in a page that is not on WordPress. Bearing does not count it by itself. If the tool can send people to a page of your site once they have signed up, count that page. Otherwise, a button clicked (the third way) works only if the tool lets you add the label to the form's button. If it does not, Bearing cannot count that form: your tool's own number of subscribers is the one to read.

4. Check that it arrives

  • A page shown afterwards needs no check: it is counted from the pages viewed. Only make sure the address is the right one: sign up once yourself and read the address of the page you land on.
  • A form, a button, an event your site sends: try it from a browser left out of the count. In the Installation tab, under “Your own visits”, click Stop counting this browser (see Exclude your own visits); on WordPress with Bearing's plugin, being signed in to WordPress is enough. Then do the sign-up in that browser: the event shows try received in the Events tab, and nothing is counted.
  • Never received is not zero. As long as the event of a button or of your site's code has never arrived, your site's page shows a dash and Never received yet for the goal, not 0. The goal also waits in your To handle list, with a button that opens its installation.
  • The last receptions. At the bottom of the Events tab, a list gives each event received with its time, its page and the source of its visit. Nothing in it says who.

5. Read what leads there

Your site's Statistics page now opens on the goal: the sign-ups of the period and their share of visits. Click that number to see them day by day in the chart. Under the chart, What leads there gives the same goal by Sources, then by Campaigns: for each one its visits, those that ended in a sign-up (the conversions) and the rate.

  • A conversion is a visit, not a person: a visit during which the sign-up happened.
  • Rows are ordered by visits: a source that brings many visits and no sign-up shows as clearly as one that brings sign-ups.
  • Campaigns only exist for links that carry tags. To tell one issue, one post or one ad from another, give each its own link: see Tag your links without mistakes.

Under 30 visits, a rate says little: Bearing writes “too few visits to conclude”, or shows the rate in grey. Wait for more visits before deciding anything.

Your AI reads the same numbers: “Which sources and campaigns led to my newsletter sign-ups this month, and is it too early to say?” Every Monday, the weekly report also tells you what led to your goal the week before.

6. What a sign-up is worth to you

A sign-up is not a payment, yet it is worth something: a subscriber may buy later, someone registered comes to the workshop. If you have an idea of that value, give it. For example, if 100 subscribers bring you €300 of sales in a year, one sign-up is worth about €3.

  1. Open the Events tab and, under your goal, Install and settings.
  2. Under What is one “Sign-up” worth to you?, type the Estimated value and choose the Currency.
  3. Click Save.

What leads there then shows an Estimated value for the period and for each source and campaign: the sign-ups times your value, always marked Estimated. A campaign's page shows an estimated revenue the same way. It is your estimate: Bearing does not check it, and never adds it to real revenue. Leave the field empty to remove it. See Goals and conversions.

7. What Bearing does not see

  • Who signed up. Bearing counts sign-ups; it has no list of them. Names and addresses are in your newsletter tool or in your own site, and Bearing never reads what is typed in a form.
  • A sign-up on a later visit. Someone reads your post on Monday and comes back on their own on Thursday to sign up: the sign-up counts for Thursday's visit, often Direct. Nothing links the two visits, so a source may have brought more sign-ups than its row says.
  • The confirmation by email. When your tool asks for the address to be confirmed, that happens in a mailbox, not on your site: Bearing counts the form sent, not the confirmation. If your tool sends people to a page of your site once they have confirmed, you can count that page as a second goal. It is opened from an email, often as a new visit: it tells how many confirmed, rarely where they first came from.
  • Unsubscribes, and sign-ups made elsewhere: on your newsletter tool's own page, in an app, added by hand. Your tool's number of subscribers will not equal Bearing's sign-ups: each counts its own thing.
  • What a browser does not send. A blocker sends nothing: that sign-up exists on your side and Bearing never hears of it, unless your server confirms it.