Campaign Monitor vs Dedicated IP Infrastructure

When the Australian-founded, agency-favourite design-forward email platform — now part of the Marigold portfolio after a 2025 corporate restructuring — runs into the same scale and economics ceilings every shared-IP ESP eventually hits

Campaign Monitor was founded in 2004 in Sydney, Australia, by David Greiner and Ben Richardson — two web designers who built the platform initially because they could not find an email tool that produced the design quality their agency clients required. That design-first founding DNA still shapes the product today, more than two decades and several corporate transitions later. The platform offers what is widely considered one of the best template libraries in the SMB segment, a clean drag-and-drop builder, and engagement-based segmentation that auto-categorises subscribers by activity level.

Campaign Monitor was acquired by CM Group in 2021, which subsequently rebranded as Marigold. Marigold also owns Emma, Liveclicker, and historically owned Sailthru and Cheetah Digital — both sold to Zeta Global in 2025 for approximately $325 million as Marigold restructured around the SMB and mid-market segment. Campaign Monitor was retained in the post-divestiture Marigold portfolio and continues to operate as a standalone brand focused on agencies, multi-brand organisations, and SMBs that prioritise template design quality and multi-client management.

This comparison evaluates the trade-off through a different operational filter. When the variables that matter become email infrastructure cost at scale, automation depth beyond template-driven campaign sends, EU data residency under regulatory scrutiny, or per-message forensic logging, at what point does dedicated PowerMTA infrastructure become the better operational answer? The crossover happens at three distinct points: when the steeply scaling contact-tier pricing post-2025-rebrand makes the economics less compelling, when automation depth limitations become binding, and when EU data residency requirements collide with Marigold's US headquarters jurisdiction.

Pricing 2026: three tiers, post-rebrand pricing

Campaign Monitor's 2025 plan rebrand significantly increased pricing across all tiers. The current structure includes three paid plans plus a limited sandbox option (no full free plan, unlike most SMB competitors).

All plans are contact-based, with annual billing offering a 10% discount. The full economic picture for a typical Campaign Monitor deployment includes line items beyond the headline subscription:

• Phone support add-on: $10/month on Lite and Essentials; included free with Premier. Most SMB platforms either include phone support across all paid tiers or offer it only at enterprise level — Campaign Monitor's pay-per-tier approach reflects the agency-targeting positioning.
• Send-time optimisation: Premier-only feature. Tier upgrade required to access AI-driven per-subscriber send-time prediction.
• Countdown timers and time zone sending: additional add-ons priced separately, approximately $130 combined.
• SMS marketing: credit-based, country-specific pricing, undisclosed publicly.
• Transactional email: included on Essentials and Premier, capped at 10× subscriber tier limit. A 5,000-contact Essentials plan supports 50,000 transactional emails monthly.
• Lite plan automation cap: severely limited automation logic on Lite — many users describe it as "a lead generator for upgrading to Essentials".
• No free plan: only a sandbox limited to 5 test subscribers. SMB customers cannot evaluate the product without committing to a paid trial.

The 2025 pricing rebrand and what it changed

In 2025, Marigold rebranded the Campaign Monitor pricing structure and increased rates across all plans. The structural changes:

• Tier names rebranded from previous structure to current Lite/Essentials/Premier naming.
• Rate increases documented across all tiers, with the Premier tier rising particularly steeply at higher contact counts.
• Send-time optimisation moved to Premier-only access. Previously available at lower tiers in some configurations.
• Lite plan send cap formalised at 5× contact count per month. Previously the entry tier had different volume rules.
• Free plan eliminated in favour of a 5-subscriber sandbox for testing only. Previous free-tier customers were migrated to paid plans.

The customer impact varied. Long-tenured agency customers using multi-client management features absorbed the increases as a cost of operational continuity. SMB customers comparing total cost of ownership against ActiveCampaign, Brevo, MailerLite, or HubSpot found Campaign Monitor's post-rebrand pricing materially less competitive. The 2025 changes are now part of the procurement context for any Campaign Monitor evaluation conversation.

