Why Does the "Skipping Integration, Not Enabled" Message Appear in Convert Chrome Debugger Logs?

The "skipping integration, not enabled" message in Convert's Chrome Debugger indicates that a specific integration for an experience or variation is not active or configured. Recognizing this helps you troubleshoot integration issues effectively.

What Does "Skipping Integration, Not Enabled" Mean?

The message "skipping integration, not enabled" indicates that the specific integration for the experience or variation you are working on is not activated or configured. This can happen for various reasons, such as:

• The integration settings have not been enabled in your Convert account.
• The specific integration (e.g., Google Analytics, Mixpanel) has not been set up correctly within the Convert platform.
• The integration may be disabled for this particular experience or variation.

In the context of the Convert Chrome Debugger, this message is not necessarily related to Google Analytics (GA) or any specific integration unless explicitly mentioned. Instead, it is a general message indicating that an integration was expected but is not active.

How to Identify Which Integration Was Skipped

If you need to determine which specific integration was skipped, you can modify the URL by appending the parameter &convert_log_level=debug to the request. This will provide a more detailed log that includes information about the integrations that were skipped and why they were not enabled.

For example:

By doing this, the debugger will offer more granular details, allowing you to identify the specific integration that was skipped during the experience.

Example Log Entry

Here is an example of a typical log entry with the "skipping integration, not enabled" message:

In this example, the experience identified by #100493787 skips integrations because they are not enabled.

Next Steps

If you encounter this message and need the integration to work, follow these steps:

1. Make sure to enable the integration you are expecting in your Convert account by checking the "Integrations" section in the Convert platform. This can be done under the "Integrations" section in the Convert platform.

2. Verify Experience Settings: Ensure that the integration is enabled for the specific experience or variation you are testing.

3. Use Debug Mode: Append &convert_log_level=debug to your request URL to obtain detailed information about which integrations are being skipped and why.

4. Consult Documentation: Review the Convert documentation for specific instructions on how to enable and configure integrations for your experiences.

By following these steps, you can effectively troubleshoot and resolve issues related to skipped integrations in Convert.

Conclusion

The "skipping integration, not enabled" message in the Convert Chrome Debugger is an important indicator that an expected integration is not active. By using the debugging tools provided by Convert, you can quickly identify and resolve any issues, ensuring that your experiments run smoothly with all necessary integrations enabled.