Fires after the WooCommerce Analytics package is initialized
woocommerce_analytics_init
woocommerce_analytics_initwoocommerce_analytics_initFires after the WooCommerce Analytics package is initialized
jetpack_blaze_dashboard_config_dataFilter to allow modification of the Blaze dashboard config data.
jetpack_public_js_script_dataFilter the public script data. See the docs for `jetpack_admin_js_script_data` filter for more information.
jetpack_admin_js_script_dataFilter the admin script data. When using this filter, ensure that the data is added only if it is used by some script. This filter may be called on almost every admin page load. So, one should check if the data is needed/used on that page. For example, the social (publicize) data is used only on Social admin page, Jetpack settings page and the post editor. So, the social data should be added only on those pages.
jetpack_full_sync_configFires when a full sync is cancelled.
jetpack_has_login_abilityFilter which provides Jetpack’s decision as to whether the current requestor can attempt logging in. Example: When Jetpack’s Brute Force Login Protection is active, this filter will return false if the user is currently locked out.
jetpack_sync_filtered_hpos_order_dataFilter the order data before syncing.
jetpack_table_checksum_force_enable_woocommerce_hposOn WordPress.com, we can’t directly check if the site has support for WooCommerce HPOS tables. Having the option to override the functionality here helps with syncing WooCommerce HPOS tables.