Site Kit by Google – Analytics, Search Console, AdSense, Speed

描述

Site Kit 是 Google 的官方 WordPress 插件,用于分析人们如何找到和使用您的站点。Site Kit 是一种一站式解决方案,用于部署、管理和从关键的 Google 工具中获得数据,使站点在网络上取得成功。其直接在 WordPress 仪表盘中提供来自多个 Google 产品的权威、最新的数据,便于访问,且完全免费。

带来最好的工具给WordPress

Site Kit包括使用这些Google产品无缝和灵活的强大功能:

  • 易于理解的统计直接在Wordpress仪表板上
  • 来自多个Google Tools的官方统计数据,全部在一个仪表板中
  • 无需编辑您网站的源代码“无需编辑多个Google工具的快速设置
  • 您的整个网站和个人帖子的指标
  • 跨WordPress和不同的Google产品易于管理,粒度权限

支持的Google工具

Site Kit 显示关键指标和见解来自不同Google产品的:

  • Search Console:了解Google搜索如何发现并在Google搜索中显示页面。 跟踪搜索结果中有多少人看到您的网站,以及他们用于搜索您的网站的查询。
  • Analytics: 探索用户如何导航您的网站和跟踪您为用户完成的目标。
  • AdSense:跟踪您的网站赚多少钱。
  • PageSpeed Insights: 了解与其他现实世界的页面相比如何执行。 从Pagespeed Insights中提高可操作提示的性能。
  • Tag Manager: 使用 Site Kit 来轻松的设置 Tag Manager- 无需代码. 然后在Tag Manager中管理你的标签.
  • 优化:使用Site Kit,以轻松设置优化 – 无需代码编辑。 然后,在优化中设置A / B测试。

安装

注意:”请确保您的网站已经上线。如果您的网站还未上线,则 Site Kit 将无法向您显示任何数据。
但如果您在生产站点之外还有一个临时环境,Site Kit 可以在临时环境中显示生产站点的数据。了解如何使用Site Kit与临时环境

从WordPress内安装

  1. 访问插件 > 添加新的
  2. 搜索 Site Kit by Google
  3. 通过Google插件安装并激活网站套件
  4. 将 Site Kit 连接到您的 Google 账号。如果有多个 WordPress 管理员,请记住每个管理员必须连接其自己的 Google 账号才能访问该插件。

手动安装

  1. 将整个google-site-kit文件夹上传到/wp-content/plugins/目录。
  2. 访问插件
  3. 启用 Site Kit by Google plugin。
  4. 将 Site Kit 连接到您的 Google 账号。如果有多个 WordPress 管理员,请记住每个管理员必须连接其自己的 Google 账号才能访问该插件。

启用后

  1. 访问新的Site Kit菜单。
  2. 遵循配置流程中的指示。
  3. 转到主站点 Site Kit,该仪表板已从 Search Console 台显示密钥指标。
  4. Site Kit Settings 下连接其他 Google 工具。 详细了解哪些工具适合您

常见问题

欲了解更多信息,请访问Site Kit 官方网站

Site Kit 是免费的吗?

Site Kit 插件是免费且开源的,并将继续如此。Site Kit 中包含的个别 Google 产品须遵守这些产品的标准条款和费用(如果有)。

What are the minimum requirements for Site Kit?

In order to successfully install and use Site Kit, your site must meet the following requirements:

  • WordPress version 4.7+
  • PHP version 5.6+
  • Modern browser – Internet Explorer is not supported
  • Is publicly accessible – it isn’t in maintenance mode, accessible only via password, or otherwise blocked
  • REST API is available – Site Kit must be able to communicate via REST API with Google services. To ensure that the REST API is available for your site, go to Tools > Site Health.

Why is my dashboard showing “gathering data” and none of my service data?

It can take a few days after connecting Site Kit to a Google service for data to begin to display in your dashboard. The “gathering data” message typically appears when you’ve recently set up a Google service (i.e. just created a new Analytics account) and/or your site is new, and data is not yet available for display.

If you are still seeing this message after a few days, feel free to get in touch with us on the support forum.

Why aren’t any ads appearing on my site after I connected AdSense?

If you’re new to AdSense when you connect via Site Kit, your new AdSense account and your site will need to be manually reviewed and approved for ads by the AdSense team. Ads will not display until your account and site have been approved. Check out this guide for more information about the approval process and timeline.

You can check your approval status in Site Kit by going to Settings > Connected Services > AdSense and clicking “Check your site status.” This link will direct you to AdSense. If you see “Ready,” your account and site have been approved and should be displaying ads. If you see “Getting ready…,” your account and site are still under review and your site will not display ads until they have been approved.

If the AdSense snippet is successfully embedded on your site and your account and site have been approved, but your site is still not showing ads, contact the AdSense Help Center for assistance.

Is Site Kit GDPR compliant?

When using Site Kit, site owners are responsible for managing notice and consent requirements – including GDPR requirements – as described in Google’s Terms of Service.

By default, Site Kit does anonymize IP addresses upon activation of the Google Analytics module. In addition, Site Kit provides a mechanism in the form of a simple API for cookie consent plugins to integrate with Site Kit and prevent Site Kit’s Google service snippets from being rendered on a page if the user has not granted consent. More information about how this API works is available in this GitHub issue.

Where can I get additional support?

Please create a new topic on our WordPress.org support forum. Be sure to follow the support forum guidelines when posting.

评价

2021年9月14日
When creating user accounts for our clients, we almost never provide an admin account out of security concern. Site Kit has a cool dashboard that our client will never see because of this policy. Google has been mum about it for a long while so if this is in your desired functionality, look elsewhere. However, it does a great job of connecting all the Google things.
2021年9月13日
I had been using Site Kit on a number of client sites for years when I had an issue properly connecting Site Kit to the correct Google Analytics account from a production site after I migrated the site from a development environment. I opened a support ticket on the WordPress plugin repo and got a very helpful reply very quickly. The Google Support Team did a great job. I was very impressed.
2021年9月13日
It is easy to set-up. I found the instructions easy to follow. Love it.
阅读所有387条评价

贡献者及开发者

“Site Kit by Google – Analytics, Search Console, AdSense, Speed” 是开源软件。 以下人员对此插件做出了贡献。

贡献者

“Site Kit by Google – Analytics, Search Console, AdSense, Speed”插件已被翻译至22种本地话语言。 感谢所有译者为本插件所做的贡献。

将“Site Kit by Google – Analytics, Search Console, AdSense, Speed”翻译成您的语言。

对开发感兴趣吗?

您可以浏览代码,查看SVN仓库,或通过RSS订阅开发日志

更新日志

1.41.0

Enhanced

  • Update the Idea_Hub class to invalidate cached ideas when an idea is modified or a new post is created. See #3922.
  • Update the Idea Hub notification text. See #3912.
  • Update WP dashboard Idea Hub CTA design and language. See #3911.
  • Update descriptions for Idea Hub module and widget. See #3908.
  • Add tooltips for action buttons in the Idea Hub dashboard widget. See #3906.
  • Improve pagination behaviour in Idea Hub. See #3859.
  • Add “Experimental” badge to Idea Hub UI. See #3810.
  • Scaffold Subscribe with Google module. See #3808.
  • Update AdSense tag code to improve Ad performance. See #3783.
  • Improve AdSense graphs on mobile screens. See #3317.
  • Update GA measurement opt-out mechanism for logged-in users to be property-specific. See #3294.
  • Improve UX to close tooltips within charts. See #2659.
  • Add surrounding comments to all HTML tags output by Site Kit modules. See #1504.
  • Add link to Settings page in plugin action links on plugins page. See #1194.

Fixed

  • Fix counts on Idea Hub widget tab labels to only show up if greater than zero. See #3964.
  • Always load Google fonts using purely CSS rather than relying on a JavaScript snippet. See #3932.
  • Fix Dashboard Search Widget zero state bug. See #3880.
  • Fix Admin Bar Analytics link when using Twenty Twenty-One theme. See #3849.
  • Ensure the icon buttons in the Idea Hub widget do not overlap idea labels. See #3839.
  • Fix “Connected” messages to avoid duplicate words for screen reader. See #3763.
  • Fix a potential error due to report data associated with an invalid URL. See #3752.
  • Update the AdSense setup CTA in the activation success banner to be disabled when an ad-blocker is detected. See #3721.
  • Update Analytics goals widget CTA link to open in a new window. See #3683.
  • Fix UI bugs in User Input’s fifth question. See #3682.
  • Fix potential error in older browsers that don’t support IntersectionObserver. See #3278.

1.40.0

Enhanced

  • Show correct footer information based on Idea Hub tab. See #3865.
  • Update styles of the topic idea element to have a light-blue background. See #3857.
  • Update position of action buttons for ideas in Idea Hub dashboard widget in mobile. See #3855.
  • Update CTA language for WP post list notifications. See #3852.
  • Update the number of ideas shown per page on the Idea Hub dashboard widget. See #3843.
  • Update language in Idea Hub feature tour to use en-US locale for consistency. See #3834.
  • Update the IdeaHub widget to display the “Updated every 2-3 days” message only for the new ideas tab. See #3832.
  • Add an open text type to user surveys. See #3762.
  • Add multiple choice selection questions to User Input surveys. See #3761.
  • Add a new “single select” option to User Input Surveys. See #3760.
  • Implement functionality for saving and dismissing an Idea Hub idea. See #3747.
  • Remove unused legacy JS code after removal of legacy components and data API. See #3646.
  • Add feature tour for Idea Hub drafts to the post list table in WP admin. See #3625.
  • Update Idea Hub to use the production API. See #3518.
  • Update viewport icons used in PageSpeed Insights widget. See #3162.
  • Add a notice to Optimize users warning them that Analytics requests are not being tracked for signed-in users. See #3000.
  • Add Tag Manager AMP tag support for Web Stories. See #2070.

Fixed

  • Fix Idea Hub tab localization text. See #3899.
  • Fix pagination in the Idea Hub dashboard widget to disable next button on last page. See #3866.
  • Fix Idea Hub CTA for saved ideas on the WordPress dashboard to only show if the user has any saved ideas. See #3845.
  • Update Sidekick zero state graphics with proper files. See #3840.
  • Fix Idea Hub dashboard widget pagination controls from stacking in small viewports. See #3838.
  • Fix Idea Hub Tour Activation bug. See #3836.
  • Update Idea Hub new, saved, and draft ideas requests to invalidate the cache when a post created for an idea changes its status. See #3757.
  • Fix a bug where Site Kit did not disable Tag Manager tag when an existing tag was detected. See #3338.

1.39.0

Enhanced

  • Update the Idea Hub widget to display its footer in the Widget.Footer prop. See #3773.
  • Add and update deep links on Analytics settings view to edit the UA property view and GA4 measurement ID. See #3702.
  • Decouple Google API client creation logic from main OAuth client tied to the current WordPress user. See #3658.
  • Remove server-side REST batch data infrastructure. See #3644.
  • Add option to insert the Anti Flicker snippet when connecting Optimize. See #3013.
  • Add method for disabling auto-ads for logged-in users. See #2681.
  • Remove legacy data API code. See #2258.
  • Update Google fonts loaded by Site Kit to be filterable. Props lkraav. See #1703.
  • Add a toggle to enable/disable the Site Kit admin bar feature. See #990.
  • Add filters to allow modifications on the AdSense code. Props Fu-San. See #336.

