Lesson 8 of 87 min read

Measure what matters to a SaaS

Connect posts to site visits and trials with tagged links, read cadence and decay, and run a 15-minute weekly review on one page.

In this lesson you will

  • Tell vanity numbers from signals that matter to a SaaS
  • Tie posts to site visits and signups with tagged links
  • Read posting cadence and content decay to adjust your plan
  • Write a one-page weekly report you will actually read

Every social network will give you numbers. Impressions, reach, followers, likes, engagement rate. They are easy to collect and easy to put in a slide, and for a SaaS company most of them answer the wrong question. The question is not "how many people saw our posts?". It is "did our posts bring people to the product, and which ones?"

This lesson closes the loop on the course. You will separate vanity numbers from signals, connect posts to visits and signups with tagged links, read two patterns most teams never look at (cadence and decay), and run a 15-minute weekly review that ends in one decision. There are no benchmark numbers in this lesson on purpose: published averages come from accounts nothing like yours. The only useful baseline is your own, and you will start building it this week.

Vanity numbers and signals

Not every number is useless, but each one answers a different question. Sort them before you report them.

NumberWhat it tells youUse it for
Impressions, reachHow many times a post was shownSpotting posts the network pushed; not much else
FollowersHow many people opted inA slow trend, read monthly, not weekly
LikesLight approvalAlmost nothing on its own
Comments and repliesSomeone cared enough to writeTopics that start conversations
Saves and sharesSomeone found it worth keeping or passing onYour best how-to and customer-problem topics
Link clicksSomeone wanted moreWhich posts drive interest
Tagged site visitsVisits you can attribute to a network and campaignThe bridge between social and product
Signups or trials from tagged visitsVisitors who became usersThe number that matters most, and the slowest to move

The top rows are easy to move and loosely connected to revenue. The bottom rows are hard to move and closely connected. A good weekly report leans on the bottom half and treats the top half as context.

Tie posts to visits and signups

You started tagging links in lesson 5. Now make it a habit for every link to your own site, on every post.

Use the same naming every time.

utm_source   = the network, lowercase (linkedin, x, bluesky, discord, instagram)
utm_medium   = social
utm_campaign = the theme or launch (launch-week, how-to, changelog)
utm_content  = optional: which post (2026-11-18-utm-howto)

Read it in your web analytics. Every common web analytics tool can show visits grouped by source and campaign. Look at three views:

  • Visits by utm_source: which network sends people.
  • Visits by utm_campaign: which kind of post sends people.
  • Signups by utm_source and utm_campaign, if your analytics can see your signup event: which of those visits turned into users.

Know the gaps. Some visits will never carry tags: people who see a post, then search your name later, or type your domain. Treat tagged visits as a floor, not the whole picture. If tagged visits from LinkedIn grow and "direct" visits grow with them, social is probably doing more than the tags show.

Two patterns most teams ignore: cadence and decay

Cadence asks: when we posted more, did each post earn more or less? Compare weeks you posted three times with weeks you posted six. If engagement per post drops sharply when you post more, you are tiring your audience; slow down and spend the time on better posts. If it holds steady, you have room to post more.

Decay asks: how long does a post keep earning after it goes out? On some networks most of a post's engagement arrives in the first hour or two. On others, a good post keeps earning for days. Decay tells you two practical things:

  • When to be around for replies. If half of a post's engagement arrives early, the first hour after posting is when replies matter most.
  • Whether to repost. If your posts stop earning after a day on a network, reposting your best how-to a few weeks later reaches people who missed it. If they earn for a week, space reposts further apart.

You can work both out by hand from the native analytics on each network: record each post's engagement after one hour, one day and one week for a month. It is tedious, but a month of data is enough to see the shape.

Worked example: how we read our own week

We do not quote numbers from our own accounts in this course: they change every week, and a number without context teaches less than a method. What we can show is exactly where our weekly report gets its inputs, and what we expect it to decide.

Our inputs each week:

  • Native analytics on our X, LinkedIn and Bluesky accounts, plus activity in our Discord.
  • Tagged visits in our web analytics, grouped by source and campaign. Every link we post to our own site is built with our UTM generator, using the naming above.
  • Our listening log from lesson 6 and our repeated-questions list from lesson 7.

The decisions the report is built to drive are small and specific: which pillar to give an extra slot next week, which network to post to less, which how-to to repost, which repeated question to turn into a post. If a number does not change one of those decisions, it does not go on the page.

The one-page weekly report

Here is the template. Copy it into a doc or a spreadsheet tab and fill it every week, in the same order. It should fit on one page; if it does not, you are reporting too much.

WEEKLY SOCIAL REPORT, week of: ________   Prepared by: ________

