Product update: Liquibase now collects anonymous usage analytics

With over 100 million downloads, Liquibase serves a wide, diverse set of users. In order to build the best tool we can, we’re always looking for ways to continuously improve our product and get feedback from our users. The latest release of Liquibase 4.30.0 now comes with the ability to automatically send anonymous usage analytics when you run commands. You can opt in or out of this functionality at any time — it is ON by default for Liquibase OSS users and OFF by default for Liquibase Pro customers. No personally identifiable information or user-specific data will be collected or sent.

With this anonymized and aggregated data, we can get a better understanding of how Liquibase is being used. These insights will help inform the product roadmap, so we can invest in the right features and fix any gaps in our product or documentation.

Anonymous usage analytics

When enabled, Liquibase will record the following information when a command is run:

• Command-specific data: This includes the command name, whether it succeeds or fails, and, if there is a failure, exception data.
• Liquibase data: This tells us the version of Liquibase that’s being run and the interface it’s being run in.
• Database platform details: This helps us understand what databases are used with Liquibase and what version they are.
• Changelog information: This includes the format and number of changelogs run.
• Extension information: This data includes what extensions are being used and their version.
• Liquibase Pro data: This tells us which Pro features are enabled.
• Operating system information: This includes the type of operating system, version, and architecture.

None of the data collected includes any personally identifiable information.

Enabling and disabling anonymous analytics

Depending on the edition of Liquibase you are using, this functionality may be enabled by default — you will always have the choice to opt in or out at any time.

For Liquibase OSS users, this functionality will be enabled by default. However, you can opt out and disable the functionality before any data is sent. For Liquibase Pro users, this functionality will be disabled by default, with the option to opt-in at any time.

How to opt out

If you do not want to participate in Liquibase anonymous analytics, there are a number of ways to opt out.

To turn off analytics for individual commands, you can add the parameter --analytics-enabled=false to the CLI command. This will turn off analytics for that single occurrence of the command.

If you would like to turn off the functionality globally, you can add liquibase.analytics.enabled: false to your defaults file or use the environment variable LIQUIBASE_ANALYTICS_ENABLED: false.

How to opt in

If you are a Liquibase Pro user or previously disabled anonymous analytics, there are a multiple ways to opt in.

To turn on analytics for individual commands, you can add the parameter --analytics-enabled=true to the CLI command. This will turn on analytics for that single occurrence of the command.

If you would like to turn on the functionality globally, you can add liquibase.analytics.enabled: true to your defaults file or use the environment variable LIQUIBASE_ANALYTICS_ENABLED: true.

Learn more

You can read more about this functionality in the documentation. If you have any questions or feedback, we’d love to hear from you! Please feel free to email us at product@liquibase.com.

Stay tuned: In early 2025, we'll be sharing a public dashboard of insights gathered from anonymous analytics. You'll be able to see data like the most used Liquibase commands, most used databases, popular ChangeLog formats, and more!