Hi @rplakas,
Still having problem with UTM not populating?
Your case seems different than caching to me (but not entirely positive). My hunch is there is something prevents capturing UTM variables in cookies. I do realized all UTM fields somehow converted and recorded as pys_fb_pixel_*. See image here http://i.imgur.com/Lst2NVO.png
Thread Starter
RichP
(@rplakas)
Still not populating for me. I can put in a ticket with WPEngine as this is happening on a few different sites.
Can you give me a little more info on your insights on what the hosting company should look for? Thanks.
Thread Starter
RichP
(@rplakas)
I did get this to work with WPEngine but the resolution is not ideal.
They basically needed to turn off caching for most of the page in order to get this to work.
They mentioned something about it working better if the plugin used javascript, but to be honest I’m not much of a coder.
I would be happy to open another ticket so you could speak with them directly.
Hi @rplakas,
I am glad you figured it out even though it is not ideal. Please go ahead and open a ticket with them, i want to listen their suggestions. Because, I know, some other people in past had similar issue. And I want to resolve this if it is all possible.
Thanks,
Haktan
Thread Starter
RichP
(@rplakas)
Actually, it only works when I manually put the utm fields in the url, not when traffic is coming in naturally from sources.
I will open another ticket up and get you looped in with it.
Screenshot: https://www.evernote.com/l/AAvcYQTDaD1EArI8Ymoj_Ql9q-GQD_tPSOU
I see that this is marked as resolved, but just in case, I’ll offer my insight. My problem with WP Engine ended up being that they needed to exclude UTM parameters from the cache. See here: https://wpengine.com/support/utm-gclid-variables-caching/
Thread Starter
RichP
(@rplakas)
Thanks for the input!
I thought I had WPEngine do this, but I will check with them again.
I only see the source/medium in Gravity Forms for urls with manually added UTMs.
They did mention to me that this would work better in Javascript. See below:
POTENTIAL CONFLICTS
For most tracking purposes with Google Analytics, this still allows your campaigns to be tracked properly as the code is tracked and sent to Google Analytics via JavaScript. However, if you also want to execute a specific action based on these variables, you may run into conflicts with our caching system.
If this is the case, Site Managers can contact WP Engine Support through the User Portal to request a cache exclusion for the needed variables. When contacting Support, please have the following information ready:
Install name affected
Example of an affected URL
Replication steps for the issue
Which variables will be added to URLs
Approximate percentage of traffic using these variables
It’s very important, if you do run into conflicts, to understand that excluding these variables from cache could very easily cause performance issues for your site. If a lot of your site’s traffic uses these variables, much more traffic will be uncached as the server will have to generate each request as new. This means your site will not be able to scale to support as much traffic as it would if it were taking full advantage of our caching layer.
It’s far better to ensure that any action based on these variables is either executed with JavaScript or to use a variable of a different name (not utm_ or gclid_). If your site runs into issues and errors because too many uncached requests are coming in, WP Engine reserves the right to take out cache exclusions if necessary.
Thread Starter
RichP
(@rplakas)
@radrei Are you able to see source/medium without manually explicit UTMs such google/organic ?
So what you’re saying is that unless you type the UTMs into the URL yourself, you’re not seeing them? I do not have to do that, they appear correctly by themselves. I am, however, having a problem with Firefox (which I created a separate ticket for). I can only get it to work in Chrome and IE.
