One Two Three Send

Author: onetwothreeadmin

Newsletter import tools lose data—here’s what doesn’t transfer

Photo by Markus Winkler on Unsplash

Every newsletter platform promises seamless imports. Upload a CSV, connect your old ESP, wait five minutes, and you’re done. Except you’re not.
Import tools handle the basics—email addresses, names, subscription dates—but they quietly drop or mangle data that matters. If you’re moving from one platform to another, you need to know what won’t survive the trip before you click “Start Import.”
Custom fields disappear or get renamed
Most platforms let you store custom data: subscriber location, referral source, purchase history, survey responses. When you import to a new platform, these fields rarely map automatically.
Beehiiv, for example, supports custom fields, but you need to create them before importing your CSV. If your old platform called a field “signup_source” and your new one expects “source,” the data lands in limbo or gets ignored entirely.
MailerLite handles this better than most—it auto-creates custom fields during import if it detects columns that don’t match standard fields—but it still won’t infer meaning. If you tagged subscribers as “paid” or “free” in your old system, you’ll need to manually map those to groups or segments after import.
Tags and segments don’t transfer consistently
Tags are metadata. Segments are dynamic queries. Most platforms treat them differently, and import tools don’t convert between the two.
If you’re moving from ConvertKit (which uses tags heavily) to a platform like Brevo (which leans on lists and attributes), your tags might import as plain text in a custom field—or not at all. You’ll need to rebuild segments manually using the new platform’s logic.
Even when platforms do support tags, they often cap how many can attach to a single subscriber during import. ConvertKit allows unlimited tags per contact, but some smaller platforms limit you to 10 or 20. If you’ve been tagging aggressively, the import will silently truncate.
Engagement history gets wiped
Open rates, click rates, and email engagement scores don’t port over. Your new platform starts everyone at zero.
This matters more than it sounds. Most ESPs use engagement history to throttle sending for new accounts. If you import 10,000 subscribers and immediately send to all of them, your new platform sees 10,000 cold contacts with no prior opens. That triggers spam filters and damages your sender reputation faster than a gradual ramp-up would.
Postmark and other transactional-focused platforms don’t track opens by default (they’re built for receipts and password resets, not marketing), so if you’re moving to a marketing ESP, you’re starting engagement tracking from scratch no matter what.
The fix: after importing, send only to your most engaged segment first—people who opened in the last 30 days—then gradually expand. This warms up your sender reputation on the new platform without triggering alarms.
Unsubscribes and suppression lists need manual handling
Unsubscribes should transfer, but they often don’t. Some platforms export unsubscribed emails in a separate CSV. Others include them in the main export with a status column. If you miss that column during import, you’ll re-subscribe people who opted out.
Suppression lists—emails that hard-bounced or marked you as spam—are even trickier. Most platforms won’t let you import suppressed addresses at all (by design), but they also won’t automatically suppress them on your new account unless you manually upload a suppression file.
If you skip this step, your first send on the new platform will attempt delivery to addresses that bounced months ago. That kills your sender score immediately.
What to do before you import
Export everything from your old platform: subscribers, unsubscribes, suppressions, custom fields, tags. Save separate CSVs for each.
Check your new platform’s import documentation—not the marketing page, the actual help docs—and map your fields manually. Create custom fields and tags before importing, so the data has somewhere to land.
Import in stages. Start with a small segment (100–500 subscribers) and verify everything looks right: names, fields, tags, suppression status. Only then import the full list.
And plan to rebuild segments. Even if tags import cleanly, your new platform’s segmentation logic probably works differently. Budget an hour to recreate your most important segments by hand.
Switching platforms isn’t one click. If you’re moving soon, factor in a half-day for data cleanup—not five minutes.
If you’re running into platform-specific import issues—or you’ve found a tool that handles this better than most—reply and let me know. I’ll cover it here.

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.

29 August 2026
AI writing assistants don’t save you time—they shift where you spend it

Photo by Randy Tarampi on Unsplash