Fixed

  • Consolidate blue colors in notice text. See #3716.
  • Improve module disconnect screen when a module doesn’t have listed features. See #3691.
  • Fix potential “Cannot read property ‘slug’ of undefined” error on Site Kit screens. See #3618.

1.38.1

Fixed

  • Fix fatal error that could be triggered by other plugins or themes using an unprefixed version of Composer. See #3830.

1.38.0

Enhanced

  • Improve the tab-switching UX in the Idea Hub dashboard widget. See #3723.
  • Add feature description to Idea Hub module. See #3692.
  • Ensure Idea Hub draft posts are properly labelled even when Idea Hub is disconnected. See #3639.
  • Update Google PHP client services library to latest version. See #3628.
  • Update language on initial setup screen. See #3581.
  • Add a new feature tour for the Idea Hub widget. See #3524.
  • Add Idea Hub dashboard notification to inform users about new Idea Hub module. See #3523.
  • Add the Idea Hub notice to the posts list table. See #3359.
  • Enhance Google API client with user-specific quota token to differentiate quota usage between users. See #2217.
  • Remove weekday alignment functionality for previous period from Analytics module and Site Kit entirely. See #2122.
  • Update module page dashboards to use Widget API unconditionally and remove legacy implementations. See #2077.
  • Add a new tag guard that prevents rendering tags for non-production environments. Props lukecav. See #2054.
  • Update dashboard and details page to display widgets only. See #1997.
  • Improve WordPress dashboard widget UX so that only one CTA per module is displayed when the module has no data or needs to be activated. See #1147.
  • Update copy in AdSense disconnect modal. See #683.

Fixed

  • Fix possible JavaScript error related to certain Google charts not rendering properly in Safari. See #3784.
  • Fix bug in Idea Hub dashboard widget that caused drafts not to refresh. See #3733.
  • Ensure the “Edit” mode for modules without a dedicated “Edit” UI for their settings can still be exited, and fall back to showing the regular “View” UI in those cases. See #3727.
  • Improve Widget layout when dismissing the Idea Hub call-to-action. See #3722.
  • Fix Idea Hub draft post links ampersand output. See #3708.
  • Update stats graphs not to duplicate dates when 7 days period is selected. See #3643.
  • Add a timeout to delay caching the survey by 30 seconds. See #3633.
  • Fix bug where the filter behavior used for Analytics and AdSense report data was not working for sites with a unicode or punycode domain. Props HFigarella. See #3606.
  • Fix a bug in Analytics setup where a matching secondary property would not be automatically selected when the primary property was changed. See #3549.
  • Improve display of long names in select dropdowns. See #3497.
  • Update settings to redirect back to the settings page after disconnecting a module. See #3393.
  • Prevent rendering errors when the Admin Menu has been customized. See #3263.
  • Fix admin bar styles conflict with W3 Total Cache Minify functionality. See #1427.

1.37.0

Enhanced

  • Update wording in permissions modal when GA4 needs to create a web data stream for the selected property. See #3622.
  • Add a new “Verification Status” row to the Site Health information for Site Kit. See #3621.
  • Show information notice about associated UA / GA4 property only once a property has been selected. See #3614.
  • Update styles of controls in the GA4 notice box on the settings page. See #3541.
  • Add selected state of 300ms to user feedback survey. See #3531.
  • Add Idea Hub setup UI. See #3522.
  • Implement Idea Hub widget functionality for saving and unsaving an idea. See #3519.
  • Add loading indicator to the Idea Hub widget when a new draft is being created. See #3387.
  • Allow Idea Hub CTA to be dismissed. See #3360.
  • Add the Idea Hub notification to the WordPress block editor. See #3272.
  • Refactor settings tabs with React Router and update URL hashes with more user-friendly names. See #2514.

Fixed

  • Fix bug in new React Router-based Settings Screen. See #3707.
  • Fix potential Uncaught (in promise) TypeError: Cannot read property 'replace' of undefined related to GA4 property matching logic. See #3706.
  • Fix message for AdSense account with no data in new widget-based screen. See #3667.
  • Fix a bug in Idea Hub where the most recent draft idea posts were not shown after creating a new draft from idea. See #3660.
  • Add a configurable timeout to User Survey components. See #3655.
  • Fix issue with Google Charts showing negative labels in some charts. See #3564.
  • Improve User Input tag creation on Mobile Safari. See #3420.
  • Fix global storybook padding issues. See #3174.

1.36.0

Enhanced

  • Enhance experience for sites with UA Analytics already configured before GA4 is enabled. See #3586.
  • Implement Idea Hub datastore infrastructure for saving and dismissing an idea. See #3556.
  • Display measurement ID for Google Analytics 4 property in Settings. See #3545.
  • Update text in some Google Analytics 4 notices. See #3544.
  • Show separate UA and GA4 snippet toggles in Analytics Settings. See #3542.
  • Improve Google Analytics 4 notices. See #3540.
  • Improve user survey styling on mobile viewports. See #3530.
  • Show Terms of Service and Privacy Policy in User Feedback survey if the user hasn’t opted-in to tracking. See #3528.
  • Implement a minimal settings panel for the Idea Hub module. See #3521.
  • Update API client library and AdSense integration to use the new version 2 of their API. See #3517.
  • Improve button tooltips across plugin. See #3516.
  • Update button links to show “opens in new tab” ARIA help text, and open all User Feedback links in a new tab. See #3510.
  • Don’t show notifications if a user survey has already been displayed. See #3508.
  • Display date range for data in the Admin Bar. See #3202.
  • Remove the option to include/exclude logged-in users when the Analytics snippet is not placed via Site Kit. See #2910.
  • Update error message shown to AMP users when connecting Tag Manager after Analytics. See #2292.

Fixed

  • Fix potential React error when using Google Translate and then changing the date range in a Site Kit admin screen. See #3636.
  • Fix a bug where GA4 settings were not cleared when deactivating Analytics. See #3616.
  • Fix AMP validation error caused by the GA opt-out snippet conditionally placed by Site Kit. See #3572.
  • Ensure account and property are preselected during setup when user has a matching GA4 property only. See #3543.
  • Update Analytics account creation to ensure a GA4 property is always created when GA4 is enabled. See #3539.
  • Fix an infinite loading state when attempting to create a new Analytics account with GA4. See #3537.
  • Only show a GA4 creation notice once an account is selected in Analytics setup. See #3536.
  • Allow posts with Idea Hub drafts to be trashed. See #3514.
  • Enhance user survey display with added animation on enter and exit. See #3509.
  • Fix a bug related to localized number formatting for browsers that have limited support for formatting options. See #3255.
  • Improve table views on mobile screens. See #3138.
  • Fix bug where AMP mode detection would not consider the AMP plugin’s template mode setting when the Web Stories plugin is active. See #2998.

1.35.0

Enhanced

  • Update shadow used by user surveys to enhance contrast and improve visibility. See #3529.
  • Make text casing in User Feedback and Idea Hub buttons consistent with the rest of the plugin. See #3507.
  • Add React components for rendering and managing user surveys. See #3380.
  • Add React components for rendering user survey UI. See #3379.
  • Add React component for triggering a user survey on view. See #3376.
  • Implement a component to render the current survey. See #3375.
  • Add REST routes for user survey endpoints. See #3374.
  • Add Idea Hub widget support for creating idea draft posts. See #3357.
  • Add support for Google Analytics 4 tags in the notices for existing Google Analytics tags in the Analytics setup. See #3289.
  • Added GA4 script tag detection. See #3288.
  • Add a module activation CTA for Idea Hub to the Site Kit dashboard. See #3275.
  • Show GA4 property in Analytics Settings when available. See #3254.
  • Update Analytics account provisioning screen to inform about GA4 property creation. See #3253.
  • Update Analytics account provisioning to create a corresponding GA4 property as well. See #3252.
  • Added a UI to manage Analytics Accounts with both Universal Analytics and GA4 properties. See #3250.
  • Add setup variant for Analytics accounts with only GA4 properties. See #3249.
  • Fix a bug where Google API requests would be made when necessary scopes were not granted. See #3227.
  • Improve the AdSense AdBlocker check. See #2749.
  • Enable Prefetch DNS Requests on external Google services used by Site Kit. Props glanglois. See #2203.

Changed

  • Limit effective values for Google proxy base URL. See #3217.

Fixed

  • Fix a React console error when viewing widget-based module screens. See #3559.
  • Fix a problem where GA4 property selection is not preserved after granting additional scopes. See #3550.
  • 修复了当所选帐户具有不同 URL 的 UA 和 GA4 属性时无法保存 Analytics 设置的问题。请参阅#3538.
  • 更新所有交通小部件图例切片标签以使用标题大小写。请参阅#3327.
  • 优化”确认更改”的行为按钮在搜索控制台的设置中被加载的情况。查看#3318.
  • 修复了 AMP 阅读器模式下 AdSense 代码段的输出。请参阅#3218.
  • 更新charts用于在模块之间使用统一的风格。查看#3083.

1.34.1

Fixed

  • 修复一个问题用于某些主机以及这里的Analytics账户的请求,或者其他被格挡的域名权限。查看#3532

1.34.0

Enhanced

  • 将Idea Hub通知添加到WP仪表板小部件,查看#3358
  • 核心/用户 数据存储添加初始操作和选择器以处理用户调查。 查看#3355.
  • 在选择 Analytics 帐户时,增强默认 Analytics 属性。 查看 #3291.
  • 激活GA4支持时,更新分析模块的成功通知。 查看 #3290
  • 更新Analytics安装程序以基于当前站点URL预选择GA4属性。 查看 #3286.
  • 在IDEA HUB窗口小部件中实现IDEA列表选项卡和基本交互。 查看 #3276.
  • 添加Idea Hub 上下文用于生成的帖子中添加想Idea Hub用于草稿通过Idea Hub。 查看 #3271.
  • 添加选择器以获取使用 Idea Hub 想法创建的草稿和发布的帖子。 查看#3270.
  • 添加Idea Hub 草稿文章支持,查看 #3269.
  • 添加Analytics属性选择组件,用于显示所有UA和GA4属性。 查看 #3246.
  • 仅显示Google Analytics属性和个人资料选择,如果父(帐户/属性)有效。 查看#3243
  • 为手动用户输入响应的长度添加高边界。 查看#3229
  • 如果区域中的所有小部件具有相同的特殊状态,增强窗口小部件将组合成一个小部件。 查看#3225
  • 更新用于匿名使用匿名跟踪复选框标签使用。 查看 #1238.

Fixed

  • 修复基于小部件的单个URL屏幕的回归将为WordPress站点中未找到的内容完全清空。 查看#3493
  • 修复潜在的 dateRangeLength 必须是正整数的问题Search Console 报告的错误,其中缺少日期。 查看#3418

1.33.0

