Bearing

Help · Guides: step by step

What each issue of your newsletter brings

Step by step: why a click from an email arrives with no origin, how Bearing knows an issue (the tags your sending tool writes) and an article (your site's feed), the series to accept once, then each issue's own numbers and the slope of the whole.

Your sending tool tells you who opened an issue and who clicked. It does not tell you what those readers then did on your site: a sign-up, a purchase. Bearing counts that, issue by issue, once it can tell the visits of one issue from the rest. This guide sets it up: about ten minutes, once.

Nobody is followed: Bearing reads the links readers arrive through, not the readers. That is why some things stay out of its sight; they are listed at the end.

1. The trap: a click from an email has no origin

Without help, Bearing names a visit after the site it came from, when the browser says it. An email is not a site. A click from a mail app usually arrives with no origin at all, and counts as Direct, with everyone who typed your address. From a webmail open in a browser, it can show as Gmail or Outlook: that says where your reader reads their mail, not which issue they clicked.

Two things let Bearing tell what you send apart from everything else:

  • Tags in the issue's links. A tag is a few words at the end of an address (the part that begins with utm_, for example utm_medium=email). Bearing reads them before anything else: they say the visit comes from your newsletter, and from which issue. Each issue then has its own numbers: the visits that came through its links. Your sending tool can write them (step 3).
  • Your site's feed. When what you send is also published as articles on your site, its feed tells Bearing what you published, and where. Each article becomes a marker by itself, measured by the visits that entered your site through it, whatever their source, your emails included (step 2).

These are two readings, and Bearing keeps them apart: one says what each send brings, the other what each article brings, whatever the way in. Use one, or both.

2. What you send is also on your site: add your feed

  1. Open your site's Markers tab, section Markers from your feeds.
  2. Paste your feed's address under Address of the feed and click Add the feed. A feed is an address that lists what you publish; Markers says where to find yours.
  3. Each new article becomes a marker within the hour, on your curve and in Your markers. Those published since the day Bearing began measuring your site are added at once.

This measures an article that is on the site Bearing measures: the feed gives its address. A feed whose articles live elsewhere (on your sending tool's own pages) still gives one marker per article, but no numbers of its own: it is listed as “Not measured”. For those, the tags are what counts (step 3).

3. Tags in the links: by your sending tool, or made in Bearing

Most sending tools can add tags to every link of an email by themselves. Their screens change, and this guide does not describe them. What matters for Bearing: is the setting turned on once or at each send, and does each issue get a campaign name of its own?

  • Kit: one setting for the whole account, “Automatically append UTM parameters to email links”. Each email gets its own campaign name, made from its subject.
  • Beehiiv: on by default, under “UTM Analytics”. The campaign name is the post's title.
  • Buttondown: one setting for all your emails. The campaign name is each email's short name.
  • Klaviyo: one account setting, “Automatically add UTM parameters to links”.
  • Mailchimp: a box to tick on each email, “Google Analytics link tracking”. The campaign name is the email's title with its date.
  • MailerLite: an option to turn on for each campaign, “UTM tags”.
  • Ghost: its link tagging writes one mark, ref, the same on every issue. Bearing reads it as the source, and cannot tell one issue from another: rely on your feed (step 2).
  • Substack: tags every link to another site by itself, with utm_source=substack and utm_medium=email, but never with a campaign name. Bearing counts these visits under the source Substack, all issues together, and cannot tell one issue from another. Substack's help does not say whether it keeps a campaign name you add to a link yourself: if you try it, the check below tells you.

After your next send, look at the Campaigns list on your Statistics page: the issue should be there under a name of its own. If your tool writes the same campaign name on every issue, they are one campaign for Bearing, which cannot tell them apart.

Your tool does not tag, or you write from your own mailbox: make the links in Bearing, for each issue.

  1. In the Markers tab, section Make a campaign link, give the issue's name in The campaign's name, in your words: “March newsletter”.
  2. Where the link will be placed: Newsletter or email.
  3. The page the link leads to: the page the issue sends your readers to. It must be a page of your site: Bearing would not see the visits of a link that leads elsewhere.
  4. Click Make the link, then Copy, and use it in the issue in place of the plain address. For another link in the same issue, make it with the same name, and tell the links apart in The ad's name: the issue's page then compares them link by link.

An issue made this way is announced: it becomes a marker at its first visit, with nothing to sort, and its page says what it brought. Once two issues made this way have had their first visit, they form your newsletter's series by themselves, with nothing to accept (step 6); Bearing looks once a day. Your AI can make the link: “Make me a link for Thursday's newsletter, to my workshop page.”

4. Accept the series, once

With tags written by a sending tool, every issue arrives under a new campaign name. Rather than ask you to sort one a week, Bearing asks once. When your tagged issues have brought 5 visits between them, a line waits under Campaigns to sort in the Markers tab, and in your To handle list: Series “Newsletter”. Bearing looks once a day, so it can appear the morning after.

  • Accept the series: every issue then files itself, from its first visit, even an issue of two clicks. Each becomes a marker on the day of its first visit, under the name your tool gave it; Change the title on its page gives it yours.
  • Ignore: these campaigns never show on your curve. The series stays listed with the ignored campaigns, where Sort again brings it back.

Bearing knows a campaign arrives by email when its links say so (utm_medium=email) or name a sending tool it knows. A tagged issue it does not recognise as a newsletter waits like any other campaign, with the question One day, or something that lasts?: answer One day: a marker. Either way, nothing shows on your curve without your say: a campaign's name is written in a link, and anyone can write a link. And an issue is never attached to an article's marker: your newsletter and your feed stay two series.

5. Read one issue

In Your markers, click a title to open its page. An issue and an article are two markers, and each page says its own thing:

  • An issue of your newsletter: What the campaign brought gives the visits that came through the issue's links since its first visit, how many reached each of your goals, the revenue tied to them and, when Bearing knows what those payments sold, What it sold. When the issue's links each say what they open, the page also compares them “link by link”: which article of the issue was clicked.
  • An article from your feed: the page opens on What this page brought: the visits that entered your site through the article during its first 14 days, the goal they reached and the sales they paid, day by day and by source. The visits your email sent are among them, under its source.
  • Around this day, on both, compares your whole site on the days before and after. An article, a post, a video says how to read it.

Without a goal, an issue only has visits: say first what your site is for (see the guides for sign-ups and for sales). And under 30 visits, Bearing says the numbers do not allow a conclusion yet.

6. Read the slope

One issue alone says little. Under Series in the Markers tab, your newsletter has its own page and each feed has its own: two series, even when they carry the same articles. Each reads its issues together:

  • The slope: your last complete issues against the ones before. The series progresses, is stable, or declines. An issue is complete once its 14 days are over, and each group needs 30 visits in all. Before that, the page says so: “Not enough complete issues yet to read a slope”.
  • Issue by issue: each issue's visits over its first 14 days. The same duration for each, so they can be compared.
  • The issues, from the most to the least effective: ranked by your goal, then by visits, with where the visits came from and whether the issue still brought visits after its first week. Look at the two ends of the list: with a few conversions per issue, the gap between two neighbours says nothing.

Bearing shows what happened, never why. Why an issue did better (its subject, its title, its day) is yours to judge, or a question for your AI, which reads the series with its titles and your notes. The series' page has the message ready, under Copy the message: “Look at my series Newsletter in Bearing. What do the issues that worked best have in common, and what do you suggest I try in the next one? Present it as a hypothesis.”

7. What Bearing does not see

  • Opens, and who clicked. Bearing counts visits to your site, not readers: who opened and who clicked is what your sending tool knows. Nobody is followed.
  • A reader who comes back later. Someone reads the issue on Tuesday, comes back on their own on Saturday and buys: Saturday's visit counts as Direct, and nothing links the two. An issue may have brought more than its numbers say; Around this day catches part of it.
  • A forward. A tagged link keeps its tags when the email is forwarded: the visit counts for the issue, and nothing says it was forwarded. A reader who types your address instead of clicking counts as Direct.
  • Your sending tool's clicks will not equal Bearing's visits. A click is not always a visit: someone clicks and leaves before your page has loaded, or their browser blocks measuring tools. And each tool counts by its own rules. Compare your issues with each other in Bearing, rather than the tool's numbers with Bearing's.