Category: Newsletters

ConvertKit assigns every account a public creator profile by default. It lives at convertkit.com/creators/your-username, displays your name, bio, subscriber count (if you allow it), and links to your newsletter and products.

Most operators don’t know it exists until someone finds it through search or the ConvertKit creator directory. Whether that’s helpful or harmful depends on what you’re building and how you talk about your list size.

What the profile shows and where it appears

The profile page includes your account display name, a short bio (pulled from your account settings), your subscriber count (optional), and any public forms or products you’ve published. ConvertKit indexes these pages in its own creator directory, and Google indexes them too.

If you’ve enabled the subscriber count display, the number updates in near-real-time. That’s useful if you want social proof — “Join 12,483 readers” — but problematic if you’re pitching sponsors with inflated figures or prefer to keep growth private.

The profile also surfaces every public landing page and form you’ve created. If you’ve launched a lead magnet, a product page, or a public archive, those URLs appear here. Retired campaigns stay visible unless you archive or delete the form.

When public profiles help

If you’re building in public or want organic discovery, the profile acts as a lightweight portfolio. Other ConvertKit users browsing the directory can find you by topic, and the page ranks for branded searches (your name plus “newsletter” or “ConvertKit”).

It’s also a clean fallback link for podcast bios, Twitter profiles, or guest-post bylines when you don’t want to send people directly to a landing page. The profile gives context without forcing a signup decision immediately.

Some operators use the subscriber count as a trust signal. If you’re at 5,000+ subscribers and competing for attention in a crowded niche, showing the number can differentiate you from newcomers. Just be prepared for that number to become your public baseline — it’s harder to hide later if growth stalls.

When to turn it off

Go to Settings → Public profile in your ConvertKit dashboard (checked November 2026). You can disable the entire profile or just hide the subscriber count.

Turn it off if:

• You’re pitching sponsors and don’t want them cross-checking your claimed list size against a public number.
• You run multiple projects under one ConvertKit account and don’t want them visibly linked.
• You’ve archived old landing pages or lead magnets and don’t want them resurfacing in search results.
• You’re in a competitive niche and prefer not to telegraph your audience size to competitors.

Disabling the profile removes it from the ConvertKit directory and blocks the public URL. Google may take a few weeks to drop the cached page, but it won’t re-index once the profile is private.

The non-obvious detail: landing page visibility

Even if you disable your creator profile, individual ConvertKit landing pages remain public and indexed unless you manually set them to private or delete them. The profile just aggregates them in one place.

If you’ve launched a one-time lead magnet, promoted it, then moved on, that page is still live and findable. Check your Forms & Landing Pages list in ConvertKit and archive anything you’re no longer promoting. Archived forms stop accepting signups but don’t disappear from search immediately — you’ll need to wait for Google to drop them, or redirect the URL if you control a custom domain.

This matters most if you’ve tested multiple hooks, offers, or positioning statements. A public profile or indexed landing page can contradict your current messaging, especially if you’ve pivoted topics or renamed your newsletter.

If you want one central place for people to find you — and you’re comfortable with transparency around list size and past campaigns — leave the profile on. If you prefer control over what’s public and when, disable it and manage landing-page visibility manually.

Got a ConvertKit setup question or a feature you’d like explained? Reply to this email — we’ll cover it in a future issue.

Most solo operators install a newsletter form once and never revisit the structure. You embed a widget, ask for name and email, and call it done. But form layout—single-page versus multi-step—affects conversion, completion rate, and the quality of subscribers who land in your list.

The choice isn’t about fashion. It’s about friction, perceived commitment, and where in your funnel the form appears. Pick wrong and you’ll either scare off casual readers or attract subscribers who never open.

Single-page forms: when to use them

A single-page form shows every field at once. Name, email, optional checkboxes for topics or frequency, and a submit button. No steps, no progress bar, no “Next.”

This format works best when:

