Track Which Blog Posts Drive the Most Signups

Your blog is getting traffic. Three posts are pulling in visitors from search and social, and you are writing more each week. But when someone clicks "Join Waitlist" after reading your schema-on-write explainer, your dashboard counts it as a signup. It does not tell you it came from that post.

Your Analytics tab shows Top Pages with visit counts per URL. You can see /blog/guides/schema-on-write had 80 visits this week. What you cannot see is how many of those 80 people signed up.

Closing that gap takes two steps: tagging your CTAs with either UTM parameters or a trackEvent() call, and reading the results in your Analytics tab.

What You Get Without Extra Setup

When the OperatorStack script tag is on your blog, it tracks every pageview. The Analytics tab shows:

• Top Pages -- visits per URL, so you can see /blog/how-to/set-up-waitlist had 200 visits and /blog/guides/schema-on-write had 80
• Referral sources -- where those blog visitors came from (search, Twitter, newsletters)
• Unique visitors -- how many distinct people hit each post

This is enough to know which posts attract an audience. It does not tell you which posts convert that audience into signups.

Approach 1: UTM Parameters on CTA Links

The simplest approach requires no code changes to your blog. Add UTM parameters to any link that points visitors toward your signup flow.

If your blog post ends with a link to your landing page:

<!-- Without tracking -->
<a href="https://yoursite.com">Start for Free</a>

<!-- With UTM tracking -->
<a href="https://yoursite.com?utm_source=blog&utm_content=schema-on-write&utm_medium=cta">
  Start for Free
</a>

When a visitor clicks that link and signs up, the signup is attributed to utm_source=blog in your Analytics tab. The utm_content value (the post slug) appears under Traffic Sources so you can compare conversions per post.

You can also use this pattern for in-line text links within the post body, not just the closing CTA.

Approach 2: Custom Events on CTA Clicks

UTM parameters require a page navigation to capture attribution. If your blog posts have a waitlist widget on the page itself (not a link to a separate landing page), use trackEvent() to fire a custom event when the visitor clicks the signup CTA.

Add the script tag to your blog layout if it is not there already:

<script src="https://operatorstack.dev/os.js" data-project="pk_your_key" defer></script>

Then attach an event handler to your CTA button:

await OperatorStack.ready;

document.querySelector("#blog-cta").addEventListener("click", () => {
  OperatorStack.trackEvent("blog_cta_click", {
    post: "guides/schema-on-write",
    category: "guides",
    keyword: "schema-on-write",
  });
});

This fires the event the moment someone clicks, regardless of whether they complete the signup. You get click intent data even from visitors who abandon the form.

To track completed signups specifically, fire a second event inside the signup callback:

const result = await OperatorStack.joinWaitlist({
  email: emailInput.value,
});

if (result.success) {
  OperatorStack.trackEvent("blog_signup_completed", {
    post: "guides/schema-on-write",
    category: "guides",
  });
}

Both events appear in the Events section of your Analytics tab with their properties.

Using the Post URL Automatically

If you have multiple blog posts using the same template, read the post slug from the URL rather than hardcoding it:

await OperatorStack.ready;

const postSlug = window.location.pathname.replace("/blog/", "").replace(/\/$/, "");

document.querySelector("#blog-cta").addEventListener("click", () => {
  OperatorStack.trackEvent("blog_cta_click", { post: postSlug });
});

Add this once to your blog post layout component (Nuxt, Next.js, Astro, or plain HTML template) and every post automatically tags its own clicks.

Approach 3: Combining Both

For the most complete picture, use UTM parameters on outbound links and trackEvent() on in-page CTAs. The two approaches track different moments:

The combination tells you which posts attract browsers vs. which ones convert browsers into signups.

Reading the Results

Common Setup for Nuxt Content Blogs

If your blog runs on Nuxt Content (the same stack this blog uses), add the script tag to your default layout and the event handler to a composable:

// composables/useBlogTracking.ts
export function useBlogTracking() {
  const route = useRoute();

  onMounted(async () => {
    if (!window.OperatorStack) return;
    await window.OperatorStack.ready;

    const postSlug = route.path.replace("/blog/", "").replace(/\/$/, "");

    document.querySelector("#blog-cta")?.addEventListener("click", () => {
      window.OperatorStack.trackEvent("blog_cta_click", { post: postSlug });
    });
  });
}

Call useBlogTracking() in your blog post layout component, and every post on the site gets automatic CTA click tracking with zero repeated code.