Every AI writing tool promises the same thing: faster content. Draft a blog post in ten minutes. Turn bullet points into polished copy. Ship more with less effort.
But after two years of watching solo operators adopt Claude, ChatGPT, Jasper, and a dozen other assistants, the pattern is clear: AI doesn’t save time. It relocates it.
The draft comes faster. The cleanup takes longer. And if you’re not tracking both sides of that equation, you’re probably spending more hours per finished piece than you did before.
Where the time goes after the AI writes
A typical workflow looks like this: you give the AI a prompt, it generates 800 words in 45 seconds, and you feel productive. Then you start reading.
The voice is slightly off. The structure is fine but predictable. There are no obvious errors, but three claims need citations you didn’t provide. Two paragraphs repeat the same idea in different words. The conclusion is a generic summary instead of a payoff.
So you edit. You rewrite transitions. You delete filler. You open five browser tabs to verify facts the AI stated with unearned confidence. You rework the ending twice because the AI doesn’t know what point you were building toward.
Thirty minutes later, you’ve turned a mediocre draft into a decent piece. Total time: 35 minutes. Without AI, you might have written it from scratch in 40.
The time savings exist—but they’re smaller than the marketing suggests, and they show up in a different part of the process than you expect.
The hidden costs: voice drift and context loss
Most operators don’t track two specific drags that AI introduces: voice calibration and context re-establishment.
Voice calibration is the work required to make AI output sound like you. If you write in a direct, opinionated style, the AI will give you something smooth and hedged. If your brand is warm and conversational, the AI defaults to corporate neutral. You can train it with better prompts, but that training is invisible labor that doesn’t show up in your draft timer.
Context re-establishment happens when you’re working on a multi-part series, a technical deep-dive, or anything that references earlier material. The AI doesn’t remember what you published last week unless you feed it that context every time. So you either paste in your previous posts (adding prep time), or you edit out the inconsistencies after the fact (adding cleanup time).
Both costs are real. Both are recurring. And neither appears in the “look how fast I drafted this” screenshot.
When AI actually saves time
AI writing tools do create leverage—but not universally, and not the way most operators assume.
They’re fastest when you need volume over voice: product descriptions, meta descriptions, FAQ answers, ad copy variations. Work where the output needs to be clear and correct, but doesn’t need to sound distinctly like you.
They’re useful for structural scaffolding: outlines, headline variations, reframing a paragraph you’ve rewritten four times and still don’t like. The AI gives you options, you pick one, you move on.
They’re effective for research summarization: feed the AI a 3,000-word source document, ask it to pull out the key points, use that as a starting point for your own synthesis. You’re not publishing the AI’s summary—you’re using it to skip the first read-through.
Where they don’t save time: long-form content that requires a specific voice, technical accuracy, or a point of view. Anything where editing the AI’s output takes longer than writing it yourself from the start.
How to measure the real cost
If you’re using AI writing tools regularly, track the full cycle: prompt time, generation time, editing time, fact-checking time, and voice-tuning time. Do that for five pieces. Compare it to your pre-AI average.
Most operators discover one of two things: either AI saves them 20–30% on high-volume, low-voice work, or it costs them 10–20% more on anything that requires editorial judgment.
The tool isn’t the problem. The mismatch between task and tool is.
If you’re drafting your weekly essay with AI and spending 40 minutes editing it back into your voice, you’re using the wrong tool for the job. If you’re writing 50 product descriptions and AI cuts that from four hours to 90 minutes, you’re using it correctly.
Want more breakdowns like this? Subscribe to One Two Three Send—no fluff, just honest tooling and workflow analysis for solo operators.

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.

28 August 2026
WordPress lazy loading delays images differently on mobile vs desktop
Photo by Stephen Phillips – Hostreviews.co.uk on Unsplash

WordPress enabled native lazy loading by default in 2020, and most operators never think about it again. The browser handles it, images load as users scroll, and Core Web Vitals improve. Simple.
Except lazy loading doesn’t work the same way on mobile and desktop. The threshold that triggers an image to start loading—called the “distance-from-viewport” threshold—varies by browser, device type, and connection speed. That inconsistency affects how fast your site feels, even when the technical metrics look fine.
How lazy loading thresholds actually work
When WordPress adds loading="lazy" to an image, it’s telling the browser: don’t load this until the user is about to see it. But “about to see it” isn’t a fixed distance.
Chrome and Edge use a threshold of roughly 1250 pixels on desktop with a fast connection. That means an image starts loading when it’s still more than a full screen away. On mobile, that threshold drops to around 2500 pixels—proportionally much larger relative to viewport height, but still about two to three scroll lengths.
On slower connections (defined by the browser’s effectiveType API), those thresholds shrink. Chrome drops to around 2500 pixels on desktop and 1250 pixels on mobile when it detects 3G speeds.
Firefox uses similar logic but calculates thresholds as a multiplier of viewport height rather than fixed pixels. Safari’s implementation is more conservative across the board.
The result: the same page can trigger image loads at wildly different scroll positions depending on device and connection. A hero image that loads instantly on desktop might not even start fetching until a mobile user scrolls halfway down the page.
Where this breaks perceived performance
Lazy loading improves Largest Contentful Paint (LCP) and Total Blocking Time by deferring offscreen images. But it can hurt perceived speed if critical above-the-fold images get lazy-loaded by mistake.
WordPress excludes the first image in the content from lazy loading, but that heuristic fails when:
- Your hero image is a background image in CSS, not an <img> tag
- Your layout uses a sidebar, and the “first” image is a small thumbnail in the sidebar, not the main content image
- You’re using a page builder that injects images via JavaScript after initial render
On mobile, where thresholds are proportionally larger, users scroll faster and notice the delay more. An image that starts loading at 2500 pixels might not finish rendering before the user reaches it, especially on slower devices or connections.
This is why some sites feel faster on desktop even when mobile scores higher in Lighthouse. The lazy loading threshold mismatch creates a perception gap that metrics don’t fully capture.
How to adjust lazy loading behavior
You can’t directly control browser thresholds, but you can control which images get the loading="lazy" attribute.
The simplest fix: remove lazy loading from above-the-fold images. WordPress provides a filter to exclude specific images:
add_filter( 'wp_lazy_loading_enabled', '__return_false' );
That disables it globally, which is overkill. Instead, target specific images by hooking into wp_get_attachment_image_attributes and removing the loading attribute for images in the first few blocks or above a certain position in the DOM.
Most page builders and themes offer a “disable lazy loading” toggle for hero sections. Use it. The performance cost of eagerly loading one or two large images is trivial compared to the perceived-speed hit of lazy-loading them incorrectly.
For mobile-specific tuning, consider using the fetchpriority="high" attribute on your primary hero image. It’s supported in Chrome, Edge, and Safari, and it tells the browser to prioritize that image even if lazy loading would otherwise delay it. WordPress doesn’t add this by default, but you can inject it via the same attribute filter.
Test with real throttling, not just Lighthouse
Lighthouse simulates a slow connection, but it doesn’t show you the scroll-and-wait behavior real users experience. Open Chrome DevTools, switch to the Network tab, and throttle to “Slow 3G.” Then actually scroll your site on a mobile viewport.
Watch where images start loading. If they’re popping in after you’ve scrolled past them, your thresholds are too conservative or your images are too large. If they’re all loading at once on page load, you’re not benefiting from lazy loading at all.
Run the same test on desktop. The behavior should be noticeably different. If it’s not, you might have a plugin overriding WordPress’s native implementation with a JavaScript-based lazy loader—those usually use fixed thresholds regardless of device.
Most solo operators optimize for Lighthouse scores and call it done. But perceived speed matters more than any single metric, and lazy loading thresholds are one of the few variables that affect perception without showing up in reports.
Reply with the laziest-loading image you’ve ever encountered. We’re collecting examples for a follow-up piece on edge cases that break WordPress’s heuristics.
28 August 2026
Analytics dashboard refresh rates: when ‘real-time’ is 15 minutes old