• The visitor already trusts you. They’ve read three articles, listened to a podcast episode, or followed a recommendation. They know what they’re signing up for.
• You ask for two fields or fewer. Email-only forms convert highest. Add name and you drop 10–15 percent. Add more and you lose another chunk with each field.
• The form lives in high-intent locations. Bottom of a long-form post, dedicated landing page after a lead magnet, footer of a resource library. Anywhere the reader has already decided.

Single-page forms lose when you try to collect preference data up front—content topics, send frequency, job title. Every visible field adds perceived effort before the visitor commits.

Multi-step forms: the delayed-ask advantage

A multi-step form splits the signup into two or more screens. Step one asks for email. Step two collects name, preferences, or segmentation tags. Some platforms let you add a third step for confirmation or a welcome offer.

Multi-step forms convert better in two scenarios:

• Cold traffic. A visitor lands on your site from search, a social post, or a backlink. They don’t know you yet. Asking only for email on step one lowers the perceived cost. Once they’ve typed their address and hit “Next,” completion bias pulls them through step two.
• You need segmentation data but don’t want to sacrifice top-of-funnel conversions. Asking for industry, company size, or content preferences on step one scares people off. Asking on step two—after they’ve already given their email—gets you the data without the initial friction.

Beehiiv, MailerLite, and ConvertKit all support multi-step forms natively. You define the fields for each step, set transitions, and embed the widget. The platform handles state between steps and writes all fields to the subscriber record once they complete.

Where multi-step fails: anywhere the visitor has already decided. If someone clicks “Subscribe” on your About page or downloads a lead magnet, adding steps just annoys them. Single-page wins there.

What breaks when you mix formats wrong

Install a single-page form with five fields in your blog sidebar and watch your conversion rate drop to single digits. Visitors skim, see the wall of inputs, and bounce.

Use a multi-step form at the end of a pillar post and you’ve added unnecessary clicks. The reader already spent ten minutes with your content—they’ve decided. Making them tap “Next” between email and name just costs completions.

Another failure mode: platforms that don’t persist partial data between steps. If a visitor enters their email on step one, closes the tab, and returns later, some tools lose the session. They start over. That’s a lost subscriber. MailerLite and Beehiiv both handle session persistence well; older WordPress plugins sometimes don’t.

One non-obvious tip: test button copy on step one

Most multi-step forms use “Next” or “Continue” on the first screen. Try “Subscribe” or “Get access” instead. It sets expectations and reduces drop-off between steps. Visitors know they’re committing to a subscription, not just filling out a survey.

The opposite works too: if your audience is skeptical or privacy-conscious, softer copy like “Continue” or “Almost there” performs better than “Subscribe now.” Test both against your baseline.

Want more tactical breakdowns like this? Subscribe to One Two Three Send—we cover tools, workflows, and the mechanics that actually move your business forward.

Heads up — some links in this article are affiliate links. If you sign up through them, we may earn a small commission at no extra cost to you. We only recommend tools we use ourselves.

Every quarter, email service providers and marketing blogs publish open-rate benchmarks: “SaaS newsletters average 22%,” “B2B sees 18%,” “media hits 25%.” Solo operators compare their own numbers to these figures, panic when they fall short, and chase tactics that don’t address the real problem.

Industry benchmarks are nearly useless for individual operators because they aggregate data across lists with wildly different histories, engagement patterns, and technical configurations. A brand-new list of 500 highly-engaged subscribers will perform nothing like a three-year-old list of 50,000 where half haven’t opened in six months. Comparing your 19% open rate to a industry average of 22% tells you nothing about whether your content works or your list is healthy.

What benchmarks hide

Published benchmarks rarely disclose how they handle Apple Mail Privacy Protection, which pre-fetches email content and inflates open rates for some senders while masking real opens for others. A newsletter platform might report that media newsletters average 25% opens, but if 40% of that list uses Apple Mail, the real engaged-open rate could be 15% or 35%—you can’t tell from the top-line number.

List age matters more than industry. A six-month-old list of operators who signed up for a lead magnet last week will open at 40%. A four-year-old list where you haven’t pruned inactive subscribers in two years might sit at 12%, even if both lists cover the same topic. Benchmarks don’t segment by list tenure, acquisition source, or cleanup cadence, so they flatten signal into noise.

