Debug Disqus in Chrome DevTools

What Disqus traffic looks like

Disqus identifies each install by a forum shortname, and that shortname is the subdomain the embed loads from. It is the reason the extension matches a Disqus subdomain wildcard rather than a single fixed host.

Endpoint pattern

The comment thread loads from <shortname>.disqus.com/embed.js, where <shortname> is the forum's Disqus shortname; listing and archive pages load disqus.com/count.js to render comment counts; the thread itself renders inside an iframe served from disqus.com/embed/comments/

Transport

Script load plus a cross-origin iframe. The page identity is passed to the iframe in its URL rather than in a POST body

Config object

window.disqus_config = function () { this.page.url = …; this.page.identifier = …; }, read by embed.js when it initializes

Key parameters

On the embed URL: f is the forum shortname · t_u the page URL · t_d the page title · t_i the thread identifier. These four are what decide which thread a visitor sees

A typical embed request, with the thread identity in the query:

https://disqus.com/embed/comments/?base=default
  &f=example-forum
  &t_u=https%3A%2F%2Fexample.com%2Fblog%2Fpost-slug
  &t_d=Post%20title
  &t_i=post-1042

Debugging Disqus with Event Watcher

• No dedicated parser. Requests are matched by hostname, named Disqus, badged with the Widgets category, and shown with their parsed query parameters.
• The parsed query on the embed request is the whole diagnosis for the most common Disqus problem: it shows the exact t_u and t_i values the page handed over, which is what Disqus keyed the thread on.
• The shortname in the subdomain tells you which Disqus forum is installed, without opening the Disqus admin.
• Worth knowing when auditing: on ad-supported Disqus plans the embed also loads sponsored content, so ad-tech requests appear in the same stream underneath the comment area. A comment widget is a common way for advertising traffic to reach a page nobody thinks of as an ad surface.

Disqus and consent

Event Watcher checks Disqus against the functional consent category.

Comments are functional. The ad-tech that arrives with a free-tier Disqus embed is not, and it is not covered by a functional classification just because the widget that loaded it is. Load the page with marketing consent denied and look at what still fires alongside the embed. If advertising requests appear, the honest fix is to gate the embed itself, since the site does not control what runs inside a third-party iframe.

Common debugging scenarios

• Comments disappeared after a URL change. Check t_i on the embed request. With no page.identifier set, Disqus keys the thread on the URL, so any change to the URL starts an empty thread.
• The same comments appear on two different pages. The opposite failure: a hardcoded or templated identifier shared across pages. Compare t_i between the two.
• Comment counts do not update. Confirm disqus.com/count.js is requested on the listing page. It is a separate script from the embed and is often left out.
• Unexpected advertising requests on an article page. Group by Endpoint and check what loads at the same time as the Disqus embed.
• Which forum is installed? Read the subdomain on the embed.js request, or the f parameter on the embed URL.