Jetpack Stats

Simply install the plugin and go to the Stats tab. It's that simple. If you need more help, check out this support article.

No. Jetpack Stats is a standalone plugin and works on its own. If you already run the full Jetpack plugin, Stats works there too — you don't need both, and running both will not create duplicate menus.

Yes! You can use both on your WordPress installation. The benefit of using Jetpack Stats is that you can see a snapshot of your blog's activity directly from your dashboard. If you want to use another analytics service to give you additional in-depth information, you can certainly do so.

Yes! Jetpack Stats will show you a heatmap of exactly where in the world your site has been receiving its visitors from.

Do Not Track (DNT) is a feature in web browsers and websites that asks advertisers and other web software providers not to track individuals' browsing habits. As a site owner, you can configure Jetpack Stats to honor requests from visitors who have DNT enabled, and prevent tracking of their activity (i.e., post and page views) with an easy-to-add snippet.

No. Any piece of data explicitly identifying a specific user (IP address, WordPress.com ID, WordPress.com username, etc.) is not visible to the site owner when using Jetpack Stats, so you won't be able to see which specific users or accounts viewed a particular post.

You can click the title of each feature on your stats page, and scroll to the bottom of that feature to download your stats. Simply click on the "Download data as CSV" link, and download the file to your computer.

This plugin relies on WordPress.com, a service operated by Automattic, to record visits and generate the reports shown in the Stats dashboard. The plugin does not work without it. It connects to the following external services: WordPress.com connection API (https://jetpack.wordpress.com)

• What it does: registers your site with WordPress.com and links it to your WordPress.com account. The view tracking, the reporting API and the data sync do not work without it. The dashboard interface is the exception: it loads before the site is connected, so that the plugin can offer you the connection.
• Data sent: when the site is registered, its address, home address, name, language, time zone, the path of the WordPress installation on the server, the date the site was created, the Stats site ID if the site already has one, the versions of the bundled Jetpack packages, the version of the Jetpack plugin if the site has that plugin, the plugins that use the Jetpack connection, the email address and user ID of the administrator who starts the connection, one-time secrets that WordPress.com uses to check the request, and either the WordPress.com user ID of that administrator or, if they have no connected WordPress.com account, a random identifier that is also kept in a tk_ai cookie in their browser. To approve the connection, your browser goes to this host with your WordPress user name and email address, the name, address and icon of the site, and the role you connect with. Your site then exchanges an authorization code for the tokens that sign all later requests. Disconnecting the site, or removing a user from the connection, also sends a request to this host.
• When: when you connect the site, when you approve the connection with your WordPress.com account, when you disconnect the site or remove a user from the connection, and once a day when the plugin makes sure that it can still reach WordPress.com over a secure connection.

• What it does: records a page view each time a visitor loads a page on your site. Once a day, a scheduled task also uses this address to report the state of your site, so that WordPress.com can keep the service working with the software your site runs.
• Data sent: for a page view, the page viewed, the referring URL, the visitor's IP address, the user agent, and your site ID. For the daily report, your WordPress and PHP versions, whether the site is public, whether it is served over HTTPS, whether it can reach WordPress.com over a secure connection, the site language and character set, whether the site is part of a network, the names of the active plugins and must-use plugins, the size of the uploads folder, the first two groups of digits of the server IP address, the versions of the bundled Jetpack packages, the plugins that use the Jetpack connection, and whether the plugin found a problem with the connection. Your visitors are not part of the daily report.
• When: a page view is recorded on every front-end page view. The daily report is sent by a scheduled task, and not more than once every 23 hours.

• What it does: loads the small JavaScript file that sends the view-tracking request above from the visitor's browser.
• Data sent: no data is sent when the file is downloaded; it is a static script served from Automattic's CDN.
• When: on every front-end page view.

• What it does: returns the aggregated statistics displayed in your Stats dashboard.
• Data sent: your site ID and the report parameters (date ranges, metric requested). Requires an authenticated WordPress.com connection.
• When: whenever you open the Stats dashboard or load a report.

• What it does: keeps a copy of your site's content and settings on WordPress.com. The reports need it to show post titles, authors and categories, and the service needs it to know how your site is set up. If your site cannot use this address, the same data goes to https://jetpack.wordpress.com/xmlrpc.php instead.
• Data sent: your posts, pages, other post types and media, with their text, authors, categories, tags and publication state; your comments, with the name, email address and website that the commenter gave; your users, with their user names, email addresses, display names, roles and permissions, but never their passwords; your site settings, menus and theme; and the list of plugins and themes on the site with their versions and available updates.
• When: continuously, as content and settings change, and in full when the site connects or when WordPress.com has to rebuild its copy.

• What it does: serves the JavaScript, styles, and icons that render the Stats dashboard interface in your WordPress admin.
• Data sent: no personal data; these are static front-end assets served from Automattic's CDN.
• When: whenever you open the Stats dashboard.

• What it does: records how people who can open the plugin screens use them, so that Automattic can improve the plugin. This is separate from your site statistics.
• Data sent: the name of the action taken, your site ID, your WordPress.com user ID and username, the browser user agent, the browser language, and the IP address of the request. If the person is not connected to a WordPress.com account, a random identifier is used in place of the user ID and username, and it is stored in a tk_ai cookie in their browser.
• When: only while a logged-in user with access to the plugin screens uses them in the WordPress admin. You control who has that access through the Stats settings. Nothing is recorded for your site visitors.

Jetpack Stats is developed in the open. The plugin, every bundled automattic/jetpack-* package, and the build tools that produce the released package are all in the Jetpack monorepo:

• Plugin source: Automattic/jetpack/projects/plugins/stats
• Stats collection and reporting: projects/packages/stats
• Stats dashboard integration: projects/packages/stats-admin
• Monorepo and build tools: Automattic/jetpack

• Odyssey Stats application: Automattic/wp-calypso/apps/odyssey-stats
• Shared Stats interface it is built from: Automattic/wp-calypso/client/my-sites/stats
• Repository and build tools: Automattic/wp-calypso