It appears that regardless of configuration, if the plugin is installed, web requests will always end up with a an _ia cookie set.
I thought this would be solely controlled with autoSendPageView, but that doesn't appear to be the case.
A blank template still sends up with a Set-Cookie: _ia=….
A response with a Set-Cookie: header is often used an indicator to caching mechanisms that this response should not be cached. This includes static caches like Craft Cloud, Fastly, Varnish, Cloudflare.
In my example, IA is only being used for the Commerce event integration, but having the plugin enabled disabled static cache globally.
It appears that regardless of configuration, if the plugin is installed, web requests will always end up with a an
_ia
cookie set. I thought this would be solely controlled withautoSendPageView
, but that doesn't appear to be the case.For example:
A blank template still sends up with a
Set-Cookie: _ia=…
.A response with a
Set-Cookie:
header is often used an indicator to caching mechanisms that this response should not be cached. This includes static caches like Craft Cloud, Fastly, Varnish, Cloudflare.In my example, IA is only being used for the Commerce event integration, but having the plugin enabled disabled static cache globally.