As I’ve just spent a few hours looking at why my Google Analytics weren’t sent out on my end of month reports and after the upgrade to V6 it seemed I needed to reconnect my Google accounts. Customers were quick to email me asking where their data went which has been a mess in itself.
I have three GA accounts because I can only manage 100 per account. The first one downloaded all my accounts properly I then had problems withe the process timing out for the second. The timeout resulted in sending me back the confirmation screen and a second, third and fourth round of importing actually ended up duplicating the partially imported records. Unfortunately there’s no easy way to clean these up especially if you’re dealing with 600+ which is the amount of records I was left with. A delete with confirmation plus a refresh of browser was going to be another big time waster.
Many of the GA accounts imported appeared to be the same domain. After a bit of database work I pruned things back added a constraint on the table so it wouldn’t duplicate in the future and I I eventually managed to figure out Litespeed was timeing the process out after 5 minutes and it needed more time. Was quick to blame WAF and Cloudflare but not the culprit this time round
I wouldn’t recommend doing any db work directly for others but there seems to be some bugs here including if you reconnect any then any duplicate you have ends up being relabelled with the same one you just relabelled.
The timeout shouldn’t take you back to the same screen to save them again and again.
A bulk delete might be handy but I only see this being used if there’s a disaster like this in future.
Are you using the older method of adding GA accounts via JSON import?
We will look into this process and see if there are any improvements we can make to prevent duplication during reconnects, especially with a large number of sites per GA account, and look into the possibility of adding a bulk delete.
"Are you using the older method of adding GA accounts via JSON import?"
No, all newer authentication method
“We will look into this process and see if there are any improvements we can make to prevent duplication during reconnects, especially with a large number of sites per GA account, and look into the possibility of adding a bulk delete.”
If other people have the timeout issue it will start being an issue. I do have a decent VPS running this and optmised memory and php settings but if it stalls and returns them back to the save screen with the accounts listed there’s a good chance they’ll end up doing exactly what I did.
I originally had the json method of adding GA accounts before the new release. I think moving to MainWP 6 may of needed me to recreate the connection as all pro reports dropped their GAs. I was thinking the method of authenticating and selecting accounts would be easier. However the accounts I had continued to get disconnected, some wouldn’t even show up on the site settings page and so I abandoned the GA auth idea and went back to json which is now working perfectly again. I’d forgotten how I actually set it up adding my service account to every site. Readding it though was a breeze and I didn’t need to change the account on any GA access list. I hope for someone this might make a bit of sense or save you the heart ache.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.
WordPress® is a registered trademark of the WordPress Foundation, and WooCommerce® is a registered trademark of WooCommerce, Inc. MainWP is an independent product and is not affiliated, associated, or endorsed by the WordPress Foundation, WooCommerce, Inc., or Automattic Inc., except where noted under the Jetpack® API and Trademark License Agreement. All product names, logos, and brands are property of their respective owners and are used for identification purposes only.