Why it is here

Benefit

You can see which pages consented visitors open, and which pages stay quiet.

A pattern that holds for two days can become a card. A person still approves every fix. The workflow does not change the site.

The path

How it works

Visits are recorded only after a person allows analytics. Text and form fields stay masked. Staff pages, token result pages, and voice audio are not recorded.

Each morning the PostHog workflow reads page counts for each connected project and stores them. The client’s PostHog tab reads those stored rows. It does not call PostHog on every page view.

A page that stays weak next to the rest of the site can become a finding. The same finding has to hold for two days before it becomes a card. At most three cards of one kind, and five cards for a client, go out in a day.

Cards are filed only when that client’s review is turned on. The workflow does not edit the site, open a pull request, or send mail.

What you get

Deliverables

When it starts

Workflows

  1. PostHogLoopWorkflow

    Starts Every day at 09:30 UTC

    Loads the page counts, then reviews them. Cards are filed only when that client’s review is turned on. It does not change the site.

On this site

Where this connects

Questions, answered

FAQ

What does the PostHog integration do?

It stores consented page counts once a day. A page that stays weak next to the rest of the site can become a finding, and that finding can become a card a person approves.

When does the PostHog workflow start?

PostHogLoopWorkflow starts every day at 09:30 UTC, one saved project at a time. The page counts are stored even when review is off. Cards are filed only when that client’s review is turned on, after the same finding has held for two days.

Does it change the site?

No. The workflow does not edit the site, open a pull request, send mail, post, or start an experiment. Visits are recorded only after a person allows analytics.