Enhanced

  • 更新 amp-dalictics 标记要在提供时包括ADS转换ID的配置。 查看 #3282.
  • 为Idea Hub 的想法添加初始化控件. 查看#3274
  • 添加IDEA HUB JS模块 (仅与IDEA HUB功能标志有效). 查看#3273.
  • 更新Analytics设置窗体UI以支持设置流的不同变体。 查看 #3247.
  • 更新 Analytics数据存储设定 提交改变 启用时,基础架构包括GA4。 查看#3245.
  • 将更改验证逻辑添加到Google Analytics 4数据存储。 查看 #3244
  • 添加选择器以检查哪个Google Analytics UI应该是活动的。 查看#3170.
  • 添加选择器来从网页数据流内容选择GA4属性。查看#3168.
  • 添加Idea Hub 来保存idea selectors 以及 actions. 查看 #3156.
  • 介绍PHP类用于在Site Kit 中建模文章元数据 #3154.
  • 迁移所有的组件用于使用GoogleChart 组件的新版本. 查看 See #2887.
  • 澄清用户输入对网站其他用户的潜在影响的解释。 查看#2853.
  • 添加能够排除可以使用Google Analytics跟踪帖子的用户。 Props scottshefler。 查看 #1891.

Fixed

  • 修复潜力 无法定义的"click"属性 js错误的属性’clicks’错误,当返回不均匀的搜索控制台报告行时可能发生的错误。 查看 #3348.
  • 修复了一个错误,其中 Analytics 报告数据对于90天日期范围不完整,当时还请求对基于小部件的模块仪表板的上一段的数据进行数据时。 查看#3232.
  • 在整个插件中标准化标点符号和各种句子和短语的格式。 看 #2597.

1.32.0

Enhanced

  • 更新Analytics的属性选择选项来展示属性的IDs在额外给到名称。查看#3164.
  • 允许管理员在分析设置中粘贴Google广告转换ID,以便将其集成到Site Kit的 Analysis 设定中。 查看 #3161.
  • 手脚架 new modules/idea-hub 数据存储在 JS. See #3152.
  • 手脚架 new Idea_Hub PHP 类. See #3150.
  • 将选择器添加到 核心/站点 数据存储区以检查给定的URL是否与站点的参考URL匹配。 查看 #3105.
  • 实现数据存储选择器,用于一次为多个属性ID选择GA4 Web数据流。 查看 #3104.
  • 添加数据存储选择器并将REST DataPoint匹配到GA4模块以检索帐户摘要。 看 #3103.
  • 更新AdSense 小结面板空间用于展示每一个相关指标的改变价值。查看 #3091.
  • 更新在Site Kit 头部的打开菜单按钮的背景颜色。查看 #3069.
  • 允许网站套件生成器元标签进行编程修改。 查看 #938.
  • 用相关货币澄清一些Adsense标签并格式化顶级赚取页面表中的变现价值。 查看 #656.
  • 更新分析模块仪表板上的流行页面列表,以与主站点套件和WordPress仪表板上的相同组件一致。 查看 #98.

Fixed

  • 修复回归在成功通知中跳转到Pagespeed Insights小部件的跳转链接不再有效。 查看#3310.
  • 更新AdSense “最近一些天的页面的性能” 深度链接以包含日期范围。 查看 #2951.
  • 修复一个错误,可能导致在检测到现有标签时在Analytics设置中选择要选择的第一个配置文件。 查看 #2888
  • 修复用户输入设置流辅助功能。 查看#2851.
  • 基于子文件夹的安装中的解决分析URL链接问题,查看 #2821.
  • 如果已被认证,将用户从Splash屏幕重定向到仪表板。 查看 #2529.
  • 解决某些网站语言的AdSense仪表板上的语言问题。 查看 #2105.

1.31.0

Enhanced

  • 添加方法以获取Site Kit 使用的所有基本功能列表。 Props JoryHogeveen。 查看#3130.
  • 更新控件header风格用于使用网格概念来代替静态的边距。查看#3119.
  • 实施用于在前端呈现 GA4 代码段的技术基础架构,包括支持与 UA 代码段集成的双重标记。请参阅#3106
  • 实现REST 数据点以及JS 数据存储选择器用于通过ID锁定单个的GA4资产。查看#3102.
  • 重命名 “Populartiy” / “Top Queries” 章节到 “Acquisition” 用于新的基于UI的控件。
    查看 #3065.
  • 提升风格用于Site Kit header,特别是在手机设备中。查看#3058
  • 更新保留额外的链接在widgets的模块页面用于包括正确的日期范围参数。查看 #3042
  • 提高分析性质匹配的速度和可靠性, 查看 #3012
  • 添加占位符给所有的”Other” 文字输入字段在用户输入流中。查看 #2993.
  • 实现数据存储选择器以检测GA4属性是否具有与当前站点匹配的Web数据流。 查看#2981.
  • 使用操作和选择器更新 Modules/Analytics-4 存储,用于创建和查询Web数据流。 看 #2980.
  • 实现JS Data Store Infrastructure以查询和创建GA4属性。 查看 #2979.
  • 为即将到来的GA4集成介绍新的JS资产。 查看#2977.
  • 将JS Data Store Modules/Analytics-4 作为即将到来的GA4集成的基础架构。 查看#2976.
  • 允许修改模块的设置面板中的活动搜索控制台属性,例如,当站点具有多种适用的属性时,相关。 查看 #2937.
  • 修复可访问性问题,在不可能使用键盘删除用户输入搜索项。 查看#2900.
  • 更新用户输入样式以修复小型设备上的视觉问题。 查看 #2886.
  • 迁移AdSense模块页面 “Top earning pages” 窗口小部件以使用窗口小部件API。 查看 #2066.

Fixed

  • 更新不同的访问者空间来展示来自搜索用户的实际数量
    #3064.
  • 通过有基于空间的控制板来修复空间问题,以及由于一些空的容器破坏的网格布局。查看#3062.
  • 更新Site Kit 部件来经常返回他们的内容并且包裹在Widget.查看 #3060.
  • 更新AdSense仪表板小部件以渲染AD阻止警告框。 查看 #3011.
  • 当有零数据时,修复数据块元素的断开对齐。 查看 #2992.
  • 在只有单个切片时修复所有流量小部件的饼图上的UI问题。 查看 #2991.
  • 修复Analytics模块页面上的新小部件中的Analytics链接,以考虑选定的日子。 查看 #2983.
  • 修复一个错误,其中可以由站点套件标题部分覆盖的选择菜单组件,使某些项目无法获取。 查看 #2885.
  • 提高潜在慢速数据库查询的性能,以从旧版网站套件中迁移用户数据。 查看 #2870.
  • 在WordPress设置中使用Camelcase URL时,请使用AdSense现有站点检测解决问题。 查看#2695.
  • 修复使用Google翻译已转换管理页时显示的JavaScript问题。 查看 #2280

1.30.0

Enhanced

  • 添加跟踪事件用于帮助可见性的菜单链接。查看#3027.
  • 手脚架 analytics-4 模块PHP类。查看#2974.
  • 当禁用AdSense 代码片段,澄清警告文字的信息。查看 #2962.
  • 介绍隐藏的标签用于搜索条目字段给用户输入设置流程。查看 #2901.
  • 修复用户输入流中关键字气泡的低对比度颜色。请参阅#2896
  • 当仍然需要在已经进行身份验证后授予附加范围时,确保用户未发送到用户输入流量,即使仍然需要提交用户输入响应。 查看#2874.
  • 更新资产跨域了带有新的品牌插画的插件。查看#2616.
  • 包括按钮重置WordPress中的“可用工具”下的站点套件,作为重置插件数据的方式。 当目前没有连接时。 查看#2384.
  • 更新模块设置以使用用于活动和非活动模块的单独组件。 查看#2184.
  • 提升预制设置的兼容性来检查正确性警告如果REST API 已经禁用而不是用意外错误失败。查看#2101.
  • 迁移Analytics块Page Top获取通道窗口小部件使用窗口小部件API。 查看#2069.
  • 迁移 Analytics模块页面流行的页面窗口小部件使用窗口小部件API。 查看#2068
  • 迁移Analytics模块页面概述窗口小部件以使用窗口小部件API。 查看#2067 .
  • 迁移AdSense 模块页面一览空间来使用Widget API,查看 #2065.
  • 迁移Search Console 模块页面流行的关键字widget用于使用Widget API。查看#2064.
  • 迁移Search Console 模块页面一栏widget 来使用Widget API.查看 #2063.

Fixed

  • 通过锁定特定版本来修复由于新版本的 Google 图表库发布而导致的严重 JS 错误。请参阅#3132
  • 修复回归,这里的模型可能会有一些在插件设置屏幕中有一些不正确的排序。查看#3093.
  • 使用标题中的帮助可见性图标修复错误,在某些情况下单击它不会触发菜单打开,并且还解决了一些视觉设计问题。请参阅#3026
  • 修复了在GooDaddy CDN 启用在站点时的Ad Blocker 侦测问题。查看#3018.
  • 确保改变站点URL 在HTTP 以及HTTPS 或者www. 以及无www.不会影响Analytics 以及AdSense 控件的结果。查看 #3005.
  • 修复了当前代码块中存在的Analytics代码块能被替代的问题。请查看 #2909.
  • 确保AdSense 代码片段不会包含在404页面的前端页面中。查看 #2784.

1.29.0

Enhanced

  • 如果整个站点上有多个授权用户,则仅显示有关影响站点其他用户的用户输入问题的通知。请参阅 #2852
  • 引入新的contextual来帮助在Site Kit header 栏以及授权服务。查看 #2846.
  • 引入tooltip 游览知道给用户,通过新版本的All Traffic Widget. 查看 #2739.
  • 增强的 PreviewBlock JS 组件通过特殊的断点的尺寸来支持。查看#2727.
  • 实现对存储在数据库中的特征游览的持续关闭。请参阅#2650
  • 引入 ReportTable 组件用于展示可重用的数据表格. 查看 #2249.

Fixed

  • 修复 Search Console 模块页面上会话持续时间图表的垂直轴标签,以不混合分钟和小时。请参阅#2967
  • 修复在 WordPress 的登录重定向机制之前触发 OAuth 回调登录,立即失败而不是按预期重定向的问题。请参阅#2935
  • 在为用户输入流程中的问题选择“其他”选项时,确保需要输入文本。请参阅#2907
  • 修复重构的 Analytics 目标小部件行为以匹配旧版本。请参阅#2858
  • 修复了在用户输入流中的问题之间切换没有将问题滚动到视图中的错误。请参阅#2848
  • 在浏览器中临时缓存用户输入响应,直到在用户通过流程时提交,以防止意外丢失输入的数据。请参阅#2844
  • 澄清了最近用户输入关于搜索条目中所出现的一些问题。查看 #2843.
  • 当检查或者没有检查“Other” 选项用于单个问题的用户输入流程的时候,修复一些bug。查看 #2828.

1.28.0

Added

  • 实现React 组件用于渲染提示框导游。查看#2626.

Enhanced

  • 在单选按钮或复选框列表中选择“其他”选项后,自动聚焦“其他”文本输入。请参阅 #2897
  • 更新副本以阐明用户输入流中的多项选择行为。请参阅#2857
  • 更新新版 AdSense 仪表板摘要小部件上的链接,以深层链接到 AdSense 前端中的相应区域。请参阅#2774
  • 在AdSense 报告中深入的链接包含了站点的URL 用于指出适当的报告。查看#2773.
  • 添加支持用于PHP 8 并且确保它能够通过CI进行维护。Props TorbenLundsgaard。查看#2724.
  • googlesitekit_authorize_usergooglesitekit_reauthorize_user 现在不使用身份验证服务流时也会触发操作。查看#2693.
  • 实现用于在 Site Kit 模块屏幕中呈现小部件的基础结构。请参阅#2653
  • 使用可靠且 React 友好的方法来检测小部件是否处于非活动状态且不应呈现。请参阅#2612
  • 增强持续时间格式的本地化。请参阅 #2588
  • 过滤所有的Analytics API 请求用于仅包括当前域名的结果。查看#2554.
  • 完全依赖 SVG 来绘制图形并移除其他图像支持。请参阅 #2468

