PostHog is an all-in-one platform for product analytics, session recording, and feature flagging. It’s a great tool for understanding user behavior.
Our new PostHog integration lets you add PostHog to your Glide apps and send custom events via Actions. Learn more about it in our Glide docs.
Have questions about the PostHog integration? Suggestions?
Drop your thoughts below.
Thanks you! 
Related links:
A MA ZING ! 
I implemented PostHog on my app this morning, and after just a few user session recordings, I was able to identify the issues my users were facing — all in less than half a day — and make some quick fixes.
Huge thanks for this implementation! It’s really going to help me make my app even more powerful by truly stepping into my users’ shoes.
Can you share more on what the issue was?
I’m interested, but not sure what issues can be identified by PostHog and not by other Glide functions, say a log of a workflow (since my issues usually tie to workflows only).
Hello, super cool announcement! I can’t see however, Glide listed in the integrations for session replays on PostHog. How do you install it?
And session replay is not listed in the features in the integrations screen on Glide. Is it doable? Thanks!
I would be interested in knowing how to clean up the URLs. It is a challenge working with these long URLs.
The first one after the dl is straightforward, it’s your tab’s slug.
Then /r/ implies opening a screen with the part right after that being its rowID.
Anything after /s/ likely is a component ID. I thought it would be included when you copy a component and try to read that through the clipboard, but it isn’t there.
What do you mean?
I don’t really understand this either. The path analysis in PostHog shows visitor paths I believe. I am assuming, perhaps wrongly, that each one of these URLs is that of a screen. In fact it’s very easy to check.
I believe we are seeing these unreadable URLs because slugs can only be defined at the tab level. It would be nice to be able to define slugs on all screens.
The screen recordings help understand the quality of the design, its inefficiencies, bugs etc. Very powerful.
The best Glide integration for me personally is Google Tag Manager, as it allows to handle many others (Facebook pixel, Google analytics, postHog and many others that don’t have integrations), but it requires some understanding of tag manager.
Absolutely amazing service!
I mean the part right after /r/ is the rowID of the row you’re interacting with.
That’s correct, and I’m just dissecting what it means.
It would be nice, but I think it would be costly to do something like that.
Let’s take this URL for example:
/dl/a-decouvrir/s/586405/r/tp7ScvwWReeDL52jJBg5vA/s/cOa8e8/r/10R6zyx2S2yek3ud6cm3kg
It means: