Forum Replies Created

Viewing 10 replies - 46 through 55 (of 55 total)
  • Thread Starter alexDx

    (@alexdx)

    @jamesosborne

    1. Your Site Health information. You can use this form to share privately if preferred.
    – I submitted this info using the form

    2. Are there any other administrators of this site?
    – There are no other admins of this site.

    3. When you noticed your site was not being tracked from the time you were disconnected from Site Kit can you share a screenshot of this from analytics.google.com? You can include a link to this within the same form when sending your Site Health information.
    – I just noticed this issue last week, but the site has apparently been showing a duplicate tag issue for over 90 days now.

    “I don’t see this when checking your site at present. I’m unable to debug what you have in your Google Tag Managaer container with Tagassistant.google.com, however, it’s possible you have a Universal Analytics tag, along with the Site Kit placed snippet. Can you confirm this, or do you see this notice after debugging your Tag Manager container?”

    https://northcountyvets.com/ This site is showing the issue … it currently has the “Same web property ID is tracked twice.” error when I use the tag assistant browser extension. I’ve found this issue on over 50 sites now … ALL showing the duplicate tag issue when I use tag assistant. They are all fixed as soon as I re-connect Sitekit.

    “however, it’s possible you have a Universal Analytics tag, along with the Site Kit placed snippet. Can you confirm this, or do you see this notice after debugging your Tag Manager container?”

    – I do not have another tag manually on the site. We don’t add any tags for GA on our sites as Sitekit adds them for us. This site ONLY has Sitekit enabled and does not have any manual tags embedded in the header of the site. If you are seeing two (in your screenshots) this has to be from Sitekit in some way, because we do not add our own tags to any sites.

    Thread Starter alexDx

    (@alexdx)

    @jamesosborne Thanks for the reply. I’m totally fine with being disconnected because of OAuth token limitation, as data is still being gathered.

    However, what I am referring to is an entirely different issue. Some of the sites that are disconnected are experiencing one of these issues:

    1. They are NOT getting data until I sign in to Sitekit again.
    Last week I found that one of my sites in Google Analytics hadn’t received any data over the last week. So I view the site using tagassistant.google.com and sure enough, there is NO GA TAG on the site. I log into the site and Sitekit is disconnected. I go through the process of signing into Sitekit again, and then I check the site in tagassistant.google.com, and BOOM the GA tag magically appeared again. Days later I check Google Analytics and the site is getting data again.

    2. They are showing a duplicate tag issue until I sign into Sitekit again.

    When I use tagassistant.google.com on https://northcountyvets.com/ it says “Same web property ID is tracked twice.” for the GA tag (you can currently see this as I haven’t fixed it yet). I log into the site, and notice that Sitekit isn’t connected. If I were to go through with connecting Sitekit again, and then refresh the page using tagassistant.google.com the “Same web property ID is tracked twice.” issue will be magically gone. I’ve gone through this on multiple sites now that have the “property ID is tracked twice” error, and every time it is Sitekit being disconnected – If I reconnect it, the issue disappears, and my data returns to normal.

    For many of my sites, if Sitekit becomes disconnected, they still get data and don’t have the duplicate tag issue, however, I keep finding plenty of sites that have the issues above, and the culprit is ALWAYS Sitekit has been disconnected on the site.

    • This reply was modified 3 years ago by alexDx.
    Thread Starter alexDx

    (@alexdx)

    Hey Ramona, that new version fixed the issue!

    Thread Starter alexDx

    (@alexdx)

    If your team can’t find a fix for this issue, I’m just going to have to find another slider plugin. I use this on hundreds of websites, but I can’t continue to use it if it is not compatible with my CSS.

    Thread Starter alexDx

    (@alexdx)

    Okay thank you, please let me know if you developer finds a fix for this. The slider was working fine (with the above CSS in place) before the update. I tried disabling the “Force Full Width” option, and the slider works, but it is very small.

    Thread Starter alexDx

    (@alexdx)

    Thank you for your quick reply! So I removed the critical CSS from each site, but now there is another issue:

    When you go to this site now (after removing critical CSS): https://vet2pet.ca/ in an incognito browser, the slider doesn’t load at all. If I go to another tab, and then go BACK to the https://vet2pet.ca/ site, the slider loads, but there is a very strange effect going on … the slider almost appears to be shaking?

    Same thing on this site:

    https://www.animalhospitalatbaldwinpark.com/

    • This reply was modified 3 years, 9 months ago by alexDx.
    • This reply was modified 3 years, 9 months ago by alexDx.
    Thread Starter alexDx

    (@alexdx)

    Last week it was working properly, but I did do some server updates last week. Tried running it yesterday, and getting the above error. I’m thinking it might be an older version of WP-CLI, but I can’t even run an update on it without getting that same error.

    Thread Starter alexDx

    (@alexdx)

    I can’t really think of anything in common other than they sit on the same server, and should be running latest version of PHP. They are all on the same version of WordPress as well. They may have some similar plugins, but no other redirect plugins.

    Thread Starter alexDx

    (@alexdx)

    Hey Matt, I really appreciate your help on this. Helped us narrow down the issue we were having ??

    Thanks man!

    Thread Starter alexDx

    (@alexdx)

    Hey Matt, thanks for the quick reply!

    This is one example post:

    https://www.seattlevetassoc.com/car-sickness-in-pets/

    This one isn’t showing for me in Screaming Frog.

    I submitted a fetch and render on this one, and this was the response:

    https://www.seattlevetassoc.com/car-sickness-in-pets/
    Googlebot type: Desktop (render requested)
    Partial on Monday, December 15, 2014 at 2:43:28 PM PST
    This is how Googlebot fetched the page:

    (image of my post)

    Googlebot couldn’t get all resources for this page. Here’s a list:
    https://www.seattlevetassoc.com/car-sickness-in-pets/redirection_mobile.min.js Type: script Reason: Not Found

    Is this post showing for you in SF?

    Also, none of the staff posts are showing for me:

    https://www.seattlevetassoc.com/sva_staff/shelly/

Viewing 10 replies - 46 through 55 (of 55 total)