Fixed

  • 提升 UX 在输入搜索条目中在这些用户的输入流中。查看#2842.
  • 修复多样化的视觉故障在用户输入流小节中查看并且修剪免费的文字内容输入用于任意的”Other” 选项。查看#2837.
  • 改变 preview/next 按钮行为在User Input flow.查看 #2829.
  • 修复AdSense bug 这里的 Ad Client not found 错误会出现在某些案例中,并且是一个代办的状态.查看#2812.
  • 通过实施更全面的广告拦截器检测解决方案,依赖 just-detect-adblock 库,修复了 Site Kit 不再识别 AdGuard 和 uBlock 广告拦截器的错误。 请参阅 #2794
  • 更新在AdSense 模块页面的链接到指向Analytics 这里有更精确的由于一些元数据。查看 #2772.
  • 修复Search Console x-axis 标签在90天图表。查看#2747.
  • 修复带有所有流量饼状图出现的一些问题。请查看 #2660.
  • 修复了以前处理 Analytics 代码时断开跟踪代码管理器模块后不会重新设置 Analytics 代码段放置的问题。请参阅 #2579
  • 修复了在不是站点成员时跟踪选择加入对多站点管理员不起作用的错误。请参阅#2103

1.27.0

Added

  • 给AdSense 自动广告高到Web Stories添加支持,允许选择一个AdSense 广告单元来使用这些结果到一个amp-story-auto-ads 被注入的元素。查看 #2602.

Enhanced

  • 改进提交用户输入设置后确认通知的措辞。请参阅 #2790
  • 允许通过 WP-CLI 重置持久站点工具包选项。请参阅 #2748
  • 显示All Traffic 控件尺寸tab作为一些下拉在窄窗口。查看 #2743.
  • 在 AdSense 深层链接中包含当前日期,以便服务前端显示与 Site Kit 相同的时间段。请参阅 #2689
  • 更新 Google API 客户端库并删除自定义配置以重试失败的 API 请求,因为它现在包含在库本身中。请参阅#2688
  • 引入 WidgetReportError 组件,它应该可以通过控件展示整体错误的一栏。查看 #2670.
  • 实施 REST 数据点和 JS 数据存储基础设施,以获取和取消工具提示导览。请参阅#2648
  • 准备基于 Widget API 的仪表板版本以供启动,呈现包括页眉和页脚在内的整个页面内容。请参阅#2646
  • 添加远程控制启用的功能标志的能力。请参阅#2533
  • 引入core/ui 数据存储用于某些在JS中存储UI的状态。查看 #2456.
  • 包括当前如期在Analytics 深度链接,以便于同时在前端显示Site Kit。查看 #2287.
  • 移除老版本的WP 工具栏widget并且通过Site Kit widget 来覆盖它。查看 #2240.

Fixed

  • 修复了旧的所有流量小部件仍显示在仪表板中单个 URL 的错误。请参阅#2856
  • 修复 PHP 8 已弃用 uasort() 用法的通知。道具 oguilleux。请参阅 #2797
  • 正在进行兼容性检查时重置隐藏的链接,请参阅 #2756.
  • 显示All Traffic饼图的工具提示,当选择切片以允许与工具提示交互,悬停时这是不可能的。查看 #2737.
  • 修复AdSense 工具面板小姐控件用于包含当前日期范围的。数据,迷你图,而不仅仅是当月 1 日的数据。详情请查看 See #2734.
  • 修复了在AdSense流中的视觉bug,切换元素可能会被复选图标标记。查看#2722.
  • 修复了带有Search Console 谋爱页面图形的bug这里有一些重叠的床说可能会在选择超过2个指标的时候选择。查看#2721.
  • 修复了关于All Traffic Pie 表单的多种bug (例如当日期范围被改变的时候有错误的切片被选择,错误的行为不允许”Others” 来进行选择),通过引入新的React-based 图表组件。查看 #2714.
  • 修复了在某些情况下使用之前已存储的相同值更新设置时会显示错误的错误。请参阅#2513
  • 修复了 Analytics 概览图表上跳出率和会话持续时间的 y 轴值的格式。请参阅 #2095

1.26.0

Enhanced

  • 确保“所有流量”小部件中的任何“其他”切片未指示为可选择且无法激活。请参阅#2716
  • 在“所有流量”小部件中查看特定用户细分时,将“所有用户”面包屑设为返回整体用户视图的链接。请参阅#2715
  • 通过使用自定义的实现增强All Traffic 控件饼,以便标签永远不会被切断并包括视觉悬停和活动状态。查看#2700.
  • 显示超过在All Traffic 控件行饼图中2个日期。查看#2699.
  • 包括在Site Health 信息中可行的以及启用的Site Kit 功能。查看 #2662.
  • 重命名 header 以及 footer Widget 的属性组件到 Header 以及 Footer到指定的他们需要的React 组件来代替一个元素。查看#2652.
  • 简化 Widget 的用法,组件因此控件组件可以使用它属性的版本而不是手动的导入它以及重新指定控件后缀。查看 #2613.
  • 在WP 控制面板widget中迁移顶部的内容表格,这些功能的狗子都是基于使用数据存储的钩子。查看 #2610.
  • 将 JS 存储、小部件和模块注册与导入分离,引入专用注册功能。请参阅#2587
  • 删除服务器端 API 请求以确定帖子是否包含 Search Console 或 Analytics 数据,因为它可能会显着减慢 WP 管理员的响应时间。道具archon810。请参阅#2528
  • 当这里没有数据用于更多同意的体验,经常展示Site Kit Admin bar 菜单,有关于可以适用的缺少的数据。请查看#2508.
  • 当点击重置对话框按钮的时候提升UX,保持对话框打开在一个完整的加载状态进程中。查看 #2347.
  • 在 Search Console 深层链接中包含当前日期,以便服务前端显示与 Site Kit 相同的时间段。请参阅#2286.
  • 增强管理栏实施以由 googlesitekit.data 注册表及其商店提供支持。请参阅#2241

Fixed

  • 确保所有流量折线图的 x 轴标签与饼图图例正确对齐。请参阅#2738
  • 当通过Site Kit Dashboard CTA 启用 Analytics模块的时候避免版面。查看#2719.
  • 避免内容切换到All Traffic 控件,由于一些不正确的加载UI 版式。查看#2710.
  • 如果用户之前没有完成设置,则只需要在设置后通过用户输入流程。请参阅 #2603.

1.25.0

Added

  • 在 Site Kit 仪表板中启动新的 All Traffic 小部件,它显示有关渠道的更多详细信息,包括基于时间的图表,并显示访问站点的国家和设备的类似指标。 请参阅#2429

Enhanced

  • 修改新的所有流量小部件的饼图工具提示行为,以便仅在将鼠标悬停在饼图切片上时才显示工具提示。请参阅#2701
  • 分数初始化Site Kit 版本给每一个用户用于更多的目标消息在未来,并且引入googlesitekit_reauthorize_user 操作。查看 #2692.
  • 改进新的所有流量小部件的用户体验,以便在加载时和没有可用相关数据时使用。请参阅#2675
  • 修复移动视口上新的所有流量小部件的布局以使用单列。请参阅#2663
  • 将上下文文档链接添加到新的所有流量小部件以解释特殊维度值“(未设置)”和“(其他)”。请参阅#2642
  • 修改新的所有流量小部件,以便折线图始终使用与当前选定的饼图切片指示的颜色相同的颜色。请参阅#2625
  • 修改新的所有流量小部件中的字体样式,以匹配搜索漏斗小部件和整个插件中其他地方使用的字体样式。请参阅#2623
  • 依靠新的 Search Console“新鲜数据”功能显示最近 1 天前的指标,改进了之前 2 天的偏移量。请参阅#2522
  • 删除 AdSense、Analytics 和 Search Console 模块中的各种旧 REST 数据点,这些数据点仅用于访问特定设置且未使用。请参阅#2507
  • 引入 core/location JS 存储,依靠它进行重定向,并修复有关在 OAuth 重定向之前不必要地出现的不满意范围的通知。请参阅 #2497
  • 摆脱 AdSense 小部件中遗留的 dateRange 参数的剩余使用。请参阅#2477
  • 改进 JS API 缓存层以缓存某些包含 cacheTTL 额外数据属性的错误响应,从而在 AdSense 帐户未链接时避免过多的 Analytics API 请求。 请参阅#2457
  • 通过 googlesitekit_is_feature_enabled 过滤器为动态控制的功能标志引入基础设施。请参阅#2452
  • 实现逻辑以自动组合处于特殊状态的小部件的 UI,例如 没有足够 API 响应数据的小部件,或需要先设置特定模块的小部件。 见 #2252.
  • 为 Site Kit 模块页面添加小部件上下文并注册小部件区域。请参阅#2062

Fixed

  • 修复所有交通小部件 UI 错误,其中饼图工具提示在悬停在它们上方时会闪烁。请参阅#2709
  • 确保所有流量中的折线图与总计数和底部的饼图正确对齐。请参阅#2708
  • 修复由于 core/modules 存储的 getModules 选择器中的问题导致的 Site Kit 屏幕上的性能延迟。请参阅#2691
  • 修复了标签管理器和分析代码段可以在 AMP 页面上插入两次的错误。请参阅#2668
  • 修复了所有流量小部件的错误,当更改当前日期范围时,所选饼图将不再保持选中状态。请参阅#2644
  • 修复所有流量小部件中的图形,以不切断小于桌面的视口上的轴标签。请参阅#2624

1.24.0

Added

  • 为新的 Analytics All Traffic 小部件实施 UserDimensionsPieChart 组件。请参阅#2425
  • 为新的所有流量小部件实现主选项卡 UI。请参阅#2424
  • 为新的 Analytics All Traffic 小部件实施 TotalUserCount 组件。请参阅#2423
  • 为新的 Analytics All Traffic 小部件实施 UserCountGraph 组件。请参阅#2422

Enhanced

  • 在插件的列表条目中添加评论和支持链接。请参阅#2516
  • registerWidgetAreaicon 参数重命名为 Icon 并要求它是 WPComponent(例如 SVG)。请参阅#2505
  • 改进用于修改用户输入设置的 UX,消除在只想更改特定响应时单击后续问题的要求。请参阅 #2499
  • 在新的所有流量小部件中实现动态源链接。请参阅#2428
  • 为新的所有流量小部件添加交互性,以便选择饼图切片根据上下文更新显示的计数和图形。请参阅#2426
  • 添加支持用于在 dimensionFilters 参数到Analytics GET:reportPHP 中的 REST 数据点和 getReport 在JS中的选择器。查看#2421.
  • 增强 whenActive 高阶组件以接受 FallbackComponentIncompleteComponent 道具。请参阅#2381
  • 删除旧版发布者获胜通知。请参阅#2285
  • storeName 参数添加到 core/modules 存储的 registerModule 操作以指定模块的 JS 数据存储的名称。请参阅#2271
  • 将 Search Console API 请求的日期感知移至客户端,从而提供更多上下文日期信息。请参阅#2237
  • 将 Analytics API 请求的日期感知移至客户端,从而提供更多上下文日期信息。请参阅#2236
  • 引入getGoogleSupportURL 选择器到 core/site 存储在JS中。查看 #2221.
  • 添加一个可选的支持 SettingsSetupIncompleteComponent 参数给到 registerModule 驱动 core/modules 商店, 允许开发者注册一个自定义的UI 组件当模块没有完全的链接。查看 #2080.
  • 更新插件的管理栏菜单以依赖使用数据存储的基于功能钩子的组件。请参阅 #2076
  • 更新插件的 WordPress 仪表板小部件,以依赖使用数据存储的基于功能挂钩的组件。
    请参阅 #2075
  • 切换 core/user/data/user-input-settings REST 端点使用远程身份验证服务 API 端点。请参阅 #2048
  • 实现用户输入块以在 Site Kit > Settings > Admin Settings 下编辑响应。请参阅 #2041
  • 引入用于渲染标签的可重用基础设施,依赖于新的 Tag_InterfaceGuard_Interface 接口以及 TagModule_Tag 类, 现在在所有模块中使用。 请参阅#475

