How to Set Up ConvertKit for Multiple Websites: A Step-by-Step Guide for Small Teams

Teams with strict client-separation requirements should verify the relevant vendor's current account, access, and data-handling model before relying on it for that workflow. This tutorial walks your team through the exact configuration so subscribers stay organized by site, automations fire correctly, and nothing bleeds across properties.

Who this is for: Small teams running between 5 and 50 websites — content networks, niche site portfolios, regional brand clusters, or multi-product creator businesses — who need one accountable email system without per-site subscription chaos.

Before You Start: Requirements Checklist

Run through the table below before opening ConvertKit. Every item in the Requirement column needs to be confirmed by at least one person on your team before you touch a single automation.

What You Will Have When This Tutorial Is Complete

By the end of all five sections, your team will have reached the following exact system state:

• One ConvertKit account handling email for all websites in your portfolio — no duplicated billing, no disconnected inboxes
• A consistent tag and segment structure that routes each subscriber to the correct site identity, preventing list contamination across properties
• At least one working opt-in form per website, each mapped to a site-specific tag and trigger sequence
• At least one automation per site that confirms a new subscriber's origin and starts the appropriate welcome sequence
• Sender identities configured so recipients see the correct brand name and sending domain for whichever site they subscribed to
• A broadcast workflow your team can repeat without revisiting the architecture — just select the right segment and send

That outcome covers the structural layer. It does not automatically set up every campaign you will ever send — but it gives your team a durable foundation so adding a new website later becomes a repeatable process rather than a rebuild.

Why One Account — Not Many — Is the Right Starting Point

Teams new to managing a website portfolio often default to the most obvious mental model: one ConvertKit account per website. It feels clean in theory. In practice, it creates a fragmentation problem that compounds as the portfolio grows. You end up managing separate billing cycles, separate subscriber counts that don't combine toward plan thresholds efficiently, separate automation libraries with no shared logic, and no way to identify subscribers who appear across multiple sites in your network.

The single-account approach — the architecture this tutorial teaches — lets your team treat the ConvertKit account as infrastructure rather than a per-project tool. Subscribers are distinguished by tags and segments, not by account boundaries. Automations can be shared or isolated at the workflow level. And when a site in your portfolio is retired or sold, removing it from the system is a tag-cleanup task rather than an account migration.

Explore ConvertKit Through Our Partner Link

There are genuine edge cases where a second account makes sense: a site with a fundamentally different audience that must never receive cross-promotional content, or a property operated

Steps 1 to 3: Building Your Multi-Site Foundation in ConvertKit

Getting ConvertKit configured correctly from the start saves your team from messy subscriber data, tangled automations, and audience overlap that compounds with every site you add. The three steps below establish the structural decisions that everything else depends on — segment logic, form strategy, and tagging architecture. Work through them in order, and the rest of the setup becomes considerably more straightforward.

Step 1: Decide Between One Account or Multiple Accounts Before You Touch Anything Else

This is the most consequential decision you will make, and most teams make it wrong by defaulting to "one account per site" because it feels tidy. For teams managing a portfolio of five to fifty websites, that approach creates a billing and operations nightmare — separate invoices, separate subscriber counts, duplicated sequences, and no way to cross-promote audiences without exporting and importing CSV files.

ConvertKit's single-account model is built to handle multiple websites through tags, segments, and custom fields rather than separate accounts. One account, one subscriber list, intelligent segmentation. That architecture is why understanding how to set up ConvertKit for multiple websites really means understanding how to use tags and segments to create clean logical separation between sites without physically separating the data.

When does a separate account actually make sense? Two scenarios justify it: when a site belongs to a genuinely separate business with its own billing, or when two properties must never share subscriber data for legal or contractual reasons. If neither applies, keep everything in one account.

How to verify you're set up correctly: After deciding on a single-account structure, confirm that your account's subscriber view is empty of any pre-existing test contacts before you build anything. A clean slate prevents inherited tag conflicts. Navigate to your subscribers list, filter by all statuses, and make sure any test emails from the account creation process are removed or clearly marked.

Step 2: Create a Consistent Site-Level Tagging Convention

