ConvertKit custom fields bloat profiles—tags often work better
The hum of the coffee machine in the corner, the faint smell of rain through the open window, and a ConvertKit automation canvas filling your second monitor—three branches deep and already losing track of which subscribers are where.
ConvertKit custom fields bloat subscriber profiles when tags would have worked
Custom fields store granular data, but tags often solve the same segmentation problem faster and cleaner.
Most operators add a custom field the moment they need to segment by preference, location, or purchase history. It feels tidy: drop-downs, text boxes, dates—structured data you can filter and sort. But custom fields introduce hidden costs. Every field adds a database column, bloats your subscriber export, and slows down bulk operations. ConvertKit charges the same whether you store five fields or fifty, but your own workflow starts to break when you’re scrolling past twenty half-empty fields to find the one that matters today.
Tags solve 80% of the same problems with none of the overhead. A tag is binary—present or absent—so you can segment just as precisely without the schema creep. If you need to know whether a subscriber downloaded your lead magnet, a tag (“Downloaded: Lead Magnet Q2 2026”) works as well as a custom field labelled “Lead Magnet Download Date”. The tag fires faster in automations, renders instantly in segment builders, and doesn’t clutter your CSV when you migrate platforms next year. Custom fields make sense when you need to store a value you’ll reference later—actual dates for anniversary emails, numeric scores for lead qualification, or free-text replies you’ll read manually. Everything else is a tag dressed up as a field.
The break-point is searchability. If you need to filter by “greater than” or “contains”, you need a custom field. If you’re just asking “yes or no”, you need a tag. Most operators get this backwards because custom fields look more professional in the UI. They’re not. They’re technical debt in a pretty wrapper.
AUTOMATION
ConvertKit’s visual automation builder breaks when branches nest too deep
ConvertKit’s drag-and-drop canvas makes automation look simple—until you add conditional branches inside other conditions and discover subscribers either skip entire sequences or receive the same email twice. The visual builder doesn’t surface conflicts between parallel paths, and there’s no warning when a subscriber qualifies for two mutually exclusive branches at once. Most operators only notice when complaint rates spike or a manual audit reveals half the list never entered the funnel. The fix isn’t more conditions—it’s fewer, flatter automations that rely on tags to route subscribers before they hit the canvas.
WORKFLOW
Zapier’s delay step silently kills automations when paired with webhooks
Zapier’s built-in delay—”wait one hour”, “wait until next Tuesday”—looks harmless in the editor, but it introduces a persistent state that webhooks and conditional logic can’t always resolve. If a webhook fires while a Zap is paused mid-delay, the data never catches up. If the delay triggers during an API timeout, the entire Zap halts without retry. You won’t see an error in the dashboard; the task just vanishes from the log. The symptom is silent: subscribers who should have received a welcome email three hours after signup never do, and your task history shows the trigger fired but the action never ran.
TRAFFIC
Google Search Console’s URL Inspection Tool checks more than indexing status
Most operators treat the URL Inspection Tool as a binary check—indexed or not—but it also reports mobile usability errors, structured data warnings, and whether Googlebot could fetch your page’s JavaScript. If you’re troubleshooting why a post isn’t ranking despite being indexed, the inspection panel often reveals a mobile viewport misconfiguration or a failed Core Web Vitals threshold that the main Search Console dashboard doesn’t surface. The tool runs a live test every time you click “Test Live URL”, so you can validate fixes in real time before waiting days for the next crawl. It’s the fastest way to confirm whether a technical change actually reached Google’s renderer.
Know someone who would like this? Forward today’s email — every operator we reach is one closer to running an online business with a little less friction.