fssbob

Thanks, I’d be happy to test it–except for unknown reasons the password prompt loop has stopped happening. If/when it recurs, I’ll test the add-on.

Bob

I’m fine enabling the REST API, so no need to follow up further on that.

One other condition I’ve run into: With the Varnish cache enabled, the password doesn’t work. (After entering the password there’s a pause, and then it requests the password again.) This isn’t an issue for my use case, as I’m fine without Varnish. (I’m using the password on a historical version of a site that will only be used for occasional research–and thus the caching doesn’t really matter.) But curious whether this is a known issue.

Thanks.

Thanks, I’ve subsequently found the fine print and figured it out. I had hit the 100 subscriber import limit on free accounts. It would be helpful if Jetpack gave a message about this rather than just erroneously stating that you’ll receive an import status email that then never arrives.

Got it. My remaining question is: I understand how this impacts ACCESS to GA reporting. But what happens to the GA data COLLECTION tag on the site?

1) I assume it remains regardless of whether an admin user with GA access is logged in. (Let me know if that’s incorrect.)

2) What happens if an admin user logs in who doesn’t have access to the current GA account but does have access to a different GA account? Will they be able to tell the site is already connected to a GA account and thus don’t attempt to reconnect it to their account? And what happens to the tag if they attempt the latter?

Thanks.

OK, thanks for the explanations.

I provide web support for a number of organizations. Typically, on a site there will be several Admin users. What is the best practice for handling their access to Analytics and Search Console? Should each WordPress Admin user be assigned their own Analytics and Search Console users (tied to the same account)? (If yes, what level of access is necessary.) Will this mean they get assigned different website tags, resulting in multiple tags on the site?

Or should all the Admin users reference one Analytics and one Search Console user? If the latter, that would mean having to share those user’s credentials and 2FA–correct?

After reading your response and the Google tag information page you referred me to, I could still use some additional clarification.

What happens if Site Kit determines the tag on the website no longer matches the Analytics property destination?

(I have a follow-up question, but it probably makes sense to wait until you answer this one.)

Thanks.

Thanks–that’s great.

However, in my case, I’ve subsequently discovered that I actually don’t need it. That’s because I have all entries set to auto-delete after X days (that feature is really nicely implemented, by the way), and spam entries end up auto-deleting just like the non-spam ones.