Once you've committed to a single-account structure, your next job is designing a tag taxonomy before you build a single form or sequence. This step is where teams consistently underinvest, and the results show up six months later as a subscriber list nobody can navigate.

The most durable approach for multi-site teams is a prefix-based tag system. Assign each website in your portfolio a short, stable identifier — typically a two-to-five character abbreviation — and prefix every site-specific tag with it. A subscriber who signed up through your travel deals site and your personal finance newsletter should carry tags like trvl-newsletter and pfin-newsletter rather than two tags both named "newsletter-subscriber." The prefix makes filtering by site instant and unambiguous.

Plan your tag categories at the same time. Most multi-site teams need at minimum three categories of tags per site: acquisition source (how the subscriber arrived), content interest (what they opted into), and behavioral state (what they've done since subscribing). You don't need to build all the behavioral tags on day one, but knowing the naming pattern in advance prevents you from creating trvl-clicked-email on one site and pfin_email_click on another, which breaks the consistency that makes segmentation fast.

ConvertKit applies tags through forms, automations, and the API. At this stage, you're only building the vocabulary — the actual application of tags happens in Step 3 and onward. Write your tag list in a shared document your team can reference. Include the prefix, the full tag name, and a one-sentence description of what triggers it.

How to verify your taxonomy is complete enough: Run through a hypothetical subscriber journey for your two most different websites. Can you answer "which tags would this person have after signing up, reading three emails, and clicking a product link?" entirely from your tag list? If any step requires you to invent a new tag on the fly, your taxonomy has gaps. Fill them now, not during a live campaign.

Step 3: Build Site-Specific Forms with Embedded Tagging Built In

Forms are where your structural decisions become live infrastructure. Every website in your portfolio needs at least one form, and each form must tag new subscribers with their origin site the moment they confirm. This is non-negotiable for multi-site setups — without origin tagging at the point of opt-in, you lose the ability to segment by site retroactively without a time-consuming manual audit.

In ConvertKit, you create forms under the Grow → Landing Pages & Forms section. For each site, create a dedicated form rather than reusing a generic form across properties. Give each form a name that includes the site prefix you established in Step 2 — for example, TRVL — Homepage Sidebar Opt-In. Clear naming discipline here prevents confusion when you're managing dozens of forms across a large portfolio.

After creating the form, go to its settings and locate the tag assignment option. Apply the site-level acquisition tag you defined in Step 2 as a form-level tag. This means every subscriber who comes through that form is tagged automatically, with no automation rule required. It's the lowest-friction, most reliable way to track origin across a multi-site setup.

If you're embedding forms on external websites rather than using ConvertKit landing pages, you have two integration paths: the embed code ConvertKit generates for each form, or the ConvertKit API for teams with developer resources. Both work well at scale. The embed code is the practical choice for most small teams because it requires no custom development and updates automatically when you change form settings inside ConvertKit.

For teams

Steps 4 to 6: Segmentation, Automation, and Digital Product Delivery Across Your Sites

Once you have your account structure, forms, and tagging logic in place for the first few properties, the real leverage of understanding how to set up ConvertKit for multiple websites comes from steps four through six. This is where your early groundwork starts compounding: the same automation sequences serve dozens of sites, product sales flow through a unified delivery system, and your team stops managing subscriber hygiene manually. The structural patterns here deliberately differ from steps one through three — rather than linear setup actions, these steps involve layered configuration choices where the order of decisions matters as much as the decisions themselves.

Step 4: Build Automation Sequences That Work Across Site Contexts

Automation in ConvertKit operates through two distinct tools: sequences (linear, time-based email series) and visual automations (conditional workflows triggered by subscriber behavior, tags, or form submissions). For a small team running five to fifty websites, the distinction matters practically. A sequence is the right choice when the follow-up logic is the same regardless of where a subscriber came from — a seven-day onboarding email course, for example, or a weekly digest. A visual automation is the right choice when a subscriber's behavior on one site should trigger a different experience than behavior on another.

The most common mistake teams make at this stage is building site-specific sequences for every property. That approach becomes unmanageable fast. Instead, build sequences around subscriber intent and audience state, not around the originating site. A subscriber who downloaded a lead magnet on a productivity site and a subscriber who did the same on a finance site may be at an identical point in their relationship with your brand — both are new, both are curious, both deserve a strong welcome series. The site they came from becomes a tag, not a separate sequence.

Where you do want to branch by site is inside visual automations. ConvertKit's visual automation builder lets you use tag-based conditions as branching logic. A subscriber tagged with the specific site slug can be routed into a path that sends one piece of content, while a subscriber tagged from a different property gets a variation. Both paths can rejoin the same main sequence afterward. This keeps your email content library lean while still allowing meaningful personalization by site origin.

When setting up automations for teams, think about who owns what. ConvertKit is a single-account environment, meaning every team member with account access can edit every automation. There is no role-based permission system that restricts a team member to only the sequences related to their assigned sites. In practice, this means your team needs a documented convention for which automations are safe to edit versus locked for review. That conversation is worth having before you have forty active sequences and someone edits the wrong one on a Friday afternoon.

For each site in your portfolio, map out three automation states before building anything: what happens immediately after a subscriber joins (the trigger), what the steady-state experience looks like (the nurture sequence), and what happens when a subscriber signals buying intent (the conversion path). Many teams starting to learn how to use ConvertKit for email marketing at scale only plan the first state and improvise the rest. That improvisation creates inconsistent subscriber experiences across your properties and makes auditing your automations painful later.

Step 5: Configure Product Delivery for Multiple Sites Using ConvertKit Commerce

See How ConvertKit Fits Your Workflow

If any of your sites sell digital products — guides, templates, courses, memberships, downloadable tools — ConvertKit's built-in commerce feature lets you handle payment, delivery, and post-purchase automation inside the same platform where you manage your subscribers. Understanding how to use ConvertKit to sell digital products across multiple sites requires thinking about the product catalog and delivery logic before you start creating individual product listings.

ConvertKit Commerce allows you to create individual product pages hosted on ConvertKit's infrastructure. Each product has its own URL, which means you can link to it from any of your websites without needing a site-specific storefront or third-party payment processor integration. For a small team managing many sites, this is a meaningful operational advantage: one product can serve multiple sites, and the purchase confirmation, receipt, and delivery automation are configured once.

The key configuration decision is how you structure post-purchase tags and automations. When a subscriber purchases a product, ConvertKit can automatically apply a tag, add them to a sequence, or trigger a visual automation. For multi-site operations, use purchase tags that encode both the product purchased and the site context where relevant. A subscriber who bought a template pack through your design site should be tagged differently than one who bought the same product through your marketing site — not because the product is different, but because the next best follow-up communication probably is.

Product delivery in ConvertKit works through automated email — the platform sends the purchaser a delivery email with the download link or access instructions you configure. For products sold across multiple sites, make sure your delivery email copy is site-agnostic unless you are using tag-conditional content. Referencing a specific brand name in a delivery email when the purchase came through a different branded property creates a confusing experience for your subscriber.

For teams where some sites are revenue-generating and others are lead-generation only, resist the temptation to skip the commerce configuration on the lead-gen properties. Even if a site is not currently selling anything, configuring a post-lead sequence that smoothly introduces your paid products from another site in your portfolio is a direct revenue path. The subscriber database is shared across your account — the question is whether you have the automation in place to use that shared context productively.

One workflow worth building early: a tag that fires when any subscriber across any of your sites has been on your list for a

Troubleshooting Common Problems When Setting Up ConvertKit for Multiple Websites

Even a well-planned ConvertKit setup for multiple websites can surface friction in the first few weeks. The problems that trip up small teams managing several properties are usually not bugs — they are configuration choices that made sense for a single site but break down at scale. This section covers the failures that show up most often, how to diagnose them quickly, and the validation checks you should run before treating any fix as complete.

Subscribers Are Landing in the Wrong Website Segment

This is the most common and most damaging problem in a multi-site setup. When a subscriber opts in on your home-improvement site but ends up in your finance newsletter sequence, the experience is immediately broken and unsubscribe rates rise. The root cause is almost always a missing or incorrect tag on the form embed code.

Check every opt-in form by opening it inside ConvertKit and confirming that the tag assigned to it exactly matches the naming convention your team agreed on — for example, site:homereview versus site:financeweekly. If two forms share a tag, subscribers from both sites will appear indistinguishable in filtered views and automated sequences will fire for the wrong audience.

After correcting a tag, submit a real test subscriber through the live form on the actual website — not the ConvertKit preview. Check the subscriber record in ConvertKit within two minutes and confirm the correct tags appear and no legacy tags persist from a previous form version. If a stale tag is present, the form embed code on the website itself may still be pointing to an old form ID. Re-copy the embed snippet from the current form and replace it on the site.

Automation Sequences Fire for All Sites Instead of One

When a welcome sequence is meant only for subscribers from a specific property but is also triggering for contacts from your other websites, the automation trigger is misconfigured. An automation set to trigger on "joins a form" with no tag filter will catch any subscriber who enters through any form, depending on how rules are stacked.

Open the automation and review the entry trigger. If it says "subscribes to a form" and the form listed is a shared or global form, that is the problem. The safest fix for multi-site teams is to change the trigger to "is tagged" and specify the site-specific tag. This way, the sequence fires only when a subscriber carries that exact tag — regardless of which form, landing page, or import method brought them into ConvertKit.

After editing the trigger, do not rely on past subscriber records to validate. Create a new test contact, manually apply the correct site tag, and confirm the automation entry event fires within a few minutes in the subscriber's activity log. Then add a second test contact without the tag and confirm the sequence does not trigger. Both checks are required.

Broadcast Emails Are Sending to the Entire List

A broadcast meant for one website's audience but sent to all subscribers across every property is one of the highest-cost mistakes in a multi-site operation. It erodes trust with subscribers who have no relationship with that content, and it inflates unsubscribe counts in ways that are hard to reverse.

Before any broadcast send, check the "Send to" filter in the broadcast composer. The filter should include the site-specific tag and exclude tags belonging to other properties. If your team routinely skips this step under deadline pressure, add a mandatory pre-send checklist item: read the segment filter aloud and confirm it against the intended website. This sounds procedural rather than technical, but broadcast filter errors are almost never caused by a ConvertKit bug — they are caused by a human skipping the review step.

For teams managing ten or more websites, the safest structural habit is to draft every broadcast in a clearly labeled folder or with a site-prefix in the subject line during the draft stage, so the intended audience is visible at a glance before anyone clicks send.

Tags Are Not Applying After Form Submission

If a subscriber completes a form but the expected tag is absent from their record, work through these checks in order. First, confirm the tag is saved to the form, not just named — open the form settings and look under the incentive or confirmation tab where tags are assigned; it is possible to name a tag on one screen without saving it to the form's trigger. Second, confirm the tag actually exists in your ConvertKit account tag list; if someone deleted or renamed it after the form was built, the assignment will silently fail. Third, check whether a subscriber already existed in the account under that email address — in some cases, an existing subscriber rejoining through a form may require different handling depending on your account's subscriber status rules.

After each of these checks, submit a fresh test subscriber and watch the activity log in real time. Do not reuse a test email address that already exists in the account, because the behavior may differ from a genuinely new subscriber's experience.

Confirmation Emails Are Sending the Wrong Incentive or Content

Each form in ConvertKit can have its own incentive email, but teams building forms quickly across multiple sites sometimes copy a form from one property and forget to update the incentive content before publishing it on a different site. A subscriber opting into a cooking website newsletter and receiving a PDF about personal finance is a serious relevance failure.

Run a periodic audit — monthly is a reasonable interval for teams managing more than a dozen sites — where you submit a test to every active form and read the resulting confirmation email. Confirm that the sender name, the incentive attachment or link, and the body copy all match the website the form lives on. This is a slow check, but it is the only way to catch drift that accumulates as forms are duplicated and modified over time.

Subscriber Counts Look Wrong in Filtered Views

When a tag-filtered segment shows a subscriber count that does not match what the team expects, the most

Did It Work? And Are You Ready to Go Live?

Evaluate current product details against your requirements and confirm time-sensitive terms before subscribing. These are different questions, and conflating them is one of the most common reasons multi-site email programs launch with holes in them.

Did It Work? Binary Objective Checks

Each of the following checks has a clear pass or fail outcome. Work through them in order. Do not move to the go-live readiness review until every item below is a confirmed pass.

1. Subscriber Source Tagging Is Firing Correctly

Pull up a test subscriber record inside ConvertKit after submitting a form on each of your sites. Confirm that the tag or custom field identifying the originating site is present on the subscriber record. If you have ten sites, verify ten test records — one per site. A tag that appears on nine out of ten is not a pass. Missing source attribution means your segmentation and any automation that depends on site-of-origin will produce incorrect behavior from the first real subscriber forward.

2. Automations Are Enrolling the Right Subscribers

Trigger the entry condition for each automation you have built — typically a form submission, a tag being applied, or a purchase event. Then verify inside the automation's subscriber list that the test address enrolled and progressed through the correct sequence steps. Check that the automation did not enroll subscribers from other sites in your account who share unrelated tags. Cross-contamination at the automation entry point is a structural problem that compounds quickly.

3. Confirmation and Welcome Emails Are Delivering

Submit a test opt-in using a real external inbox — not an address at the same domain you are testing — and confirm that the double opt-in or single opt-in confirmation email arrives, that the sender name and reply-to address are correct for that specific site, and that any welcome sequence email follows in the expected window. Check the email rendering in at least two clients. A welcome email that fires but sends broken HTML or the wrong sender identity is a fail.

4. Segments Reflect Accurate Subscriber Counts

Open each segment or tag filter you have created for individual sites. The count should match the number of confirmed test submissions you have made for that site and no more. If a segment intended for Site A is pulling in subscribers tagged for Site B, your tag logic has an error that needs to be resolved before launch.

5. Commerce or Product Delivery Triggers Are Functional (If Applicable)

If you are using ConvertKit to support digital product delivery or purchase-triggered sequences across any of your sites, complete an end-to-end test purchase using a test transaction. Confirm that the purchase event fires the correct tag or automation entry, that the delivery email reaches the buyer inbox, and that the subscriber record reflects the purchase event. A product delivery sequence that fails silently on the first real sale is a support and refund problem, not just a configuration note.

Ready to Go Live? Subjective Readiness Assessment

Passing the binary checks confirms that the wiring works. The readiness questions below ask whether your team and your processes are in a position to manage what happens after subscribers start arriving at scale across multiple properties.

Team Ownership Is Assigned

At minimum, someone on your team should own ConvertKit account-level decisions — broadcast scheduling, list hygiene, suppression management, deliverability monitoring — and someone should own per-site configuration changes such as form updates and tag additions. In small teams these may be the same person, but that person should know they own it. Ambiguous ownership across five or more sites means that deliverability problems, broken automations, and unsubscribe compliance issues go unnoticed for longer than they should.

Your Naming Convention Is Documented and Enforced

If you have more than three sites running through the same ConvertKit account, a consistent naming convention for tags, segments, forms, and automations is not optional — it is the difference between an account that is manageable in six months and one that requires hours of archaeology to interpret. Before going live, confirm that the naming convention is written down, accessible to everyone who touches the account, and that no existing tags or forms violate it. Cleaning up a broken naming convention after thousands of subscribers have been tagged is a significant time cost.

Your Unsubscribe and Compliance Workflow Is In Place

ConvertKit handles global unsubscribes mechanically, but your team needs to understand what that means for multi-site operations. A subscriber who opts out from one site's list may be globally unsubscribed from all sends through your account depending on how your sequences and broadcasts are configured. Confirm that your team understands how unsubscribe scope works in your specific setup, that you have a process for handling manual opt-out requests that arrive outside ConvertKit, and that any legal requirements relevant to your subscriber geographies are addressed.

You Have a Broadcast Review Step Before Any Multi-Site Send

Sending a broadcast to the wrong segment — or forgetting to scope a broadcast to a specific site's audience and accidentally mailing your entire list — is one of the most common and damaging mistakes in multi-site ConvertKit accounts. Before going live, establish a two-step review for any broadcast: one person drafts and sets the segment filter, a second person verifies the recipient count and segment logic before sending. The cost of this step is a few minutes. The cost of skipping it can be significant subscriber churn and deliverability damage.

You Have a

Check ConvertKit Fit and Current Options

Current plans and pricing: Use our partner link to view current plans, pricing, and any available offers. Final pricing and promotional terms are set by the provider and may vary by plan, billing cycle, usage, region, and eligibility.