Help · Guides: step by step
Where do my sales come from?
Step by step: say that your site is for selling, let Bearing read your payments, make sure each sale finds its visit, then read which sources and campaigns bring money, and what stays out of sight.
Your payment tool tells you how much you sold. It does not tell you what brought the buyer: this post, this newsletter, this ad. Bearing joins each payment to the visit during which it began, and reads where that visit came from. Two things to set up: the purchase as your goal, which counts the visits that end in a sale, and your payments, which give the amounts. Twenty minutes when your payment tool is one Bearing reads without code.
Nobody is followed. A payment joins its visit through a code made in the page's memory when the visitor starts to pay. It is not a cookie, nothing is stored on the visitor's device, and it says nothing of who they are.
1. Say that your site is for selling
- Open your site's Statistics page and its invitation What is your site for? With a goal already there, click Add a goal under the table What leads there.
- Under What you expect from a visitor, choose That they buy.
- Under How do we know it happened?, choose A page shows afterwards and give the address of the page your buyers see once they have paid: a confirmation or a thank-you page. Nothing to install, and past visits are counted.
- Click Save this goal.
- The page's address changes with each order? End it with
*:/checkout/order-received/*counts every order confirmation of a WooCommerce shop (check the address of yours). - No page of your own after the payment? Count the click on the button that leads to the payment (A button or a link is clicked), knowing that a click is not yet a sale. The payments of step 2 say the rest.
- Why a goal when payments are read too: the goal gives the share of visits that buy, source by source, and it works from today, whether Bearing reads your payments or not.
- More purchases than payments? A buyer who reloads the thank-you page, or opens it again later, counts again. When Bearing reads your payments, a sentence under the goal says so; for your sales, the payments are the reliable count.
2. Let Bearing read your payments
According to what collects your sales:
- Stripe: paste a read-only key in your site's Settings, section Revenue (Stripe). Bearing reads your payments itself. The Stripe guide
- A WooCommerce shop, whatever the payment method: the WooCommerce guide.
- Paddle or Polar: they tell Bearing each payment themselves, once connected in the same Settings. Guides: Paddle, Polar.
- Anything else (PayPal, a booking tool that warns your site of each sale): your site's server tells Bearing each payment. For a developer, or for the AI that writes your site's code: Payments from your server.
- You sell on someone else's site (Amazon, a marketplace, your publisher): no payment can be read there. Count the click that leads to it and give it an estimated value: A sale that happens elsewhere.
One payment, one way in: a payment Bearing already reads in Stripe must not also be sent by your server, or it would count twice. And revenue starts where visits start: nothing dated before the first day Bearing measured your site, since it could be joined to no visit.
3. Make sure a sale finds its visit
A payment Bearing can join to no visit is counted all the same, as Source unknown. It is real revenue, and Bearing never spreads it over your sources. What decides whether a sale finds its visit is how the buyer reaches the payment:
- A Stripe payment link (an address that begins with
buy.stripe.com), or a Polar payment link placed on your site: nothing to do. When a visitor clicks it, Bearing adds the visit's code to the link. - A WooCommerce shop with Bearing's plugin for WordPress: nothing to do.
- A payment page made by a developer, or Paddle: one line to add where your site opens the payment. Send them the guide of your payment tool: it says which.
- A subscription: its first payment takes the source of the visit, and its renewals keep it.
- A sale made away from your site (an invoice paid by transfer, a sale in person): Source unknown, rightly.
4. Look at your first sale
There is nothing to try with false money: wait for a real sale, then look where it lands. With Stripe, payments are read once a day, and Read now, in your site's Settings, reads them at once. The Revenue card of your Statistics page then shows the sale with the source of its visit, or as Source unknown. If every sale says Source unknown while your buyers do come through your site, step 3 is not in place yet.
5. Read where your sales come from
- The Revenue card: what came in over the period, then by source and by campaign. It also says what comes from new customers and from customers who were already paying, from subscriptions and from one-off sales.
- By product: when the period sold two products or more, the Revenue card has a Products tab. A click on a product shows where its sales come from; a click on a source or a campaign, what it sold.
- What leads there: for each source and each campaign, the visits, the visits that bought, their rate and the Revenue they paid. Rows are ordered by visits, so a source that brings many visits and no sale shows as much as one that sells.
- On the chart: the money that came in, as bars under your visitors, on the same days.
- A campaign's page: what it brought and what it sold since its first visit and, once you type what it cost, its result. See a Facebook ad or an ad anywhere else.
- A publication's page: the sales of the visits that entered through it. See An article, a post, a video: what did it bring?
- Subscriptions: with Stripe, your recurring revenue (MRR), and which sources brought your subscribers.
Your AI reads the same numbers: “Where did my sales come from this month, and which campaign brought visits and no sale?”
6. Before you conclude
- Under 30 visits, a source has no rate: Bearing writes too few visits to conclude. Two sales from one newsletter are two sales, not a law.
- One large sale can make a source look like the best. Read the number of visits that bought next to the amount.
- Currencies are never added. A site that sells in two currencies shows two amounts.
- Compare like with like: a whole month with the month before, not today, which is not over, with yesterday.
7. What Bearing does not see
- A purchase made on a later visit. Someone reads your newsletter on Monday, comes back by themselves on Thursday and buys: the sale belongs to Thursday's visit, often Direct. Nobody is followed, so nothing links the two visits. What makes people think before buying looks weaker than it is; the days around its marker catch part of it.
- Who bought. Bearing keeps the amount, the currency, the date and what was refunded, never the buyer's name, email, address or card.
- A sale made elsewhere: in a shop, on a marketplace, by phone.
- Why. Bearing shows which visits ended in a sale, not what convinced the buyer.