The agency multi-client architecture: a real differentiator

Campaign Monitor's most distinctive capability is its multi-client agency architecture. Agencies managing email marketing for multiple end-clients can create separate client accounts under a single agency master account, with centralised billing, white-labelled interfaces showing the agency's branding (not Campaign Monitor's), per-client permission controls, and consolidated reporting across all clients. The architectural pattern saves administrative hours for agencies managing 10+ clients.

Few competitors offer this depth of multi-client management. Mailchimp's Mandrill subaccounts cover similar territory but with less polished agency UX. ActiveCampaign and Klaviyo do not have native multi-client architectures. HubSpot offers HubSpot Partner accounts but at a different scale and pricing model. For agencies whose business is specifically managing multiple clients' email programmes, Campaign Monitor's architecture is genuinely differentiated.

The trade-off is that the multi-client features are unused capability for single-brand businesses paying for them in the platform price. A direct-to-consumer ecommerce brand running its own email is not benefiting from agency-tier features that contribute to the platform's higher cost. The procurement question becomes whether the multi-client feature contributes value proportional to the price premium versus single-tenant alternatives.

Template quality: the design-first founding DNA

Campaign Monitor's template library is consistently rated among the best in the SMB email marketing segment. Independent reviewers describe the templates as "modern, clean, and well-designed" — a meaningful contrast with the dated layouts found in many competing platforms. Emails built in Campaign Monitor render consistently across email clients, follow current responsive design best practices, and produce visually polished output without requiring custom HTML work.

The design quality reflects the founders' background. David Greiner and Ben Richardson came from web design and front-end development; the platform was built to satisfy the visual standards they applied to their agency client work. Two decades later, Campaign Monitor continues to invest in template design and editor polish at a level that distinguishes it from feature-breadth-focused competitors.

For brands where email visual quality is a primary procurement criterion — luxury retailers, design agencies, hospitality, fashion publishers, and other visually-driven sectors — Campaign Monitor's template advantage is operationally meaningful. For brands where automation depth, ecommerce integration, or behavioural segmentation are more important than template polish, the design advantage is offset by feature-breadth gaps relative to ActiveCampaign, Klaviyo, or HubSpot.

Automation depth: limited compared to competitors

Campaign Monitor's automation builder handles standard SMB workflows competently. Welcome sequences, simple drip campaigns, basic conditional branches, and engagement-based triggers all work as expected. The platform also includes prebuilt automated journeys for common use cases (welcome series, win-back sequences, post-purchase follow-up) that reduce setup effort.

Where Campaign Monitor's automation falls short relative to category leaders:

• Multi-step branching journeys with sophisticated conditional logic are limited. The kind of "if subscriber clicked link A, send sequence X with delay; if also engaged with sequence X, route to sequence Y; if not, return to main flow after 10 days" logic that ActiveCampaign Pro or Klaviyo handle natively requires workarounds in Campaign Monitor.
• Behavioural lead scoring with weighted multi-attribute models is not part of the platform. Tag-based segmentation is supported; sophisticated scoring is not.
• Real-time event triggers from external sources (e-commerce events, custom application events, webhook-based behavioural signals) require Zapier or custom API integration rather than native event ingestion.
• Native abandoned cart flows with deep ecommerce platform integration require third-party tooling. The Shopify integration syncs customer and order data but does not provide the kind of native abandoned-cart automation that Klaviyo or Omnisend offer out of the box.
• A/B testing within automation flows is more constrained than in ActiveCampaign, Klaviyo, or HubSpot. Standard campaign A/B testing works well; in-flow split testing within an automation is not as flexible.

The trade-off matches the platform's positioning: Campaign Monitor invests in template polish and agency-management features rather than automation depth. For senders whose primary need is well-designed broadcast campaigns and basic autoresponders, the simpler engine is appropriate. For senders evaluating against automation-first competitors, the gap surfaces in feature comparisons and often becomes the migration trigger.

EU data residency and the Marigold US jurisdiction

Campaign Monitor was founded in Sydney, Australia, but is now operated by Marigold, which is US-incorporated and headquartered in Nashville, Tennessee. The platform's data infrastructure is operated under Marigold's US corporate jurisdiction, with EU subscribers processed through US data centres under standard data transfer mechanisms (Standard Contractual Clauses, EU-US Data Privacy Framework where applicable).

Campaign Monitor signs DPAs and is GDPR-compliant; subscriber consent management, unsubscribe handling, and data access workflows are all supported. For SMB customers whose EU subscriber base is moderate and whose compliance posture is "GDPR-compliant via standard mechanisms", Campaign Monitor's US infrastructure is functional.

For organisations whose risk frameworks treat US extraterritorial jurisdiction as a residual risk requiring documented mitigation — banking, healthcare, government, defence, regulated EU sectors operating under Schrems II compliance scrutiny — Marigold's US incorporation creates the same architectural gap that applies to Salesforce, Adobe, HubSpot, and ActiveCampaign. EU-headquartered alternatives (Brevo, Mailjet) and dedicated EU infrastructure address both physical and jurisdictional residency dimensions; Campaign Monitor addresses physical residency only through standard data transfer mechanisms.

CSE is a European-incorporated company running infrastructure exclusively from DE, FR, and NL data centres operated by ISO 27001-certified partners. Physical EU data location and freedom from US extraterritorial reach are baked-in architectural defaults — not options that have to be selected.

Per-message visibility: Campaign Monitor reports vs PowerMTA acct.csv

Campaign Monitor's reporting suite is competent for SMB and agency operations. Subscriber growth and engagement reports, detailed open and click analytics, engagement-based segmentation visualisations, and bot-click filtering that automatically removes machine-generated engagement from reports. For agencies managing multiple clients, the consolidated cross-client reporting saves operational effort.

For a deliverability operator debugging why a specific recipient at a specific Australian enterprise domain receives mail with extended time-to-accept latency while other recipients on the same domain receive in under two seconds, the data model is structurally limited. The underlying SMTP transaction — verbatim dsnDiag from the receiving MX, source IP for the specific delivery attempt, TLS capabilities negotiated, throttling state at submission time — is not surfaced in Campaign Monitor's reporting layer because the granular transaction data is not retained at that level.

PowerMTA's acct.csv records this per message:

d,2026-04-26 09:47:23+0000,2026-04-26 09:47:20+0000,
quarterly-newsletter@send.example.eu,
m***@telstra.com.au,,relayed,
2.0.0,smtp;250 2.0.0 OK 1714124843 g42-20020a05600c4d7100b00415f3e5d2f1si,
mx-au.telstra.com.au (203.50.10.45),delivery,smtp,
mta-eu-fr1 (192.168.2.10),smtp,185.224.4.51,185.224.4.51,
"ENHANCEDSTATUSCODES,8BITMIME,STARTTLS,SMTPUTF8",,
vmta-eu-fr1,job-q2-2026-04,env-newsletter-au,
telstra.com.au.rollup/vmta-eu-fr1

Pivoted into a query layer, this data answers questions like "show me all deliveries to *.telstra.com.au over the past 60 days where time-to-accept exceeded 5 seconds, grouped by hour-of-day" with a single SQL query. Campaign Monitor's reporting layer cannot answer this question because the granular transaction data does not exist in its tracking model.

When Campaign Monitor is the right answer

Campaign Monitor is the right choice when:

• You are an agency managing 5+ end-client email programmes. The multi-client architecture is genuinely differentiated and saves operational time.
• Template design quality is a primary procurement criterion. The design-first founding DNA produces visually polished output that competitors do not consistently match.
• You operate in design-driven verticals — luxury, fashion, hospitality, design agencies, visual publishers — where email visual standards are tightly enforced.
• Your team values polished UX over feature breadth. The drag-and-drop editor and template library are best-in-class; the trade-off is automation depth.
• Phone support during business hours matters at the Premier tier, and the agency-tools investment justifies the premium pricing.
• You operate from US, AU, or non-EU markets where the jurisdictional residency consideration does not apply.

When dedicated infrastructure wins

The crossover happens when:

• Contact count exceeds 25,000 with steady growth. The Essentials and Premier tier pricing curves climb steeply post-2025 rebrand.
• Monthly send volume exceeds 500,000. Shared-IP economics reach deliverability ceilings around this volume on most platforms.
• Automation depth limitations become a hard constraint. Most migrations in this category land at ActiveCampaign, Klaviyo, or HubSpot rather than dedicated infrastructure — but accounts that want infrastructure independence can pair dedicated PowerMTA with application-layer automation tooling to preserve flexibility.
• EU data residency requires jurisdictional independence. Marigold's US incorporation creates the gap that EU-incorporated alternatives address.
• Granular per-message audit data is needed at the operational level. Audit-trail reconstruction, deliverability investigations, and per-recipient incident reviews all benefit from raw transaction logs.
• The 2025 rebrand pricing increase made the contract economics untenable. Customers who were on legacy pricing pre-2025 may find the new rates uncompetitive against Brevo, MailerLite, or dedicated infrastructure.

The Campaign Monitor API and integration architecture

Campaign Monitor provides a REST API covering subscribers, lists, segments, campaigns, automations, and reporting endpoints. The documentation is well-maintained, and SDK availability covers the major runtimes (Node.js, PHP, Python, Ruby, .NET). The platform has been API-mature for many years, with stable endpoints and consistent backward compatibility — a virtue in the category.

Integration capability includes 100+ native connectors covering Shopify, Salesforce, WordPress, WooCommerce, Google Analytics, Unbounce, and the major business tools. The Zapier integration extends reach to thousands more apps. For technical teams building custom integrations, the API is sufficient for most use cases; for sophisticated real-time event-driven architectures, the polling-based webhook patterns can require more middleware effort than platforms with deeper webhook coverage.

For hybrid stack patterns where Campaign Monitor handles campaign management and dedicated infrastructure handles SMTP submission, the API is workable but the integration is less natural than with event-first platforms. The middleware pattern typically polls Campaign Monitor for outgoing send queues, routes through PowerMTA, and updates engagement events through subscriber update API calls. Engineering effort runs 5-7 weeks for a properly-scoped hybrid build.

For full migrations away from Campaign Monitor, the export workflow is straightforward through the subscriber list endpoints and campaign template HTML export. Total export effort for a typical SMB account runs 1-3 engineering days; for agencies with multi-client architectures, the migration complexity scales with the number of client accounts.

Side-by-side: Campaign Monitor Essentials vs CSE Bulk Professional

For an SMB sender or single-brand agency client with 25,000 contacts sending approximately 200,000 emails per month — a typical Campaign Monitor Essentials customer:

The pattern: at this volume slice, Campaign Monitor Essentials is materially cheaper than CSE Bulk Professional and provides best-in-class templates, multi-client agency tools, and unlimited sends in a managed platform. The economic crossover is not at 25K contacts; it is qualitative. CSE's value proposition versus Campaign Monitor is per-message forensic visibility, dedicated IP control, EU jurisdictional independence, and send capacity headroom for senders growing past 50K contacts. For most Campaign Monitor customers in this volume slice, the platform is the architecturally appropriate choice.

Migration timeline: Campaign Monitor to dedicated infrastructure

A clean migration from Campaign Monitor to dedicated infrastructure runs 14-18 weeks end-to-end:

• Weeks 1-2 — Audit and architecture. Inventory of subscriber lists, segments, campaigns, automation journeys, transactional flows, multi-client account structures (for agency users), template library.
• Weeks 3-4 — DNS records and sender authentication. SPF, DKIM, DMARC alignment on new sending domains; VMTA pool design; subscriber and suppression list export from Campaign Monitor via the REST API.
• Weeks 5-12 — IP warming. Eight-week graduated warm-up across two EU dedicated IPs (one allocated to transactional flows, one to marketing). Throttling configuration tuned to each major mailbox provider (Google, Microsoft, Yahoo, Apple) and the regional European networks (Orange, Free, GMX, Web.de, Libero).
• Weeks 13-15 — Template and automation rebuild. Existing templates rebuilt in the destination stack — MailWizz for broadcast marketing, Mautic for behavioural automation, or a custom renderer where neither fits. The template-quality investment that Campaign Monitor customers value typically requires careful design preservation during port.
• Weeks 16-17 — Dual-stack period. Both Campaign Monitor and the dedicated stack run in parallel; send traffic shifts incrementally driven by per-mailbox-provider placement signals.
• Week 18 — Cutover. Campaign Monitor subscription cancelled at billing cycle end; sending fully on dedicated infrastructure.

For agency customers with multi-client architectures, the migration timeline extends because each client account needs its own subscriber export, template port, and authentication setup. A 10-client agency typically runs 22-28 weeks rather than 14-18.

Production case study: a UK design agency on Campaign Monitor Premier

An anonymised but representative migration profile.

Starting point. A UK-based brand-design and digital agency headquartered in Manchester, ~25 employees, on Campaign Monitor Premier for eight years (originally on the agency-tier plan for the multi-client management features). Managing email programmes for 14 end-clients across hospitality, retail, professional services, and B2B SaaS verticals. Aggregate subscriber base across all clients: 380,000 contacts. Aggregate monthly send volume: 1.6 million emails. Campaign Monitor Premier with multi-client agency configuration: ~$1,580/month effective ≈ €1,460/month. The agency-tier features were the primary value driver; the multi-client billing and white-label interface saved approximately 40 hours/month of administration.

Trigger. Two converging factors. First, the 2025 Marigold pricing rebrand increased the agency-tier costs by approximately 35% at contract renewal — a material change for an established agency contract. Second, the agency had won a tier-1 UK financial services client whose vendor onboarding review flagged Marigold's US incorporation as a residual jurisdictional risk requiring documented mitigation. The agency's procurement team initiated a platform architecture review. Third factor: deteriorating Outlook/Hotmail deliverability for two ecommerce clients running B2C campaigns — a recurring issue across Campaign Monitor's shared infrastructure that competitive benchmarking suggested was structural rather than account-specific.

Migration approach. Hybrid stack — keep Campaign Monitor Essentials at a reduced contact tier for the design-driven hospitality and retail clients where template quality was the primary procurement value; offload the high-volume B2C ecommerce clients and the financial services client to a multi-tenant MailWizz instance running on CSE Bulk Professional infrastructure. The financial services client gained jurisdictional EU residency for both physical infrastructure and corporate jurisdiction.

Implementation. 24-week structured migration (extended timeline due to multi-client complexity). Phase 1: subscriber list export from Campaign Monitor for the 6 clients moving to dedicated infrastructure (5,400 lines of Python migration scripts handling per-client tag preservation, segment recreation, and suppression list reconciliation). Phase 2: SPF/DKIM/DMARC alignment for 6 separate client sending sub-domains. Phase 3: 10-week IP warming on three dedicated EU IPs (Frankfurt × 2, Amsterdam × 1) with traffic separation by client at the VMTA layer. Phase 4: MailWizz multi-tenant configuration for the 6 client accounts with white-labelled login experiences preserving the agency's existing branding. Phase 5: parallel operation for 5 weeks with per-client traffic shifting based on individual placement metrics.

Results at month 9 post-migration:

• Inbox placement (across migrated clients): 86.8% on Campaign Monitor shared IPs → 95.3% on CSE dedicated EU IPs (200-seed inbox panel testing across Mailtrap and Glock Apps)
• Outlook/Hotmail placement (the trigger metric): 74% (degraded baseline for ecommerce clients) → 94.2% (largest delta — Microsoft's filtering of US-routed Marigold IPs was the dominant pre-migration ceiling)
• Effective monthly cost: €1,460 (Campaign Monitor Premier post-2025-rebrand) → €1,210 (€990 CSE + €220 Campaign Monitor Essentials at reduced tier for the 8 retained design-driven clients) — savings of €250/month, €3,000/year
• Compliance posture: EU data residency satisfied for the financial services client (both physical and jurisdictional); Marigold's residual US jurisdiction limited to the 8 design-driven SMB clients where the issue is not material
• Forensic visibility: from "Campaign Monitor aggregate dashboards" to "full PowerMTA acct.csv stream with 90-day retention queryable via SQL" — a capability that enabled the agency to bill premium rates for "deliverability-as-a-service" to the migrated B2C clients
• New revenue opportunity: the deliverability visibility and EU jurisdictional independence enabled the agency to win additional regulated-sector clients that had previously declined to engage

The strategic outcome: the migration was not driven by a single client need but by a portfolio diversification opportunity. By splitting clients between platform-tier Campaign Monitor (for clients where template polish drove value) and infrastructure-tier dedicated CSE (for clients where deliverability and jurisdictional independence drove value), the agency expanded its service positioning and increased average client revenue.

The Marigold portfolio context and the 2025 restructuring

A consideration that affects multi-year procurement decisions: Campaign Monitor sits within a private equity-backed corporate portfolio that has undergone significant restructuring. Marigold (formerly CM Group) acquired Campaign Monitor in 2021, then went through the divestiture of Sailthru and Cheetah Digital to Zeta Global in 2025 for approximately $325 million. The post-2025 Marigold focus is explicitly on the SMB and mid-market segment, with Campaign Monitor and Emma as the flagship products.

For long-tenured Campaign Monitor customers, the 2025 restructuring caused no operational disruption — accounts continued unchanged, with the pricing rebrand as the visible change. For procurement teams running multi-year contracts, the question becomes whether Marigold's strategic direction continues to align with Campaign Monitor's design-quality and agency-management positioning, or whether further portfolio restructuring could affect the product roadmap.

The pattern is not unique to Campaign Monitor — similar PE-portfolio context applies to Acoustic (Centerbridge), and historically applied to Marketo (Vista Equity before Adobe acquisition). PE ownership creates structural uncertainty that is real but not necessarily negative; many PE-owned software companies operate stably for years. The procurement implication is to negotiate appropriate exit terms in multi-year contracts and to plan for product roadmap variability over a 3-5 year horizon.

The bottom line

Campaign Monitor is a defensible choice for agencies, multi-brand organisations, and SMBs in design-driven verticals where template polish, multi-client management, and visual quality are primary procurement criteria. The Sydney founding heritage, the design-first DNA, and two decades of operational refinement produce a product that genuinely earns its niche. For agencies managing 5+ clients, the multi-client architecture is meaningfully differentiated.

For senders whose primary need is high-volume email, automation depth, EU jurisdictional independence, or per-message forensic logging, the cost-to-capability ratio inverts — particularly post-2025 pricing rebrand. The right answer is rarely "abandon Campaign Monitor entirely" because the design quality and agency tools have real value for the right use cases. It is "use Campaign Monitor where its strengths fit (design-driven SMB clients, multi-client agency management) and offload SMTP-layer email to dedicated infrastructure with the cost predictability, dedicated IP control, deliverability headroom, and EU jurisdictional independence that platform-bundled email cannot match."

Infrastructure expertise is not a workaround for poor practice — it is an amplifier of good practice. Campaign Monitor has built a design-forward email marketing platform with template polish and agency tools as defining strengths; dedicated infrastructure provides the email layer at a cost, latency, and visibility level that platform-bundled email cannot match. The infrastructure choice that fits the use case depends on which capability constraint becomes binding first.