All the state of the module is managed by a separate variables. The issue comes when there is a high traffic site and the cron get's executed. Variables are written to the database WAY too often. And that is killing the performance for client requests that get the bootstrap cache trashed.
Google's access tokens are preserved in variables as well. Causing the same issues as well as features and variables noice. Consider using cache API for that. This are access tokens they are short lived either way...
The simpler solution I see is to have all the state for the cron processes stored as a single variable. So it does not matter how long it takes, and how many times the data is changed if it's written in bulk to the DB.
Discussion, patch, etc.
None.
None.
Configurations variables structure changes.
Closed: outdated
3.0
Code
It affects performance. It is often combined with the Needs profiling tag.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Because of the Universal Analytics shutdown, version 7.x-3.x is no longer supported.
As Drupal 7 EOL is close, please consider upgrading to the latest Drupal and latest version of this module with Google Analytics 4 support.
If you are still here and experiencing problems with the latest version using GA4, then please open an issue about it.