Engagement history compounds over time. If you’ve been sending consistently valuable content for a year, your open rate should climb as your list self-selects for people who actually want to hear from you. If you’ve been inconsistent or changed topics mid-stream, your rate will sag regardless of industry. Benchmarks assume a static audience; real lists evolve.

What to track instead

Compare your open rate to your own trailing average, not an industry figure. If you normally sit at 28% and this week hit 22%, investigate the subject line, send time, or whether you skipped a week and lost rhythm. If you’re steady at 19% for six months and your click rate is climbing, your open rate isn’t the problem—your subject lines might be honest rather than clickbaity, and that’s fine.

Segment by subscriber cohort and measure each group’s trend. New subscribers (0–30 days) should open at a higher rate than your list average. If they don’t, your onboarding sequence or acquisition source is weak. Subscribers older than 180 days who haven’t opened in 90 days are dead weight; archive or re-engage them, then watch how your open rate moves when you remove that drag.

Track click-to-open rate instead of raw opens. If 25% of people open and 8% click, your click-to-open rate is 32%—meaning nearly a third of people who opened took action. That ratio tells you whether your content delivers on the subject line’s promise. A falling open rate with a rising click-to-open rate means you’re getting better at writing for the people who care, even if fewer people care overall. That’s often a healthy sign for a maturing list.

When benchmarks do matter

Benchmarks become useful when you control for list age, acquisition source, and privacy configuration—and compare only to operators with similar profiles. If you run a six-month-old SaaS newsletter, acquired entirely through content upgrades, and you’re seeing 18% opens while a peer with the same profile sees 32%, then you have a real gap to investigate. But that’s not an industry benchmark; it’s a matched cohort.

Platform-level data can surface technical issues. If Beehiiv reports that lists using custom domains see 5% higher placement rates than shared domains (checked November 2026, Beehiiv deliverability guide), that’s actionable—you’re comparing apples to apples within one platform’s infrastructure. But cross-platform averages wash out those details.

Use benchmarks to spot outliers in your own data, not to judge performance. If your Monday sends consistently open 10 percentage points higher than Thursday sends, and industry data shows no day-of-week effect, you’ve found a scheduling advantage specific to your audience. The benchmark didn’t tell you what to do—it just confirmed your pattern isn’t universal, so you should exploit it.

Want more on what to measure when aggregates don’t help? Reply and tell us which metric you’re struggling to interpret—we’ll cover it in a future issue. Or subscribe below if this landed in a forward.

The real benchmark is last month

If your open rate is climbing month-over-month, your click rate is stable or rising, and your unsubscribe rate stays below 0.5% per send, you’re doing fine—regardless of whether you’re at 15% or 35%. Industry averages can’t account for your list’s unique composition, your content’s value density, or the trust you’ve built over time. Track your own trend, segment ruthlessly, and ignore the rest.

Heads up — some links in this article are affiliate links. If you sign up through them, we may earn a small commission at no extra cost to you. We only recommend tools we use ourselves.

Open any newsletter and you’ll see a row of links at the top: About, Archives, Unsubscribe, Sponsor, maybe a social icon or two. Most operators add them once during template setup and never look back. But header link behavior is different from in-body links—and the structure you pick changes what readers do next.

Where header links sit and what they do

Newsletter headers typically live in one of three places: above the logo, between the logo and the first headline, or in a thin utility bar at the very top. Email clients render them as live links in HTML emails; plain-text newsletters sometimes repeat them as a footer block instead.

The most common links are:

• View in browser — lets readers escape rendering problems or forward the issue
• Archives — index of past issues, often the second-highest traffic driver after the homepage
• Unsubscribe — required under CAN-SPAM (checked October 2026, FTC CAN-SPAM guidance), though most platforms auto-inject it in the footer
• Sponsor / Advertise — pitch page for potential advertisers
• About / Start here — intro page for new readers

