• Resolved ryanrs83

    (@ryanrs83)


    I am having issues with SitKit as it states it is connected in WP but in GA4 it states the tag cannot be detected.

    The page I need help with: [log in to see the link]

Viewing 15 replies - 1 through 15 (of 17 total)
  • Plugin Support Adam Dunnage

    (@adamdunnage)

    Hello @ryanrs83 and thanks for opening the topic. I’d be happy to help you with this. Please could you first share the following information:

    1. Your?Site Health information. You can?use this form?to share privately if preferred.??
    2. Do you see your Analytics tag firing when testing your site in the Google tag assistant?
    3. Did you encounter any issues when connecting the Analytics module in Site Kit?

    Once you have shared the information above I can review and help with some next steps for you to take. Let me know if you have any questions of your own in the meantime.

    Plugin Support Adam Dunnage

    (@adamdunnage)

    @ryanrs83 I see that you have shared your site health information so thanks for that! When checking your site via the tag assistant I don’t see your Analytics tag being fired. It also looks like that something is stopping Site Kit from placing the expected Analytics code on your site. This could be another plugin you have active on your site.

    If possible, could you try temporarily disabling all other plugins except for Site Kit on your site and test with the tag assistant once more or check your source code to see if you can see Site Kit placing the code. If you’re unsure on this then I’d be happy to do this for you once you have disabled all plugins so let me know.

    Thread Starter ryanrs83

    (@ryanrs83)

    Thanks Adam, I have disabled the plugins, please have a look now.

    Plugin Support Adam Dunnage

    (@adamdunnage)

    @ryanrs83 Thanks for doing this. When checking your site once more I still don’t see the Analytics code snippet that Site Kit should be placing on your site. Could you next try switching to a default WordPress theme and I can again check your source once more for the expected code.

    Let me know once you have done this and I can check for you.

    Thread Starter ryanrs83

    (@ryanrs83)

    Thanks, the default WP theme is now active ??

    Plugin Support Adam Dunnage

    (@adamdunnage)

    @ryanrs83 Thanks once again for trying this but unfortunately no luck again. We have had a recent report similar to this where the users WP_ENVIRONMENT_TYPE?was set to?local?in their wp-config.php file.

    From your site health I can’t see what value this is set to but please could you check as this needs to be set to?production?otherwise Site Kit will not place any code snippets on your site. If you’re unsure on how to do this then your hosting provider should be able to help you with that.

    Let me know how you get on with the above and if this isn’t the cause then we can continue to investigate further.

    Thread Starter ryanrs83

    (@ryanrs83)

    Thanks I just checked and it is set to production.



    ` wp-core

    version: 6.6.2
    site_language: en_US
    user_language: en_US
    timezone: +00:00
    permalink: /%postname%/
    https_status: true
    multisite: false
    user_registration: 0
    blog_public: 1
    default_comment_status: open
    environment_type: production
    user_count: 2
    dotorg_communication: true wp-paths-sizes

    What is strange is it works perfectly on the other sites on my server.
    Plugin Support Adam Dunnage

    (@adamdunnage)

    @ryanrs83 That is indeed strange. Can I ask if the other sites that are working with Site Kit have the same setup? I.e. plugins, theme.

    Is it possible for you to set up another fresh site on the same host to see if you get the same issue when installing and setting up Site Kit?

    Thread Starter ryanrs83

    (@ryanrs83)

    Hi Adam, yes I have two other sites set up similarly. I can try and create another website and see if the same issues persist.

    Plugin Support Adam Dunnage

    (@adamdunnage)

    @ryanrs83 Yes if you could try this and let me know if you encounter the same issue. If you do then please can you share the site URL for me to check. Let me know if you have any questions in the meantime.

    Thread Starter ryanrs83

    (@ryanrs83)

    Thanks Adam, I have now done the above and only have Wordfence installed on the site and Site Kit. I am getting the same issue but it might be due to it being too early to detect. Here is the site – heavenlygiggles.com

    Plugin Support Adam Dunnage

    (@adamdunnage)

    @ryanrs83 Thanks for trying this. Could I just check with you that the other sites that you have Site Kit working on, do they use Thrive themes as well? I think this might be the result of a plugin and theme conflict as we have seen this previously.

    If you could, would you be able to disable all plugins as well as switching your theme to a default theme so that I can inspect your site source code once more? I appreciate this might not be ideal for you but it will help us in identifying the cause of this.

    Thanks for your cooperation thus far.

    Thread Starter ryanrs83

    (@ryanrs83)

    Hi Adam, this new site is even using Thrive. All the other do as well, I like their tech-stack. The new site is working perfectly now. I have connect Site Kit, GA4, GTM and GSC with no issues.

    Please let me know what email I can use to share some sensitive data on readoverthis.com. It might help us troubleshoot this better. It is very strange that the same tech-stack is working perfectly for Heavenlygiggles.com. Same server, same theme, same plugins.

    • This reply was modified 1 week, 1 day ago by ryanrs83.
    • This reply was modified 1 week, 1 day ago by ryanrs83.
    Plugin Support Adam Dunnage

    (@adamdunnage)

    @ryanrs83 Thanks for confirming. With this in mind, could you then please try the steps listed above and let me know when ready so that I can check your site source code please?

    Thread Starter ryanrs83

    (@ryanrs83)

    Done ??

Viewing 15 replies - 1 through 15 (of 17 total)
  • You must be logged in to reply to this topic.