Hello (again, heh:). I have to apologize to you because, after sending you my previous comment, I proceeded (as I mentioned) to;
1) Unlink Ajax Search Lite from Google Analitycs
2) Remove from Analitycs the ajax-search parameter
However.
When I went to my Analitycs (to remove the aforementioned parameter), I found this;
https://ibb.co/8rdkFD2
In other words, as you can see, your recommendations YES. They worked!
What happened is that these results were only seen the next day (and NOT in a couple of hours, as you say in your article, heh:)
Having said that, it seems that searches are reflected like any other event, but NOT immediately (ie in the “live traffic window”, as you mentioned in a previous thread).
So if – apparently – your plugin + the script you sent me… THEY WORK!
As for the “error” you mention, I THINK it has to do with the fact that the script that loads GALite is async
That is…
<script async src=”/wp-content/uploads/external/gal.js”></script>
And at the same time, my caching plugin (W3TC) was combining it and… adding “defer” to it! 🙂
Anyway.
I just added the file in question (the one that runs GALite on my site) to the W3TC minified (and combined) “exceptions” list, but it’s “taking” a long time to finish “cleaning” it of all the source code. .
Which leads me to “suspect” that, despite the fact that, as you say, said error appears immediately after loading GALite, apparently it has NOT to do with said script! (But with someone else) (*)
Anyway, I already tried everything again (after excepting the js file mentioned above) and apparently it works ok (That is, the code loads, the “stuff” is seen in my Analitycs, it does NOT block me from loading the site , etc.).
But, as I mentioned, in the source code, you still see the “combination” of that file (external/gal.js) as async and – at the same time – defer, heh.
Okay. I have already reintegrated your tool with my Google Analitycs as I had previously described.
I’m going to keep trying to do test searches in your search engine and tomorrow I’ll tell you the results.
For now that’s all.
Thank you very much and, again, a thousand apologies.
Greetings.
PS: (*) Update:
1) Indeed, the only code that looks like that is the Facebook pixel!
<!– Facebook Pixel Code –>
<script>async defer crossorigin=”anonymous”
‘/wp-content/uploads/external/fb.js’;
fbq(‘init’, ‘xxxxxxxxxxxxxxxxxx’);
fbq(‘track’, ‘PageView’);
</script>
Therefore, I removed the GALite one from the exceptions, and added this one.
2) Anyway, in my source code, the “error” you mention still appears because, strictly speaking, if you look closely, it is part of the “construction” of the Facebook pixel insertion function.
This is…”<script>async defer crossorigin=”anonymous”
But, as you surely know, this code is the one that “offers” Facebook itself, to insert its pixel.
3) So, I leave it as it is and remove the script file for said pixel from the W3TC minify / merge exclusions.
In any case, I still don’t know very well what I’m installing said pixel for, because I just “informed” that they NO LONGER have Analitycs!
Anyway, as it does NOT bother me (it does not block the loading of the site) for now I leave it.
Later I will see if I can hire a FB Marketing specialist (Community Manager) and see if he finds any use for it. Or, I will proceed directly to delete it.
Okay. For now that’s all. I’ll keep doing search tests (with and without sense for my site) to see what results my Analitycs registers.
I’ll tell you tomorrow.
