• Jon

    (@freshyjon)


    We have proper Google Analytics code in the head. But it seems after the 4.6.0 update of your plugin, the events are no longer being logged.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author yuvalo

    (@yuvalo)

    Hi @freshyjon

    Can you post a link to the website? I’ll try and see what is going on there.

    Thanks,

    Yuval

    Thread Starter Jon

    (@freshyjon)

    https://www.foodbankst.org/

    I’m going to be debugging it soon, so may end up switching to a different plugin.

    Plugin Author yuvalo

    (@yuvalo)

    @freshyjon thanks for adding the link.
    The new version prefers using the Google Tag Manager code when both are on the website to prevent a few issues.

    Here is what should solve it –
    Go over this document and make sure that you have everything ready on the Google Tag Manager side. Steps 2 and 3 – https://wpflow.com/knowledgebase/google-tag-manager-support/#Step_2:_Create_a_New_Tag_Using_The_Custom_Variables
    Nothing you should do on the plugin settings.

    If you don’t mind me asking, why did you choose to add the Google Analytics code manually to the header if you are using Google Tag Manager alongside it?

    Yuval

    Thread Starter Jon

    (@freshyjon)

    I’m not adding Google Analytics “manually”, but am actually adding it via All In One SEO plugin.

    Why the Google Tag Manager code is on there, I’m not sure. It was likely requested by the client for some other purpose other than Google Analytics.

    I’m not sure it’s the best idea for your plugin to not work, if Google Tag Manager is added… since it’s possible it was added for other reasons beyond Google Analytics tracking. Especially when I’m referencing the ideal UA ID in your plugin.

    Edit: went back to using the trusty (albeit outdated) Gravitate plugin.

    • This reply was modified 5 years, 3 months ago by Jon.
    Plugin Author yuvalo

    (@yuvalo)

    @freshyjon

    The plugin does support Google Tag Manager but requires a few settings on that side.
    When you work with Google Tag Manager, you usually use that to include Google Analytics tracking, instead of adding the code manually to prevent conflicts and possible double tracking. I’m not saying there is one way of doing things but trying to explain our reasoning.
    We used to have conflicts when both are on the page, so when we auto-detect the code snippet to use, we chose GTM.

    I’ll try to revisit this decision and see if there is a better way to support both use cases.

    Yuval

    Plugin Author yuvalo

    (@yuvalo)

    Quick update – I may have a solution for all of this that will support your use case.
    It will take a day or two to release because it is bundled with new features that require more testing.

    Yuval

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘No longer tracking’ is closed to new replies.