Fixed

  • 修复 AdSense 概览图 UI,以便根据需要扩展总数的可用空间。请参阅#2555
  • 阻止对插件未使用身份验证服务的开发站点的远程通知 API 请求。请参阅#2495
  • 修复重置插件数据时触发的 JavaScript 错误。请参阅#2478
  • 更新所有 Analytics 深层链接以使用 getServiceReportURL 选择器来正确编码参数和一致的行为。请参阅 #2405
  • 修复遗留 API 层中处理批处理响应中的错误的错误,这些错误可能导致模块页面上的无限加载状态。请参阅 #2403
  • 改进 Analytics 属性匹配逻辑,以便拥有多个 Analytics 帐户的用户不会遇到用户配额错误。请参阅#2218
  • 引入 numFmt 函数用于集中 Site Kit 特定的数字格式,本地化百分比格式,并修复各种数字格式不一致。 请参阅 #2200

1.23.0

Added

  • Scaffold components for a new version of the Analytics All Traffic widget. See #2392.
  • Display graph with historic AdSense data on module page, showing earnings, RPM, impressions and CTR over time. See #1921.

Enhanced

  • Introduce listFormat function to format entries in a comma-separated list. See #2486.
  • Rename arguments across various datastore actions requiring a WPComponent type to use capitalized names to better indicate a WPComponent (and not a WPElement) is required. See #2413.
  • 改进用户输入提交状态的验证。请参阅#2323
  • 引入 ActivateModuleCTACompleteModuleActivationCTA 组件来集中管理这些场景的 UI。请参阅 #2299
  • 删除旧的 googlesitekit.moduleHasSetupWizard JS 过滤器。请参阅#2291
  • 删除旧的闪屏和相关组件。请参阅#2290
  • 允许通过 core/modules 操作 registerModule 注册模块图标 SVG。请参阅#2143

Fixed

  • 通过依赖跨入口点的单个重用 Webpack 运行时,修复由于重复模块初始化而导致的各种低级技术错误。请参阅#2444
  • 删除模块设置面板顶部的重复错误消息 UI,因为错误消息现在已经显示在面板的主要内容中。请参阅#2396
  • 修复 Google 图表库特定于组件的初始化逻辑,以防止重复初始化。请参阅#2247

1.22.0

Added

  • 在 PageSpeed Insights 小部件中显示特定于 WordPress 的用户体验建议。请参阅#2390
  • core/modules 存储的 registerModule 操作添加对 checkRequirements 参数的支持,这允许阻止模块被激活,直到满足某些要求。 请参阅#2130

Enhanced

  • 确保在以用户身份连接到已连接的站点时,根据需要自动刷新身份验证服务上的所有 URI,修复更新 URL 后站点可能卡住的问题。 请参阅#2383
  • 将日期选择器移到 Site Kit 标题栏中并使其具有粘性,以便在滚动时始终可见。请参阅#2331
  • 模糊地删除有关缺少权限的过时仪表板通知警告,现在包含更具体的小部件 CTA。请参阅#2329
  • 在 PHP 中添加对功能标志的支持,并在设置时通过实验要求用户输入完成。请参阅#2316
  • 执行完成用户输入流程后显示的成功通知。请参阅#2283
  • 添加对在插件标头中显示数据存储驱动的全局错误通知的支持。请参阅#2261
  • 通过 Search Console 的新 isZeroReport 函数改进逻辑以确定 Search Console API 报告响应是否为“空”。请参阅#2244
  • 通过针对 Analytics 的新 isZeroReport 函数改进逻辑以确定 Analytics API 报告响应是否为“空”。请参阅#2243
  • 依靠对 AdSense 小部件的 JavaScript 日期解析。请参阅#2235
  • 添加用于管理模块设置面板状态的 core/modules 操作和选择器。请参阅#2181
  • Implement Site Kit dashboard notification for when requesting user input to be completed. See #2043.
  • Implement exponential backoff to retry Google service API requests a limited amount of time if they fail with temporary errors. See #1998.

Fixed

  • Fix Search Console latest data threshold back to 2 days ago as that is the latest data the API provides. See #2458.
  • Make e2e tests pass for WordPress 5.6. See #2455.
  • Fix race condition where widgets could run into an error when their necessary datastore selector had not started resolving yet. See #2436.
  • Fix various spelling errors throughout the UI of the plugin. See #2401.
  • Flush browser session storage on plugin updates to prevent stale data from being served against new logic. See #2334.
  • Ensure that REST API preloaded data is not computed and included outside of Site Kit admin screens. See #2315.
  • Fix failing PHPUnit tests for compatibility with upcoming WordPress 5.6. See #2264.
  • Fix broken Analytics frontend deep links on AdSense module page. See #2228.

1.21.0

Enhanced

  • 在站点运行状况报告中包括当前用户的站点工具包功能。请参阅#2314
  • 用户提交信息后,将用户输入状态标记为已完成。请参阅#2310
  • Finalize copy for new googlesitekit-user-input screen. See #2302.
  • Display informational warning before setup about limited support for WordPress versions before 5.0. See #2289.
  • Modify Search Console API queries so that they include results up until one day ago. See #2284.
  • Add support for widgets to have multiple (fallback) widths via googlesitekit.widgets.registerWidget, laying out widget grid with as few gaps as possible. See #2251.
  • Modify widgets registered with quarter width to render for half the screen width on mobile viewports. See #2250.
  • Introduce ReportError and ReportZero components which should be returned by widgets that are in error state or have no data to display. See #2246.
  • Add JS utility functions sumObjectListValue, averageObjectListValue, and enhance capabilities of extractForSparkline function. See #2245.
  • Improve logic to determine whether an AdSense API report response is “empty”, via new isZeroReport function for AdSense. See #2242.
  • Simplify adding strings only visible to screen reader users by implementing a VisuallyHidden component. See #2165.
  • Reduce complexity of implementing and registering settingsEdit components for a module by centrally handling setting submission. See #2137.
  • Modify the createModuleStore JavaScript function so that every module store has a canSubmitChanges selector and a submitChanges action. See #2136.
  • Implement UI design for googlesitekit-user-input screen. See #2040.
  • Simplify module class infrastructure and implement (internal) module registry. See #1939.

Fixed

  • Fix bug where Analytics widgets would fire their API requests even when the module wasn’t completely set up, resulting in unnecessary error responses. See #2358.
  • Fix JavaScript translations that were not appearing to work correctly, given the site uses WordPress >= 5.0, which is required for support of JavaScript translations. See #2171.
  • 修复了再次尝试相同操作时无法清除操作中先前错误的错误。请参阅#2156
  • 修复一些连接日期范围的翻译字符串,使其可正确翻译。请参阅#2146
  • 修复了在还使用 Yoast SEO 插件时 amp-auto-ads 元素不会出现在 AMP 单一内容中的兼容性问题。请参阅#2111

1.20.0

Added

  • Implement post search widget using the new Widget API. See #2023.
  • Allow registering a settingsViewComponent and settingsEditComponent when calling the registerModule action on the core/modules store. See #1623.

Enhanced

  • Unregister the site from the authentication service when the plugin is deleted. See #2311.
  • 将选择器 canSubmitChangesisDoingSubmitChanges 和操作 submitChanges 添加到 core/modules 数据存储。请参阅#2182
  • 将选择器 getModuleDependencyNamesgetModuleDependantNames 添加到 core/modules 存储。请参阅#2180
  • Allow registering a setupComponent when calling the registerModule action on the core/modules store. See #2074.
  • Implement UI for new splash screen based on authentication service improvements. See #2046.
  • Detect and store whether each user has already answered the user input questions to customize the plugin behavior. See #2042.
  • Implement UI components to use in googlesitekit-user-input screen. See #2039.
  • Add Analytics tracking events for API request errors. See #1999.

Fixed

  • Fix bug where errors would be inconsistently keyed and not cleared as expected in certain cases. See #2210.
  • Fix Search Console deep links to point to correct locations in case of a domain property as well. See #2110.
  • Fix accessibility issue with links opening in a new tab by annotating them with screen reader text informing about it. See #2093.
  • Fix several UI loading state issues across module setup flows. See #1995.
  • Display text field to specify name when creating a new Tag Manager container, and prevent duplicate names which could have resulted in an error before. See #1817.
  • 删除 JavaScript 块文件的使用以修复某些服务器配置的潜在问题。请参阅#1391

1.19.0

Added

  • Introduce getUserInputSettings selector and setUserInputSettings and saveUserInputSettings actions on core/user store. See #2037.
  • Introduce core/user/data/user-input-settings REST datapoint. See #2036.

Enhanced

  • Display notice about new Analytics and link to relevant support resource. See #2219.
  • Make canSubmitChanges selectors throughout different module datastores more testable and consistent. See #2108.
  • Enhance new widget API so that only widget areas that have active widgets are rendered. See #2021.
  • Provide accurate deep links for all Search Console and Analytics widgets, pointing to the corresponding location in the Google service frontend. See #1923.
  • Use direct SVG imports instead of an SVG sprite which can cause accessibility and testing issues. See #1878.
  • Make AdSense module page UI more consistent with other modules, allowing to filter information by date instead of showing at-a-glance information for different date periods. See #317.

Fixed

  • Fix bug where some data stores would be registered multiple times in JS. See #2145.
  • Fix issue where admin bar would not show for URLs with unicode paths. Props kabirbd89. See #1968.
  • Improve error handling during module setup and editing module settings so that any API errors are displayed. See #1859.
  • Fix menu positioning bug that would move menu item for WP Engine and Bluehost hosting providers. See #1541.

1.18.0

Added

  • Introduce several filters to allow blocking rendering or execution of Google service scripts in the frontend, allowing integration with e.g. 3P cookie consent plugins. See #2087.
  • Introduce API layer for advanced Analytics event tracking configurations from other plugins. See #1728.

