ConvertKit’s visual automation builder is powerful, but it has one behavior that trips up nearly every operator the first time they encounter it: automations can trigger the same sequence or action more than once for the same subscriber.
This isn’t a bug. It’s how the platform handles conditional branching and re-entry logic. But if you don’t understand when and why it happens, you’ll send duplicate emails, apply tags twice, or fire webhook actions that were only supposed to run once.
Here’s how to structure your automations so they behave the way you expect.
What causes duplicate triggers
ConvertKit automations are event-driven. Every time a subscriber meets a trigger condition—subscribing to a form, clicking a link, being tagged—the automation evaluates whether to run.
The problem arises when a subscriber re-enters an automation they’ve already completed. By default, ConvertKit allows re-entry unless you explicitly configure the automation to block it.
Common scenarios where this happens:
- A subscriber clicks the same link twice in two different emails, and both clicks trigger the same automation.
- You tag someone manually, then a separate automation tags them again with the same tag, re-triggering a tag-based automation.
- A form submission triggers an automation, and you later re-import that subscriber via CSV, which fires the form’s “new subscriber” trigger a second time.
ConvertKit doesn’t deduplicate these events automatically. If the trigger fires, the automation runs—even if the subscriber has already been through it.
How to prevent re-entry
ConvertKit gives you two ways to control re-entry: automation-level settings and conditional branching within the automation itself.
Automation-level re-entry settings: When you create or edit an automation, you can toggle whether subscribers are allowed to re-enter after completing it. This is buried in the automation’s settings panel (top-right corner of the builder). If you turn off re-entry, a subscriber who completes the automation will never trigger it again, even if they meet the trigger condition multiple times.
This works well for one-time sequences: welcome emails, onboarding flows, or product-launch announcements. Once someone’s been through it, they don’t need to see it again.
Conditional branching: For automations that should sometimes re-run but not always, use ConvertKit’s “Conditions” step. You can add a condition at the top of your automation that checks whether the subscriber already has a specific tag. If they do, branch them to an empty path that does nothing. If they don’t, proceed with the sequence and apply the tag at the end.
This approach gives you fine-grained control. For example, if you’re running a link-click automation that sends a resource, you can check for a “resource_sent” tag before delivering it. The automation can fire as many times as the subscriber clicks, but the email only goes out once.
When duplicate triggers are intentional
Not all duplicate triggers are mistakes. Some automations are designed to run repeatedly.
If you’re tracking engagement—say, tagging subscribers every time they click a specific link—you want the automation to fire on every click. You’re not sending an email; you’re incrementing a behavioral signal.
Similarly, if you’re using ConvertKit’s “Events and Triggers” to fire webhooks to external tools (like Zapier or Make), you may want every instance of the trigger to pass through. A subscriber clicking a “buy now” link twice might indicate two separate purchase intents, and your external workflow should handle both.
In these cases, leave re-entry enabled and structure your automation to handle repeat runs gracefully. Use tags or custom fields to track state, and let your downstream logic decide what to do with duplicate events.
What to check if you’re seeing duplicates
If you’re already seeing duplicate sends or actions, audit your automations in this order:
- Check the automation’s re-entry setting. If it’s on, decide whether it should be.
- Look for overlapping triggers. Two automations with the same trigger (e.g., “subscriber added tag X”) will both fire. Consolidate them or add conditions to prevent overlap.
- Review your tagging logic. If multiple automations or manual actions apply the same tag, every tag application will re-trigger tag-based automations.
- Check your form settings. ConvertKit’s “subscribe on form submit” trigger fires every time the form is submitted, even if the email is already in your list. If you’re re-importing subscribers or using the same form for multiple purposes, this can cause unexpected re-entry.
ConvertKit’s automation history (under “Subscribers” → individual subscriber profile → “Automation History”) shows every automation run for that subscriber, including timestamps. If you see the same automation listed multiple times, trace back to the trigger event and check your re-entry settings.
Bottom line
ConvertKit’s automation re-entry behavior is consistent once you know the rules, but it’s not obvious from the interface. Treat every automation as re-entry-enabled by default, and explicitly configure the ones that should only run once.
If you’re building complex flows—multi-step onboarding, behavioral segmentation, or event-driven sequences—test with a dummy subscriber and watch the automation history. You’ll catch duplicate triggers before they reach your list.
Got a ConvertKit automation question? Reply to this email—I read every one.
