See where people stop with Sessions

Sessions reads the sessions that PostHog records of your product. A teammate tells what each person did, where the person stopped, and why. It names the problems that block people, with links to the replays. This page tells how to turn Sessions on, read what it found, and make a bug ticket of a problem.

Before you begin

• Your product sends its events to PostHog, and PostHog records sessions. Troopy records no sessions itself.
• PostHog is connected in Settings > Apps. See Connect PostHog.
• Your troop has an AI plan that works. Each look is one run of the Product analyst, or else the lead, on that plan.
• Owners and admins turn Sessions on and change its settings. Everyone reads what it found.
• Sessions is a product. A person sees it only when it has the product.

Turn Sessions on

1. Open Sessions from Products.
2. If PostHog is not connected, connect it in the card on the page.
3. Select Turn on Session watch. Troopy hires a Product analyst when your troop has none.

The first look comes within a few minutes. You can also turn on Session watch on the Templates page of Routines.

Troopy reads the sessions with a query of PostHog. If PostHog refuses the key, the page says why. Then give the key Session recording read too, and connect it again.

What a look does

1. Every 3 hours, Troopy reads the sessions that PostHog recorded since the last look.
2. It keeps the sessions from your countries. It leaves out a session that only visits the paths that you leave out.
3. It takes the busiest sessions first: those with errors, then those with the most clicks and keys.
4. It reads the events of each one: the pages, the clicks, the words of each click, and the errors.
5. The teammate reads them, and writes what each person did and where the person stopped.
6. It names each problem that the events show, with the sessions that show it.

Troopy hides emails, long numbers and secrets before the teammate reads the events. The teammate never watches a replay. A person opens a replay in PostHog.

Read what Sessions found

The page shows what the latest look found, then the problems, the worst first.

Select a problem to open it. The list becomes a narrow column, and the problem takes the rest of the page. On a phone, the problem takes the whole page, and All problems goes back.

A problem that a later look sees again keeps its number. Troopy adds the new sessions to it.

Under the problems, Looks lists each look. Open a look to read each session that the teammate read.

Watch a session

A problem shows the sessions that show it, the newest first. Select a session to see it.

1. Select Play the session. Troopy loads the replay from PostHog, and it starts when its first part is there.
2. Use the bar under the replay: play and pause, the time, the speed, and Skip idle time.
3. Select a step in Steps to move the replay to it. A mark on the bar shows each step, and an error is red.

What the person did gives the words of the teammate: where the person stopped, and why.

The replay loads only when you select Play the session. A session of 30 minutes is about 15 MB.

Troopy reads the replay with the key of your PostHog, and keeps none of it. The replay shows the images and the fonts of your own pages. Your browser loads them from your sites, as PostHog's own player does.

Open in PostHog opens the session in PostHog.

Act on a problem

• Fix it makes a bug ticket for the Engineer. A problem has one open ticket.
• Ignore keeps the problem out of the open list, also when a later look sees it again.
• Open again puts an ignored problem back in the open list.

A person always approves the plan of such a ticket before the build starts, and Troopy never releases it by itself. The reason is that what visitors did steers the ticket.

When the ticket is done, the problem is fixed. If a later session shows it again, the problem comes back and needs a look again. A ticket that went into a branch such as staging fixes the problem only when its change reaches the default branch. Until then, the problem stays open with its done ticket, and Troopy makes no second ticket for it.

Who hears of a problem

A new problem of medium or higher, or a problem that came back, goes to:

• Needs you, until a person opens it
• the bell and email of the people who have Sessions. See Choose your notifications.
• the troop chat, for a high or critical problem. The analyst names it by its number.

Settings

Open Sessions > Settings.

Add the EU countries adds the 27 countries of the European Union to Countries.

Repository and Branch need GitHub. Until it is connected, the card of GitHub shows there: Connect GitHub brings you back to this page.

A ticket keeps the branch that was set when Troopy made it. A branch such as staging does not go to Production by itself. So Troopy checks Production after a release only when the ticket went into the default branch.

Look now starts a look at once. A workspace looks 12 times a day at most.

Related

• Connect PostHog
• Hire and manage teammates
• Catch the errors of your apps
• Ship code with engineering tickets