Photo: Saleemkce via Wikimedia Commons (CC BY-SA 4.0)

You refresh your analytics dashboard, see a spike in traffic, and make a decision. Twenty minutes later, the numbers change. The spike wasn’t real—it was a delayed batch update finally catching up.
Most analytics platforms advertise “real-time” data, but the definition varies wildly. Some update every few seconds. Others label data “real-time” when it’s actually on a 10- or 15-minute delay. If you’re running paid campaigns, testing content, or troubleshooting a technical issue, that lag can cost you.
Here’s what the refresh intervals actually look like across the tools solo operators use most.

Google Analytics 4: real-time vs. standard reports

GA4 splits its interface into two modes with completely different refresh schedules.
The Realtime report updates every few seconds and shows activity from the last 30 minutes. It’s genuinely live. You can watch users land on pages, see referral sources, and track active sessions as they happen.
Every other report in GA4—traffic acquisition, landing pages, conversions—runs on processed data that lags 24 to 48 hours. The interface doesn’t always make this obvious. You can select “today” as a date range, but the data you’re seeing might be incomplete or entirely missing if Google hasn’t finished processing it yet.
This matters when you’re trying to measure same-day campaign performance. If you launch a newsletter at 9 a.m. and check your landing page traffic at noon, GA4’s standard reports might show zero visits even if 500 people clicked through. The Realtime report will show them; the rest of the dashboard won’t.

Plausible, Fathom, and privacy-first tools

Privacy-focused analytics platforms tend to update faster because they process less data and don’t rely on Google’s infrastructure.
Plausible refreshes every 60 seconds. You’ll see new pageviews, referrers, and goals within a minute of them happening. There’s no separate “real-time” mode—the entire dashboard operates on the same refresh cycle.
Fathom Analytics works similarly, with updates every 30 to 60 seconds depending on server load. Both tools are built for solo operators who want to check traffic without waiting for batch processing.
The tradeoff: these platforms don’t offer the same segmentation depth as GA4. You get fast data, but fewer filtering options.

Paid ad platforms: Facebook, Google Ads, LinkedIn

Ad dashboards have their own refresh logic, and it’s slower than most operators expect.
Facebook Ads Manager updates every 15 minutes for active campaigns. If you’re testing ad creative or adjusting budgets, you won’t see the impact of your changes until at least one refresh cycle passes. Conversion data—especially for events tracked via the Pixel—can lag an additional hour as Facebook attributes clicks and validates events.
Google Ads refreshes every 3 hours for most metrics. Impressions and clicks appear faster, but conversion data tied to GA4 goals or imported offline events can take 6 to 24 hours to populate.
LinkedIn Campaign Manager updates every 24 hours. You can’t optimise LinkedIn ads intraday—the platform doesn’t surface enough data to make that possible.
If you’re split-testing ad creative, this lag forces you to wait longer than you’d expect before making decisions. A campaign that looks like it’s underperforming at 10 a.m. might show strong results by 2 p.m. once delayed conversions populate.

What this means for decision-making

The biggest mistake is treating delayed data as if it were complete. If you check your analytics dashboard and see low traffic or weak conversions, ask whether the platform has actually finished processing the time window you’re looking at.
For same-day decisions—like killing an underperforming ad or tweaking a landing page—use tools with sub-60-second refresh rates. Plausible, Fathom, or GA4’s Realtime report are your best options.
For campaign analysis and attribution, wait at least 48 hours before drawing conclusions. Conversion tracking, especially across multiple touchpoints, needs time to reconcile.
And if you’re running a high-stakes launch—a product drop, a webinar, a sponsorship deal—set up multiple dashboards. Cross-reference GA4 Realtime with your email platform’s click tracking and your payment processor’s revenue feed. No single dashboard will give you the full picture on the same refresh cycle.

Want more breakdowns like this? Subscribe to One Two Three Send—we cover the tools, tactics, and operational details solo operators actually need.

28 August 2026
Stripe disputes force refunds before you reply—here’s the timeline
Photo by rupixen on Unsplash

When a customer files a chargeback or dispute through their bank, Stripe doesn’t wait for you to respond before pulling money out of your account. The funds are held—or outright reversed—immediately, and you’re racing a clock most operators don’t know exists.

