Configure the Logger

Every backend application relies on some kind of logs to debug it. The VWO SDK logger logs information about your running campaigns to help you with debugging. You can customize what kind of logs you need and where to send these, that is, you can write your own logger implementation to write the logs on some file, database, or some third-party logging service.



For the production environment, we recommend that you pass in your custom logger implementation while creating a VWO client instance.

Log Levels

Log LevelDescription
ERROR The events that prevent campaigns from functioning properly (for example, invalid settingsFile while initializing the VWO SDK, invalid campaign keys, or goal identifiers) are logged.
WARNING The events that don't prevent campaigns from functioning correctly, but can have unexpected outcomes (for example, future API deprecation) are logged.
INFO The events which are useful and provide a certain level of information (for example, activate started, bucket value assigned, part of a campaign, tracking user, conversion succeeded, and others) are logged. This depicts the flow of the API method used.
DEBUG Any kind of useful information that can help VWO debug the issue in case of unexpected behavior (for example, a user is not in a campaign, bucket value assigned, hash value assigned, and stored User Storage Service used, and others) are logged.

See the code example below on how to use these appropriately.


import com.vwo.VWO;

VWO.getSettingsFile(accountId, sdkKey);

public static VWOLogger getCustomLogger() {
    return new VWOLogger() {
        public void debug(String message, Object... params) {
            LOGGER.debug(message, params);

        public void info(String message, Object... params) {
  , params);

        public void warn(String message, Object... params) {
            LOGGER.warn(message, params);

        public void error(String message, Object... params) {
            LOGGER.error(message, params);