Taxonomy Standardizer

Last updated:

|Edit this page

This transformation standardizes all your event names into a single pattern, so that data becomes more consistent and marketing teams aren't driven wild.

Supported taxonomies

This transformation can convert from any of these taxonomies, to any other.

  • Camel Case: helloThereHedgehog
  • Pascal Case: HelloThereHedgehog
  • Snake Case: hello_there_hedgehog
  • Kebab Case: hello-there-hedgehog
  • Spaces: hello there hedgehog


Using this requires either PostHog Cloud with the data pipeline add-on, or a self-hosted PostHog instance running version 1.30.0 or later.

Self-hosting and not running 1.30.0? Find out how to update your self-hosted PostHog deployment.


  1. In PostHog, click the "Data pipeline" tab in the left sidebar.
  2. Search for 'Taxonomy Standardizer' and select the transformation, press Install.
  3. Follow the on-screen steps to configure the transformation.


Select your default naming pattern
Type: choice
Required: True


Is the source code for this transformation available?

PostHog is open-source and so are all transformations on the platform. The source code for the Taxonomy Standardizer is available on GitHub.

Who created this transformation?

We'd like to thank PostHog team member Yakko Majuri for creating the Taxonomy Standardizer. Thank you, Yakko!

Who maintains this?

This is maintained by PostHog. If you have issues with it not functioning as intended, please let us know!

What if I have feedback on this destination?

We love feature requests and feedback. Please tell us what you think..

What if my question isn't answered above?

We love answering questions. Ask us anything via our community forum.


Was this page useful?

Next article

GeoIP Enricher

This transformation enriches PostHog events and persons with IP location data. Simply enable this transformation and from that point on, your new events will have GeoIP data added, allowing you to locate users and run queries based on geographic data. How it works This transformation prefers to use event property $ip (which should be of type string ), but if that is not provided, it uses the IP address of the client that sent the event. This way the transformation can, in most cases, infer…

Read next article