Beehiiv and MailerLite both offer drag-and-drop header editors that let you reorder or hide these without touching code. Substack bakes the structure in and gives you less control.

Click behavior: headers vs. body links

Header links get fewer clicks than body links, but the people who do click them behave differently. A reader who clicks “Archives” is often hunting for a specific past issue or trying to decide whether to subscribe. A reader who clicks “About” in the header is usually new—either forwarded the email or landed via search.

Body links, by contrast, get clicked by engaged readers already moving through your content. Click-through rates on body links typically run 2–5× higher than header links, but header links drive longer session durations once someone lands. That makes header links better for onboarding and navigation, worse for immediate conversion.

One pattern worth noting: “View in browser” links see a spike when an email renders poorly—Gmail image blocking, dark mode color inversions, or Outlook layout breaks. If your “view in browser” clicks jump above 8–10% of opens, check your template rendering across clients.

How many links to include

There’s no hard limit, but usability degrades past six or seven links. Mobile email clients compress headers aggressively, and a row of eight tiny links turns into a visual mess. Readers also suffer decision fatigue: too many options and they pick none.

A conservative header might carry three links: Archives, About, and Sponsor. A maximalist header might include those plus social icons, a Shop link, a podcast feed, and a secondary CTA. The right count depends on how many distinct actions you want to offer and how much you trust readers to self-navigate.

If you’re running a content-driven business with multiple revenue streams—newsletter sponsorships, a course, affiliate guides, and a membership tier—you’ll need more links than someone running a simple personal essay newsletter. But even then, consider grouping: a single “Work with me” link that leads to a hub page beats three separate CTAs fighting for attention.

Placement and priority

Left-to-right reading means the first link in your header gets the most attention. If you’re optimizing for subscriber retention, put Archives first. If you’re optimizing for revenue, lead with Sponsor or Shop. If you’re optimizing for growth, lead with a referral CTA or a “Forward to a friend” link.

Some operators run a utility bar above the main header with low-priority links—Unsubscribe, Update preferences, View in browser—and reserve the main header row for high-value actions. That separation works well if your template has the vertical space, but it adds another visual layer readers have to parse.

One underused option: dynamic header links. Beehiiv and some custom setups let you show different headers to different segments. New subscribers see “Start here” and “Archives”; long-time readers see “Sponsor” and “Refer a friend.” It’s more complex to maintain, but it aligns the header with where each reader sits in your funnel.

What to test

If you want to optimize your header, start by pulling click data from your ESP. Most platforms (MailerLite, Beehiiv, Buttondown) break out link performance by URL. Compare header link clicks to total opens, and compare header CTR to body link CTR.

Then test removing one link. If you’re carrying seven and nobody clicks “Podcast,” drop it for a month and watch what happens. Fewer choices often means more action on the links that remain.

Also test reordering. Swap your first and third links for two issues and compare click counts. Small changes in sequence can shift behavior—especially on mobile, where only the first two or three links show above the fold.

If you’re just setting up your newsletter template and aren’t sure where to start, go minimal: Archives, About, and one revenue link. Add more only when you have a specific reader need that isn’t being met.

Want more operator tactics like this? Subscribe to One Two Three Send and we’ll send you one article every day—no fluff, no filler, just the tooling and structure that makes online businesses run.

Heads up — some links in this article are affiliate links. If you sign up through them, we may earn a small commission at no extra cost to you. We only recommend tools we use ourselves.

You click “send” on an automation trigger, and nothing happens for thirty seconds. Or you set up a welcome sequence that should fire immediately when someone subscribes, but the first email lands three minutes later. Or a tag-based filter that should route new subscribers into different sequences processes them in batches instead of one at a time.

Automation platforms don’t advertise their execution delays, but every step in your workflow sits in a queue somewhere, waiting its turn. When you’re running time-sensitive campaigns—flash sales, webinar reminders, breaking-news updates—those invisible delays compound fast.

Where the clock starts ticking

Most newsletter platforms process automation triggers in one of two ways: real-time event listeners or scheduled batch jobs. The difference matters.

