Releases: google/site-kit-wp
Releases · google/site-kit-wp
1.149.1
1.149.0
Enhanced
- Update Ads setup via PAX to enable the enhanced conversion tracking by default. See #10413.
- Update the WooCommerce Redirect modal logic to trigger at the Ads setup wizard. See #10404.
- Fix the learn more link in the ACR lost events banner. See #10397.
- Add GA events tracking for user interaction with the Reader Revenue Manager introductory overlay notification. See #10330.
- Unguard the
productIDs
andpaymentOption
module settings to enable publication data synchronization without therrmModuleV2
feature flag. See #10314. - Update text in "Top earning pages" widget. See #10158.
- Remove the
audienceSegmentation
feature flag. See #10148. - Add support for outputting the Sign in with Google button where
wp_login_form
is used. See #10047. - Update Google Tag ID mismatch notifications to use new notifications infrastructure to improve reliability/user experience. See #9292.
Changed
- Update Guzzle to v7. See #10302.
- Update the PAX setup success notifications to lead the "Show me" link to the official Google Ads campaigns overview page. See #10272.
Fixed
- Fix PAX layout issues. See #10412.
- Ensure that warning notices for Reader Revenue Manager blocks appear as expected for view-only Site Kit users. See #10394.
- Fix console warning that could appear when Sign in with Google module is not connected. See #10325.
- Fix the All Traffic pie chart tooltip issue that didn't appear after deselecting a segment. See #10318.
- Fix incorrect user count in the "Others" segment of the Locations pie chart and ensure matching percentages in All Traffic widget pie charts. See #10243.
- Update key metric widgets to skip showing empty rows. See #10156.
- Upgrade Google API client library to avoid deprecation notices on latest versions of PHP. See #9977.
1.148.0
Added
- Unregister the
PartnerAdsPAXWidget
widget. See #10219.
Enhanced
- Update the Ads setup CTA banner to appear before the Audience Segmentation banner. See #10290.
- Update the "Learn more" link in the Ads Module Setup banner. See #10278.
- Show warning when Google for WooCommerce ads account is enabled. See #10257.
- Add WordPress post list bulk edit setting for Reader Revenue Manager. See #10248.
- Update the Ads module setup layout. See #10193.
- Fix bug that could cause console errors when answering tailored metrics questions. See #10182.
- Add the subtle notification component for existing Google for WooCommerce Ads users. See #10176.
- Update Ads Setup CTA to add support for WooCommerce plugins. See #10175.
- Add the
WooCommerceRedirectModal
component. See #10172. - Add plugin detection selectors to the core/site datastore. See #10170.
- Add support for detecting WooCommerce and Google for Woo plugins. See #10169.
- Handle the error case where the saved product ID is no longer available in the current Reader Revenue Manager publication. See #10131.
- Display context-aware messaging based on the publication’s monetization mode in the Reader Revenue Manager module's the setup success notification. See #10068.
- Add a dropdown and associated informational elements to the Reader Revenue Manager setup and settings screens, to aid the selection of a product ID. See #10065.
- Enable conditional and context-aware placement of the Reader Revenue Manager code snippet. See #9973.
- Add WordPress editor blocks for Reader Revenue Manager inline CTA buttons. See #9963.
- Add a panel to the WordPress post editor to users to override the Reader Revenue Manager snippet configuration at the post level. See #9962.
- When enabling groups, ensure Analytics scope is only requested when needed. See #9595.
- Rework the Auto Update banner to use the new notification infrastructure. See #9295.
Changed
- Ensure that client-side filtering of unset Analytics report values filters out empty strings as well as '(not set)', to align with changes to the Analytics Data API. See #10143.
Fixed
- Fix the console error that appears when the
conversionReporting
flag is enabled and the Analytics module is not connected. See #10289. - Add a datastore slice with actions and selectors for retrieving and updating the new set of audience settings. See #10154.
- Add a new option for audience settings, with REST endpoints to retrieve and update it. See #10153.
- Hide the new badge in the key metrics settings when they have been configured in the full screen editing for the first time. See #10083.
1.147.0
Enhanced
- Retain the publication ID prefix for product IDs when storing them in Reader Revenue Manager settings. See #10228.
- Update URL for RRM publication creation to streamline configuration. See #10166.
- Update the Analytics zero-data report to include the comparison date range, ensuring we check for data across both the previous and current date range when determining the gathering data state. See #10105.
- Add Reader Revenue Manager introductory overlay notifications. See #10070.
- Add Reader Revenue Manager product ID notifications. See #10069.
- Add a new "CTA placement" section to the Reader Revenue Manager settings, allowing users to select where CTAs should appear using a dropdown and chip multi-select. See #10066.
- Add the learn more link to the lost events banner. See #10045.
- Update Ads PAX Application to be aware of supported conversion events. See #10032.
Changed
- Move js dependencies required for backstop tests to their own workspace. See #10093.
- Refactor filtering of
(not set)
values in reports to use the newEmptyFilter
filter type. See #10059. - Implement the Sign in with Google block. See #10046.
- Move e2e related dependencies into their own workspace. See #10013.
- Refactor report filters so as to be usable for both dimensions and metrics. See #7634.
Fixed
- Fix error that could occur on the dashboard when connecting a new Analytics account after connecting a previously-connected account. See #10187.
- Fix Key Metrics positioning on large screens. See #10050.
- Update description of the new detected events notice. See #10049.
- Update language used in tailored metrics questionnaire. See #10040.
- Fix incorrect dismiss notification event tracking. See #10038.
- Fix duplicate survey triggers issue. See #10036.
1.146.0
Enhanced
- Add warning to users when Sign in with Google One-tap appears site-wide without open user registrations. See #10079.
- Update the Reader Revenue Manager settings view screen to include new settings introduced in Phase 2. See #10067.
- Add a reusable chip multi-select component. See #10064.
- Update the Reader Revenue Manager setup CTA banner copy to highlight paywall support when the feature flag is enabled. See #10063.
- Add mechanism to clear term meta on Site Kit reset. See #10061.
- Add mechanism to store term-level Reader Revenue Manager settings. See #9956.
- Add mechanism to synchronize Reader Revenue Manager publication information. See #9954.
- Add mechanism to reset publication-specific information when the publication is changed. See #9953.
- Update Reader Revenue Manager publication selection to populate new settings. See #9952.
- Add infrastructure to interface with WordPress term metadata. See #9949.
- Improve the styling of the Sign in with Google button on WooCommerce login forms. See #9932.
- Update Ads settings view screen to display items in the correct order. See #9908.
- Update the First-party mode status in Site Health to use "Enabled" or "Disabled" instead of "Yes" or "No" and update the label from "First-party mode: Enabled" to "First-party mode". See #9904.
- Refactor consent mode setup CTA to use new infrastructure. See #9887.
- Update the Audience Segmentation Setup CTA so it does not appear alongside other CTAs. See #9886.
- Update visitor group card to prevent including
(not set)
in cities with the most visitors. See #9604.
Changed
- Ensure user is redirected back to original page when using Sign in with Google. See #10015.
Fixed
- Improve reliability of Sign in with Google rendering on WooCommerce account pages. See #10120.
- Fix bug that could cause CTA to add new metrics to Analytics. See #10044.
- Fix bug that caused the "Top traffic source driving leads" metric to show no data in the "90 days" view. See #10043.
- Fix bug that could cause metrics not to update properly if answers were changed several times before saving changes. See #10034.
- Ensure suggested metrics include new events. See #10033.
- Fix user registration notification dismissal issue on the Sign in with Google settings screen. See #9933.
- Fix key metrics setup CTA layout at 960px. See #9911.
1.145.0
Enhanced
- Add Site Health information for Reader Revenue Manager expansions. See #9974.
- Add an empty RRM V2 JavaScript entry point for the WordPress block editor, with functionality to be added in subsequent issues. See #9957.
- Add mechanism to store post-level Reader Revenue Manager settings. See #9955.
- Update Reader Revenue Manager module settings infrastructure. See #9951.
- Add a trigger for a survey when the user sees the FPM setup banner, and one when the user enables FPM, in order to help track usage of the feature. See #9940.
- Update copy on disconnect module modal. See #9935.
- Standardize the capitalization of "First-party mode" across the plugin for consistency. See #9902.
- Ensure the Reader Revenue Manager Setup CTA does not appear alongside other CTAs. See #9889.
- Add error handling to the First-party mode setup banner to display errors and prevent premature dismissal when saving settings fail. See #9846.
- Update auth error notification to use new notifications infrastructure. See #9284.
- Update tooltip tours to display on smaller screen sizes. See #3003.
Changed
- Update the service provisioning URL not to contain the
supportemail
query param. See #10024.
Fixed
1.144.0
Added
- Add
library_name
parameter to Sign in with Google button. See #9924. - Add incremental ESLint rule to avoid defining
scenario.label
on stories. See #9865. - Add option to enable "One-tap" sign-in across site when using Sign in with Google. See #9861.
Enhanced
- Add the
rrmModuleV2
feature flag, this will be used for phase two of the Reader Revenue Manager module's development. See #9948. - Update FPM health check to use the approach from the measurement script. See #9916.
- Improve Analytics Conversion Reporting new/lost events callouts experience for each Site Kit user. See #9897.
- Update subtle notification padding for consistency with the Figma design. See #9860.
- Add a loading spinner to the "Enable First-party mode" CTA button on the setup banner to indicate progress during the setup process. See #9856.
- Only run the periodic server requirement health checks for First-party mode when the mode is enabled. See #9842.
- Update Partner Ads Experience with knowledge of supported conversion events. See #9816.
- Improve logic for persisting badges in the Key Metrics selection panel. See #9798.
- Add the Suggested group to the key metrics selection panel. See #9797.
- Add a warning notification on the dashboard to alert users when First-party mode is disabled due to failed server requirement checks. See #9767.
- Update to the latest version of the First-party mode proxy script. See #9710.
- Add "Learn more" links for First-party mode. See #9699.
- Introduce GA4 tracking events for the First-party mode feature. See #9669.
- Add loading state with placeholder elements to Site Kit's WP dashboard widget. See #9570.
- Fix issues with Audience Creation Notice when browser viewport is very short. See #9562.
- Improve accuracy of periodic network connection check. See #9485.
- Add badge to new Analytics Conversion Reporting widget tiles and groups. See #9386.
- Update the Setup Error Banner notification to use the new Notifications API. See #9283.
- Move settings edit dependency loading state to module stores. See #8730.
- Improve the "See full details" link in AdSense settings, linking to the list of sites for the account where possible. See #8076.
- Ensure that cities and countries with unset values don't show up in the "Top cities driving traffic" and "Top countries driving traffic" Key Metric tiles. See #7884.
Changed
- Remove the deprecated
OAuth_Client::using_proxy
method and its associated tests. See #8366.
Fixed
- Ensure measurement tracking requests succeed when both the Analytics and Ads modules are connected and First-party mode is enabled. See #9901.
- Improve sort order in module list. See #9877.
- Ensure "Enhanced Measurement" setting is not activated when disabled during Analytics setup. See #9827.
- Fix a glitch where setup CTA banners would momentarily appear again when dismissing their admin settings tooltip. See #9791.
- Fix iPad 10 Safari inconsistencies. See #9776.
- Fix potential for PHP warning related to accessing a property
post_type
on null. See #9762. - Ensure Site Kit's Google chart on the WordPress dashboard widget correctly adapts to viewport width changes. See #9756.
- Fix the deprecation error in the Ads module related to the creation of a dynamic property in the
Web_Tag
class. See #9531. - Prevent unnecessary requests on dashboard. See #9178.
- Prevent PHP warnings when creating custom dimensions. See #7801.
1.142.0
Added
- Add Analytics events to Sign in with Google. See #9747.
Enhanced
- Fix the "improve your measurement" section's layout in mobile viewports. See #9830.
- Update the default value of the First-party mode
isEnabled
setting tofalse
. See #9828. - Add periodic server requirement health checks for first-party mode. See #9768.
- Always display the "Anyone can register" WordPress setting in Sign in with Google settings. See #9735.
- Update learn more link in Sign in with Google module settings. See #9734.
- Update copy in Sign in with Google "Connect more services" UI. See #9733.
- Update Sign in with Google setup success notification UI. See #9724.
- Automatically dismiss the First-Party Mode setup banner notification when the toggle is enabled from the settings screen, preventing redundant notifications. See #9698.
- Add a selector to detect changes and an action to reset First-party mode settings, integrated with Analytics and Ads rollback and validation processes. See #9688.
- Add FPFE health check and script access statuses to Site Kit’s Site Health section, displaying whether these checks are enabled or disabled. See #9668.
- Add First-Party Mode status to Site Kit’s Site Health section, displaying whether the feature is enabled or not when either the Analytics or Ads modules are connected and the
firstPartyMode
feature flag is active. See #9667. - Add support for gtag to load in first-party mode when enabled. See #9664.
- Display the First-party mode enabled status in the Ads settings view. See #9659.
- Display the First-party mode enabled status in the Analytics settings view. See #9658.
- Integrate the First-party mode toggle into the Ads module’s settings form, allowing users to enable or disable First-party mode. See #9655.
- Integrate the First-party mode toggle into the Analytics module’s settings form, allowing users to enable or disable First-party mode. See #9654.
- Group measurement toggles together on the settings screen in the Ads and Analytics module edit sections. See #9651.
- Add a "Beta" badge to the First-party mode toggle. See #9650.
- Implement the First-party mode toggle as a component which is presented in Storybook. See #9649.
- Add first-party mode setup success notification. See #9648.
- Add the First-party mode setup banner to let users know about the feature and enable it from the dashboard. See #9647.
- Update spacing between CTA actions for consistency. See #9600.
- Add notification banner when event data has been missing for ninety days. See #9578.
- Improve notifications rendering performance. See #9488.
- Add full size selection panel on the new screen. See #9375.
- Update Analytics Conversion Report notifications to be more context-aware. See #9373.
- Ensure Analytics Conversion Reports notification appears for users who set up Key Metrics manually. See #9372.
- Ensure that the setup flow for a module is automatically continued when clicking the "Redo setup" CTA on the "Site Kit can’t access necessary data" unsatisfied scopes notification. See #9261.
- Extend Consent Mode conditions logic. See #9147.
Fixed
- Update the Sign in with Google module to suggest using the previous client ID when re-connecting the module. See #9744.
- Ensure Sign in with Google translations are consistent. See #9738.
- Add Sign in with Google live preview in settings. See #9718.
- Update layout of Top Content widget in smaller viewports to use a tab per metric column. See #7563.
1.141.0
Added
- Add Sign in with Google to WooCommerce login page. See #9340.
Enhanced
- Update Sign in with Google descriptions in Site Health. See #9680.
- Update the Sign in with Google login to use the popup approach. See #9677.
- Integrate the First-party mode proxy script that will allow Analytics events to be tracked via requests made from the browser to the user's site rather than directly to Google's servers. See #9665.
- Add info to the "One-tap" option in Sign in with Google settings. See #9643.
- Do not show "Maybe later" in Key Metrics Admin Settings callout banner. See #9636.
- Implement the
fetchGetFPMServerRequirementStatus()
Redux action used to retrieve the FPM server requirement status. See #9634. - Add an
fpm-server-requirement-status
API endpoint to verify First-Party Mode readiness by performing FPFE health checks and verifying direct PHP script access. See #9632. - Add a partial datastore for First-Party Mode in the
core/site
datastore to manage its settings. See #9628. - Add REST endpoints for First-Party Mode module settings. See #9625.
- Update "Get your Client ID" link in Sign in with Google setup. See #9621.
- Ensure tailored metrics override previous metrics when switching from manually-selected metrics. See #9613.
- Improve the accuracy of the mechanism that scrolls the user to a widget area. See #9603.
- Improve visitor groups selection panel to prevent a console warning. See #9602.
- Add an external icon to external links in the audience selection panel and placeholder tile. See #9598.
- Remove visitor groups setup success notifications when the user chooses not to display visitor groups in dashboard. See #9596.
- Introduce grouping of notification queues. See #9568.
- Add notice for users who used a legacy answer in Key Metrics settings. See #9518.
- Split the "Sell products or services" answer in the User Input app. See #9489.
- Persist selection group in Key Metrics selection panel. See #9385.
- Add support for disconnecting associated Google account for sign in from WordPress user edit screen. See #9380.
- Implement new subtle notification banner in KMW dashboard area. See #9371.
- Move on-demand onboarding state synchronization to the server side, avoiding the need to reload the full list of publications. See #9363.
- Improve selection panels so that they perform actions only when in view. See #9312.
- Improve Reader Revenue Manager publication onboarding state synchronization. See #9149.
- Add Key Metrics info to Site Health report. See #9112.
Changed
- Implement settings view for Sign in with Google. See #9477.
- Implement Sign in with Google token response login handling. See #9339.
Fixed
- Fix a bug that caused a custom dimension to not be created while setting up visitor groups. See #9597.
1.140.0
Added
- Add Sign in with Google to Site Health. See #9571.
- Add new feature notification for Sign in with Google module. See #9335.
Enhanced
- Add a survey to be triggered when audience groups are set up. See #9656.
- Update styles for the admin settings. See #9580.
- Add GA event tracking for user interactions with the Audience Segmentation Setup in the Settings section. See #9499.
- Add opt-in event tracking for the Audience Segmentation introductory popup/banner. See #9498.
- Add GA event tracking for user interactions with the Audience Selection Panel. See #9497.
- Add opt-in user activity tracking in the audience tiles area. See #9494.
- Add opt-in user activity tracking in the audience setup CTA widget and related setting areas. See #9493.
- Don't unnecessarily render the Key Metrics Selection Panel into the DOM. See #9468.
- Add a stub survey trigger that is called when viewing the Reader Revenue Manager Setup CTA. See #9447.
- Update the widget area renderer to accept React components for subtitles. See #9444.
- Add modal of tailored metrics to User Input Questionnaire. See #9439.
- Add confirmation modal for users changing key metrics. See #9438.
- Add support for lost events to Conversion Reporting events datastore. See #9379.
- Add a new "Chip Tab Group" component. See #9378.
- Add new notification to Key Metrics Widget Settings Area. See #9344.
- Implement the Sign in with Google callback action. See #9338.
- Fix a bug that prevented the appearance of the Reader Revenue Manager setup banner graphic. See #9329.
- Include a "Learn more" link on the Reader Revenue Manager setup screen shown when the user doesn't have an existing publication. See #9259.
Fixed
- Only place the Reader Revenue Manager snippet on singular WordPress posts. See #9670.
- Fix typo in Key Metrics Widget. See #9614.
- Fix the issue where an extra "Failed to enable metric" modal appears when canceled in the Audience Segmentation "Top Content" custom dimension creation flow. See #9563.
- Fix dashboard error when selecting specific key metrics on the view-only dashboard. See #9548.
- Remove the “Temporarily hidden” badge when temporarily hidden tiles reappear with only a single tile visible. See #9472.
- Ensure "Add a metric" tiles are always visible on the view-only dashboard when fewer than 4 metrics are available or fewer than 8 metrics if the
conversionReporting
feature flag is enabled. See #8712.