Switched to Google Site Kit, now analytics no longer working
-
I originally connected my site to GA using a plugin called ‘GA Google Analytics’, which worked well for several years. However, recently I decided to replace this with Google Site Kit. I deactivated the original plugin, installed Site Kit and set it up. I confirmed that the same id was being used as before. Nothing came through to GA. So I deactivated Site Kit, reactivated the original plugin – and still nothing. Now neither plugin will send data to GA. I’m not very technical; I used Chrome’s Tag Assistant, which shows the tag with the correct id but says “no hits were sent by this tag”. I also connected Site Kit to my Ads account (the original reason for switching to Site Kit), following the instructions on the Ads site for Site Kit, at the bottom of which is a ‘test your website’ option. This returns “Your Google tag wasn’t detected on your website.”
The Site Kit dashboard shows historical traffic i.e. up to the point when I switched over, so it is correctly connected to GA. It’s also connected PageSpeed, and showing correct data from that on the dashboard.
The page I need help with: [log in to see the link]
-
Thanks for reaching out @justinhill001. Based on what you’re describing, it is possible that the old Google Analytics property which you’re referring to, was a Universal Analytics type property, which proceeds the newer Google Analytics 4 type?
Note also that I checked your site and I don’t see any standard Site Kit placed Google Analytics snippet. This may be due to the optimizations you have performed, as I can see a GA4 property when checking your site using the tagassistant.google.com service. So we can determine more on this, please share the following:
- Your Site Health information. You can use this form to share privately if preferred.??
- Are you seeing data for this site (possibly for a G-02S181GG2H property) when visiting analytics.google.com?
Let me know if you have any questions with the above.
Thanks for your reply. The old plugin was already running GA4 – originally UA but updated at some point in the past.
No, There is no tracking showing on Google Analytics. G-02S181GG2H is the correct property.
Here’s my site info:
` wp-core version: 6.4.2
site_language: en_GB
user_language: en_GB
timezone: Europe/London
permalink: /%year%/%monthnum%/%day%/%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 wordpress_path: /home/theother1/public_html
wordpress_size: 402.12 MB (421648906 bytes)
uploads_path: /home/theother1/public_html/wp-content/uploads
uploads_size: 95.47 MB (100111233 bytes)
themes_path: /home/theother1/public_html/wp-content/themes
themes_size: 1.86 MB (1952807 bytes)
plugins_path: /home/theother1/public_html/wp-content/plugins
plugins_size: 78.54 MB (82352104 bytes)
database_size: 4.96 MB (5205151 bytes)
total_size: 582.95 MB (611270201 bytes) wp-dropins (1) advanced-cache.php: true wp-active-theme name: Twenty Seventeen (twentyseventeen)
version: 3.4
author: the WordPress team
author_website: https://en-gb.www.ads-software.com/
parent_theme: none
theme_features: core-block-patterns, widgets-block-editor, automatic-feed-links, title-tag, custom-line-height, post-thumbnails, menus, html5, post-formats, custom-logo, customize-selective-refresh-widgets, editor-style, editor-styles, wp-block-styles, responsive-embeds, starter-content, custom-header, jetpack-geo-location, widgets
theme_path: /home/theother1/public_html/wp-content/themes/twentyseventeen
auto_update: Disabled wp-themes-inactive (2) Twenty Twenty-Four: version: 1.0, author: the WordPress team, Auto-updates disabled
Twenty Twenty-Three: version: 1.3, author: the WordPress team, Auto-updates disabled wp-plugins-active (18) Advanced Editor Tools: version: 5.9.2, author: Automattic, Auto-updates disabled
Akismet Anti-spam: Spam Protection: version: 5.3, author: Automattic - Anti-spam Team, Auto-updates enabled
Async JavaScript: version: 2.21.08.31, author: Frank Goossens (futtta), Auto-updates disabled
Classic Editor: version: 1.6.3, author: WordPress Contributors, Auto-updates disabled
Classic Widgets: version: 0.3, author: WordPress Contributors, Auto-updates disabled
Code Snippets: version: 3.6.2, author: Code Snippets Pro, Auto-updates disabled
Contact Form 7: version: 5.8.6, author: Takayuki Miyoshi, Auto-updates disabled
Flying Scripts: version: 1.2.3, author: WP Speed Matters, Auto-updates disabled
Jetpack: version: 13.0, author: Automattic, Auto-updates disabled
Jetpack Boost: version: 2.2.1, author: Automattic - Jetpack Site Speed team, Auto-updates disabled
MaxButtons: version: 9.7.6, author: Max Foundry, Auto-updates disabled
RapidLoad 2.2 - Speed Monster in One Plugin: version: 2.2.9, author: RapidLoad, Auto-updates disabled
Site Kit by Google: version: 1.116.0, author: Google, Auto-updates enabled
SiteOrigin CSS: version: 1.5.9, author: SiteOrigin, Auto-updates disabled
W3 Total Cache: version: 2.6.1, author: BoldGrid, Auto-updates disabled
WP Image CAPTCHA: version: 3.3.12, author: WP Image CAPTCHA, Auto-updates disabled
Yoast SEO: version: 21.8, author: Team Yoast, Auto-updates disabled
Yoast SEO: Local: version: 15.1, author: Team Yoast and Arjan Snaterse, Auto-updates disabled wp-plugins-inactive (3) 404 to 301 - Redirect, Log and Notify 404 Errors: version: 3.1.4, author: Joel James, Auto-updates disabled
EWWW Image Optimizer: version: 7.2.3, author: Exactly WWW, Auto-updates disabled
GA Google Analytics: version: 20231101, author: Jeff Starr, Auto-updates disabled code-snippets (1) snippet-5: name: Disable WP Core scripts, scope: front-end, modified: 2022-11-24 10:11:38 wp-media image_editor: WP_Image_Editor_Imagick
imagick_module_version: 1809
imagemagick_version: ImageMagick 7.1.1-25 Q16-HDRI x86_64 21883 https://imagemagick.org
imagick_version: 3.7.0
file_uploads: 1
post_max_size: 128M
upload_max_filesize: 32M
max_effective_size: 32 MB
max_file_uploads: 20
imagick_limits:
imagick::RESOURCETYPE_AREA: 748 GB
imagick::RESOURCETYPE_DISK: 9.2233720368548E+18
imagick::RESOURCETYPE_FILE: 196608
imagick::RESOURCETYPE_MAP: 374 GB
imagick::RESOURCETYPE_MEMORY: 187 GB
imagick::RESOURCETYPE_THREAD: 1
imagick::RESOURCETYPE_TIME: 0
imagemagick_file_formats: 3FR, 3G2, 3GP, AAI, AI, APNG, ART, ARW, ASHLAR, AVI, AVS, BAYER, BAYERA, BGR, BGRA, BGRO, BIE, BMP, BMP2, BMP3, BRF, CAL, CALS, CANVAS, CAPTION, CIN, CIP, CLIP, CMYK, CMYKA, CR2, CR3, CRW, CUBE, CUR, CUT, DATA, DCM, DCR, DCRAW, DCX, DDS, DFONT, DNG, DOT, DPX, DXT1, DXT5, EPDF, EPI, EPS, EPS2, EPS3, EPSF, EPSI, EPT, EPT2, EPT3, ERF, EXR, FARBFELD, FAX, FF, FILE, FITS, FL32, FLV, FRACTAL, FTP, FTS, FTXT, G3, G4, GIF, GIF87, GRADIENT, GRAY, GRAYA, GROUP4, GV, HALD, HDR, HISTOGRAM, HRZ, HTM, HTML, HTTP, HTTPS, ICB, ICO, ICON, IIQ, INFO, INLINE, IPL, ISOBRL, ISOBRL6, J2C, J2K, JBG, JBIG, JNG, JNX, JP2, JPC, JPE, JPEG, JPG, JPM, JPS, JPT, JSON, K25, KDC, KERNEL, LABEL, M2V, M4V, MAC, MAP, MASK, MAT, MATTE, MEF, MIFF, MKV, MNG, MONO, MOV, MP4, MPC, MPEG, MPG, MPO, MRW, MSL, MSVG, MTV, MVG, NEF, NRW, NULL, ORA, ORF, OTB, OTF, PAL, PALM, PAM, PANGO, PATTERN, PBM, PCD, PCDS, PCL, PCT, PCX, PDB, PDF, PDFA, PEF, PES, PFA, PFB, PFM, PGM, PGX, PHM, PICON, PICT, PIX, PJPEG, PLASMA, PNG, PNG00, PNG24, PNG32, PNG48, PNG64, PNG8, PNM, POCKETMOD, PPM, PS, PS2, PS3, PSB, PSD, PTIF, PWP, QOI, RADIAL-GRADIENT, RAF, RAS, RAW, RGB, RGB565, RGBA, RGBO, RGF, RLA, RLE, RMF, RSVG, RW2, SCR, SCT, SFW, SGI, SHTML, SIX, SIXEL, SPARSE-COLOR, SR2, SRF, STEGANO, STRIMG, SUN, SVG, SVGZ, TEXT, TGA, THUMBNAIL, TIFF, TIFF64, TILE, TIM, TM2, TTC, TTF, TXT, UBRL, UBRL6, UIL, UYVY, VDA, VICAR, VID, VIFF, VIPS, VST, WBMP, WEBM, WEBP, WMF, WMV, WMZ, WPG, X, X3F, XBM, XC, XCF, XPM, XPS, XV, XWD, YAML, YCbCr, YCbCrA, YUV
gd_version: 2.3.3
gd_formats: GIF, JPEG, PNG, WebP, BMP, XPM
ghostscript_version: not available wp-server server_architecture: Linux 4.18.0-477.27.1.el8_8.x86_64 x86_64
httpd_software: LiteSpeed
php_version: 7.4.33 64bit
php_sapi: litespeed
max_input_variables: 10000
time_limit: 60
memory_limit: 384M
max_input_time: 60
upload_max_filesize: 32M
php_post_max_size: 128M
curl_version: 7.61.1 OpenSSL/1.1.1k
suhosin: false
imagick_availability: true
pretty_permalinks: true
htaccess_extra_rules: true
current: 2024-01-11T14:05:32+00:00
utc-time: Thursday, 11-Jan-24 14:05:32 UTC
server-time: 2024-01-11T14:05:31+00:00 wp-database extension: mysqli
server_version: 10.5.23-MariaDB
client_version: mysqlnd 7.4.33
max_allowed_packet: 67108864
max_connections: 450 wp-constants WP_HOME: https://theotheroperation.com/
WP_SITEURL: https://theotheroperation.com/
WP_CONTENT_DIR: /home/theother1/public_html/wp-content
WP_PLUGIN_DIR: /home/theother1/public_html/wp-content/plugins
WP_MEMORY_LIMIT: 40M
WP_MAX_MEMORY_LIMIT: 384M
WP_DEBUG: false
WP_DEBUG_DISPLAY: false
WP_DEBUG_LOG: false
SCRIPT_DEBUG: false
WP_CACHE: true
CONCATENATE_SCRIPTS: undefined
COMPRESS_SCRIPTS: undefined
COMPRESS_CSS: undefined
WP_ENVIRONMENT_TYPE: Undefined
WP_DEVELOPMENT_MODE: undefined
DB_CHARSET: utf8
DB_COLLATE: undefined wp-filesystem wordpress: writable
wp-content: writable
uploads: writable
plugins: writable
themes: writable jetpack site_id: 199521956
ssl_cert: No
time_diff: undefined
version_option: 13.0:1704981168
old_version: 12.9.3:1703322238
public: Public
master_user: #2 justin
is_offline_mode: off
is_offline_mode_constant: off
current_user: #2 justin
tokens_set: Blog User
blog_token: YnP8cZoG7WpLUCpX$2fYVx(gzNI%b!
user_token: sQKJPHPsCnhtn@0%rfr&A1$fk1AYMmx3
version: 13.0
jp_plugin_dir: /home/theother1/public_html/wp-content/plugins/jetpack/
plan: security
protect_header: {"trusted_header":"REMOTE_ADDR","segments":1,"reverse":false}
full_sync: {"started":"Thu, 23 Feb 2023 11:50:08 +0000","finished":"Thu, 23 Feb 2023 11:50:11 +0000","progress":{"options":{"finished":true},"functions":{"finished":true},"constants":{"finished":true},"users":{"total":"1","sent":1,"finished":true,"last_sent":"2"},"network_options":{"finished":true}},"config":{"options":true,"functions":true,"constants":true,"users":[2],"network_options":true}}
sync_size: undefined
sync_lag: 0 seconds
full_sync_size: undefined
full_sync_lag: 0 seconds
idc_urls: {"home":"https:\/\/theotheroperation.com\/","siteurl":"https:\/\/theotheroperation.com\/","WP_HOME":"https:\/\/theotheroperation.com\/","WP_SITEURL":"https:\/\/theotheroperation.com\/"}
idc_error_option: false
idc_optin: true
cxn_tests: All Pass. google-site-kit version: 1.116.0
php_version: 7.4.33
wp_version: 6.4.2
reference_url: https://theotheroperation.com
amp_mode: no
site_status: connected-site
user_status: authenticated
verification_status: verified-non-site-kit
connected_user_count: 1
active_modules: site-verification, search-console, analytics, analytics-4, pagespeed-insights
recoverable_modules: none
required_scopes:
openid: ?
https://www.googleapis.com/auth/userinfo.profile: ?
https://www.googleapis.com/auth/userinfo.email: ?
https://www.googleapis.com/auth/siteverification: ?
https://www.googleapis.com/auth/webmasters: ?
https://www.googleapis.com/auth/analytics.readonly: ?
https://www.googleapis.com/auth/tagmanager.readonly: ?
capabilities:
googlesitekit_authenticate: ?
googlesitekit_setup: ?
googlesitekit_view_posts_insights: ?
googlesitekit_view_dashboard: ?
googlesitekit_manage_options: ?
googlesitekit_update_plugins: ?
googlesitekit_view_splash: ?
googlesitekit_view_authenticated_dashboard: ?
googlesitekit_view_wp_dashboard_widget: ?
googlesitekit_view_admin_bar_menu: ?
googlesitekit_view_shared_dashboard: ?
googlesitekit_read_shared_module_data::["search-console"]: ?
googlesitekit_read_shared_module_data::["analytics-4"]: ?
googlesitekit_read_shared_module_data::["pagespeed-insights"]: ?
googlesitekit_manage_module_sharing_options::["search-console"]: ?
googlesitekit_manage_module_sharing_options::["analytics-4"]: ?
googlesitekit_manage_module_sharing_options::["pagespeed-insights"]: ?
googlesitekit_delegate_module_sharing_management::["search-console"]: ?
googlesitekit_delegate_module_sharing_management::["analytics-4"]: ?
googlesitekit_delegate_module_sharing_management::["pagespeed-insights"]: ?
enabled_features:
gm3Components: ?
keyMetrics: ?
search-console_shared_roles: none
search-console_management: owner
analytics-4_shared_roles: none
analytics-4_management: owner
pagespeed-insights_shared_roles: none
pagespeed-insights_management: all_admins
search_console_property: https://theotheroperation.com/
analytics_account_id: 1756?????
analytics_property_id: none
analytics_profile_id: none
analytics_use_snippet: yes
analytics_4_property_id: 2799770??
analytics_4_web_data_stream_id: 2708??????
analytics_4_measurement_id: G-02????????
analytics_4_use_snippet: yes
analytics_4_available_custom_dimensions: noneThanks for the update @justinhill001. Just to confirm, you’re not seeing any data on analytics.google.com for G-02S181GG2H, which is the currently connected Google Analytics property? If so, then this is normal that no data will appear within the Site Kit dashboard, as the plugin pulls this information from a users Google Analytics account.
As to why site visits are not being tracked to your site at present, to troubleshoot this further, can you temporarily deactivate your Async JavaScript, Flying Scripts, Jetpack Boost, W3 Total Cache and Rapid Load plugins and let me know once done? I will then check your site and see if my site visits are recording, using the tagassistant.google.com service.
I ask as it looks like the standard Site Kit placed snippet has been modified and doesn’t seem to be tracking, likely as a result of a configuration or conflict between your optimization plugins.
That’s correct. The issue is no tracking being sent to Google Analytics.
I have temporarily deactivated the plugins you’ve mentioned. Let me know as soon as I can re-activate them…
Thanks for that @justinhill001. I can confirm all is working as expected with the Site Kit placed snippet now (see screenshot of confirmation).
As it looks like you have multiple optimization plugins, it’s very possible that one configuration, or a conflict between these plugins, is resulting in the non tracking for visitors based on a modification to how the snippet is placed and how it operates.
While you’re enabling the other plugins, I would suggest doing so one by one, checking for tracking each time, using the tagassistant.google.com service.
Let me know if you have any questions with the above.
Thank you! I will do as you suggest.
James,
I reactivated everything, one by one, testing as I went. Interestingly it’s working fine now with all those plugins re-activated. Fingers crossed all will be well. Pagespeed is more or less back to where it was before I disabled those plugs.
Thank you very much for your help with this!
No problem at all, happy to assist. And great that it remains tracking with the plugins activated once more. Do keep an eye out on it, and get in touch if you have any further queries. Thank you!
I spoke too soon. A few hours later, the tags stopped firing again. Deactivating RapidLoad fixes it.
I suppose the delay before it fails is something to do with caching and CDN.
RapidLoad’s settings allow me to enter javascripts to be excluded from delaying and/or deferring and/or optimisation altogether and I want to try excluding whatever the Google tag files are from optimisation. Can you tell me the file name(s) I need to enter in that field? Is it just ‘gtag.js’?
- This reply was modified 10 months, 2 weeks ago by justinhill001.
Sorry to hear that @justinhill001, but great that you were able to determine the cause.
In relation to any defer or optimization setting, I don’t recommend doing so for Analytics code snippets, as it can impact reporting. While I didn’t test RapidLoad at this stage, I will do so today and check for exclusion options. From reviewing the plugin description it looks like exclusions can be applied.
I’ll report back to you today after testing this. You may also wish to apply a path exclusion (
/wp-content/plugins/google-site-kit/
) or specifically Site Kit JavaScript assets via/wp-content/plugins/google-site-kit/dist/assets/js/(.*).js
Let me know if you have any questions with the above in the meantime.
Thanks James. I’ve added /wp-content/plugins/google-site-kit/dist/assets/js/(.*).js to RapidLoad’s exclusion list. I’ll see how things go.
I’ve also discarded the Flying Scripts plugin. It was added by my hosting provider (WPX) during an optimisation but as far as I can see its functionality is duplicated by RapidLoad. RapidLoad does wonders for my PageSpeed and I can’t live without it.
Certainly do let me know how it goes with the changes you made. I’ve reopened this support topic in the meantime.
Note also that I installed RapidLoad and many of the optimizations are limited in the free version. I can confirm that with the default settings of the free version that the Google Analytics snippet as placed via Site Kit does not function as expected, with the snippets not placed.
You may wish to reach out to the RadpidLoad support team for further assistance if the exclusions suggested don’t work with your verion.
James,
I have the paid version. I did raise a support case with RapidLoad, and they told me to add the Site Kit scripts to the exclusion list (but of course they couldn’t tell me what they actually were).
I will certainly confirm to them your comment that the default settings of the free version do interfere with Site Kit.
Just to close this out – I can confirm that Site Kit is still working and transmitting data some hours after setting the exclusion I mentioned above. Problem solved, and worth noting for other users of Site kit and RapidLoad.
Excellent! Thanks for the update based on your testing of the pro version. And glad to hear all is now working as expected. If you run into any further errors or if you have any Site Kit related queries, be sure to get in touch. If you have a moment free please also consider sharing your thoughts on the plugin.
- The topic ‘Switched to Google Site Kit, now analytics no longer working’ is closed to new replies.