If you run a subscription, sell a course, or process one-time payments for services, you need to understand how Stripe’s dispute process actually works. The timeline is tighter than you think, the evidence requirements are specific, and the outcome often depends on how fast you move in the first 48 hours.

What happens the moment a dispute arrives

Stripe receives the dispute notification from the card network—Visa, Mastercard, Amex—and immediately debits your Stripe balance. If your balance is zero or negative, Stripe pulls from your bank account on the next payout cycle.

You get an email and a dashboard notification. The dispute reason—fraudulent, unrecognized, product not received, product unacceptable, duplicate charge, or credit not processed—determines what evidence Stripe will ask for and how the card network will weigh your response.

The clock starts immediately. You have 7 days to submit evidence for most disputes. Some card networks give you up to 21 days, but Stripe’s default deadline is one week. Miss it, and you forfeit by default.

Even if you submit evidence on time, the card network takes 60 to 75 days to issue a final decision. Your funds stay held during that entire period. If you lose, Stripe charges you a dispute fee—currently $15 for most disputes in the U.S., higher in other regions or for certain card types.

What evidence actually matters

Stripe provides a dispute evidence form in the dashboard. It’s tempting to write a narrative explaining why the customer is wrong. That’s not what wins disputes.

Card networks want documentation that proves the customer received what they paid for and authorized the transaction. The strongest evidence:
- Delivery confirmation: Tracking numbers, delivery signatures, IP logs showing account access after purchase.
- Customer communication: Email threads, support tickets, or messages where the customer acknowledged receipt or asked for help using the product.
- Terms of service acceptance: Timestamped logs showing the customer agreed to your refund policy or terms at checkout.
- Usage logs: For digital products, show login timestamps, downloads, course progress, or API calls after the purchase date.
For “product not as described” disputes, comparison screenshots—what you advertised vs. what you delivered—help, but only if you can show the customer had access and didn’t contact you first.

For “fraudulent” disputes, evidence that the purchase matched the customer’s billing address, IP geolocation, or previous purchase history can swing the decision. But if the cardholder claims the card was stolen, you’ll lose unless you have very strong delivery proof tied to the cardholder’s verified identity.

When to fight and when to refund preemptively

Stripe’s dispute win rate across all merchants hovers around 20 to 30 percent. Some categories—digital goods, services, subscriptions—perform worse because card networks favor cardholders in ambiguous cases.

If the dispute reason is “fraudulent” and you have no delivery confirmation or communication from the customer, you’ll almost certainly lose. In that case, accepting the dispute and treating it as a fraud loss is often faster than spending time gathering evidence that won’t change the outcome.

If the dispute is “product not received” and you have tracking showing delivery to the cardholder’s address, fight it. If it’s “unrecognized” and you have emails from the customer using the product, fight it.

One non-obvious tactic: if you catch the dispute within 24 hours and the customer is reachable, offer a direct refund in exchange for them withdrawing the dispute with their bank. Stripe allows you to issue a refund even after a dispute is filed, and if the customer withdraws, you avoid the dispute fee. This only works if the customer responds quickly—and many won’t.

How to reduce disputes before they happen

Stripe’s Radar tool flags high-risk transactions, but it won’t catch disputes that stem from buyer’s remorse or confusion. The two most effective levers:
- Descriptor clarity: Make sure your Stripe statement descriptor matches your brand name exactly. “XYZ MEDIA LLC” doesn’t help if your customer knows you as “Daily Insights Newsletter.” Mismatched descriptors are the leading cause of “unrecognized” disputes.
- Proactive communication: Send a receipt email immediately after purchase with a clear description of what was bought, when it was delivered, and how to contact you. For subscriptions, send renewal reminders 3 to 7 days before each charge.
If you’re seeing repeat disputes from a specific product or customer segment, that’s a signal that your positioning, pricing, or onboarding needs work—not just your dispute-response process.

Disputes cost you time, money, and cash flow. Stripe doesn’t return the dispute fee even if you win. The best defense is documentation you gather at the point of sale, not evidence you scramble to assemble a week later.

Have a question about payment processors, dispute handling, or monetisation infrastructure? Reply to this email—we cover what solo operators actually run into, not just what the docs say.
27 August 2026
Canva Brand Kit limits: when asset libraries hit the wall

Photo by appshunter.io on Unsplash

