Pair this with ConvertKit for 5 to 50 Websites Pricing: Is It Worth It for Small Multi-Site Teams? and ConvertKit Review for Marketing Teams: Honest Verdict for Small Teams Running 5 to 50 Webs to plan your next move.
If your team manages five or more websites and you need a single email platform that keeps subscriber lists, automations, and broadcasts cleanly separated by client or property, ConvertKit handles that without requiring a separate account for each site. By the end of this tutorial, every team member will be operating from one shared workspace with organized tags, segmented audiences, and at least one live automation per website property.
Requirements Before You Start
| Requirement | Have It? | Where to Get It |
|---|---|---|
| A ConvertKit account (Creator or Creator Pro plan) | Needed | ConvertKit.com — choose the plan that covers your total subscriber count across all properties |
| Admin or owner-level access for at least one team member | Needed | Set in ConvertKit account settings under Team Members |
| A confirmed sending domain for each website you manage | Needed | Your DNS provider (Cloudflare, Namecheap, or similar); ConvertKit walks you through the DKIM and SPF records |
| A tag and segment naming convention agreed on by the team | Needed | Create a shared doc in Notion, Google Docs, or any team wiki before logging in |
| Subscriber import files (CSV) for any existing lists | If migrating | Export from your current platform; ensure consent records are included |
| Opt-in form embed codes or API access for each website's CMS | Needed | Generated inside ConvertKit after forms are created; paste into your CMS or use a plugin if WordPress is in the mix |
Pricing note: Promotional discounts and bonus limits may be time-limited and may not be available at renewal. Always confirm current pricing on the vendor's official site before purchasing.
What You Will Have When This Tutorial Is Complete
When you finish all five sections of this tutorial, your team's ConvertKit workspace will be in the following exact state:
- One ConvertKit account shared across your team with named user roles assigned
- A consistent tag structure that separates subscribers by website property, lead source, and engagement level
- At least one opt-in form per website, each feeding subscribers into a property-specific tag automatically
- A welcome sequence automation active for at least one property, with branching logic ready to extend to others
- A broadcast template approved by the team so anyone can send a campaign without reformatting from scratch
- A reporting view filtered per property so you can show each client or site owner their own numbers without exposing data from other properties
[SiteName]-[Source]-[Status] (for example, acmeblog-newsletter-active) prevents the tag library from becoming a mess of duplicates that nobody can interpret six months later.This tutorial is written specifically for small marketing teams running between five and fifty websites — whether those are client sites, owned media properties, or a combination. If your team only manages one or two websites, ConvertKit's free tier and a simpler single-list setup may be all you need, and this level of structure would be overkill. If you are running a large agency with dedicated account managers per client, you will likely want separate ConvertKit accounts per client rather than the shared workspace approach described here.
Open the Email Marketing hubSteps 1–3: Building the Foundation for Multi-Site Email Operations in ConvertKit
Getting ConvertKit working well across five or more websites is less about learning the interface and more about making the right structural decisions early. A team that skips setup planning often ends up with tangled subscriber lists, overlapping automations, and no clean way to report on a single site's performance. The three steps below address that directly.
Step 1: Decide on a Single-Account vs. Multiple-Account Structure
Before importing a single subscriber, every team managing several websites needs to answer one question: should all sites live under one ConvertKit account, or should each site have its own?
ConvertKit's subscriber count is account-wide, so running ten sites from one account means you pay for the combined audience. That is often cheaper than ten separate plans. However, one account means one broadcast sender name and one global unsubscribe — a subscriber who opts out from one site's list leaves your entire account. For client work where each site belongs to a different business owner, separate accounts per client almost always make more sense, both legally and operationally.
For internal multi-site teams — think a media company running several niche publications — a single account with strict tagging discipline usually works. To verify your choice is right, sketch out two scenarios: one where a subscriber from Site A accidentally receives an email intended for Site B, and one where a client demands a full data export of their audience. If either scenario creates a serious problem, adjust your structure before proceeding.
Step 2: Build Your Tag and Custom Field Schema Before Importing Anyone
Tags in ConvertKit are how you identify which site a subscriber came from, what they opted into, and where they are in a funnel. Custom fields let you store metadata like the referring site slug, acquisition date, or lead magnet title. Neither costs extra, but both require a naming convention your whole team agrees on before any data enters the system.
A workable schema for multi-site teams uses three tag layers: source (which site), interest (which topic or product), and status (lead, customer, or churn risk). Keep tag names lowercase, hyphenated, and unambiguous — site-financeweekly is better than FW or finance. Custom fields should mirror the data you will actually use in segmentation or personalization, not every piece of information you could theoretically collect.
To verify this step, build a test subscriber record manually and assign all the tags and field values you expect a real opt-in to carry. If you can identify exactly which site, form, and interest the test record represents just by reading its tags, your schema works.
Step 3: Connect Your First Site's Opt-In Forms and Confirm Data Is Flowing Correctly
Once the account structure and tag schema are set, connect one site first. ConvertKit's native form builder generates embeddable code that works on most CMS platforms. For teams using WordPress, the official ConvertKit plugin handles form injection without custom code. Other platforms typically accept the raw JavaScript embed or an API-connected integration via Zapier.
After a test submission, check three things in ConvertKit: the subscriber appears in the correct segment, the source tag is applied automatically, and any automation tied to that form fires as expected. Do not scale to additional sites until all three are confirmed on the first one.
Open the Email Marketing hubSteps 4 to 6: Building Client Workflows, Broadcast Strategy, and Reporting Habits
Once your tags and sequences are running (covered in steps 1 through 3), the practical challenge for a small team managing multiple websites shifts to keeping everything organized across clients, maintaining a consistent broadcast rhythm, and reading the right numbers at the right time. Steps 4 through 6 address exactly those decision points.
Step 4: Set Up Separate Automations for Each Client Property
One of the most important choices in learning how to use ConvertKit for client workflows is deciding how automation is scoped per site. ConvertKit organizes everything within a single account, so the separation you create is entirely structural — it lives in how you name and nest your automations.
Create one Visual Automation per website or client brand. Give each automation a naming prefix that matches the property, for example SITE-ALPHA: Welcome + Nurture or SITE-BRAVO: Lead Magnet Delivery. Inside each automation, use the entry trigger tied to that site's opt-in form. This ensures a subscriber who comes through Site Alpha never receives Site Bravo's onboarding sequence.
Within each automation, build logical branches using ConvertKit's conditional steps. A subscriber who clicks a specific link gets tagged and routed differently from one who does not. This is the foundation of how to use ConvertKit for email marketing in a multi-site environment — one account, clean lane separation, no subscriber crossover.
Step 5: Build a Repeatable Broadcast Schedule Across Properties
Broadcasts in ConvertKit are one-time sends to a filtered segment. For teams running 5 or more websites, the risk is either over-sending to a shared list or under-sending because no one owns the broadcast calendar. Neither is acceptable when clients measure results weekly.
Use ConvertKit's subscriber filter at the broadcast level to restrict sends by tag. Before scheduling, always confirm the tag filter returns only subscribers belonging to that specific site. Send a test to yourself using the preview function, verify the sender name and reply-to address match the client property, then schedule.
A practical cadence for most content-driven sites is one broadcast per week, scheduled Tuesday through Thursday, between 8 a.m. and 11 a.m. in the subscriber's local timezone if you have enough data to enable timezone sending. ConvertKit supports this natively on paid plans.
Step 6: Read the Right Metrics and Act on Them
ConvertKit's reporting surfaces open rate, click rate, unsubscribes per broadcast, and sequence-level performance. For a team managing many sites, how to use ConvertKit best practices means resisting the urge to optimize every number simultaneously.
Pick two metrics per client property each month: open rate trend and click rate trend. If open rates drop two broadcasts in a row, the subject line approach needs testing. If click rates stay flat while opens are healthy, the body copy or call-to-action placement needs attention. ConvertKit's A/B subject line testing on broadcasts gives you a direct tool for the first problem.
With automations scoped correctly, broadcasts running on a reliable schedule, and metrics reviewed on a fixed cadence, your team has a repeatable operating model — not just a tool configuration.
Explore ConvertKit's Automation and Broadcast FeaturesTroubleshooting ConvertKit for Marketing Teams: Common Failures and Fixes
Even teams who have a solid grip on how to use ConvertKit for marketing teams run into recurring problems. The issues below appear most often when a small team is juggling five or more websites inside a single ConvertKit account. Each fix includes a validation check so you can confirm the problem is actually resolved before moving on.
1. Subscribers Are Not Receiving Confirmation Emails
Double opt-in is enabled by default on most ConvertKit forms. If a subscriber never clicks the confirmation link, they land in an unconfirmed state and will never receive your sequences. First, go to Forms > Settings > Incentive for the specific form and verify that the confirmation email is active and not accidentally set to a custom domain that has no DNS records pointing to it. Then check your sending domain under Account Settings > Email and confirm DKIM and SPF records are verified. Unverified sending domains push confirmation emails straight to spam.
Validation check: Subscribe yourself using an address on Gmail, Outlook, and one inbox with strict filters. If any of those fail, your DNS records need attention before you run any campaign for that website.
2. Automations Trigger but Subscribers Fall Out Mid-Sequence
This is the most disruptive failure when learning how to use ConvertKit for client workflows across multiple properties. Subscribers exit an automation silently when a second automation removes a tag that the first automation uses as a condition. With many websites feeding into one account, tag collisions are common.
Open Automations > Visual Builder and trace every "Remove Tag" action. Cross-reference your tag naming convention. A site-prefixed tag structure—for example site-alpha: lead versus site-beta: lead—prevents one site's automation from stripping a tag that another site's sequence depends on.
Validation check: Use ConvertKit's subscriber activity log on any test subscriber to confirm each automation step fires in order without an unexpected exit point.
3. Broadcast Open Rates Drop Suddenly Across Multiple Sites
A shared sending domain means that deliverability problems on one site's list affect every broadcast you send. If your overall open rate drops more than eight percentage points in a single send cycle, check your subscriber list health. High bounce rates and spam complaints on one website's segment drag down sender reputation for all of them.
Navigate to Subscribers > Cold Subscribers and run a re-engagement sequence before purging. ConvertKit's built-in cold subscriber filter identifies contacts who have not opened in 90 days. Removing non-responders after a re-engagement attempt is one of the most consistent how to use ConvertKit best practices that directly protects domain reputation.
4. Custom Fields Are Blank in Broadcast Personalization
Personalization tags such as {{ subscriber.first_name }} appear as blank space when the field was never populated at opt-in. Audit your forms under Forms > Fields and confirm every field you reference in emails is actually collected on the corresponding form. This is especially important in how to use ConvertKit for email marketing when running campaigns across sites with different opt-in forms built at different times by different team members.
Validation check: Send a preview email to yourself and check every personalization tag renders correctly. ConvertKit's preview feature fills in your own subscriber data, so a blank in preview means the field is genuinely missing from your record.
Review troubleshooting optionsDid It Work? And Are You Ready to Go Live?
Binary Checks: Did It Work?
Before your team flips anything live across your client portfolio, run through each item below. Every answer should be a clean yes or no. If anything lands in "maybe," treat it as a no and fix it first.
- Did your test subscriber receive the welcome email within two minutes of opting in?
- Does each sequence email send on the correct delay and from the correct sender name for that client?
- Are custom fields populated correctly in at least one live test submission?
- Does the confirmation page redirect to the intended URL rather than a default ConvertKit page?
- Are tags applied automatically upon form submission without manual intervention?
- Has at least one team member other than the person who built the sequence reviewed the full send preview?
- Is subscriber data visible in the correct segment before any broadcast goes out?
Ready to Go Live? Subjective Readiness Check
Passing the binary checks means the mechanics work. It does not mean you are ready to go live. Subjective readiness for a small team managing multiple client sites involves a second layer of judgment. Ask your team these questions before activating any broadcast or live sequence.
Does every email in the sequence reflect the client's current offer, not a draft from three weeks ago? Has someone read each email aloud to catch awkward phrasing? Is the unsubscribe flow mapped to a page the client has approved? If a subscriber replies to an automated email, does someone on your team have a process to respond within one business day? These are not technical checks; they are operational readiness questions that separate teams who use ConvertKit well from those who create deliverability problems later.
One of the strongest ConvertKit best practices for client workflows is to gate your go-live on client sign-off, not just internal review. A short approval email with the test sequence included gives clients ownership and protects your team if messaging is later disputed.
Frequently Asked Questions
How do I know if my ConvertKit automation is actually running?
Check the subscriber's activity log inside their individual profile. ConvertKit records each automation step as it triggers. If the log shows no activity after opt-in, the trigger is disconnected or the form is not linked to the automation.
Can multiple team members manage the same ConvertKit account without overwriting each other's work?
ConvertKit supports multiple user roles. Assign team members appropriate permission levels before going live. Avoid sharing a single login across the team, as this makes the audit trail unusable if something breaks.
What is the right way to separate client subscriber lists inside one ConvertKit account?
Use tags and segments rather than separate accounts where possible. A consistent tagging convention applied at the form level keeps client data cleanly separated without the overhead of managing multiple logins.
How do I handle unsubscribes across multiple client sites managed from one account?
An unsubscribe in ConvertKit applies account-wide by default. This is important for teams managing multiple brands. If clients require fully separate unsubscribe pools, separate ConvertKit accounts are the only reliable solution.
Is ConvertKit a realistic choice for a team running email marketing for 20 or more websites?
It is realistic for teams where those sites share an audience or topic cluster. When sites serve entirely unrelated audiences with no subscriber overlap, the account-wide unsubscribe behavior and shared sender reputation become operational risks worth evaluating carefully.