A launch is a block that goes live at a time you choose. Formspring takes care of the timing, the redirects before and after, and an optional email to the people who signed up for your updates.
Set the time zone first
Open the Styling tab and pick a time zone under Schedule and emails. Times you type for a block ("Visible from", "Hide after") are read in that zone, so 9:00 means 9:00 where you are, summer time included. A time that carries its own offset, such as 2026-11-01T09:00:00Z, keeps that exact moment. If you do not pick a zone, times are read in UTC.
Teaser before launch, fallback after
On a link block you can set:
- Before launch, send visitors to: a public address, for example a waitlist. Until the launch time the block stays on the page with the label you set for it, and a tap goes to the teaser.
- After it ends, send visitors to: a public address used once the block expires, so a finished campaign points somewhere useful instead of a dead link.
Without a teaser the block simply stays hidden until launch, and without a fallback it disappears when it expires. A block that is switched off, or a page that is a draft, never goes live on schedule. Addresses that point to private or internal networks are refused.
Email your subscribers when it launches
Turn on "Email confirmed subscribers when this launches" on a block. Within a minute of the launch time, people who confirmed your email signup get one email with a link to your page and an unsubscribe link.
- Only people with a current marketing consent receive it. Pending, unsubscribed and withdrawn people are left out, and so are addresses that bounced or reported spam.
- The unsubscribe is checked again at the moment each email is sent.
- Each block is announced once. If you move the launch time, it is announced again at the new time.
- If the page is still a draft or the block is switched off at launch time, nothing is sent until it is live. A launch more than two days old when it goes live is not announced as news.
- The email is in the language you chose for your page.
What each block produced
The page analytics list every block with its clicks, confirmed and pending email signups, text signups and purchases. Purchases are counted two ways and never mixed:
- Direct: the product, tip or shop block that took the payment.
- Assisted: another block the buyer opened earlier in the same visit, kept only in that browser tab for 30 minutes.
Refunds are subtracted. Launch blocks also show how many people were emailed, skipped and why.
Bookings are an outcome too. When a block sends visitors to one of your own booking pages, the booking page is told which block they came from. A booking made after that counts for the block, and a visitor who comes back later and books is still credited (the booking page remembers the visit for 30 days). This needs the visitor to have allowed analytics on the page that took the booking; otherwise the booking is not linked to the block. A cancelled booking no longer counts. Calendly and Cal.com embeds are not counted, because they cannot report a booking back.
Scans of your page's QR code
The QR code of a page now carries a small marker, so a scan is counted apart from a visit. The analytics show the number of scans (qr_scans) next to views, and the scans are part of the views. A code printed before this was added still opens the page; it is counted as a normal visit, and downloading the code again gives you one with the marker.
The same figures are available through the API (GET /api/v1/bio-pages/{id}/stats/counters, in block_outcomes) and the get_bio_analytics assistant tool.