Enhanced

  • Introduce googlesitekit_canonical_home_url filter, allowing (e.g. multilingual) plugins that contextually alter the home URL to fix potential issues with Site Kit. See #2131.
  • Remove unused properties in module PHP classes. See #2050.
  • Scaffold new googlesitekit-user-input screen. See #2038.
  • Expand Widget component to correctly align vertically and support optional header and footer component props. See #2022.
  • Improve authentication service permissions link to check Site Kit permissions first while not exposing the actual URL on the client. See #1985.
  • Introduce User_Transients PHP class for storing user-specific transients. See #1964.
  • Introduce getDateRangeDates() selector to core/user datastore to retrieve actual date strings based on the current date range. See #1925.
  • Display error notification when refreshing an access token failed due to missing Site Kit authentication service requirements. See #1848.
  • Update the Reset Site Kit dialog message to be more clear. See #1825.
  • Provide guidance in Analytics setup flow when Tag Manager is already active and its container is configured to use Analytics. See #1382.
  • Provide guidance in Tag Manager setup flow when container is configured to use Analytics, including checks to ensure an eventual AMP container behaves correctly as well. See #1381.
  • Remove Analytics module as requirement for Tag Manager module, decoupling them to be individual. See #1380.

Fixed

  • Fix new AdSense Top Earning Pages widget displaying error instead of CTA to link AdSense and Analytics. See #2098.
  • Fix inconsistent loading state in Search Console Popular Keywords widget, which previously caused content shifting. See #2013.
  • Show an error message if the URL for the single URL detail view cannot be identified as part of the site. See #2001.
  • Improve support for URLs containing unicode, mixed case, and bidirectional control characters when requesting and sending data to Search Console. See #1567.

1.17.0

Enhanced

  • 在JavaScript中简化的模块注册,并且仅允许子每一个模块中进行注册。查看#2024.
  • 提高AdSense 账户状态侦擦基于指定错误的精确性.查看 #1919
  • 迁移AdSense Top Earning Pages widget 到新的 Widget API。查看#1902.
  • 迁移AdSense 小结widget 到新的Widget API。查看 #1901.
  • 迁移Analytics Popular Pages widget 到新的Widget API,查看 #1900.
  • 迁移搜索Console Top Keywords 控件到新的Widget API。查看 #1899.
  • 迁移 Analytics 不同的访问者,跳出率,以及目标的widgets到新的Widget API. 查看#1898.
  • 存储连接到网站套件身份验证服务的站点URL,并提示用户如果站点URL已更改,则允许更新已注册的配置并修复将来的连接问题。 看 #1857.
  • 显示一个按钮来刷新PageSpeed Insights 报告数据在控件中。Props amirsadeghian。查看 #87.

Fixed

  • 修复初始化数据存储状态有错误的注册来确保一致的初始化状态。查看#2083
  • 通过避免不必要的数据存储更新来提高数据存储的性能。 查看#2052
  • 修复各种翻译字符串以不再违反本地化最佳实践。 查看#2049
  • 当AdSense 设置流没有聚焦或者重新聚焦在tab中所出现的控制台错误。查看#2033.
  • 修复关键字小部件中特定关键字的 Search Console 深层链接以指向正确的位置。请参阅 #2019
  • 修复分析图表中跳出率和会话持续时间的工具提示,以正确设置值的格式。请参阅 #2008
  • 如果站点标题为空,则在创建新的 Analytics 帐户时提供站点 URL 作为后备默认值。请参阅 #1960
  • 避免不必要的过多请求,不断检查活动的 Analytics 媒体资源和 AdSense 客户端是否已连接。请参阅#1858
  • 仅在活动媒体资源仍然存在时自动为其选择 Analytics 默认视图。请参阅#1691

1.16.0

Enhanced

  • 修改 Site Kit 仪表板和 WordPress 仪表板小部件中热门页面表中的标题链接,以指向相关 URL 的详细信息视图。请参阅#1922
  • 迁移Search Console Impressions 然后点击 widgets 到新的widget API。查看#1897.
  • 迁移Analytics All Traffic 控件到新的Widget API. 查看 #1896.
  • 对于有关缺少 Google 服务权限的 API 错误,请根据模块所有权澄清联系谁以获取更多信息。请参阅#1824
  • 根据设置模块的人引入模块的所有权概念,查看#1743.

Fixed

  • 提升整个侦测,因此单个的URL 详情查看仅用于URLs的内容,不会导致每个WordPress的404行为。查看 #1980.
  • 修复了基于 URL 的实体检测的错误,其中 Site Kit URL 详细信息视图中的主页统计信息不会按预期显示。请参阅 #1978
  • 使用需要或不需要身份验证的 HTTP 代理修复对 WordPress 配置的支持. 请参阅 #1976.
  • 提供 permission_callbackcore/search/data/post-search 数据点并且依赖更高级的 register_rest_route 来自WordPress 核心的函数。请查看#1924.
  • 修复有关不必要地引发事件跟踪超时的控制台警告.请参阅 #1886.
  • Fix Analytics reporting graph tooltip to match Analytics frontend UI and expose the same information. See #1836.
  • Update post search input to use a better maintained and more accessible autocomplete library. See #1761.

1.15.0

Enhanced

  • Introduce more granular error handling, with consistent error behavior in every store and API request errors being automatically stored. See #1814.
  • Enhance getReport( options ) selector in modules/adsense store to allow for flexibly querying AdSense reports. See #1776.
  • Add getReport( options ) selector to modules/search-console store for querying Search Console reports. See #1774.
  • Add copy-to-clipboard functionality and link to WordPress support forums to generic JavaScript error handler. See #1184.
  • Enable Site Kit admin bar menu and URL details view for any WordPress content beyond single posts, for example category, tag, author, or post type archives. See #174.

Fixed

  • Fix opting out of Analytics for logged in users not working correctly for Web Stories. See #1920.
  • 确保搜索引擎数据在Site Kit 中仅包括当前站点的数据,当使用一个域名属性的时候。请查看#1917
  • Fix internal error handling so that invalid usages of API-based selectors result in errors being thrown as expected. See #1801.
  • Use hashes for all JavaScript asset file names to avoid stale versions from being served on hosts with aggressive caching. See #1700.

1.14.0

Enhanced

  • Add new action hooks googlesitekit_analytics_init_tag, googlesitekit_analytics_init_tag_amp, googlesitekit_adsense_init_tag, googlesitekit_adsense_init_tag_amp, googlesitekit_tagmanager_init_tag, googlesitekit_tagmanager_init_tag_amp which fire when the respective tag will be printed for the current request, but before any HTML output has been generated. See #1862.
  • Clarify messaging on initial setup screen for secondary users who need to connect to Site Kit. Props sonjaleix. See #1714.
  • Detect potential problems with issuing API requests to Google services and AMP prior to setup and inform the user about it. See #1549.

Fixed

  • Migrate away from using AMP_Theme_Support::get_support_mode() which will be deprecated in the AMP plugin version 2.0.0. Props maciejmackowiak. See #1895.
  • Fix bug where certain React code being imported in third-party code could cause JavaScript errors. See #1888.
  • Link to the Manage sites screen including an hl query parameter for a localized experience. See #1860.
  • Fix bug where the displayed Analytics user count percentage change was slightly off from Analytics service frontend. See #1681.
  • Fix bug where deep links to the AdSense service frontend could result in blank screens there for users with a single Google account logged in. See #1652.
  • Consistently enhance deep links to Google services to support users logged into multiple Google accounts in their browser. See #1456.
  • Fix inconsistency where Analytics numbers displayed for the last 90 days were slightly off from the values in the Analytics frontend. See #1280.
  • Fix bug where another plugin (e.g. WP User Frontend) could mess up the post detection process within the Site Kit dashboard. See #1253.
  • Fix bug where state of not having sufficient data for a Site Kit widget would sometimes incorrectly persist when switching the date range. See #184.

1.13.1

Fixed

  • Fix regression where Analytics top content wouldn’t be sorted correctly by views. Props gmmedia. See #1867.

1.13.0

Added

  • Introduce registerModule action to core/modules store, which allows for JS module registration and will in the future enable registration of module components. See #1622.

Enhanced

  • Add getReport( options ) selector to modules/analytics store for querying Analytics reports. See #1775.
  • Pass hl query parameter to Site Kit service for setup and authentication, for a localized experience. See #1726.
  • Modify getURLChannels selector in modules/adsense store to require both accountID and clientID parameters, and no longer rely on infering AdSense account ID from client ID in general. See #1709.
  • Implement logic and styling for managing widget areas and widgets in a dynamic grid, respective registered widget widths and aligning them properly. See #1678.
  • Migrate the existing date range selector component to rely on the centrally managed date range from datastore. See #1531.
  • Simplify detection of existing tags and combine functionality in the JS store. See #1328.
  • Migrate PageSpeed Insights widget to use the new Site Kit widgets API. See #1302.

Fixed

  • No longer cache API response errors within batch requests. See #1800.
  • Fix publisher win notifications regression where they would not be displayed anymore. See #1781.
  • Fix new JS API layer to prefer sessionStorage over localStorage for caching. See #1780.
  • Improve Google profile data lookup to retry periodically if it temporarily fails. See #1731.
  • Display correct labels for Analytics top acquisition channels by relying on ga:channelGrouping dimension. See #1719.
  • Handle error conditions more gracefully when refreshing access token fails due to e.g. the user having revoked access previously, providing the user with a link to resolve the problem. See #1646.
  • Fix usage of apiFetch with a custom middleware to only rely on preloaded data for initial requests on pageload. See #1611.
  • Fix notification bubble on Site Kit menu so that it only displays if there are actual notifications available. See #1540.
  • Fix PHP warning that could occur when retrieving REST API information via help endpoint. Props majemedia. See #1208.

1.12.0

Added

  • Add getDateRange() selector and setDateRange( slug ) action to the core/user store. See #1529.

Enhanced

  • Introduce new wrapWidget setting to core/widgets store’s registerWidget selector which adds the wrapping Widget component by default. See #1724.
  • Deprecate Module::get_datapoint_services() PHP method in favor of Module::get_datapoint_definitions() for more flexibility in annotating API datapoints. See #1609.
  • Only require the https://www.googleapis.com/auth/tagmanager.readonly scope by default for Tag Manager, and request write scopes only as needed for a specific action. See #1608.
  • Redirect users to the setup screen when trying to access the Site Kit dashboard with insufficient permissions. See #1526.
  • Implement widget areas using new Site Kit widgets API. See #1392.
  • Significantly improve stability and maintainability of Tag Manager module setup and settings. See #1386.
  • Update the majority of 3P dependencies to their latest versions. See #1356.

Fixed

  • Require accountID to be passed to getProfiles selector in modules/analytics store, in order to supported moved Analytics properties. See #1707.
  • Fix bug where placing an invalid Analytics tag through another plugin could cause the Site Kit Analytics setup UI to break. See #1651.
  • Fix bug where users with full Analytics access would see error message about lack of permissions, due to the property having been moved. See #1548.

1.11.1

Fixed

  • Fix bug where users attempting to create a new Analytics view during module setup would be blocked from proceeding. See #1754.

1.11.0

Added

  • Introduce base components for upcoming Site Kit Widgets API. See #1300.

Enhanced

  • Rename wp google-site-kit auth revoke to wp google-site-kit auth disconnect and adjust internal CLI commands infrastructure. See #1677.
  • Significantly improve stability and maintainability of Optimize module setup and settings, and fix bug where editing Optimize settings with AMP active could cause an error due to the ampExperimentJSON module setting not being stored as JSON string. See #1621.
  • Add hasScope( scope ) selector to core/user store, which allows checking whether the user has explicitly granted access to the respective scope. See #1610.
  • Introduce modules/tagmanager datastore to enable JS-based access to Tag Manager data. See #1385.
  • Allow specifying Analytics view name when creating a new one, and display a deep link to modify view settings in Analytics module settings. See #716.