Real-time triggers—someone subscribes, clicks a link, or completes a purchase—usually enter a queue within seconds. But “queue” doesn’t mean “send.” The platform still has to validate the contact, check suppression lists, render the email template, and hand it off to the sending infrastructure. That’s rarely instant.

According to MailerLite’s automation documentation (checked November 2026), their system processes automation triggers with up to a two-minute delay during normal load. Under heavy traffic—say, a product launch when thousands of people subscribe at once—that window stretches longer.

Beehiiv’s help docs (checked November 2026) note that their automation workflows run every sixty seconds, which means a subscriber who joins at 10:00:15 might not enter your sequence until 10:01:00.

Batch-based systems are slower by design. If your platform checks for new automation candidates every five or ten minutes, your “instant” welcome email might sit idle until the next sweep runs.

Compounding delays in multi-step workflows

Single-step automations are predictable. Multi-step sequences multiply the problem.

Say you build a three-email welcome series: email one sends immediately, email two waits one day, email three waits another two days. If your platform processes each step with a two-minute queue delay, and you’re using conditional logic to filter recipients by behavior, each gate adds latency.

Conditional waits—”send email B only if they clicked email A”—introduce another variable. Most platforms check conditions on the same batch schedule they use for triggers. A subscriber who clicks at 9:45 AM might not satisfy the condition check until 10:00 AM, then enter the next queue, then wait for the send job to process.

We’ve seen workflows where a subscriber action at 3:00 PM triggers an email that doesn’t land in their inbox until 3:08 PM—not because the SMTP handoff was slow, but because three separate queues each added two minutes.

When delays break your campaign

For evergreen content, a few minutes don’t matter. For time-bound offers, they do.

Flash sales with hourly countdowns can’t tolerate five-minute delays. If someone subscribes at 11:55 AM for a sale that ends at noon, and your welcome email with the discount code doesn’t send until 12:02 PM, the automation failed.

Webinar reminder sequences have the same problem. A “starts in 15 minutes” email that arrives twelve minutes late isn’t a reminder—it’s noise.

Breaking news or event-triggered content loses relevance fast. If you’re covering live developments and your automation publishes updates with a ten-minute lag, you’re better off scheduling manually or using a transactional email API like Postmark, which processes messages in seconds, not minutes.

How to work around platform lag

First, test your actual delay. Subscribe to your own list at a known timestamp and check when the welcome email lands. Do it three times, at different times of day, to see if server load changes the window.

Second, pad your timing. If your platform averages a three-minute delay, don’t schedule a “starts in 10 minutes” reminder—schedule it for fifteen. Build margin into every conditional step.

Third, simplify your logic. Every conditional branch adds another queue. If you can collapse three conditional steps into one segment filter applied at the entry point, you eliminate two delay windows.

For truly time-sensitive sends—password resets, order confirmations, login codes—use transactional infrastructure, not marketing automation. Transactional services are built for sub-second delivery and don’t share queue resources with bulk campaigns.

Finally, document what you learn. If you know your platform’s typical delay is two minutes under normal load and five during peak hours, you can design workflows that account for it instead of discovering the gap when a campaign misfires.

Want to compare how different platforms handle automation timing? Reply with the tools you’re evaluating—we’ll dig into their queue behavior and help you pick the one that matches your send cadence.

Heads up — some links in this article are affiliate links. If you sign up through them, we may earn a small commission at no extra cost to you. We only recommend tools we use ourselves.

You hit send on your newsletter, run a deliverability test, and see green checkmarks across Gmail, Outlook, and Yahoo. Success. Except three subscribers email you an hour later asking if you sent anything today—it still hasn’t arrived.

Deliverability testing tools measure whether your email reaches the inbox at the moment they check. They don’t measure when it lands for real subscribers, and that timing gap creates a blind spot most operators don’t know exists.

Why inbox placement is never instant

When you send a newsletter, your ESP hands the message to the receiving mail server. That server doesn’t immediately drop it into inboxes. It queues the message, runs spam filters, checks sender reputation, scans attachments, and applies recipient-specific rules—mail forwarding, vacation responders, custom filters.

