asafm7

Thanks, @jamesosborne.

It is possible that we are talking about different things. I’m only talking about the CTA button itself. It does not use an iframe and can be customized with CSS.

This HTML can be placed on templates successfully using a Custom HTML block:

<button swg-standard-button="contribution"></button>

You can likely enable the “Contribute with Google” Site Kit’s block on templates as well.

This block simply adds the HTML mentioned above, which can be successfully added to templates in other ways. (Display CTAs: Site-wide should be enabled on the Site Kit RRM module settings)

While the Custom HTML block solution works for now, I assume using the dedicated block will make things more future-proof (and also help improve the editing experience, allowing users to see the actual button design when editing instead of HTML code).

Let me know if I’m missing something.

Thanks again.

That’s interesting. I wonder if the Google team is aware of this. Thanks for the update, @jamesosborne.

My original issue was a bit confused, as my memory of the old issue was lacking.

I will try again.

Currently, LiteSpeed is hardcoding this whenever a page shouldn’t be cached:

lscache_wp/src/core.cls.php

This is added on the admin pages as well.

This is in response to my old issue:
https://wordpress.org/support/topic/apply_filterslitespeed_control_cacheable-returns-false-for-cacheable/

If I remember correctly, though, my old issue wasn’t about admin pages, but other cases (such as frontend pages that are excluded from cache via LiteSpeed page-specific settings).

I believe LiteSpeed’s hardcoding of the Cache-Control, as mentioned above, is problematic for a few reasons:

• For admin pages, it is redundant as WordPress core already adds the required no-cache header. LiteSpeed’s code overrides the header set by WordPress core.
• Unlike WordPress core, LiteSpeed doesn’t add the private value, which may be necessary.
• LiteSpeed is hardcoding the header, so it can’t be filtered and changed by the website owner. This is a problem, for example, because it means this plugin can’t be used: https://wordpress.org/plugins/nocache-bfcache/

Fixes may be:

• LiteSpeed adding the header only when necessary, and not on admin pages because WordPress already takes care of it.
• Anyway, allowing to filter the header.

Thanks.

Thanks for the update, @jamesosborne.

Site Kit logged in traffic isn’t counted by default

Yes. The kind of filtering I referred to is different. It also works for non-logged-in traffic, automated tastings, etc.

It will be relatively easy to check if Site Kit’s implementation breaks GA4 filters the same way Cloudflare’s does.

I will check in with the team on this, and let you know here should I have any update.

Thanks. It will also be easy to test with EU/UK IPs. Looking forward to learn if that’s s Google tag gateway limitation (possibly GDPR related?), or a Cloudflare implementation limitation.

Note that I’ll be asking based on a Site Kit implementation

Yes, of course. I’m only asking about Site Kit implementation.

Thanks again for your time!

@jamesosborne, thank you so much for the testing and the update.

Regarding filtering out internal traffic, I use this GA4 feature:

[GA4] Filter out internal traffic – Analytics Help

It filters by IP, and it worked great up until I implemented Google tag gateway via Cloudflare (which probably obstructs the IPs). Now, traffic from the IPs set to be excluded is recorded regularly instead of being filtered out.

I posted a question on both Cloudflare and GA4 communities, but I wonder if there will be a similar issue when using your implementation, instead of Cloudflare’s.

Also, is it possible to opt-in to the early release?

Thanks again.

Great, @jamesosborne.

Thanks for checking.

Looking forward to updates.

Thanks, @jamesosborne.

It is great to hear about the upcoming feature.

I’m using Cloudflare as a CDN, and implemented Google tag ateway using Google Tag Manager’s “Automated setup with Cloudflare“.

Will you call it a manual implementation?

Will Site Kit’s Google tag gateway feature work different? better?

Thanks again.