Last updated:

Interested in what plugins we have available? Check out our Integrations.

Plugins are a way to extend PostHog's functionality by either pulling data into or sending data out of PostHog.

Our goal with plugins is to allow anyone to extend and customize PostHog in order to better fit their analytics and business needs.

They serve three key purposes:

  • Enriching: Getting data into PostHog
  • Exporting: Getting data out of PostHog
  • Cleaning: Data parsing and filtering at the ingestion step

Plugins Diagram

Example use-cases

Plugins can be used for a wide variety of use cases, such as:

Sending the event data to a data warehouse

If you have a data lake or data warehouse, you can use plugins to send PostHog event data there, while ensuring you still have that data in PostHog to perform your analytics processes.

Pulling data from a third-party API to enrich the event

Plugins can pull in information like exchange rates, GeoIP location data, online reviews, and anything else you can think of and add it to your PostHog events, enriching the data to improve your analytics processes.

Adding your own data from other sources to PostHog

In addition to pulling data from third-parties, you might also want to bring in data from your own sources, such as other tools and platforms you use.

Labeling events

In order to facilitate sorting through your events, plugins can be used to determine arbitrary logic that can label an event (e.g. by setting a label property). This can help you tailor your metrics in PostHog, as well as facilitate data ordering if you ever use PostHog data somewhere else.

Enforcing event schemas

By default, PostHog does not enforce schemas on events it receives. However, a plugin could do so, preventing ingestion of events that do not match the specified schema in order to keep your data clean and following specific guidelines you need it to follow.

Using plugins

To use plugins on your self-hosted instance, head over to 'Project' -> 'Plugins' on the left sidebar:

Plugins screenshot

Here you will be able to install our default plugins to test out the functionality or install a custom plugin by pasting a link to its public repository.

Given that plugins are still in Beta, our default library is currently limited to test plugins. We are working to expand the number of plugins available and will soon release tutorials on how to build your own plugin.

In the meanwhile, you can follow our progress on GitHub.

Installing plugins from private sources

To install plugins from private sources, like private npm packages or private repositories, you can either:

  1. Use the following environment variables:
VariableDescriptionDefault Value
NPM_TOKENAccess token for npm, used to allow installation of plugins released as a private npm packageNone
GITHUB_TOKENGitHub personal access token, used to prevent rate limiting when using plugins and to allow installation of plugins from private reposNone
GITLAB_TOKENGitLab personal access token, used to prevent rate limiting when using plugins and to allow installation of plugins from private reposNone
  1. Append ?private_token=<YOUR_TOKEN> to the plugin URL

Reordering plugins

PostHog will automatically create an order for your plugins based on the order of installation.

This order determines the sequence in which your plugins will run. For example, here's a model workflow:

  1. You send an event to PostHog
  2. Plugin 1 runs on the raw events
  3. Plugin 2 runs on the results of Plugin 1's processing
  4. Plugin 3 runs on the results of Plugin 2's processing
  5. Events returned from Plugin 3 are ingested (inserted into the database)

Plugin ordering is important if you have a plugin that depends on another. For example, Plugin A might add the company name based on the email of the user, while Plugin B adds company data to the event based on the company name.

Updating plugins

Plugins update screenshot

Plugins can be updated to the latest version directly on the PostHog UI.

By default, PostHog will check if there are any updates available and notify you of them, but you can also force PostHog to check again by clicking 'Check again'.

Before updating a plugin, if you want to check what has changed between versions, simply click on the button that says 'Update available'. This will open a new tab and show you the diff between your current version and the latest one.

Ask a question