Connecting analytics services to PhariaAssistant

In PhariaAssistant, you often need to track user behaviour and interactions. This guide describes how to connect PostHog and Grafana Faro to gain insights into how users engage with your apps.


Supported analytics providers

Prerequisites

  • Access to your PhariaAssistant Helm deployment.

  • PostHog and/or Grafana Faro accounts.

Set up PostHog analytics

First, get credentials:

  • API key: Project settings → Project API keys

  • API host: Your PostHog instance URL (for example: https://app.posthog.com)

See the PostHog setup guide for detailed instructions.

Configure PostHog as follows:

pharia-assistant:
  posthogToken: "phc_xxxxxxxxxxxxxxxxx"
  posthogApiHost: "https://app.posthog.com"
  instrumentationAppIdentifier: "my-assistant" # Optional

Optionally, you can specify an app identifier for collected telemetry.

Set up Grafana Faro telemetry

First, get credentials. After setting up your Faro instance, you can get the telemetry URL and public API key from the Faro instance.

See the Faro setup guide for detailed instructions.

Configure Grafana Faro as follows:

pharia-assistant:
  faroTelemetryUrl: "https://your-faro-instance.com/collect"
  faroPublicApiKey: "your-public-api-key"  # Optional
  instrumentationAppIdentifier: "my-assistant" # Optional

Optionally, you can specify an app identifier for collected telemetry.

Tracked data: Privacy and compliance

We track user interactions including chat messages, feature usage, and page navigation to understand how users engage with PhariaAssistant.

Note the following:

  • PII: We do not track personally identifiable information (PII) in analytics data.

  • Identifiers: We generate anonymous identifiers using SHA-256 hashing with a salt. In this way, it is cryptographically impossible to reverse-engineer the original user ID while still allowing us to track consistent user behaviour patterns.

  • GDPR: We are actively improving our analytics setup to ensure GDPR compliance.