Fixed

  • Fix admin tracking regression where snippet would not be loaded on the page. See #1717.
  • Ensure ad blocker detection is active throughout the entire AdSense module setup. See #1666.
  • Fix redirect to Google Analytics terms of service occasionally failing due to unnecessary extra redirect. See #1632.
  • Fix bug Cannot read property 'destroy' of undefined from AMP experiment JSON field in Optimize module. See #1605.

1.10.0

Learn more about the new feature in this release

Added

  • Implement new version of PageSpeed Insights widget that focuses on core web vitals. See #1636.
  • Introduce modules/optimize JS datastore for Optimize module. See #1620.

Enhanced

  • Detect current URL and related data when on the Site Kit screen for single URL details. See #1653.
  • Implement tabbed UI for new web vitals widget separating between mobile and desktop as well as lab and field data. See #1649.
  • Only load Site Kit-specific Analytics script on Site Kit admin screens. See #1648.
  • Pass user_roles query parameter during setup. See #1639.
  • Simplify module datastore creation by including commonStore in the store returned googlesitekit.modules.createModuleStore. See #1607.
  • Add selectors to get module-specific admin screen URLs to every module datastore. See #1559.
  • Fix accessibility issues in Site Kit settings due to semantically incorrect tag usage. See #1557.
  • Add getReport selector to modules/pagespeed-insights datastore to get UX reports. See #1426.
  • Implement meta programming approach for API-based datastore selectors and actions to reduce boilerplate. See #1288.
  • Include anchor link in success notification after setting up PageSpeed Insights module. See #532.

Fixed

  • Reduce bundle size of Analytics and Optimize module JS assets. See #1661.
  • Do not run Site Kit assets logic when not applicable for the current user, avoiding unnecessary checks e.g. on the login screen. See #1650.
  • Fix incompatibility with WooCommerce due to Webpack conflict. See #1637.
  • Fix bug with event firing when activating or deactivating a module. See #1629.
  • Enhance functionality of new core/modules store so that module activation/deactivation results in authentication data to be refreshed. See #1507.
  • Fix ad blocker detection failing for popular AdBlock browser extension. See #1491.
  • Ensure dashboard search form can only be submitted with valid content. See #1434.
  • Fix Analytics data displayed for Users being partially incorrect due to incorrect date parsing. See #1394.
  • Fix table content overflow issues in narrow viewports. Props AlexandreOrlowski. See #1376.

1.9.0

Added

  • Introduce modules/pagespeed-insights datastore in JS. See #1500.
  • Introduce modules/search-console datastore in JS. See #1498.
  • Implement Site Kit widgets API datastore wrapper on googlesitekit.widgets. See #1301.
  • Introduce core/widgets datastore for Site Kit widget registrations. See #1298.
  • Integrate with the Analytics Provisioning API to enable creation of Analytics accounts directly from the plugin. See #1271.
  • Introduce modules/adsense JavaScript datastore with core functionality for the AdSense module. See #1247.
  • Add create-account-ticket datapoint for Analytics module that creates a new Analytics account ticket using the Provisioning API. See #1212.
  • Add notifications functionality to core/user store. See #1177.
  • Introduce core/user datastore for managing user-specific data in JS. See #1175.

Enhanced

  • Only request readonly OAuth scopes for each module by default, and prompt for additional scopes when needed for a specific action. See #1566.
  • Wrap all JavaScript apps into Root component with essential providers, error handlers etc. See #1530.
  • Introduce core/forms datastore to manage form state. See #1510.
  • Render amp-analytics snippet for Web Stories. See #1506.
  • Migrate PageSpeed Insights settings to using the datastore. See #1501.
  • Display actual Search Console property used in settings, and migrate to using the datastore. See #1499.
  • Rename Analytics profiles to views consistently. See #1486.
  • Improve AdSense account status and site status detection logic to be more error-proof. See #1332.
  • Add user profile information and verification state to core/user datastore. See #1176.
  • Significantly improve stability and maintainability of AdSense module setup and settings. See #1014.
  • Clarify message for when user needs to reauthenticate to grant required scopes. See #189.

Fixed

  • Ensure all module caches are cleared when modifying Analytics settings. See #1593.
  • Fix bugs where CTAs to link Analytics to AdSense would never show. See #1545.
  • Fix AdSense report URL to not include user-specific affix. See #1516.
  • Fix Search Console deep links to use the correct property identifier. See #1497.
  • Fix bug where having a graylisted AdSense account would prevent the AdSense code from being placed. See #1494.

1.8.1

This release includes security fixes. An update is strongly recommended.

Enhanced

  • Check for users that verified through Site Kit without being authorized to do so, and disconnect them from Site Kit. See #1573.
  • Provide application_name query parameter to authentication service. See #1571.

1.8.0

This release includes security fixes. An update is strongly recommended.

Added

  • Introduce standalone UI mode for plugin admin screens. Props EvanHerman. See #1281.
  • Introduce modules/analytics datastore for managing Analytics state in JS. See #1224.
  • Introduce core/modules datastore for managing module information and activation state. See #1179.

Enhanced

  • Preload REST API datapoints for core/site and core/user datastores to avoid firing these extra requests. See #1478.
  • Add support for new Optimize container IDs starting in OPT-. See #1471.
  • Improve alignment of dialog buttons. See #1436.
  • Rely on the default profile specified in an Analytics property for the profile to pre-select in the dropdown in Analytics setup/settings. See #1404.
  • Remove periods from single sentences in settings panel lists. See #1401.
  • Add googlesitekit.data.combineStores utility function to combine multiple datastore objects. See #1400.
  • Significantly improve stability and maintainability of Analytics module setup and settings. See #1101.
  • Update Analytics control for whether to place snippet to use a toggle instead of radio buttons for consistency. See #1048.

Fixed

  • Fix bug where Analytics would never request AdSense metrics even with a successful AdSense connection. See #1524.
  • Fix bug where amp-auto-ads snippet would not always be printed if the theme didn’t support the wp_body_open action. See #1495.
  • Do not request remote notifications if the site is not connected to the remote. See #1479.
  • Update registered site name on authentication service when it is updated in WordPress. See #1397.
  • Display only paths instead of full URLs in Analytics tables for better visibility and consistency with Analytics frontend. See #1116.
  • Add missing translator comments to ease plugin localization for contributors. See #820.

1.7.1

Added

  • Add notifications functionality to core/site datastore. See #1174.

Enhanced

  • Add rollbackSettings action to settings datastores and refine overall datastore infrastructure. See #1375.
  • Expand AdSense settings panel to expose more helpful information. See #585.

Fixed

  • Fix bug where similar batch request to the API could occur multiple times. See #1406.
  • Fix bug where single post stats would display the unique visitors from Search for the overall site instead of only that post. Props phamquangbaoplus. See #1371.
  • Fix Analytics incorrectly triggering re-authentication notice when the user does not have any accounts. See #1368.
  • Fix JS datastore actions to never have an associated control and reducer at the same time. See #1361.
  • Place Tag Manager snippet for non-JavaScript support after opening body tag as commonly expected. Props ShahAaron. See #1308.
  • Fix layout issue in Tag Manager settings panel when no container is selected. See #1296.
  • Fix issue related to added _gl query parameter from AMP linker. Props ShahAaron. See #1275.

1.7.0

Enhanced

  • Allow modules to register and enqueue their own assets by implementing a Module_With_Assets interface. See #1319.
  • Decouple datastores from global registry by using createRegistryControl and createRegistrySelector. See #1287.
  • Update datastore resolvers to only issue API requests when lacking data. See #1286.
  • Add preloading middleware for REST API data and preload module settings routes on pageload. See #1246.
  • Add more granular selectors to the core/site datastore. See #1173.
  • Add several additional selectors for commonly used site data to the core/site datastore. See #1000.

Fixed

  • Fix bug where plugins modifying the site address during frontend requests would prevent the setup flow from being completed. See #1357.
  • Fix bug where googlesitekit.api.set would not pass through request data correctly to the API endpoints. See #1346.
  • Fix bug where using a WordPress locale with a third segment (e.g. formal variant) would cause JavaScript errors on some screens. See #1309.
  • Do not revoke token remotely when token is deleted, unless explicitly requested via disconnect. See #1305.
  • Fix unicode domains being displayed in punycode version in disconnect feedback message. See #1297.
  • Fix bug where certain numbers were rounded differently from how the respective Google service rounds them. See #1279.
  • Optimize JavaScript dependency loading, decreasing the chance of conflicts and reducing the plugin size. See #1222.
  • Ensure the total user count in the Analytics module matches the numbers displayed in the Google Analytics frontend. See #1202.

1.6.0

Added

  • Add support for reading and editing settings to datastores created via googlesitekit.modules.createModuleStore. See #1249.
  • Introduce googlesitekit-modules asset with createModuleStore function to create a base datastore for a Site Kit module. See #1063.

Enhanced

  • Ensure module settings are consistently passed from PHP to JavaScript, and fix some minor logic issues in the consuming JavaScript code. See #1245.
  • Automatically include a REST route to read and edit settings for every module that supports them. See #1244.

Fixed

  • Fix issue where users would get stuck on setup screen after seemingly successful completion of the setup flow on the authentication service. See #1266.
  • Provide clear error message informing the user when they did not grant the necessary permissions, instead of a generic access_denied error code. See #1192.
  • Fix JavaScript errors in AdSense screens that was a result of Intl.NumberFormat.formatToParts not being supported in Safari. See #1107.
  • Fix JavaScript error e.replace is not a function in AdSense screens related to formatting numbers. See #1092.
  • Fix problems around comparing domains with unicode characters that could result in blocking the plugin setup. See #794.

1.5.1

Fixed

  • Ensure tracking opt-out mechanism works consistently between both Analytics and Tag Manager in AMP, and fix regression with Site Kit admin bar menu no longer expanding on AMP pages. See #1251.

1.5.0

Added

  • Expose googlesitekit.data registry and register initial core/site store on it. See #999.
  • Add user-facing warnings to Site Kit areas when JavaScript is disabled. Props Shavindra. See #177.

Enhanced

  • Standardize several REST API route names for consistency with JavaScript API. See #1178.
  • Fix various plugin setup issues related to inconsistent URLs by automatically updating registered URIs on the authentication service. See #1034.
  • Improve asset handling in PHP by introducing dedicated data-only scripts, to use as dependencies. See #1004.
  • Respect Analytics tracking exclusion of logged-in WordPress users also if Tag Manager is used. See #944.
  • Integrate with WordPress Site Health feature to provide contextual Site Kit information for support and troubleshooting. See #169.

Changed

  • Display helpful link in previously empty PageSpeed Insights settings area. See #1129.
  • Use latest product icon for the Optimize module. See #969.

Fixed

  • Ensure date range selectors functionality is decoupled from localizable strings. See #1183.
  • Fix bugs where some untranslated strings would show despite being translated, caused by too early usage of these strings in JavaScript. See #1163.
  • Replace outdated AMP client ID mechanism for tracking AMP traffic with recommended AMP linker approach, and enable it by default. See #1160.
  • Fix compatibility error where google.charts.load was not called before google.charts.setOnLoadCallback. See #1155.
  • Do not show empty data table in Analytics module screen when there is no data to display. See #464.

