Comments let signed-in readers discuss your articles. Readers can reply, like, sort the thread, share a comment and report comments that break your rules. Your editors moderate on the page, and your team handles reports in the dashboard.
Comments keep basic formatting such as bold, italics, lists and quotes, and can be up to 2,000 characters. Readers who aren't signed in can start writing; their comment is kept while they sign in. When someone replies to a comment, its author gets a notification in their notification bell.
Audience Operation > Experience and click New Experience.Comment and click Next Step.| Setting | What it does |
|---|---|
| Community guidelines | Shown above the comment box, in HTML, for example a short reminder with a link to your full guidelines. |
| Open in a side drawer | The page shows the first few comments, and the rest open in a drawer. |
Save Changes. The preview shows how the comments look.Readers who are not signed in see a prompt to sign up or log in before they can post.
Readers can report a comment as Identity Attack, Hate Speech, Inappropriate Language, Spam, False Information or Other.
Go to Features > Comments to see reported comments. Filter by project and by status (Unprocessed, Deleted, Hidden, Ignored or All), or search by article. Each row shows the reporter, the reported user, the comment with a link to it on the article, the reason and the status.
| Action | What it does |
|---|---|
| Delete | Deletes the comment for everyone. |
| Hide | Hides the comment from everyone. |
| Ignore | Keeps the comment and closes the report. |
| Block | Stops the user from posting comments. |
Give a member of your newsroom the Editor role for the project: go to Data Management > User Data, open their profile, click the edit icon and set Roles to Editor for the project, then save.
When editors are signed in on your site, the menu on each reader comment lets them hide, unhide or delete it. Editors can edit and delete their own comments.
Place the container where the comments should appear, usually below the article. Copy it from the experience, which fills in its ID. Without it, the comments appear at the end of the page:
<div data-exp="unis-comment" data-exp-id="EXPERIENCE_ID" data-post-id="ARTICLE_ID"></div>
data-exp-id is the ID of the Comment experience you created.data-post-id is a unique ID for the article, such as your CMS article ID. If you leave it out, the post ID your CMS prints in the page is used (a WordPress or Drupal shortlink, a JSON-LD article identifier or a Parse.ly post ID), or else the page's canonical address, so one article with several URLs keeps one thread. Use the same ID as the article's live blog data-post-id if it has one.You can also deliver the Comment experience with Orchestration. See the Comments experience and Set up experiences on your website.
Add data-ad-start, and optionally data-ad-interval, to put ad slots between comments, for example a slot after the 3rd comment and then after every 5 more:
<div data-exp="unis-comment" data-exp-id="EXPERIENCE_ID" data-ad-start="3" data-ad-interval="5"></div>
The slots are filled by BiddingStack or your own ad server, see Ads in Live Blog, Comments and Stories.
Identity, consent, audience, and subscription insights for publishers. A few emails a month, no spam.