Should you show recent signups on your landing page?

You publish a landing page on Webflow, Lovable, or a static host. The offer is clear. The form works. The page still feels empty.

A common fix is a corner popup: “Maya from Lisbon just joined.” Tools sell that as social proof. Open the live site and ask a simpler question. Do you have real recent activity to show?

Invented names are marketing copy

A toast with a first name and a city is easy to fake. Visitors notice when the same person appears on every refresh. After that, they treat the rest of the page as a pitch.

If nobody has signed up this week, leave the corner empty. You can add a toast when a waiting list, newsletter field, or download starts collecting real emails.

Quotes and live activity answer different questions

A useful testimonial explains what changed for one customer, published with their permission. That belongs near the offer. Follow the testimonials guide if you have quotes ready.

Live activity is a weaker signal. It only says that other people took the same step. “Someone from Berlin just joined the waiting list” is enough. It does not need a first name, an email, or the text they typed.

Keep private inquiries off that stream. A contact form is a conversation. Custom forms can collect sensitive answers. Those should stay off unless you choose to include them.

If you show toasts, they have to be real

Some widgets let you seed fake events so the corner never looks quiet. That is the same problem as the hardcoded name.

Sitebase’s social proof only shows recent activity from the same website. Waiting list signups, newsletter subscribers, lead magnet requests, and testimonials can appear. Contact forms and custom forms start off.

The toast stays generic. It can mention the event and a coarse place. It does not print names, emails, or submission text. Events older than 30 days are dropped. The default window is the last 7 days. If that window is empty, nothing is shown.

Sitebase is in private beta. Public signup isn’t open.

The notification has to run on your domain

An iframe cannot sit in the corner of the surrounding page. The toast needs a script on the host site.

That matters on Notion, Wix, or Squarespace, which strip or isolate scripts. On a regular HTML, Webflow, or Lovable page, the snippet lives in the shared layout.

You can build the same rule yourself. Read recent public events from your own backend. Never invent a row. Stop when the list is empty.

A static block like this is advertising unless Maya is a real signup you can point to:

<aside aria-live="polite">
  Maya from Lisbon just joined
</aside>

Check the empty state first

Open the published URL in a fresh window before you have traffic.

Confirm that no toast appears. Submit a signup you control, then reload. The notification should mention the event type, not your name.

On a phone-sized screen, check that the toast does not cover the submit button. The main action on the page still matters more than the popup. Use the launch checklist if you have not walked that path yet.