Canva’s Brand Kit is one of those features that feels infinite until it isn’t. You upload logos, set brand colors, add custom fonts—then one day you hit a cap you didn’t know existed, and suddenly your workflow grinds to a halt.
If you’re running multiple projects, client brands, or spin-off products under one Canva account, you’ve probably already felt this. Here’s what the limits actually are, what happens when you exceed them, and how to structure your assets so you don’t lose access to the designs you need.
The hard caps: what Canva restricts
Canva Free accounts get one Brand Kit. That’s one set of colors, one logo slot, and zero custom fonts. If you’re operating solo and have a single brand, that’s fine. The moment you need to juggle two visual identities—say, a main newsletter and a paid community—you’re stuck.
Canva Pro unlocks 100 Brand Kits per account. Each kit can hold up to 100 logos, 100 brand colors, and unlimited uploaded fonts (subject to a 500 MB total storage cap). That sounds generous until you’re managing kits for multiple clients, testing logo variations, or maintaining archived brand versions.
Canva for Teams keeps the same 100-kit limit but lets you share kits across users. If you’re on a small team and everyone’s uploading their own variations of the same logo, you’ll burn through slots fast.
What breaks when you hit the limit
Unlike other Canva features that throw a warning dialog, Brand Kit limits fail quietly. You won’t get an error when you try to upload your 101st logo—it just won’t appear in the kit selector. If you’re working quickly, you might not notice until you open a design later and realize the asset isn’t there.
The same applies to brand colors. Canva lets you save colors to your palette, but once you exceed 100, older entries start disappearing from the dropdown. They’re not deleted—they still exist in designs where you’ve already applied them—but you can’t select them from the palette anymore. You’ll need to eyedropper-sample them from an existing design or re-add them manually, which defeats the purpose of a brand kit in the first place.
Custom fonts hit a different wall. The 500 MB storage cap covers all uploaded fonts across all kits. If you’ve uploaded heavy font families with multiple weights and styles, you can hit that ceiling with fewer than 50 font files. When you do, Canva stops accepting new uploads and doesn’t tell you which fonts are taking up the most space.
Workarounds: how to structure around the caps
The cleanest fix is to treat Brand Kits as projects, not brands. Instead of one kit per client, create one kit per active design system. Archive or delete kits for completed projects. Canva doesn’t version-control Brand Kits, so if you delete one, any designs using it will lose the linked assets—but the designs themselves won’t break. Colors and fonts remain embedded; you just can’t update them globally anymore.
For logo bloat, delete outdated variations. If you’ve saved 15 versions of the same logo with different padding tweaks, keep the one you actually use and delete the rest. Canva doesn’t deduplicate assets, so two identical files uploaded separately count as two slots.
For fonts, consolidate weights. If you’re uploading a complete type family with nine weights, ask yourself if you’re actually using all of them. Most operators stick to regular, bold, and maybe italic. Delete the rest and you’ll free up storage without losing functionality.
If you’re on a team and sharing kits, set a naming convention and assign one person to manage uploads. Otherwise you’ll end up with three people uploading the same logo under different filenames, burning through slots unnecessarily.
When to split accounts instead
If you’re consistently hitting the 100-kit ceiling, you’re probably managing too many brands under one Canva account. At that scale, it’s cleaner to separate accounts: one for client work, one for internal projects, or one per major business vertical.
Canva Pro is $120/year per user. If splitting accounts costs you an extra $120 but saves you five hours a month hunting for missing assets or re-uploading fonts, the math works. Canva for Teams pricing starts at $100/year for five users, so if you’re already paying team rates, adding a second team workspace can make more sense than trying to cram everything into one account.
The tradeoff is duplication. You’ll need to upload the same fonts and logos to multiple accounts, and updates won’t sync. But if your brands are distinct enough to need separate kits anyway, that’s not a real loss.
If you’re running into these limits and want more breakdowns of online-business tools that hit capacity in non-obvious ways, subscribe to One Two Three Send—operator-to-operator insights, no filler.
What Canva doesn’t tell you
Canva’s help docs mention the 100-kit and 100-asset-per-kit limits, but they bury the font storage cap and don’t explain what happens when you exceed it. The color palette overflow behavior isn’t documented at all—I only discovered it after watching colors disappear from a kit I knew I’d added them to.
If you’re building a design system for a content business, treat Brand Kits like a database with row limits. Plan your structure upfront, audit regularly, and delete ruthlessly. Otherwise you’ll spend more time managing Canva than actually designing.

27 August 2026
ConvertKit’s visual automation builder vs. rule-based sequences

ConvertKit gives you two distinct ways to automate email flows: visual automations and rule-based sequences. They look similar in the dashboard, but they’re built on different engines, trigger differently, and impose different constraints on what you can build.

If you’ve been using one without understanding the other, you’ve probably hit a wall trying to do something that feels simple but won’t work in the tool you picked. Here’s how they differ, when to use each, and one non-obvious trick that makes visual automations significantly more powerful.

Visual automations: event-driven, branch-heavy

Visual automations are ConvertKit’s newer system. They trigger based on events—someone subscribes to a form, clicks a link, makes a purchase, or gets tagged. You drag blocks onto a canvas, connect them with lines, and build conditional branches.

The engine checks conditions in real time. If a subscriber meets the criteria for a branch, they move down that path immediately. If they don’t, they skip it. You can nest conditions, add delays, and split paths based on behavior.

Visual automations handle complexity well. You can build onboarding sequences that fork based on which lead magnet someone downloaded, re-engagement flows that pause if someone opens an email, or post-purchase sequences that change based on product type.

But they have two practical limits. First, each automation can have a maximum of 50 steps. That sounds like a lot until you realize that every condition, delay, and email counts as a step. A moderately complex flow hits that ceiling fast. Second, visual automations don’t let you manually add subscribers in bulk. They only trigger from events. If you want to enroll 200 people at once, you need a workaround—usually tagging them, then using the tag as a trigger.

Rule-based sequences: linear, broadcast-style

Sequences are ConvertKit’s original automation system. They’re linear: a list of emails sent in order, each after a set delay. You write the emails, set the intervals, and subscribers move through from top to bottom.

Sequences trigger when you manually add someone or when an automation rule enrolls them. You can set rules like “subscribe to this sequence when someone joins Form A” or “subscribe when someone is tagged with X.” Once someone’s in, they get every email in order unless you manually remove them or they unsubscribe.

Sequences are simple and predictable. They work well for drip courses, evergreen onboarding, or any flow where everyone gets the same emails in the same order. But they don’t branch. If you need conditional logic—send Email A to buyers and Email B to non-buyers—you can’t do it inside a sequence. You’d need to split it into two sequences and use tags or visual automations to route people correctly.