1. WHAT WE SHIPPED
   Posts published per network:   LinkedIn __  X __  Bluesky __  Other __
   Posts planned but not sent: __  Why: ________

2. SIGNALS (from web analytics, tagged links only)
   Tagged visits by source:   linkedin __  x __  bluesky __  other __
   Signups from tagged visits:  __        Top campaign: ________
   Compared with last week:  up / flat / down

3. CONVERSATION
   Replies and comments that needed an answer: __   All answered? yes / no
   Leads from listening: __    Best one: ________
   Most repeated question: ________

4. WHAT WORKED, WHAT DIDN'T
   Best post (by clicks or replies, not likes): ________   Why we think so: ________
   Weakest post: ________   Why we think so: ________

5. CADENCE AND DECAY (monthly, or when something changes)
   Posting more or less than our plan?  ________
   Anything new about how long posts keep earning?  ________

6. ONE DECISION FOR NEXT WEEK
   We will: ________

Rules for filling it:

  • Fill it at the same time every week. Monday morning works for most teams.
  • Compare with last week, not with an industry average. Your own trend is the only baseline that means something.
  • "Why we think so" is a guess, and that's fine. Write it anyway. After a few weeks your guesses become patterns.
  • Section 6 is mandatory. A report that does not end in a decision is a status update nobody acts on.

The 15-minute weekly review

  • 5 minutes: pull the numbers for sections 1 and 2.
  • 5 minutes: fill sections 3 and 4 from your inbox, listening log and post list.
  • 5 minutes: read it once, top to bottom, and write the one decision.

Once a month, add section 5 and reread the last four reports together. That is when patterns show: a pillar that keeps winning, a network that never sends visits, a question that keeps coming back. Use them to adjust the plan from lesson 4 and, every quarter, to check whether your message bank from lesson 1 still holds.

Common measurement mistakes

Judging a network after two weeks. B2B buyers move slowly, and so do the numbers that matter. Give a network at least two months of steady posting before you decide it does not work.

Celebrating a spike. One post that the network pushed to many people is pleasant, but it rarely changes signups. Check whether tagged visits moved before you rebuild your plan around it.

Changing everything at once. If you change cadence, pillars and networks in the same week, you cannot tell which change mattered. Make one decision a week, which is exactly why the report ends with one.

Untagged links in the most important posts. Launch posts and founder posts are often written in a hurry and posted by hand, so they are the ones most likely to go out untagged. Build their links first.

Reporting to impress. A report that only shows the numbers that went up is a report nobody can learn from. Write down the weakest post every week, too.

Recap

  • Report the bottom of the funnel: clicks, tagged visits and signups. Treat impressions and likes as context.
  • Tag every link to your own site with consistent UTM values and read visits by source and campaign.
  • Read cadence (does posting more help or hurt per post?) and decay (how long do posts keep earning?).
  • Use the one-page report every week, compare only with your own past weeks, and end with one decision.
  • Once a month, reread four reports together and adjust your plan.

Exercise

Write your first weekly report

  1. Open any free spreadsheet or doc and paste in the one-page report template above.
  2. List every link to your own site you plan to post next week and rebuild each one with the UTM generator, using the naming rules from this lesson.
  3. Fill sections 1, 3 and 4 for last week from the native analytics on each network and your notifications.
  4. Fill section 2 from your web analytics. If last week's links were not tagged, write "no tagged data yet" and leave the numbers blank rather than guessing.
  5. Write one decision for next week in section 6.

Done looks like: a filled one-page report for last week (with blanks where you have no data yet), one decision written down, and a list of tagged links ready for next week's posts.

Go further

Analytics

In FoPost, analytics pulls the numbers from every account you connect into one screen, and two views answer this lesson's questions directly: posting frequency shows what each posting cadence earned per post, and content decay shows how long a post keeps earning after it goes out. Use them for section 5 of the report, and keep reading tagged visits in your web analytics for section 2. See analytics for what is included.

Check yourself

  1. 1Why should a SaaS weekly report lean on tagged visits and signups instead of impressions?

    Impressions are easy to move and only loosely connected to the product. Tagged visits and signups show whether posts actually brought people to it.

  2. 2What does content decay tell you that a single engagement number does not?

    How long a post keeps earning after it goes out, which tells you when to be around for replies and how far apart to space reposts.

  3. 3Why compare with your own past weeks instead of industry averages?

    Published averages come from accounts with different audiences and goals. Your own trend is the only baseline that reflects your situation.

Academy

Keep reading, free

Tell us a little about you and the rest of this lesson, and every lesson in every course, opens on this device. No account and no card.

What describes you best?
Where do you post today? Pick any that apply.
What do you want most right now?

We use your answers to suggest lessons and to improve the Academy. They are never shown publicly. Read our Privacy Policy.