Wordpress APO: Exclude analytics parameters from seznam.cz

we run a .cz site (with APO plugin), which regularly gets huge waves of a traffic from a homepage of seznam.cz (the site with the largest amount of visitors in the Czech republice - see https://en.wikipedia.org/wiki/Seznam.cz). They are promoting articles from different sites through their “Newsfeed”. The problem is that these links contains some analytic query parameters (beside “standard” utm_source/utm_medium) which have unique values per user and therefore APO can’t help us with mitigating this traffic :frowning:

So my question - would it be possible to add these query parameters:

* consent
* dop_req_id
* dop_id

(I’ve picked only parameters with seemingly unique values per user)
into the list of ignored parameters? I think that many other larger Wordpress media/magazine instances in Czech republic could benefit from this.

Or are theirs names too general so it could break other sites? If so, is there some option how we can tweak this in APO plugin just for our domain?

How the link could look like:




While waiting for the APO Team to respond to your request re: adding your query string parameters to their list, you can add a Cache Rule (beta) with an expression that will add to cache

When incoming requests:match...

(http.request.uri.query contains "content") or (http.request.uri.query contains "dop_req_id") or etc.

Cache Rules are very flexible and you can tailor them to more specific needs, such as restricting this rule to a specific hostname, or some specific path, or path pattern, if that’s the case.

Then you click on Cache Keys > Ignore Query String.

You’ll see that requests containing these parameters will return the header

cf-apo-via: origin,qs

However they should also contain the header

cf-cache-status: HIT instead of DYNAMIC, indicating the page is being cached,

Two caveats:

  1. Cache Rules is in beta, and some features may not be available on a permanent basis.
  2. Once you set Ignore Query String, if there’s a request that comes with both a functionally dynamic query parameter along with any of the ones included in your rule (for ex., /content=12345&some_product_key=12345), the page would be served from cache. You’d need to refine the rule to exclude from cache accordingly.
1 Like

thanks a lot for your tip with Cache rules, I’ve just set it up and it seems working like a charm for us!


1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.