• Resolved hatschiii

    (@hatschiii)


    The plugin is working very well… it is using the actual analytics.js. Is there a way to tell the plugin that it should use the older oga.js instead?

Viewing 6 replies - 16 through 21 (of 21 total)
  • Plugin Author DaanvandenBergh

    (@daanvandenbergh)

    @hatschiii, nevermind! Haha, the first time I loaded your message the snippets were truncated, so at first I asked if that was intentional or accidental. Then after posting my reply, the full snippets were loaded. So I edited my message ??

    I’ll have to try and reproduce this issue locally. The strange thing is, is that this plugin has worked fine with ga.js in the past and nothing has changed codewise within the snippet. I updated it to analytic.js at one point, which worked fine as well. So implementing ga.js again shouldn’t be that much of a challenge, but sadly it is. ??

    I’ll get back to you.

    Plugin Author DaanvandenBergh

    (@daanvandenbergh)

    @hatschiii I’ve made some code optimizations in the new version. I also added support for gtag.js.

    I wasn’t able to reproduce your issue though. Could you let me know if you’re still running into issues?

    Thread Starter hatschiii

    (@hatschiii)

    Yes, I’m still running in this issue ??

    Plugin Author DaanvandenBergh

    (@daanvandenbergh)

    @hatschiii,

    One more question: did you do the following?

    – Change to ga.js,
    – click Save Changes
    – click Update ga.js

    Because the file needs to be downloaded, before it can be used.

    Thread Starter hatschiii

    (@hatschiii)

    yes,I did

    Plugin Author DaanvandenBergh

    (@daanvandenbergh)

    @hatschiii,

    Just a heads up, I’m going to remove ga.js-support in the future. It’s legacy code anyway, and trying to resolve this issue is creating too much overhead. IMO the benefits don’t weigh up to the costs.

Viewing 6 replies - 16 through 21 (of 21 total)
  • The topic ‘Host ga.js locally, not analytics.js’ is closed to new replies.