In this article

action

jetpack_site_data_fetched

Fires after the site record was served, whether it was fetched or read from the cache. Consumers that cache anything derived from the record, such as the current plan, can refresh it here. This fires on a cached read too, so a consumer stays in step with every request that serves the record rather than only the ones that reached WordPress.com. The record is passed as an array rather than the object this method returns, so that a listener cannot mutate the instance that becomes the REST response.

Parameters

$record
array

The decoded site record from the WordPress.com `/sites/%d` endpoint.

Changelog

How to use this hook

See “How to use actions and filters to customize Jetpack”.