G2

Documentation A.

CEO

Small-Business (50 or fewer emp.)

10/16/2026

"Instant Autocapture and Simple Event Tracking with PostHog"

4/5

What do you like best about PostHog?

We installed PostHog on documentation.ai through Google Tag Manager, and autocapture started recording clicks and pageviews straight away. We didn't have to tag anything first. What we use most is how it joins anonymous visits to the person who later signs in, so we can follow someone from a blog post through to the product. The capture() API is simple. We send all our custom events (CTA clicks, demo bookings, pricing toggles, video plays, chat opens) through one helper. Adding a data-attr attribute to an element gives its autocaptured clicks a readable name without writing any code. Review collected by and hosted on G2.com.

What do you dislike about PostHog?

Autocapture records clicks, but it can't tell identical buttons apart. Every signup button on our site says "Start for Free" and links to the same URL. To see which placement got the click (header, hero or a pricing tier), we had to write our own event with placement and plan properties. Loading PostHog through GTM also caught us out. Custom events pushed to the dataLayer don't reach PostHog unless you call it directly, and some events went missing before we noticed. Review collected by and hosted on G2.com.

What problems is PostHog solving and how is that benefiting you?

It shows us which pages and CTAs lead to signups and demo bookings, so we decide content and layout from data. We also used its pageview data to find every 404 the site had served over six months. We redirected the most common broken paths and added a "Did you mean" suggestion to the 404 page. Without PostHog's records we wouldn't have known those visitors were being lost. Review collected by and hosted on G2.com.