Google’s Email message delivery documentation (checked October 2026) describes greylisting, a tactic where mail servers temporarily reject messages from unfamiliar senders, then accept them on retry minutes later. Legitimate senders retry; spammers often don’t. Microsoft and Yahoo use similar throttling.

For high-volume senders, inbox placement can lag 15–90 minutes behind the send timestamp. Smaller lists see faster delivery, but individual subscriber rules—especially corporate mail servers with extra filtering layers—add unpredictable delays.

What deliverability tools actually test

Services like Mail-Tester, GlockApps, and MailGenius send a test email to seed addresses they control, then report where it landed: inbox, spam, or rejected. These tools are useful for spotting authentication problems (missing SPF, DKIM, or DMARC records) and content triggers (spammy subject lines, broken HTML).

But they test one message to their servers at the moment you run the check. They don’t simulate:

• Reputation decay from previous sends
• Engagement history with your domain
• Throttling applied to bulk sends
• Recipient mail client processing delays

A test might show 100% inbox placement while your actual campaign sits in a processing queue for 20 minutes before subscribers see it.

When delayed delivery becomes a problem

For most newsletters, a 10–30 minute delivery window is invisible. Subscribers check email sporadically; they don’t notice if your 9am send arrives at 9:17am.

Delays matter when:

• You’re sending time-sensitive content—flash sales, event reminders, breaking news. A two-hour lag kills urgency.
• Subscribers expect instant confirmation—password resets, purchase receipts, download links. These transactional emails should use a dedicated sending service like Postmark, not your bulk newsletter ESP.
• You’re troubleshooting deliverability and testing changes (new from-address, re-engagement campaign). If you test immediately after sending, you might declare success before the real filtering happens.

Check your ESP’s delivery reports. Postmark’s Activity feed (checked October 2026) shows per-message delivery timestamps; MailerLite and Beehiiv show aggregate delivery speed in campaign reports.

How to spot and reduce lag

If subscribers regularly report late delivery, check three things:

Domain and IP reputation. Use Google Postmaster Tools (free, requires domain verification) to see how Gmail rates your sending domain. A “low” or “bad” reputation triggers aggressive throttling. Consistent send volume, low complaint rates, and strong engagement improve reputation over time.

List hygiene. High bounce rates signal poor list quality, and ESPs respond by slowing your delivery. Remove hard bounces immediately and suppress addresses that haven’t opened in six months.

Send volume spikes. If you normally send 5,000 emails weekly and suddenly send 50,000, mail servers treat the spike as suspicious and queue aggressively. Ramp volume gradually—double your list size over weeks, not days.

For transactional email (receipts, login codes, account notifications), move those messages off your newsletter platform entirely. Postmark and services like it prioritise speed and maintain separate infrastructure with higher delivery priority.

Test delivery, not just placement

Add a few seed addresses you control—a Gmail account, an Outlook account, a custom domain mailbox—to every campaign as hidden BCC recipients or list members. Note the send time in your ESP, then check when each seed address actually receives the email.

Run this for three consecutive sends. If your Gmail seed consistently receives email 40 minutes after send time while Outlook arrives in five, you’ve found a throttling pattern worth investigating.

Deliverability tools tell you if you’ll reach the inbox. Seed monitoring tells you when. Both matter, but only the second one explains why subscribers say they didn’t get your newsletter—even when your dashboard shows 98% delivered.

Subscribe to One Two Three Send for weekly breakdowns of the email and online-business mechanics nobody documents clearly.

Heads up — some links in this article are affiliate links. If you sign up through them, we may earn a small commission at no extra cost to you. We only recommend tools we use ourselves.

You’ve published 200 issues. Subscribers know you wrote something about API rate limits last spring, but they can’t find it. They scroll your archive page, give up, and email you instead—or worse, they unsubscribe because they think you never covered it.

