Ghost powers tens of thousands of independent publications, and every one of those sites has the same problem: adding a small piece of live data — how many people are reading, which countries visit, where people click — usually means installing an integration you'll have to maintain, update and trust.
No integration to configure. Ghost renders raw HTML and script tags from Code injection and from an HTML card, so there is nothing to install and no third party in the loop. Every widget below is one snippet, pasted in once. Pick one and the page tells you the exact menu path for Ghost, the gotchas, and what to do if you're on an older theme or a page builder.
People choose Ghost because it's fast and focused on publishing. Heavy integrations undo that. A FeedPulse widget is one small async script, pasted into Code injection or an HTML card, that loads after your post is already readable. There's no integration to configure and no extra account for your members.
Ghost has two places for code. Settings → Code injection adds a script to the Site Header or Site Footer of every page, which suits sitewide widgets such as a footer counter or the heatmap. An HTML card in the editor places a widget inside a specific post or page, which suits a GitHub badge in a project post or a countdown in an announcement. Post-level code injection sits in between, for one post only.
Goes in Settings → Code injection → Site Header, because it has to load on every page before your clicks happen, and it renders nothing visible.
Goes in Settings → Code injection → Site Footer, because an all-time total is a footer artefact — nobody scrolls up to check it.
Goes in Site Footer injection, or an HTML card in a recurring spot, because local conditions are a glanceable sidebar item, not a content block.
Goes in Site Footer injection, or an HTML card in a recurring spot, because a ticker reads best as a persistent strip beside the content.
Goes in Site Footer injection, or an HTML card in a recurring spot, because quotes are reference data — visible, but never competing with the article.
Goes in an HTML card in the editor, because a countdown works above the fold on the page that's actually selling the thing.
Goes in an HTML card in the editor, because it's the most visual widget you have, so it earns a spot in the content rather than the chrome.
Goes in an HTML card under the post body, or post-level injection, because it belongs directly under the article body, which means the blog-post template rather than a global widget area.
Goes in Settings → Code injection → Site Footer, because trust badges are read at the moment of hesitation, which is usually the footer.
Goes in Site Footer injection, or an HTML card in a recurring spot, because a live pill is only useful if it's visible before the visitor decides to leave.
Goes in Site Footer injection, or an HTML card in a recurring spot, because the whole point is catching someone while you're actually live.
Goes in an HTML card in the editor, because it's social proof for a specific project, so it goes inline next to what it's vouching for.
Goes in an HTML card in the editor, because it belongs beside the install command, in the post or docs page that teaches it.
Goes in Site Footer injection, or an HTML card in a recurring spot, because a live member count is a standing invitation, so it should follow the reader down every page.
Goes in Settings → Code injection → Site Footer, because it's a floating bubble, so it only needs to exist once per page and should load last.
Goes in Settings → Code injection → Site Header, because one paste in the head gives every page its own score — the badge auto-detects which page it's on.
Goes in Settings → Code injection → Site Footer, because a ranked country list belongs at the bottom, where its lazy-loaded flags stay below the fold.
Goes in an HTML card in the editor, because a live count only changes behaviour when it sits in the same line of sight as the price or the button.
Scripts in the Site Header are handled before the page paints; scripts in the Site Footer run after. FeedPulse snippets are async either way, but the footer box is the better default for anything visible. Only sitewide tracking-style tools such as the heatmap need the header.
If you add a snippet directly to a theme's .hbs files, the next theme update or switch removes it silently. Code injection is stored in your Ghost settings, not in the theme, so it survives updates. On Ghost(Pro)'s entry plan you can't upload custom themes anyway, so code injection is the reliable route.
Newsletters and blogs on Ghost get the most from the comments widget for open discussion beside members-only comments, the flag counter and visitor globe for showing an international readership, the Discord widget for communities, and the verified traffic badge for publications that sell sponsorships.
Ghost lets you limit posts, or the part of a post after the public preview, to members or paying subscribers. A widget in an HTML card inside the restricted part only shows to people who can see that content, while Site Footer code injection runs on every page, public ones included. Choose the location based on who should see the widget.
Delete the line from Code injection or remove the HTML card, then save. Nothing else in your publication depends on it.
Code injection is available on every Ghost(Pro) plan and on self-hosted Ghost, both sitewide (Settings → Code injection) and per post. HTML cards are available in the editor on all plans too. The main limit is on Ghost(Pro)'s entry plan, which doesn't allow custom themes, so use code injection or HTML cards rather than editing theme files.