One advantage: sequences let you bulk-add subscribers. You can upload a CSV or select a segment and enroll hundreds of people at once. Visual automations can’t do that without a tag-based trigger step.

When each system breaks down

Visual automations struggle with scale in two ways. The 50-step limit forces you to split large flows into multiple automations, which means managing handoffs between them—usually with tags. And because they’re event-driven, debugging gets messy when subscribers don’t move as expected. You’ll find yourself checking event logs to see if a link click registered or if a tag applied at the right time.

Sequences struggle with personalization. If you want to send different emails based on behavior mid-flow, you can’t. You’d need to pause the sequence, tag people based on their actions, and move them into a different sequence or visual automation. That’s clunky and introduces delays.

Another thing: sequences don’t let you A/B test individual emails inside the sequence. You can A/B test the first email when someone subscribes, but not Email 3 or Email 7. Visual automations let you split paths and send different emails to different groups, which functions as a manual A/B test if you’re willing to analyze the results yourself.

The non-obvious trick: hybrid workflows

The most powerful ConvertKit setups use both systems together. Start with a sequence for the linear parts—your core onboarding emails that everyone should get. Then use visual automations to handle the branching logic.

For example: run a 5-email welcome sequence. At the end, tag people based on whether they’ve opened or clicked. Then trigger a visual automation off those tags. If someone engaged, send them a product pitch. If they didn’t, send a re-engagement email or move them to a different nurture track.

This keeps your sequences simple and your visual automations focused. You’re not trying to cram everything into one system or hitting step limits because you’re splitting the work across tools that each do one thing well.

One more thing: if you’re using ConvertKit’s Creator or Creator Pro plan, you get access to link triggers in visual automations. That means you can embed a URL in any email—even a broadcast or a sequence email—and trigger a visual automation when someone clicks it. That’s how you add conditional logic to sequences without rebuilding them as visual automations.

If you’re running ConvertKit and haven’t audited which system you’re using for each flow, do it this week. Chances are you’re using sequences for something that should be a visual automation, or you’ve built a visual automation that’s unnecessarily complex because it’s trying to do what a sequence handles better.

And if you’re just starting out, default to sequences for anything linear and predictable. Save visual automations for the moments where behavior actually matters.

27 August 2026
Content republishing to Medium and LinkedIn: SEO penalty or free reach?

Photo by Swello on Unsplash

You publish a post on your WordPress site. Traffic trickles in. Then someone tells you to cross-post it to Medium, LinkedIn, or Dev.to for extra eyeballs. Sounds smart—until you wonder if Google will ding you for duplicate content.
The short answer: it depends on how you do it. Republishing can expand your reach without SEO penalties, but only if you handle canonical tags correctly and understand platform timing quirks. Get it wrong, and you risk diluting your rankings or confusing search engines about which version is original.
Here’s what actually happens when you republish content, and how to do it without shooting yourself in the foot.
Canonical tags tell Google which version to index
When you republish an article on Medium or LinkedIn, you’re creating duplicate content. Google doesn’t penalize duplicates outright—it just picks one version to show in search results. The problem: if Medium outranks your original post, your site loses the traffic.
The fix is the canonical tag. It’s an HTML element in the page header that tells search engines, “This is a copy—index the original instead.” Medium and LinkedIn both support canonical tags when you import content.
On Medium, use the “Import a story” feature (not copy-paste). Paste your original URL, and Medium automatically adds a canonical tag pointing back to your site. On LinkedIn articles, there’s no built-in import tool, so you’ll need to manually add the canonical tag if you’re republishing via their API or a tool—but for standard LinkedIn posts, canonicals aren’t supported at all. That means LinkedIn text posts don’t typically create SEO conflicts because they’re not crawled as standalone articles the way Medium stories are.
If you’re cross-posting to Dev.to, Hashnode, or other developer platforms, check their republishing settings. Most offer a canonical URL field during post creation.
Timing matters: publish on your site first
Google uses crawl timestamps and index priority to determine the original source. If Medium indexes your story before Google crawls your WordPress post, you risk Medium being treated as the source—even with a canonical tag.
Best practice: publish on your site, wait 24–48 hours for Google to index it (check via Search Console or a manual site:yourdomain.com query), then republish elsewhere. This ensures your site is recognized as the origin.
If you’re in a hurry, submit your original post URL directly to Google via Search Console’s URL Inspection tool. Indexing usually happens within a few hours for sites with decent crawl rates.
Medium’s algorithm rewards early engagement—plan accordingly
Medium’s distribution algorithm favors stories that get engagement in the first few hours. If you republish too late, your story might not surface in Medium’s feeds, limiting its reach.
The trade-off: republish too early, and Google might not recognize your site as the source. Republish too late, and Medium’s algorithm ignores it.
A practical middle ground: if your site has strong domain authority and gets crawled frequently, you can republish to Medium within 12–24 hours. If your site is newer or slower to index, wait the full 48 hours and accept that Medium reach may be lower. Medium is a long-tail play anyway—stories resurface in recommendations for months.
LinkedIn and Dev.to have different reach dynamics
LinkedIn articles (the long-form publishing feature) don’t get much organic distribution unless you already have a large, engaged follower base. Most operators see better results posting a summary or excerpt as a standard LinkedIn post, then linking to the original article. No canonical issue, no duplicate content, and LinkedIn’s algorithm favors native posts over article links anyway.
Dev.to and Hashnode, on the other hand, have active discovery feeds and tag-based distribution. Canonical tags work well here, and republishing a week after your original post won’t hurt reach—these platforms reward evergreen content more than Medium does.
One risk no one mentions: partial syndication signals
If you republish only an excerpt (say, the first three paragraphs) and link back to the full post, Google usually treats that as a teaser, not a duplicate. But if the excerpt is long enough—roughly 300+ words—and includes your primary keyword clusters, Google may still index both versions and split ranking signals between them.
I’ve seen this happen with LinkedIn articles that included a 400-word intro and a “read more” link. Google indexed both, and the LinkedIn version ranked for a long-tail keyword I wanted on my site. The fix was to shorten the LinkedIn excerpt to under 200 words and remove the keyword from the republished intro.
Tools that automate republishing (and their limits)
Some WordPress plugins and Zapier workflows can auto-post to Medium or Dev.to via API. Most handle canonical tags correctly, but double-check the first time. Medium’s API, for example, requires you to pass the canonicalUrl parameter explicitly—if your tool doesn’t, you’ll end up with duplicate content and no canonical.
For LinkedIn, there’s no official republishing API that supports articles with canonicals, so automation is limited to link-sharing posts.
If you’re using a tool like Publer or Buffer to schedule social posts, note that these don’t create duplicate content issues—they’re sharing links, not republishing full text.
When republishing doesn’t make sense
If your site already ranks well for your target keywords and gets steady organic traffic, republishing is a marginal gain at best. Medium and LinkedIn won’t outperform your own domain for branded or niche queries, and you risk diluting backlinks (people might link to the Medium post instead of yours).
Republishing works best when you’re building initial reach, targeting audiences native to those platforms (e.g., developers on Dev.to), or when your site’s domain authority is still low and you want Medium’s DA to give your content a temporary boost.
One clear win: republishing older posts (6+ months old) that have already peaked in Google traffic. You get a second wave of reach with near-zero downside.
Got a specific republishing setup you’re unsure about? Reply to this email—I’ll tell you if your canonical setup will hold up.

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.