Archive search should be table stakes for any newsletter platform in 2026. It isn’t. Most platforms either hide it, break it with paywall logic, or never built it at all. The result: your back catalog—often your most valuable evergreen content—becomes invisible the moment it leaves the inbox.

What archive search actually does (and doesn’t)

Archive search lets readers query your published posts by keyword, usually from a public-facing page. It’s not the same as your platform’s internal post search (the one you use in the editor to find drafts). Reader-facing search needs to index published content, respect paywall settings, and return results fast enough that people don’t bounce.

Good archive search indexes headlines, body text, and sometimes metadata like tags or categories. Bad implementations only search titles, or they index paywalled content but show locked snippets that frustrate readers. The worst case: no search at all, just a paginated list sorted by publish date.

How the major platforms handle it

Substack offers archive search on every publication’s homepage and archive page. It’s fast, indexes full text, and respects paywall boundaries—free subscribers see free posts, paid subscribers see everything. The search bar sits at the top of the archive by default. (Substack support docs, checked October 2026.)

Beehiiv added archive search in late 2025. It’s available on the public archive page for all tiers, indexes post titles and body content, and filters by free vs. premium. The implementation is slower than Substack’s—queries can take two or three seconds on archives over 500 posts—but it works. (Beehiiv features page, checked October 2026.)

ConvertKit does not offer built-in archive search. The public archive page lists posts chronologically with no search box. If you want search, you need to embed a third-party tool like Algolia or build a custom solution using ConvertKit’s API and a static site generator. Most operators don’t bother. (ConvertKit help center, checked October 2026.)

Ghost includes archive search by default on its public site. Because Ghost runs as a full website CMS, search works across posts, pages, and tags. It’s one of the platform’s strongest discoverability features, especially for operators who treat their newsletter as a content library. (Ghost help docs, checked October 2026.)

MailerLite does not provide archive search. The platform’s blog/landing-page builder lets you display recent posts, but there’s no search index for readers. If you’re using MailerLite and want searchable archives, you’ll need to host them elsewhere—usually WordPress or a static site. (MailerLite features, checked October 2026.)

Why this matters more than open rates

Open rates measure what happens in the first 48 hours. Archive search measures what happens in month six, month twelve, and year two. Evergreen content—tutorials, tool comparisons, case studies—drives long-tail signups and reduces support load. If readers can’t find it, you’re recreating the same content every quarter.

Operators who migrate from platforms without search to platforms with it report two consistent changes: referral traffic from archive pages increases, and “hey, did you ever write about…” emails drop. Both compound over time. A searchable archive turns your newsletter into a reference library instead of a chronological feed that only rewards the most recent readers.

What to do if your platform doesn’t have it

If you’re on ConvertKit or MailerLite and archive search matters to your business, you have three options. First, migrate to a platform that supports it—Ghost and Substack are the strongest here. Second, build a custom archive using your platform’s API, a static site generator like Hugo or Eleventy, and a search tool like Pagefind or Algolia. Third, accept the limitation and organize your archive by category or tag, then link prominently to high-value posts in your welcome sequence and website nav.

The third option is the lowest-friction compromise, but it only works if you have fewer than 50 posts or a tightly focused editorial niche. Once you cross 100 issues, manual curation doesn’t scale.

Want more breakdowns like this? Subscribe to One Two Three Send for weekly deep-dives on the tools and tactics that power content-driven online businesses. Reply with the feature you want dissected next.

Heads up — some links in this article are affiliate links. If you sign up through them, we may earn a small commission at no extra cost to you. We only recommend tools we use ourselves.

Every newsletter platform embeds a tracking pixel in your emails. It’s a one-by-one transparent image, loaded from the platform’s server when a recipient’s email client renders the message. The request tells the platform which subscriber opened which email, when, and roughly where.

But tracking pixels only measure image loads. They don’t measure reading time, scroll depth, or whether the subscriber actually looked at your content. They report technical events, not human attention—and the difference matters when you’re deciding what to write next or which subscribers to segment.

What the pixel actually records

When a subscriber’s email client requests the tracking pixel, your platform logs:

