Other plugins are no longer working properly after activating QA Heatmap Analytics

More often than not, plugins stop working due to compatibility issues between them, rather than due to QA itself. Please be especially careful with the following three types.

  • Cache plugins
  • Backup plugins
  • Security plugins

Regarding cache plugins

– Disable JavaScript compression and rewriting.

Some cache-based plugins compress or rewrite JavaScript without permission. In that case, the QA measurement tag will not work properly and you will not be able to get any data. In this case, as described in this article, please set the cache plugin’s settings so that it does not compress or rewrite JavaScript.

– Shorten the cache lifespan.

QA is built in such a way that it does not record bot access. However, some cache plugins create a cache even for bot access. Then, while the cache is being accessed, QA will assume that it is a bot access and it will not be recorded.

Also, QA uses a nonce value as a security measure, and accesses to the cache that are more than 24 hours old will not be measured.

The countermeasure to the above two points is to make the lifespan of the cache as short as possible. If you set it to about 1 hour, the maximum unmeasured data time will be about 1 hour. If you are concerned about server load, you can set it so that it does not exceed 24 hours.

Regarding backup and security plugins

– Exclude QA data storage area.

Some backup and security plugins may not be designed for software that measures data as frequently as QA or stores large data.

Therefore, after adding QA, it may not be backed up properly or the load of security plugins may increase.

This can be avoided by excluding QA from the configuration screen if there is one.

Specifically, it often works well by excluding the data area named ‘wp-content/qa-heatmap-analytics-data’.

– Use a different plugin or security settings on the rental server side.

Even if they are famous, there are plugins that do not have the configuration screens mentioned above. There are also plugins that do not have a very good system to begin with. In that case, the server may be overloaded by the use of that plugin regardless of QA in the first place.

QA recommends that you use the backups that come with your rental server. This way, the load on the server will be smaller and the data will be restored without fail.

Security may be handled on the server side as well. If possible, it is recommended that you check from this perspective when you rent a server.

Other problems with existing plugins or templates

As described above, this is not only a problem on the QA side, but also a compatibility problem. Therefore, you will often have to change the settings of plugins that were already in place.

Search the official support forum of the original plugin on WordPress.org forum, search in QA support forum, or ask questions at there. Please use these services as you may be able to get solutions from knowledgeable people.

Was this article helpful?

Related Articles