26 August 2026
Zapier premium feature gates: what free plans actually let you automate
Photo by Ben Grayland on Unsplash

Zapier markets itself as the automation glue for online operators, but its feature gates aren’t transparent until you’re mid-build and hit a paywall modal. If you’re running a content business on a tight budget, knowing exactly what the free plan allows—and what it doesn’t—saves you from half-built workflows and surprise upgrade prompts.
Here’s what actually separates free from paid, based on the tier structure as of August 2026.
What the free plan includes (and what most operators miss)
Zapier’s free tier gives you 100 tasks per month and up to five single-step Zaps. That much is obvious. What catches people off guard: you can build multi-step Zaps on the free plan. The limit is five Zaps, not five steps total. A three-step Zap counts as one Zap.
You also get basic filters—the “only continue if” logic that lets you stop a Zap from running unless a condition is met. For example, you can filter out emails that don’t contain a specific keyword before they hit your task tracker. That’s free.
The 100-task limit is the real ceiling. A task is counted every time a Zap step executes, excluding triggers and internal steps like filters and formatters in some cases. If you automate 25 form submissions a month with a two-step Zap (trigger + action), that’s 25 tasks. Add a third step—say, a Slack notification—and you’re at 50 tasks for the same 25 submissions.
What gets locked behind the $20/month tier
Zapier’s Starter plan ($19.99/month as of mid-2026, billed annually) unlocks 750 tasks and removes the five-Zap cap. But the functional gates matter more than volume:
- Paths: Conditional branching (“if this, do A; if that, do B”) requires Starter or higher. Without paths, you’re limited to linear workflows or clunky workarounds using multiple Zaps with overlapping filters.
- Scheduled triggers: Want a Zap to run every morning at 9 a.m., or once a week? That’s paywalled. The free plan only supports event-based triggers (“when this happens, do that”).
- Premium app integrations: Some apps—mostly enterprise tools and newer platforms—are marked “premium” and unavailable on free plans. The list shifts, but expect restrictions on tools like Salesforce, Shopify (some actions), and certain CRMs.
- Custom logic with code steps: Python or JavaScript steps to manipulate data mid-Zap are Starter-tier or higher.
The Starter plan also includes autoreplay, which reruns failed tasks automatically. On the free plan, if a Zap fails because an API was down, you manually replay it or lose the event.
Where free plans force awkward workarounds
The lack of paths and scheduling creates the most friction. Say you want to automate lead routing: free-tier operators often build separate Zaps with tight filters (“if source = Facebook, send to CRM A; if source = Google, send to CRM B”). That works until you hit the five-Zap cap or your filtering logic gets complex enough that you’re duplicating steps across Zaps.
Scheduling is harder to fake. If you need a weekly digest or a recurring task, your options on the free plan are: use a separate scheduling tool (like a cron job or a WordPress plugin) to trigger Zapier via webhook, or accept that Zapier isn’t the right tool for time-based automation until you pay.
When to upgrade vs. when to switch tools
If you’re brushing up against the 100-task limit and your workflows are simple (linear, event-triggered), the Starter plan is a reasonable jump. You’re paying for volume and reliability, not fundamentally different capabilities.
But if you need paths, scheduling, or code steps and you’re pre-revenue or bootstrapped, consider alternatives before committing $240/year:
- Make (formerly Integromat): Free tier includes 1,000 operations/month, and conditional logic (routers) isn’t paywalled. Steeper learning curve, but better for complex workflows.
- Pabbly Connect: Lifetime deal model, no monthly task limits on paid plans. UI is clunkier, but it’s a flat cost.
- n8n: Self-hosted, open-source. No task limits if you run it yourself. Requires technical setup, but if you’re already managing a VPS, it’s an option.
Zapier’s strength is its app directory and polish. If you’re integrating niche tools or you value “it just works” over cost optimization, the premium tiers are defensible. But for operators who need conditional logic or scheduling and aren’t yet at scale, the free plan’s gates arrive earlier than the marketing suggests.
Hit a Zapier paywall on a workflow you thought would be free? Reply and tell us what feature surprised you—we’re tracking the most common friction points for a future breakdown.
26 August 2026
Beehiiv referral program double-counting: how it happens and what it costs
Photo: Johan Schiff/Miljöpartiet de gröna via Wikimedia Commons (CC0)

