Viewing 2 replies - 16 through 17 (of 17 total)
  • Thread Starter Alex Kladov

    (@prowebassist)

    Hi @stevenjmcconnell ,

    Unfortunately, it’s an absolute shame how this very critical bug has been treated to this day – they have accepted @jamescollins’s fix in 1.4.10, which fixed the issue for everyone with correct plugin settings, BUT then they reverted everything back in 1.4.11, breaking all the sites again. The reason for a rollback was the fact that most users had incorrect settings, so the 1.4.10 update has silently affected everyone’s tracking.

    On the “bright” side, they’ve added a filter now, that lets developers bypass the setting entirely using a simple filter function. Seems like a copout solution to a very serious problem. I have suggested a different approach, but so far haven’t heard anything back..

    As for your question, it would probably be best to use this code below in your functions.php file in your child theme, instead of modifying the core plugin files directly:
    add_filter('wc_goole_analytics_send_pageview', '__return_false');

    Otherwise, every time you edit core plugin files & update the plugin, all of your changes will be gone. That’s why you might’ve continued seeing duplicates.

    This means the last 2 months of my GA data is unreliable.

    I’d say more like ANY GA data becomes unreliable, if you use this plugin + a standard GA tracking code. Until they fix this issue, you are better off not using this plugin or using it EXCLUSIVELY (since it tracks standard GA data, whether you want it or not).

    Cheers,
    Alex

    • This reply was modified 4 years, 8 months ago by Alex Kladov. Reason: Edited incorrect filter hook

    Personally, I am switching to Google Tag Manager tracking using the gtm4wp plugin (ex Duracell Tomi’s) which is completely free.

    It also has a simple guide to enable Advanced Ecommerce tracking => https://gtm4wp.com/how-to-articles/how-to-setup-enhanced-ecommerce-tracking

    The SkyVerge plugin alas has proven to be too unreliable… and expensive at that.

Viewing 2 replies - 16 through 17 (of 17 total)
  • The topic ‘Compatibility issues with GADWP’ is closed to new replies.