No longer tracking

Hi @freshyjon

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

Thanks,

Yuval

@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

@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