dApp: PostHog integration

[kpyszkowski]

Closes: #747
Closes: AENG-30

Overview

This PR integrates dApp with PostHog service to track users activities and analyze it. The PostHog project was created. All dApp activity is now accessible through the dashboard.
The API key and endpoint are available in the project settings.

Features

• dApp integration using PostHog's official React SDK
• Autocapture: all user interactions are tracked, any button click, any form fill
• Manually triggered $pageview capture event: autocapture for page view event was disabled to prevent false positive captures. It is triggered manually as user visits the dApp.
• User identification via wallet address
• Added custom events with additional payload information:
  • deposit_success - payload: { transactionHash }
  • deposit_failure - payload: { cause }
  • withdrawal_success - wasn't able to easily get any reasonable payload here, can be done later
  • withdrawal_failure - payload: { cause }
  • points_claim_success - payload: { claimedAmount, totalAmount }
  • points_claim_failure - payload: { cause }
• Defined feature flag to toggle PostHog integration

Changes

• Added new env variables to define API key and endpoint and a feature flag
• Defined preconfigured PostHogProvider to inject the service into application
• Defined hooks: usePostHogCapture, usePostHogIdentity, usePostHogPageViewCapture
• Integrated key actions to capture PostHog custom events (see above)

Caveats

To ensure the $pageview event is captured properly it's needed to call it as a side effect as the location value changes. To access this value (via useLocation hook) the router's context needs to be in scope of PostHog's context.
The only way to achieve it was to do it in the Layout component where both contexts are available.

Note

It's impossible to exclude captures for development environment. To keep data logs clean and ensure it contains only user's data I suggest to keep the feature flag disabled while using development environment.

[netlify]

✅ Deploy Preview for acre-dapp ready!

Name	Link
🔨 Latest commit	943d5da
🔍 Latest deploy log	https://app.netlify.com/sites/acre-dapp/deploys/675188edf7ff4400080b1fdd
😎 Deploy Preview	https://deploy-preview-871--acre-dapp.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[netlify]

✅ Deploy Preview for acre-dapp-testnet ready!

Name	Link
🔨 Latest commit	943d5da
🔍 Latest deploy log	https://app.netlify.com/sites/acre-dapp-testnet/deploys/675188ed2103d7000885de35
😎 Deploy Preview	https://deploy-preview-871--acre-dapp-testnet.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[kpyszkowski]

@r-czajkowski

withdrawal_success - wasn't able to easily get any reasonable payload here, can be done later

Do you have any ideas about payload we could attach to the capture there? I mean something useful and available in the scope so can be used.

[linear]

AENG-30 Initial PostHog integration in the dApp

[r-czajkowski]

@kpyszkowski we should probably hash the Bitcoin address and then use it as ID, please see #904

[r-czajkowski]

@r-czajkowski

withdrawal_success - wasn't able to easily get any reasonable payload here, can be done later

Do you have any ideas about payload we could attach to the capture there? I mean something useful and available in the scope so can be used.

Maybe we can add transactionHash and redemptionKey see https://github.com/thesis/acre/blob/main/sdk/src/modules/account.ts#L200.

[kpyszkowski]

@r-czajkowski

Maybe we can add transactionHash and redemptionKey

It's not that straight forward. I need to play around with mutation function to pass these parameters to callbacks.
Such change might affect whole withdrawal flow. I don't want to risk it. It's doable but let's not block the PR.

I prepared POC which looks fine for further investigation:
withdrawal-success-payload-poc.patch

[r-czajkowski]

Let's remember to set up correct env variables on testnet and production. I belive we should disable the posthog support on testnet.

[kpyszkowski]

Updated environmental variables:

Mainnet (bitcoin.acre.fi)

Testnet (bitcoin.test.acre.fi)

[r-czajkowski]

Let's disable by default.

Suggested change

	VITE_FEATURE_POSTHOG_ENABLED="true"
	VITE_FEATURE_POSTHOG_ENABLED="false"