Beehiiv‘s built-in referral program is one of the platform’s strongest features. It tracks who refers whom, awards milestones automatically, and gives you a dashboard that looks clean enough to screenshot for Twitter.
But under specific conditions, the system can credit a single subscriber twice—once as an organic signup, once as a referral—and you won’t notice until you’re reconciling milestone rewards or trying to understand why your referral conversion rate looks suspiciously high.
This isn’t a bug in the traditional sense. It’s a timing issue between how Beehiiv handles cookie persistence, URL parameters, and post-signup attribution. And it happens more often than you’d think.
How the double-count happens
Beehiiv’s referral tracking relies on a ref parameter in the signup URL. When someone clicks a referral link, the platform sets a cookie that persists for 30 days. If that person subscribes within the window, the referrer gets credit.
The problem surfaces when someone does both of these things:
- Clicks a referral link but doesn’t subscribe immediately
- Returns later via a different entry point (direct traffic, search, social) and subscribes
- Then clicks another referral link from the same or a different referrer after subscribing
If the second referral link is clicked within 30 days of the first, and if the subscriber’s email matches, Beehiiv can attribute the signup to both the original cookie and the post-subscription click. The dashboard shows two referral credits for one person.
This doesn’t happen every time. It requires overlapping attribution windows and a subscriber who’s clicking around your ecosystem post-signup. But in communities where readers forward issues to each other, or in niches where your audience is also your referral base, it’s common enough to skew your numbers by 5–12%.
Why it matters
If you’re running a milestone-based referral program—three referrals gets a PDF, ten gets a course—double-counting means you’re awarding rewards for phantom signups. That’s a direct cost.
If you’re using referral metrics to evaluate which subscribers are your best advocates, the data is noisy. Someone who looks like a top referrer might have half their credits inflated by attribution overlap.
And if you’re trying to model referral-driven growth or calculate the viral coefficient of your newsletter, double-counted subscribers artificially inflate both the numerator and denominator. Your k-factor looks better than it is, and your CAC math breaks.
How to audit your referral data
Beehiiv doesn’t surface this in the dashboard. You need to export your subscriber list and cross-reference referral credits manually.
Go to Audience → Export and download the full subscriber CSV. Open it in Google Sheets or Excel. Filter by the Referred By column. Look for duplicate email addresses with different referrer values.
If you see the same email credited to two different referrers, check the signup timestamps. If they’re within 30 days of each other and the second timestamp is after the subscription date, you’ve found a double-count.
For newsletters with 5,000+ subscribers and active referral programs, expect to find 50–150 duplicates. For smaller lists, it’s less common but still worth checking before you ship milestone rewards.
What Beehiiv should do
The fix is straightforward: deduplicate referral credits by email address and prioritize the first attributed referrer within the 30-day window. If someone subscribes, lock their referral attribution. Don’t let post-subscription clicks overwrite or append credit.
Other platforms—MailerLite, SparkLoop, Viral Loops—handle this by treating the subscription event as the attribution cutoff. Once you’re in, subsequent referral link clicks don’t retrigger credit.
Beehiiv hasn’t shipped this yet. It’s been reported in their community forum since mid-2025, acknowledged by support, but not prioritized in the public roadmap.
Workarounds until they fix it
If you’re awarding physical rewards or high-value digital products, audit your referral credits manually before each batch. Export, filter, deduplicate, then fulfill.
If you’re using referral milestones as a growth lever but don’t want to audit constantly, pad your reward thresholds by 10–15%. Assume some credits are phantom and price accordingly.
And if you’re building a referral program from scratch and need clean attribution out of the gate, consider running it outside Beehiiv. SparkLoop integrates with Beehiiv via API and handles attribution more conservatively. You’ll pay $50/month minimum, but the data is cleaner.
If you’ve spotted referral double-counting in your own newsletter—Beehiiv or otherwise—reply and let us know how you’re handling it. We’re tracking workarounds and will update this piece if the platform patches it.

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.
26 August 2026

► Necessary Cookies Always Active

Necessary cookies enable essential site features like secure log-ins and consent preference adjustments. They do not store personal data.

► Functional Cookies Remark

Functional cookies support features like content sharing on social media, collecting feedback, and enabling third-party tools.

► Analytical Cookies Remark

Analytical cookies track visitor interactions, providing insights on metrics like visitor count, bounce rate, and traffic sources.

► Advertisement Cookies Remark

Advertisement cookies deliver personalized ads based on your previous visits and analyze the effectiveness of ad campaigns.