Connecting your own analytics

Bloggable counts views and visitors for every blog on its own, with no cookies and nothing for you to set up. This article is about the other thing: putting your own analytics tag on a blog, so it appears in the dashboard your team already reports from.

The two don't compete. Adding your own tag doesn't switch Bloggable's built-in numbers off, and the two will never quite agree — see Analytics — views and visitors for why that's normal.

Which one should you use?

If your marketing team already lives in GA, use GA4. If you're starting fresh and don't want to run a cookie banner, Plausible and Fathom are both cookieless and neither needs one.

Where to set it up

Analytics is set per blog, because each blog is a separate site with its own address and its own property.

Two routes to the same screen:

• Blog settings → Analytics — for one blog you're already working on.
• Integrations → Analytics (main nav) — for the account view, with every blog in one list.

Each provider is its own row. Pressing Connect opens the same form either way, so use whichever you're nearest.

Google Analytics 4

1. In Google Analytics, open Admin → Data streams and select the web stream for this site (or create one, using your blog's public address).
2. Copy the Measurement ID at the top right. It starts with G- followed by letters and numbers.
3. In Bloggable, pick Google Analytics 4, paste the ID, and press Save analytics.

Bloggable loads gtag.js and sends a page view on every public page of that blog.

You will need a cookie consent banner. GA4 sets cookies, which in the UK and EU means you need consent before it loads. Bloggable doesn't ship a consent banner, so this is yours to add — or pick Plausible or Fathom instead, which don't need one.

Plausible

1. In Plausible, add the site if you haven't already. The domain you enter there is the identifier.
2. In Bloggable, pick Plausible and enter that same domain — no https://, no trailing slash, no www.
3. Save.

Self-hosting Plausible? Fill in the optional Self-hosted script address with your instance's origin, e.g. https://stats.example.com. It must be https — a plain http address would make the whole page mixed-content and browsers would block the script anyway.

Fathom

1. In Fathom, open Settings → Sites and find the site.
2. Copy the Site ID — the short block of capital letters in the tracking snippet, usually eight characters.
3. In Bloggable, pick Fathom, paste the Site ID, and save.

Respect Do Not Track

An optional switch under the ID field. With it on, the tag isn't loaded at all for visitors whose browser sends a Do Not Track header — not loaded and then told to stay quiet, genuinely not loaded.

It's off by default because DNT is sent by a small and unrepresentative slice of browsers, and turning it on means those visits are missing from your numbers entirely. Turn it on if you'd rather honour the signal than count the visit.

What gets tracked, and what doesn't

Tracked: every public page of that blog — the homepage, each post, category and tag archives, and the search page.

Not tracked:

• The Bloggable app itself. Your own admin sessions never touch your analytics.
• Previews rendered inside the dashboard. The blog homepage preview and the theme previews load your blog in an iframe, and the tag deliberately skips embedded loads — otherwise clicking around your own settings would inflate your traffic.
• Anything, if you've switched the integration off or cleared the provider.

Turning it off

Pick None in the provider list and save. The tag stops loading on the next page view. Your historical data stays with Google, Plausible or Fathom — Bloggable never had it.

Troubleshooting

"I saved it but nothing shows up." Open your blog's public address in a private window and check the realtime view in your analytics tool. Give it a minute — GA4's realtime report can lag.

Still nothing. Check the ID itself. A Measurement ID (G-…) is not the same as a Tag ID or a Property ID, and pasting a Google Tag Manager container (GTM-…) won't work — Bloggable loads GA4 directly, not through Tag Manager.

"It works on the homepage but not on posts." That shouldn't happen — the tag is loaded once for the whole blog. If you're seeing it, get in touch with the blog address.

An ad blocker. Blockers stop GA4, Plausible and Fathom for a meaningful share of visitors. This is the main reason a third-party tool reports fewer views than Bloggable's own count, which is measured server-side and isn't blocked.