Title: cache (just a specific) query string
Last modified: March 18, 2020

---

# cache (just a specific) query string

 *  [takaacstamaas](https://wordpress.org/support/users/takaacstamaas/)
 * (@takaacstamaas)
 * [6 years, 2 months ago](https://wordpress.org/support/topic/cache-just-a-specific-query-string/)
 * Hello!
 * We have some custom query parameters which are not standard UTM:
    [https://providentonline.hu/?ipf_source=google&ipf_medium=cpc](https://providentonline.hu/?ipf_source=google&ipf_medium=cpc)
   [https://providentonline.hu/?utm_formType=online](https://providentonline.hu/?utm_formType=online)
   [https://providentonline.hu/?utm_period=57&utm_productType=MT&utm_issueValue=80000](https://providentonline.hu/?utm_period=57&utm_productType=MT&utm_issueValue=80000)
   Can we config WP Fastest Cache to make these work like UTM queries? To be served
   froom cache, but keep parameters for measurements.
 * I got this trick:
    [https://www.wpfastestcache.com/tutorial/cache-url-with-querystring/](https://www.wpfastestcache.com/tutorial/cache-url-with-querystring/)..
   but I’m affraid it would cache unique gclid & fbclid parameters as well. Or not?
   If not, it would be good.
 * What do you recommend?
    Thanks! Tom
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fcache-just-a-specific-query-string%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Plugin Author [Emre Vona](https://wordpress.org/support/users/emrevona/)
 * (@emrevona)
 * [6 years, 2 months ago](https://wordpress.org/support/topic/cache-just-a-specific-query-string/#post-12558751)
 * /utm_period=57&utm_productType=MT&utm_issueValue=80000
    /utm_period=57&utm_productType
   =MT&utm_issueValue=70000 /utm_period=57&utm_productType=MT&utm_issueValue=60000
 * The caches of these three addresses are different from each other. is it ok for
   you?
 *  Thread Starter [takaacstamaas](https://wordpress.org/support/users/takaacstamaas/)
 * (@takaacstamaas)
 * [6 years, 2 months ago](https://wordpress.org/support/topic/cache-just-a-specific-query-string/#post-12558877)
 * Hello!
 * Its’ ok to be different in case of UTM parameters, these versions are limited.
   But if they can be served from the identical version, it’s also good because 
   we refresh issueValue after pageload by JS/ajax as well.
 * Thats why I was thinking about turning this ON:
    [https://www.wpfastestcache.com/tutorial/cache-url-with-querystring/](https://www.wpfastestcache.com/tutorial/cache-url-with-querystring/)..
   but I’m affraid it would cache the unlimited number of unique gclid & fbclid 
   parameters as well. Or not?
 *  Plugin Author [Emre Vona](https://wordpress.org/support/users/emrevona/)
 * (@emrevona)
 * [6 years, 2 months ago](https://wordpress.org/support/topic/cache-just-a-specific-query-string/#post-12562680)
 * > ..but I’m affraid it would cache the unlimited number of unique gclid & fbclid
   > parameters as well. Or not?
 * no, only one cache is created.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘cache (just a specific) query string’ is closed to new replies.

 * ![](https://ps.w.org/wp-fastest-cache/assets/icon-256x256.png?rev=2064586)
 * [WP Fastest Cache - WordPress Cache Plugin](https://wordpress.org/plugins/wp-fastest-cache/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wp-fastest-cache/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wp-fastest-cache/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-fastest-cache/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-fastest-cache/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-fastest-cache/reviews/)

## Tags

 * [queries](https://wordpress.org/support/topic-tag/queries/)

 * 3 replies
 * 2 participants
 * Last reply from: [Emre Vona](https://wordpress.org/support/users/emrevona/)
 * Last activity: [6 years, 2 months ago](https://wordpress.org/support/topic/cache-just-a-specific-query-string/#post-12562680)
 * Status: not resolved