Jetpack Comments replaces your default comment form with a new comment system that has integrated social media login options.
We’re breaking down the barriers between you and your audience. When someone reads an article on your site and wants to comment, they can now use one of their existing social networking accounts to post a comment. No longer do they need to create yet another account and profile!
Since it will replace the default WordPress comment form, Jetpack Comments are opt-in. To activate it, just visit Jetpack → Settings → Discussion on your Dashboard and switch on “Let readers use WordPress.com, Twitter, Facebook, or Google+ accounts to comment.”
When activated, Jetpack Comments takes the place of your theme’s comment form in this nifty, sleek form:
To leave a comment, just click in the box and start typing.
After a visitor has written a comment, they will have several ways to identify themselves. A visitor can leave a comment¹ as a guest, or they can choose to use their WordPress.com, Twitter, Google+, or Facebook account. For example:
You can also change the “Leave a Reply” heading and the color scheme of the Jetpack Comments form under the Jetpack → Settings → Discussion tab.
¹ If you have “Users must be registered and logged in to comment” enabled in Settings -> Discussion, you will not be able to use the Jetpack Comment form.
Privacy Information
This feature is deactivated by default. If you ever need to deactivate it, you can toggle the Let readers use WordPress.com, Twitter, Facebook, or Google+ accounts to comment setting from the Comments section at Jetpack — Settings — Discussion.
Data Used
Site Owners / Users
This features the same data as the core WordPress commenting system: commenter’s name, email address, and site URL (if provided to the comment form), submission date/time, and IP address.
Additionally, a jetpack.wordpress.com IFrame receives the following data: WordPress.com blog ID attached to the site, ID of the post on which the comment is being submitted, commenter’s local user ID (if available), commenter’s local username (if available), commenter’s site URL (if available), MD5 hash of the commenter’s email address (if available), and the comment content.
If Akismet (also owned by Automattic) is enabled on the site, the following information is sent to the service for the sole purpose of spam checking: commenter’s name, email address, site URL, IP address, and user agent.
For toggle activity tracking (detailed below): IP address, WordPress.com user ID, WordPress.com username, WordPress.com-connected site ID and URL, Jetpack version, user agent, visiting URL, referring URL, timestamp of event, browser language, country code.
Site Visitors
This features the same data as the core WordPress commenting system: commenter’s name, email address, and site URL (if provided to the comment form), submission date/time, and IP address.
Additionally, a jetpack.wordpress.com IFrame receives the following data: WordPress.com blog ID attached to the site, ID of the post on which the comment is being submitted, commenter’s local user ID (if available), commenter’s local username (if available), commenter’s site URL (if available), MD5 hash of the commenter’s email address (if available), and the comment content.
If Akismet (also owned by Automattic) is enabled on the site, the following information is sent to the service for the sole purpose of spam checking: commenter’s name, email address, site URL, IP address, and user agent.
Activity Tracked
Site Owners / Users
The comment author’s name, email address, and site URL (if provided during the comment submission) are stored in cookies. Learn more about these cookies.
We also track when, and by which user, the feature is activated and deactivated. We also track when, and which, configuration settings are modified.
Site Visitors
The comment author’s name, email address, and site URL (if provided during the comment submission) are stored in cookies. Learn more about these cookies.
We sync all data and metadata associated with a user’s comment. We also sync options that identify whether or not the feature is activated and how its available settings are configured.
Site Visitors
We sync all data and metadata associated with a user’s comment.
Jetpack Comments
Jetpack Comments replaces your default comment form with a new comment system that has integrated social media login options.
We’re breaking down the barriers between you and your audience. When someone reads an article on your site and wants to comment, they can now use one of their existing social networking accounts to post a comment. No longer do they need to create yet another account and profile!
Since it will replace the default WordPress comment form, Jetpack Comments are opt-in. To activate it, just visit Jetpack → Settings → Discussion on your Dashboard and switch on “Let readers use WordPress.com, Twitter, Facebook, or Google+ accounts to comment.”
When activated, Jetpack Comments takes the place of your theme’s comment form in this nifty, sleek form:
To leave a comment, just click in the box and start typing.
After a visitor has written a comment, they will have several ways to identify themselves. A visitor can leave a comment¹ as a guest, or they can choose to use their WordPress.com, Twitter, Google+, or Facebook account. For example:
You can also change the “Leave a Reply” heading and the color scheme of the Jetpack Comments form under the Jetpack → Settings → Discussion tab.
Having trouble?
See our Troubleshooting Jetpack Comments page for some help.
¹ If you have “Users must be registered and logged in to comment” enabled in Settings -> Discussion, you will not be able to use the Jetpack Comment form.
Privacy Information
This feature is deactivated by default. If you ever need to deactivate it, you can toggle the Let readers use WordPress.com, Twitter, Facebook, or Google+ accounts to comment setting from the Comments section at Jetpack — Settings — Discussion.
This features the same data as the core WordPress commenting system: commenter’s name, email address, and site URL (if provided to the comment form), submission date/time, and IP address.
Additionally, a jetpack.wordpress.com IFrame receives the following data: WordPress.com blog ID attached to the site, ID of the post on which the comment is being submitted, commenter’s local user ID (if available), commenter’s local username (if available), commenter’s site URL (if available), MD5 hash of the commenter’s email address (if available), and the comment content.
If Akismet (also owned by Automattic) is enabled on the site, the following information is sent to the service for the sole purpose of spam checking: commenter’s name, email address, site URL, IP address, and user agent.
For toggle activity tracking (detailed below): IP address, WordPress.com user ID, WordPress.com username, WordPress.com-connected site ID and URL, Jetpack version, user agent, visiting URL, referring URL, timestamp of event, browser language, country code.
This features the same data as the core WordPress commenting system: commenter’s name, email address, and site URL (if provided to the comment form), submission date/time, and IP address.
Additionally, a jetpack.wordpress.com IFrame receives the following data: WordPress.com blog ID attached to the site, ID of the post on which the comment is being submitted, commenter’s local user ID (if available), commenter’s local username (if available), commenter’s site URL (if available), MD5 hash of the commenter’s email address (if available), and the comment content.
If Akismet (also owned by Automattic) is enabled on the site, the following information is sent to the service for the sole purpose of spam checking: commenter’s name, email address, site URL, IP address, and user agent.
The comment author’s name, email address, and site URL (if provided during the comment submission) are stored in cookies. Learn more about these cookies.
We also track when, and by which user, the feature is activated and deactivated. We also track when, and which, configuration settings are modified.
The comment author’s name, email address, and site URL (if provided during the comment submission) are stored in cookies. Learn more about these cookies.
We sync all data and metadata associated with a user’s comment. We also sync options that identify whether or not the feature is activated and how its available settings are configured.
We sync all data and metadata associated with a user’s comment.
Related