IntegrationsTracking & Pixels

Tracking & Pixels

Add third-party tracking to your public pages — a Google Analytics (GA4) Measurement ID, pixels and tags by ID (Meta Pixel, TikTok Pixel, Google Tag Manager, LinkedIn Insight Tag, Snap, X, Plausible, Fathom, Microsoft Clarity, Hotjar), custom head code on paid plans, and per-landing-page tracking code. Where each one runs, what gets stripped, and consent.

Ways to add tracking

Nashra reports on your traffic, email, and subscribers in Insights with nothing to set up. Add third-party tracking only when you specifically want another tool watching your public pages too — for ad retargeting, conversion tracking, or a marketing stack you already use.

Site-wide tracking lives in Settings → Integrations, in three sections. Landing pages also have their own per-page field.

WhereWhat you addRuns onPlans
Google AnalyticsSettings → IntegrationsA GA4 Measurement IDYour Hub and public pagesEvery plan
Pixels and tagsSettings → IntegrationsA vendor ID — Nashra builds the snippetYour Hub, posts, landing pages, and resourcesEvery plan
Custom codeSettings → IntegrationsYour own <head> HTMLYour Hub, posts, landing pages, and resourcesPaid plans
Tracking codeThe landing page editorYour own <head> HTMLThat one landing pagePaid plans

Start with Pixels and tags if your tool is on the list — it's the simplest and works on every plan. Use Custom code for anything else, and a landing page's Tracking code for a snippet that belongs to one campaign page only.

Changes in Settings → Integrations are saved from the bar at the bottom of the page — Save or Discard. Saving needs Full access on your team (or ownership of the workspace).

Google Analytics

Open Settings → Integrations

Find the Google Analytics section at the top.

Paste your Measurement ID

Enter your GA4 Measurement ID — it looks like G-XXXXXXXXXX. Nashra checks the format before saving.

Save

Click Save. Nashra adds GA4 to your Hub and public pages automatically — there's no code to paste anywhere.

Pixels and tags

Give Nashra an ID and it adds the vendor's official snippet to your Hub, posts, landing pages, and resources. You never paste JavaScript, so there's nothing to break — and it's available on every plan, including Free.

Click Add

In the Pixels and tags section, click Add and pick a provider.

Paste the ID

Paste just the ID from your provider's dashboard — not the whole snippet. Nashra checks it against that provider's format and tells you if it doesn't look right.

Save

Click Save. Add as many providers as you like; hover a row and click × to remove one.

ProviderWhat to pasteLooks like
Google Tag ManagerContainer IDGTM-XXXXXXX
Meta PixelPixel ID1234567890123456
TikTok PixelPixel IDCXXXXXXXXXXXXXXXXXXX
LinkedIn Insight TagPartner ID1234567
Snap PixelPixel ID00000000-0000-0000-0000-000000000000
X PixelPixel IDo1abc
PlausibleSite domainexample.com
FathomSite IDABCDEFGH
Microsoft ClarityProject IDabcdefghij
HotjarSite ID1234567

Each snippet loads the provider's standard page-view tracking. For custom events or anything the ID alone can't configure, use Google Tag Manager here and set it up inside GTM, or use Custom code.

Custom code

For tools that aren't in the list, paste your own snippet into Custom code. It goes into the <head> of your Hub, posts, landing pages, and resources, for every visitor.

Custom code is available on paid plans (Newsletter and Publisher). On Free, the field is locked with an Upgrade button — Pixels and tags still work. If a workspace moves back to Free, its saved custom code stops running on the live site.

When you save, Nashra keeps only what belongs in a tracking snippet and strips everything else:

  • Kept — <script> tags, either inline or loaded over https from a well-known analytics or advertising vendor (Google, Meta, TikTok, LinkedIn, Snap, X, Pinterest, Plausible, Fathom, Cloudflare, Clarity, Hotjar, Matomo Cloud, HubSpot, Segment, Amplitude, Mixpanel, and a few others); verification <meta> tags; no-script image pixels; and preconnect / dns-prefetch hints.
  • Stripped — anything else, including <iframe>, <form>, <style>, stylesheets, <a> links, visible text, comments, inline event handlers, and javascript: or data: URLs.

If a script disappears after you save, check that it loads over https from its vendor's own domain. Custom code is limited to 20,000 characters.

Per-page tracking code

Each landing page has its own Tracking code for a snippet that belongs to one campaign — a conversion pixel for a single promotion, or a verification tag only that page needs. It runs on top of your site-wide tracking, not instead of it.

Open the landing page

In the landing page editor toolbar, click the Tracking code icon.

Paste your snippet

Paste the HTML your provider gave you. This applies to this page only — site-wide pixels belong in Settings → Integrations, where they also cover your Hub, posts, and resources.

Save

Click Save. The same rules as Custom code apply: scripts, verification meta tags, and no-script pixels are kept; anything else is stripped.

Per-page tracking code is on paid plans and limited to 10,000 characters per page. On Free, the dialog shows an Upgrade button instead of Save.

Nashra's own reader-level tracking only follows visitors who accept it on your public site. That's why some details in Insights — like which site first sent a new subscriber — say how many people they cover (Known for 40 of 120) instead of counting everyone.

Third-party tools are your responsibility.

Adding Google Analytics, a pixel, or custom code means that provider collects data on your visitors. Depending on where your readers are, you may need a cookie or consent notice that covers it, and your privacy policy should disclose what you've added. Check each provider's own requirements before you publish.

What's next