Skip to content
My Beast
Cart
Developer docsMenu

Sessions · Getting started

Sessions

Record visits to your web app with each person's yes, masked in the browser before anything leaves. Watch them back, follow a signed-in person's journey through your Laravel app, and see where people get stuck.

Sessions is for teams who run a web app and want to see what happened to a person when something went wrong, instead of guessing from a support message.

How it works

Three parts, each with its own job:

  • Your server signs a short-lived token for each page with mybeast/sessions-laravel. The token says who the person is, by your own ids, and the moment they said yes to being recorded. With no yes, it says not to record.
  • The browser records the page with @mybeast/sessions, masks it, and sends it in small compressed chunks every 5 seconds and on each page change.
  • Sessions checks each chunk again, encrypts it with your project's own key and keeps it for as long as your project says. You watch recordings back in Sessions at services.my-beast.com.

Your server can also send the journey: one step for each page shown or write taken by a signed-in person, recorded or not. A step holds the route's name, the status and the time it took, never a value. Sessions reads the journey every five minutes for stuck points, such as a form sent back three times or a slow page, and counts how many people finish your key flows.

What you need

  • A My Beast project with Sessions, bought at id.my-beast.com. Prices and packages are on Sessions' page.
  • A Laravel 12 or 13 app on PHP 8.2 or later: it signs each page's token and sends the journey.
  • Pages in an evergreen browser. Node 20 or later to build them with the SDK from npm.
  • A way to ask your visitors for their yes, and a place to keep when they gave it.

Asking your visitors is your part

Sessions records a person only after they've said yes, but it never asks them. Asking, as the law where they are requires, and telling them about it in your privacy policy, is up to you. That's in our terms for developer services. Record only with a yes shows how the yes travels from your app to each recording.

Explore the docs

QuickstartFrom a new project to your first recording, step by step.Record only with a yesHow the person's yes reaches each page, and what happens without it.Mask what a recording showsWhat is masked, your UI strings, and the check on arrival.Follow the journeySteps from your server, key flows and stuck points.Laravel SDKEvery config key, command and method.Browser SDKThe recorder, its options and what it sends.