• Subscriber identifier: usually a hashed token in the image URL that maps back to the contact record
• Timestamp: server time of the request, sometimes multiple if the email is re-opened
• IP address and user agent: used to infer location, device type, and email client
• Referrer header: occasionally present, mostly stripped by modern clients

The platform translates these signals into open rate, device breakdown, and geographic distribution. But it can’t tell whether the subscriber skimmed the first sentence and closed the tab, or read every word twice.

More importantly: many email clients now block or proxy tracking pixels. Apple Mail Privacy Protection, introduced in 2021 and now nearly universal among iOS users, prefetches images through relay servers. The pixel fires when Apple’s server caches the email—not when the subscriber opens it. Gmail’s image proxy does something similar. The result is inflated open rates and timestamps that don’t reflect actual reading behavior.

The engagement signals you’re not seeing

Tracking pixels miss the metrics that correlate most strongly with subscriber value:

Time in message. A subscriber who spends three minutes with your email is more engaged than one who opens and closes in five seconds. Email platforms don’t measure dwell time because the pixel fires once on load—there’s no scroll listener or exit event.

Scroll depth. Did the subscriber reach your call-to-action? Did they see the PS at the bottom? The pixel can’t answer that. Web analytics tools measure scroll percentage; email can’t.

Re-reads. Some platforms count multiple opens if the pixel fires again, but most modern clients cache images aggressively. A subscriber who revisits your email three times over a week looks identical to one who opened it once.

Forwarding without opens. If a subscriber forwards your email to a colleague who reads it but never loads images, you see zero engagement. The original subscriber gets no credit for distribution, and the new reader is invisible.

What to measure instead

Clicks are a better proxy for attention than opens. A subscriber who clicks a link demonstrated intent—they moved from passive receipt to active navigation. Track click rate as your primary engagement metric, not open rate.

Link clicks also let you infer content preference. If 12% of your list clicks the tutorial link and 2% clicks the sponsor block, you know what’s working. Open rates tell you the subject line succeeded; click rates tell you the body delivered.

Reply rate is even better. A reply costs the subscriber time and thought. If you’re running a smaller list—under 5,000 subscribers—track replies per send and treat them as your North Star metric. Platforms like Beehiiv and MailerLite surface reply counts in campaign reports; use them.

For high-value subscribers, consider moving conversations off email entirely. A Slack community, a Discord server, or a lightweight forum gives you read receipts, typing indicators, and reaction counts—all the engagement signals email strips away.

When pixel data still matters

Tracking pixels aren’t useless. They’re just overweighted.

Use open data to test subject lines. Run A/B tests on small segments, measure open rate delta, and apply the winner to the rest of your list. The pixel is reliable enough for relative comparison, even if absolute numbers are inflated.

Use device and client breakdowns to guide design decisions. If 60% of your opens happen on mobile and your email renders poorly in Gmail’s mobile app, fix the template. The pixel tells you where your subscribers read, even if it doesn’t tell you whether they absorbed anything.

Use geographic data to time your sends. If most opens cluster in US Eastern morning hours, schedule accordingly. The timestamp might be proxied, but aggregate patterns smooth out the noise.

And use suppression lists built from non-openers cautiously. If a subscriber hasn’t opened in 90 days but clicks every third email, they’re engaged—the pixel just isn’t firing. Segment on clicks and replies before you prune based on opens alone.

One more thing: if you’re debugging deliverability, open rate by domain is still useful. If Gmail opens drop suddenly while Outlook and Apple Mail hold steady, you’ve likely hit a spam filter. The pixel won’t tell you why, but it’ll tell you where to investigate.

Tracking pixels measure technical events. Clicks, replies, and conversions measure attention. Optimize for the latter, and treat open rates as a rough directional signal—not ground truth.

Want more tooling deep-dives like this? Subscribe to One Two Three Send and get operator-focused breakdowns every week—no fluff, no beginner listicles, just the mechanics that matter.

Heads up — some links in this article are affiliate links. If you sign up through them, we may earn a small commission at no extra cost to you. We only recommend tools we use ourselves.