Filter whether test (preview) submissions should trigger the notification email.
jetpack_forms_send_test_feedback_email
jetpack_forms_send_test_feedback_email-
filter -
filter jetpack_forms_test_subject_prefixFilter the subject prefix applied to test (preview) feedback emails.
-
filter jetpack_stats_abilities_wpcom_statsFilters the WPCOM_Stats instance used by the Stats abilities.
-
filter jetpack_wp_abilities_should_registerFilters whether an Abilities API category or ability should be registered. Returning false from any filter callback skips the registration, which is how consumers gate rollout per-site, per-user, or per feature flag. The filter fires once per category and once per individual ability, so callbacks can allow-list or deny-list by `$slug`.
-
filter jetpack_wp_abilities_enabledFilters whether Jetpack Abilities API registration should run. Default `false`. Return `true` to enable registration for this request, typically gated on a site option, user capability, or feature flag to support staged rollout.
-
filter jetpack_account_protection_send_auth_emailFilters whether the Account Protection verification email should be handled externally. When the filter returns a truthy value, the default WPCOM API email send is skipped, allowing sites to deliver the email locally (e.g. via `wp_mail()`).
-
filter jetpack_block_notes_has_paid_ai_planFilter whether the site has a paid AI plan.
-
filter jetpack_sso_accept_wpcom_2faFilter whether to accept WordPress.com 2FA in place of a local Two-Factor prompt during SSO login. Return false to always require the local Two-Factor prompt, even when the user has completed 2FA on WordPress.com.
-
filter jetpack_sync_actor_dataFilters the actor data attached to sync events. Actor data identifies who or what triggered a sync event (user info, request context, MCP client details, etc.) and is sent alongside every event to WordPress.com.
Jetpack Developer Resources 