763a6deb12
* First draft of the article! Still need to update author and header image * Apply suggestions from code review Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com> * Adding myself as the author * Table update * revert yarn.lock change * import less * Apply suggestions from code review Co-authored-by: Ian Vanagas <34755028+ivanagas@users.noreply.github.com> * unified feature comparisons: error tracking WIP * converted session replay, flags * moved over remaining competitors * clean up old comparison table spacing * smarter table cell widths * proof of concept: break table out of .prose width * more content width child sizing * make library comparison use OSTable * fit table width * center * table, video width "fixes" * simplified product comparison slides * fixed customers slide * renamed files * simplify calling of products/features * simplified usage * inline the rows * created feature definitions for remaining products * more features from core, add docs * nested labels, descriptions, and featuresets * product/feature links in comparison tables * Merge branch 'master' into best-error-tracking-tools-blog-post * leave cells blank if undefined, top-level product URLs * Clauded the rest of PH va Amp blog * vs mixpanel features * Clauded standardized features across competitors * make iframes (videos) full width * added statsig * feature "realignment" * component documentation * finished amplitude post * rows with arbitrary values * verified fathom, fullstory posts * updated GA4 * updated growthbook * heap comparison * hotjar done * fixed launchdarkly * updated logrocket * updated matomo * migrated mixpanel * Merge branch 'master' into best-error-tracking-tools-blog-post * cleaned up ArrayCTA signup component * custom label example * updated optimizely * changed style of linked tutorials in comparison article (pendo) * updated optimizely, pendo * plausible, + moved import/export to dw, cdp * verified sentry * fixed some sentry data * updated statsig * finally got best error tracking tools done! * removed unnecessary imports * makes the snippet available globally, uses it in a few places * converted best adobe analytics alts * fixed subscribe form responsiveness * converted amplitude article * fathom, amplitude, eppo articles * updated flagsmith alts * growthbook alts, launchdarkly alts * optimizely alts * converted statsig alts * split alts * fullstory alts * heap alts * hotjar alts * logrocket alts, matomo alts * mixpanel alts * Copy edits to the article * mouseflow, pendo, plausible alternatives * sentry alts * fixed best error tracking table * sprig alts * sprig alts * survicate, userpilot, uxcam, vwo alts * clarity alts * best mobile app replay tools * more * use feature arrays from new source, delete old shiz * show feature comparisons when there's data * don't render comparison links when on z page * amplitude don't got * fix build * order posthog first * include platform features in each product presentation * only show all groups/features on product pages * added LLM competitors * excluded sections * fixed rows with arbitrary inline data * sentence case * updated readme * remove hard coded data * Update contents/blog/posthog-vs-fullstory.mdx Co-authored-by: Vincent (Wen Yu) Ge <29069505+gewenyu99@users.noreply.github.com> * Update contents/blog/posthog-vs-fullstory.mdx Co-authored-by: Vincent (Wen Yu) Ge <29069505+gewenyu99@users.noreply.github.com> * fixes from PR feedback --------- Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com> Co-authored-by: Eli Kinsey <eli@ekinsey.dev> Co-authored-by: Ian Vanagas <34755028+ivanagas@users.noreply.github.com> Co-authored-by: Cory Watilo <corywatilo@gmail.com> Co-authored-by: Vincent (Wen Yu) Ge <29069505+gewenyu99@users.noreply.github.com>
3.1 KiB
title, sidebar, showTitle, author, date, featuredVideo, tags
| title | sidebar | showTitle | author | date | featuredVideo | tags | ||||
|---|---|---|---|---|---|---|---|---|---|---|
| How to set up Webflow analytics and session recordings | Docs | true |
|
2023-01-12 | https://www.youtube-nocookie.com/embed/2dNSr93N5Ns |
|
Webflow is one of the most popular no-code site builders. It makes building high-quality marketing sites, blogs, landing pages, and ecommerce stores a breeze.
To ensure your Webflow site is as good as possible, you need data about its usage. PostHog provides tools to capture and analyze this data. This tutorial goes over how to add PostHog to your Webflow site to capture pageviews, events like button clicks, session recordings, and more.
It requires both a PostHog and Webflow account, along with a Webflow paid site plan (PostHog is free up to 1M events and 5k session recordings per month).
Create a Webflow site
First, you need a Webflow site to add PostHog to. Sign up at webflow.com, go through the tutorial, and create a new site. There are pre-made templates available to make this process easy, such as the one we used for this tutorial. Once you're happy with the site you've made, publish it.
You should get a .webflow.io URL we can test with. Once you published your site, go to the top right menu and open the Project Settings page.
Adding PostHog to your Webflow site
In PostHog, get the JavaScript snippet from the Getting Started page or in your Project settings. It looks like this:
Copy the snippet and go back to Webflow. In the Webflow “Project Settings” page, go to the “Custom Code” tab. If you haven’t already, add a site plan to enable custom code. Once active, just paste the PostHog snippet in and save the changes.
Once you’ve done that, publish the site again, go to the published site, refresh, and click around (to capture some events). After a minute, events appear in PostHog.
From here, you can analyze data from your Webflow site with our suite of product analytics tools like trends, funnels, and recordings. It also enables you to combine your website data with your product data leading to better insights about the full journey.
Note: You must enable session recordings for to capture them on your Webflow site. To do this, go to Project settings in PostHog, scroll down to Recordings, and toggle on “Record user sessions.”