1.4.0

Enhanced

  • Introduce basic notifications system for information displayed in the Site Kit dashboard. See #1110.
  • Register all of the plugin’s user options in WordPress via register_meta(). See #1029.
  • Improve JS error handling consistently across individual React apps and allow for better contextualization. See #943.
  • Display information about lack of data instead of displaying empty top search queries box. Props Shavindra. See #314.
  • Ensure admin bar displays when at least Search Console or Analytics have stats for the current URL. See #167.

Fixed

  • Fix minor bug causing potentially incorrect token expiry to be recorded. See #1158.
  • Fix AMP violations when user is logged in and Site Kit admin bar menu is active. See #1142.
  • Fix incompatibility issue with Jetpack by resolving bug where the bundled lodash was causing a conflict. See #1141.
  • Fix double-rendered HTML markup on Site Kit dashboard screen. See #1140.
  • Fix misleading sparkline color for metrics that should use the inverted color, such as bounce rate. See #1128.
  • Work around bug in ModSecurity by relying on only providing granted OAuth scopes in token API response. See #1113.
  • Make JS and CSS asset names consistent. Props Shavindra. See #1040.
  • Properly support paired AMP in Tag Manager module by allowing to select two different containers, one for web context and the other for amp context. Props kmwilkerson. See #413.
  • Fix accessibility issues in dialog component with potentially duplicate IDs and invalid ARIA attributes. See #345.
  • Fix issue where disconnecting a user from a site would disconnect that user from all their sites.

1.3.1

Fixed

  • Ensure opcache_reset() exists before calling it. See #1136.

1.3.0

Added

  • Introduce googlesitekit.data registry for JS datastores. See #997.

Enhanced

  • No longer delete plugin data when uninstalling and instead rely on the more explicit reset functionality. See #1069.
  • Remove legacy migrations that were only relevant to pre-1.0.0 users. See #1062.
  • Migrate stray module settings into object-like option for consistency and future scalability. See #1030.
  • Introduce core/site/data/connection REST API route for retrieving site connection info. See #998.
  • Fully rely on Webpack for third-party dependencies and decouple from WordPress-shipped assets for more stability across all versions. See #993.
  • Inform the site owner about potential issues with their site that will likely cause problems when setting up the plugin. See #933.
  • Make opting in to tracking specific per user instead of per site. See #913.
  • Bump minimum required PHP version to 5.6, rely on up-to-date linting tools and fix various PHPCS issues. See #547.
  • Move REST route definitions into more applicable classes that handle the respective functionality. See #166.

Fixed

  • Allow users with existing Tag Manager accounts to create additional accounts during module setup. See #1080.
  • Fix partly outdated PHP files being served due to OpCache issues currently not addressed by WordPress core. See #1066.
  • Prevent unexpected PageSpeed Insights API responses from breaking the dashboard. See #1061.
  • Standardize GA tracking snippets and inconsistent data passed in events by introducing a proper tracking API in JavaScript. See #1055.
  • Fix several temporary blank screen errors by loading script dependencies more reliably via Webpack. See #1054.
  • Ensure that the Tag Manager snippet rendered is always compatible with the current context (AMP vs non-AMP). See #1036.
  • Do not render amp-auto-ads element in AMP stories because it is invalid in that context. See #979.
  • Ensure that Google Charts JS library is loaded as expected even when a window.google global already exists because of another library. See #939.
  • Do not refetch PageSpeed Insights data when the date range selector is changed, as its data its date-unaware. See #890.
  • Fix incorrect change arrow direction and color on “inverted” properties like bounce rate. Props WebFactoryLtd. See #481.
  • Add missing support for Search Console domain properties and rely on the correct property when requesting Search Console data. Props IgorCode. See #325.

1.2.0

Added

  • Introduce new googlesitekit.api layer for accessing Site Kit datapoints with reliable caching. See #953.
  • Detect already existing Tag Manager snippets from other sources and inform about them in the setup flow. See #433.

Enhanced

  • Introduce Site Kit-specific Google_Client implementation and use that throughout the codebase. See #1003.
  • Reduce maintenance by implementing dynamic activation notice in React. See #991.
  • Include platform and plugin version information in API client requests. See #989.
  • Ensure that all module settings are properly registered in WordPress for consistent behavior. See #859.
  • Allow users to rely on WP_PROXY_* constants to use an HTTP proxy for requests issued by Google_Client. See #661.
  • Allow users that have existing Google Analytics account to create a new account in module setup and settings. See #198.
  • Remove very limited debug bar integration for now. See #178.

Fixed

  • Fix bug and potential JavaScript error where user was able to select Analytics property before selecting an account. See #1039.
  • Optimize initialization of the Google API client and minimize JavaScript assets and inline data being loaded in regular requests. See #980.
  • Fix Search Console average position graph to show the smallest value on top of the Y axis. Props connorhsm. See #874.
  • Display warnings about insufficient scopes across all Site Kit screens instead of only the dashboard, since they are just as relevant during setup. See #729.
  • Ensure that PageSpeed Insights module can be deactivated again once activated. See #682.

1.1.4

Enhanced

  • Improve compatibility with WordPress VIP environment. Props moraleida. See #901.
  • Update wording on setup screen for secondary users to clarify they need to connect their account, but not set up the plugin. See #881.
  • Use OAuth login_hint parameter to indicate that the user should use the same Google account across all modules. See #867.
  • Anonymize IP addresses by default in Google Analytics snippet, and grant the user control to modify with a new setting. Props gx10. See #18.

Fixed

  • Fix compatibility issues with older versions of the AMP plugin. See #975.
  • Ensure that only options and user options starting with googlesitekit_ (including underscore) are deleted on reset or disconnect. See #968.
  • Optimize disconnecting users by only running a single database query. See #960.
  • Ensure Site Kit admin bar content is styled independently from the current theme. See #888.
  • Fix bug in Analytics module setup where the user would not be informed about an existing tag before selecting a property. See #803.
  • Fix bug where admin bar stats would not display under certain circumstances when editing a post in the backend. See #521.
  • Display impressions before clicks in admin bar as that is the commonly expected order. See #297.

1.1.3

Fixed

  • Fix critical AdSense issue where users were not able to place the snippet and would end up on a blank screen under certain conditions. See #891.

1.1.2

Enhanced

  • Introduce new mechanism for a site to receive its credentials from the authentication service, replacing the previous mechanism using the REST API that was error-prone on certain environments. See #905.

Fixed

  • Remove unnecessary logic to refresh an access token on login, since the Google API client already accounts for that. See #903.
  • Fix too long request URLs for Google API batch requests to use POST instead, as the query length was problematic on certain environments. Props sksaju. See #779.
  • Fix bug resulting in blank plugin dashboard screen under certain circumstances. Props ThomasTr. See #767.
  • Ensure that opting in or out of tracking takes effect immediately. See #727.
  • Fix spacing issue in Search Console step for local development setup. See #637.
  • Fix display of the disconnect modal which could potentially appear below the “section locked” indicator in the plugin settings UI. See #636.

1.1.1

Fixed

  • Fix reset and uninstall data removal by optimizing database queries. See #809.

1.1.0

Enhanced

  • Update usage of G icon in admin menu, dashboard widget and screen options to align better with WordPress admin UI. See #877.
  • Add support for site verification via file as primary method while keeping site verification via meta tag as fallback, resolving potential site verification failures. See #836.
  • Move checkbox above submit button in setup screen and banner for better accessibility. See #788.
  • Use more secure nonce generation mechanism for the authentication service. See #756.
  • Show PageSpeed Insights performance stats for every individual URL in its details view, accessible from Site Kit dashboard and admin bar. See #654.
  • Display Tag Manager container names instead of IDs in dropdowns for more user-friendly selection. See #591.
  • Remove redundant notification title for AdSense notifications. Props OisinOConnor. See #586.
  • Always use root domain for AdSense site because subdomains are typically not supported. Props OisinOConnor. See #578.
  • Add support for displaying the full Site Kit admin bar menu with stats also for AMP requests, by leveraging AMP’s dev mode feature. See #438.
  • Simplify AdSense account status detection as a base for easier future enhancements and fixes. See #427.
  • Add a checkbox to allow disabling Analytics tracking for logged-in users, and introduce a filter to adjust the behavior programmatically. Props Paras16699. See #88.

Fixed

  • Ensure that a newly created Tag Manager container is properly saved so that the module setup is completed. See #821.
  • Improve detection of existing AdSense snippets to cover more variants of snippets. See #798.
  • Only display the Reset button on the setup screen if there actually is something to reset, and provide a feedback notice. See #758.
  • Update incorrect message in development setup flow referring to site verification instead of Search Console. Props AVGP. See #600.
  • Only show Tag Manager containers that are relevant to the site’s mode, and accordingly support AMP-first by only exposing AMP containers. See #470.

1.0.4

Fixed

  • Fix critical bug causing unnecessary requests to Google People API although no user is logged-in. See #854.

1.0.3

Fixed

  • Fix critical issue where an invalid refresh token would not revoke the current token, resulting in recurring requests with further attempts. See #831.
  • Fix REST request sending credentials potentially being blocked due to user agent.

1.0.2

Enhanced

  • Introduce Jest for JS unit tests, migrate existing tests, and improve various related infrastructure components. See #524.

Fixed

  • Do not disconnect user when refreshing an access token randomly fails, and ensure the user sees an error message about any errors during the process. See #818.
  • Fix error that could occur when setting up a new Analytics profile from the module setup. See #816.
  • Fix bug where the site verification nonce was not sent to the authentication service. See #797.
  • Fix false positive when detecting existing Analytics tags, which previously blocked users from completing the module setup. See #793.
  • Ensure that google-site-kit translation strings in JavaScript files are maintained after minification so that they can be translated on wordpress.org. See #782.
  • Improve various translation strings by removing trailing spaces, adding a context, fixing capitalization, and more. Props pedro-mendonca. See #769.
  • Remove irrelevant translation strings from codebase by eliminating @wordpress/components dependency. See #759.
  • Improve detection of existing Analytics snippet by covering a further variant that is used e.g. by the Analytify plugin. Props ernee. See #744.
  • Improve UX and fix performance issues with excessive re-rendering in the module settings screen. See #742.
  • Fix style issues in various data tables which previously would break out of their parent containers on certain device widths. See #480.
  • Fix Unknown error (code: checking requirements failed). by resolving quota issues on the authentication service.
  • Improve stability of REST API request issued by the authentication service when setting up a new site.
  • Fix Method not allowed error on the authentication service.

1.0.1

Fixed

  • Ensure verification tokens and other plugin user data correctly get cleared when resetting the plugin before the user has authenticated. See #771.
  • Fix bug where the verification tag sent from the service to the plugin would result in a 404 response, preventing the verification from being completed. Props theeducatedbarfly. See #765.
  • Improve compatibility with sites that have a http:// website address stored as home_url, but actually require HTTPS. Props drcrow. See #760.

1.0.0

Enhanced

  • Display a reset button alongside the setup button so that the plugin can also be reset before completing the initial flow. See #753.
  • Remove custom updater to instead fully rely on wordpress.org. See #644.

Fixed

  • Correctly disconnect the user when revoking access from the proxy, and update the wording accordingly. See #724.
  • Show error message in PageSpeed Insights widget when API response incorrectly comes back with a score of 0. See #723.