Hello,
If “Purge HTML pages only” is enabled, the plugin will only clear the cached HTML pages from Cloudflare. It will not clear images or other static files like CSS or JS.
So if you update an image and want Cloudflare to fetch the new version, you would need to either:
- purge that specific image URL
- use Force purge everything
- or upload/use a new image URL so Cloudflare sees it as a new file
As for the difference between the two purge options:
- Purge whole cache follows your current plugin settings
- Force purge everything ignores that setting and clears everything from Cloudflare, including images and other static assets
So with “Purge HTML pages only” turned on, Purge whole cache would still leave images alone, while Force purge everything would remove everything.
About “Ignore marketing parameters”: yes, it can help improve cache hit rate, especially if you get traffic from Google Ads, Facebook ads, email campaigns, etc., where URLs often include things like gclid, fbclid, or utm_*.
In normal use, that should not break Google Ads tracking or conversion tracking, because those parameters are still in the visitor’s browser URL. The plugin is basically just ignoring them for cache purposes, so Cloudflare can serve the same cached page instead of creating a separate cache entry for every tracked URL variation.
The only time you’d want to be careful is if your site changes page content on the server side based on those parameters. In that case, ignoring them for caching could cause problems.
