Email Marketing & Newsletter
ActiveCampaign
Rest of world Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by ActiveCampaign, LLC · www.activecampaign.com
Report an error on this page Is this your product? →
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
ActiveCampaign, LLC of Chicago sells an email marketing and automation platform the bench rates highest on campaign and automation and integrations: judges credit a drag-and-drop builder with split and conditional paths, dynamic content blocks, predictive send timing and split testing of up to five elements, plus an open version 3 API with webhooks and a marketplace of over 950 apps. The weakest criterion is sovereignty: transfers are disclosed to the United States, Australia, Ireland, Brazil and Costa Rica, the stated safeguards are Data Privacy Framework certification and Standard Contractual Clauses, and we found no public information confirming EU data residency or naming hosting, storage or email-delivery providers. Consent and proof and list data control score low because the consent record is one customers assemble themselves and we found no public information on export or documented deletion. Deliverability and pricing transparency sit mid-band. The judges did not meaningfully diverge: every criterion's scores sit within two points.
Speaks for it
- Confirmation opt-in (double opt-in) is on by default for all forms, and unconfirmed contacts cannot be emailed.
- The bulk import API is available on all plans in batches of up to 250 contacts with stated rate limits, and migration into the platform is free.
- The automation builder covers split and conditional paths, dynamic content blocks, predictive send timing and split testing of up to five elements per email.
- An open API at version 3 with token authentication, webhooks and three documented pagination styles joins a marketplace of over 950 apps.
- Four plan prices are public with the billing period stated — "Starts at $15 /mo", "$49 /mo", "$79 /mo" and "$145 /mo", each "Billed annually".
Held against it
- We found no public information on export of subscribers, engagement history, campaigns or templates, or on documented deletion of a contact across records.
- The contracting entity is ActiveCampaign, LLC of Chicago, transfers are disclosed to the United States, Australia, Ireland, Brazil and Costa Rica, and we found no public information confirming EU data residency or naming hosting, storage or email-delivery providers.
- The documented consent record is a date an automation writes into a custom field, and we found no public information on capturing the consent source, IP or versioned wording.
- SPF, DKIM and DMARC are not named on the captured pages, and we found no public information on dedicated-IP options or inbox-placement and seed testing.
- We found no public information on prices for the SMS, WhatsApp, transactional email, AI Activities and custom-reporting add-ons, on overage rates, or on VAT treatment.
Best for
- You run a shop on Shopify, Square or WooCommerce and want abandoned-cart, upsell, cross-sell and review-request automations written out in plain words.
- You are migrating in from another platform and want the inbound path documented in detail, from bulk import on every plan to free migration at no cost.
- You build against an API and need webhooks, token authentication, three pagination styles and 950-plus marketplace apps to wire into.
- You want to try before committing: the free trial runs 14 days with email sign-up and no credit card needed.
Avoid if
- You must evidence per-subscriber consent wording, since the documented record is a consent date in a custom field and the privacy policy excludes clients' Contact Data from its scope.
- You need to compute a full invoice before purchase, since starting prices scale by contact volume and we found no public information on the contact-tier ladder, overage rates or add-on prices.
- You are buying at the Starter price expecting the full automation surface, since Starter automations cap at 5 actions, segmentation is 'Limited' there, and A/B testing of automations appears from Pro upward.
The scores
Campaigns & automation
Show reasoningHide reasoning
How this is scored
Building the mail and the journey around it: editor, templates, segmentation, triggered sequences, A/B testing.
0 — One-off broadcasts from a fixed template; no segmentation and no automation of any kind.
3 — A drag-and-drop editor and simple list segmentation, but automation is a single welcome mail and there is no testing.
5 — Reusable templates, attribute and behaviour segmentation, multi-step automations on common triggers, and subject-line A/B testing.
8 — A visual journey builder with branching on behaviour and data, dynamic content per segment, send-time optimisation, and testing that reports significance rather than raw counts.
10 — Journeys treat the whole lifecycle: event-driven entry from other systems, branching on any attribute or event, holdout groups for measurement, and automations a marketer can read months later without a diagram.
The CRM Manager
This is a real journey engine: split and conditional paths on preferences, actions and engagement history, dynamic content blocks per segment, predictive send-time, and split testing of up to five elements, with A/B testing covering both email and automation on the higher plans. What I cannot find is the part I actually read reports for — nothing captured shows testing that reports significance, holdout groups, or journey measurement against a control — so I stop short of the top band. The Starter plan's five-actions-per-automation cap is worth knowing before anyone buys on price. 2 4 5 6
The Deliverability Engineer
The visual automation builder with split and conditional paths, multiple triggers and unlimited actions, dynamic content blocks, predictive send timing and split testing of up to five elements per email cover the journey-builder ground squarely. What keeps it off the top is that the captured pages show no holdout groups and no significance reporting behind the tests. 4 5 6 2
The Data Protection Officer
The visual automation builder is documented with split and conditional branching on behaviour, preferences and engagement history, dynamic content blocks per segment, predictive send-time placement, and split testing of up to five elements per email. We found no public information on tests that report statistical significance or on holdout groups for measurement. 2 4 5 6
The Shop Owner
The visual builder with split and conditional paths, behaviour-based triggers, dynamic content blocks, send-time optimisation and multiple triggers per automation is exactly what I need to run journeys, and the Shopify pages spell out abandoned-cart alerts, upsell, cross-sell and review requests in plain words. Custom objects and event tracking give me event-driven entry from my shop systems. We found no public information on split testing that reports statistical significance or on holdout groups, and A/B testing of automations only appears from Pro upward. 4 5 6 14 2
The Integrator
There is a documented drag-and-drop builder with split and conditional branching, dynamic content blocks per segment, predictive send timing, and split testing of up to five elements across email and automation, with tiered segmentation and 900-plus prebuilt recipes. What separates this from the top band is absent from the captured pages: we found no public information on holdout groups for measurement or on testing that reports statistical significance rather than raw counts. 2 4 5 6
The Skeptic
A drag-and-drop builder with split and conditional paths, dynamic content blocks, predictive send timing and testing of up to five elements per email meets most of the visual-journey standard, but we found no public information on tests that report significance or on holdout groups. The staircase is visible in public view: automation A/B testing begins two tiers above Starter, segmentation is "Limited" there, and Starter automations cap at 5 actions. 2 4 5 6
Deliverability infrastructure
Show reasoningHide reasoning
How this is scored
Whether the mail arrives — authentication, sending reputation, bounce and complaint handling — judged on what the vendor documents rather than the inbox rate it advertises.
0 — No documentation of authentication or bounce handling; deliverability appears only as a marketing number.
3 — SPF and DKIM setup documented, but no DMARC guidance, no stated bounce policy and shared sending only.
5 — SPF, DKIM and DMARC documented with a custom sending domain, automatic hard-bounce suppression, and complaint-loop handling stated.
8 — The above plus dedicated-IP options with a documented warm-up, seed or inbox-placement testing, engagement-based sunsetting, and published guidance on list hygiene.
10 — Deliverability is operated as a service: reputation monitoring surfaced to the customer, per-domain and per-ISP diagnostics, enforced authentication before first send, and postmaster or blocklist handling the vendor documents doing on the customer's behalf.
The CRM Manager
Domain authentication for a primary plus up to three alternate sending domains per the Google and Yahoo requirements is documented, alongside a genuine warm-up playbook (prescribed daily volumes, tagging engaged contacts, monitoring), ISP relationships, and account review for abnormal bounce, complaint and unsubscribe rates. But we found no public information on dedicated-IP options, seed or inbox-placement testing, engagement-based sunsetting, or automatic hard-bounce suppression, so I can't credit the higher band. The $79 USD expert Zoom session is advice you pay for, not infrastructure evidence. 7 8 11
The Deliverability Engineer
Sending-domain authentication per the Google and Yahoo mailbox-provider requirements, a documented warm-up methodology with prescribed daily volumes and engaged-contact tagging, and account review on abnormal bounce, complaint and unsubscribe rates are real infrastructure on the record — though the pages never name SPF, DKIM or DMARC outright. I found no public information on dedicated IP options, inbox-placement or seed testing, or engagement-based sunsetting, and the paid $79 deliverability session is consulting, not infrastructure. 7 8 11 2
The Data Protection Officer
Authentication of a primary and up to three alternate sending domains is documented by reference to the Google and Yahoo sender requirements, a prescribed warm-up workflow is published, and the anti-spam policy states review of accounts with abnormal bounce, complaint and unsubscribe rates. We found no public information naming SPF, DKIM or DMARC setup guidance, dedicated IP options, seed or inbox-placement testing, or engagement-based sunsetting. 7 8
The Shop Owner
Authentication and verification of a primary plus three alternate sending domains per the Google and Yahoo requirements, a documented warm-up with prescribed daily volumes, ISP relationships, bounced-address suppression on import, and account review on abnormal bounce, complaint and unsubscribe rates take this past the middle of the road. We found no public information on dedicated IP options, inbox-placement testing, or engagement-based sunsetting, and the captured pages do not spell out SPF, DKIM and DMARC guidance by name. 7 8 2 11
The Integrator
Authentication and verification of a primary domain plus up to three alternates per the Google and Yahoo requirements, a documented warm-up plan with monitoring, and stated review of abnormal bounce, complaint and unsubscribe rates give a real operational picture, with purchased lists prohibited. We found no public information naming SPF, DKIM or DMARC setup, dedicated IP options, seed or inbox-placement testing, or engagement-based sunsetting, so the documented picture stops short of the top band. 7 8 11
The Skeptic
Sending-domain authentication per Google and Yahoo requirements, a custom mailserver domain, bounce-list suppression at import, and account review for abnormal bounce, complaint and unsubscribe rates are documented, alongside warm-up guidance with prescribed daily volumes. We found no public information on dedicated-IP options, inbox-placement testing, or SPF/DKIM/DMARC named individually — and deliverability help beyond the docs is sold as a "$79 USD" Zoom session. 7 8
Consent, proof & tracking limits
Show reasoningHide reasoning
How this is scored
How subscribers arrive and what the sender can prove afterwards: double opt-in, logged consent, unsubscribe handling, and whether open and click tracking can be limited or switched off.
0 — Single opt-in with no consent record; tracking is always on and cannot be disabled.
3 — Double opt-in available but not the default, and the consent record is a timestamp without the source, IP or the wording consented to.
5 — Double opt-in as the documented default with a stored consent record including source and timestamp, one-click unsubscribe, and tracking that can be turned off per campaign.
8 — Consent is reproducible as evidence: the confirmation mail and form wording versioned and retrievable per subscriber, unsubscribe honoured across lists, tracking off-by-default available, and retention rules for inactive subscribers.
10 — Built for the burden of proof: a per-subscriber consent history an authority would accept, documented handling of Art. 15 access and Art. 17 erasure requests, pixel-free and link-tracking-free sending as a supported mode, and preference-centre granularity rather than all-or-nothing.
The CRM Manager
Double opt-in is on by default for all forms and unconfirmed contacts cannot be emailed, which is the right default, and the consent playbook — timestamping consent into a custom field, checkbox consent fields, segmenting by consent date, emailing yourself a copy of every submission — shows they take proof seriously. But the record stops at the timestamp: we found no public information on capturing the source or IP of consent, versioned form wording retrievable per subscriber, a preference centre, or turning open and click tracking off per campaign beyond a GDPR-friendly site-tracking guide. 10 8 3
The Deliverability Engineer
Confirmation opt-in is on by default for every form, unconfirmed contacts cannot be mailed, and there is documented practice for timestamping consent into custom fields and emailing yourself each form submission. But the consent record is a date field without source or wording consented to, the automatic unsubscribe link is not documented as one-click, and I found no public information on turning open and click tracking off per campaign or on pixel-free sending. 10 8 9
The Data Protection Officer
Confirmation opt-in is documented as on by default for all forms and unconfirmed contacts cannot be emailed, with documented patterns for timestamping and segmenting by consent date and for mailing yourself a copy of every form submission — a record the sender assembles rather than a reproducible per-subscriber proof, though an unsubscribe link is placed automatically. We found no public information on turning open and click tracking off per campaign or by default, on unsubscribe honoured across lists, or on retention rules for inactive subscribers. 8 9 10
The Shop Owner
Double opt-in is on by default for every form, consent dates land in a custom field I can segment on, unconfirmed contacts cannot be mailed, and an unsubscribe link is placed automatically. We found no public information on turning open and click tracking off per campaign, on one-click unsubscribe, or on consent wording being versioned and retrievable per subscriber; the privacy pages confirm session replay and web beacons are in use. 10 8 3
The Integrator
Confirmation opt-in is documented as the default for all forms and unconfirmed contacts cannot be mailed, which is enforcement rather than advice. The consent trail, though, is something a customer assembles themselves — an automation writing a date into a custom field with a form-submission copy by email — and we found no public information on capturing the consent source, versioned and retrievable form wording, unsubscribe honoured across lists, or turning open and click tracking off per campaign. 8 9 10
The Skeptic
Double opt-in is documented as the default for all forms and unconfirmed contacts cannot be emailed, which is solid — but the consent record is a do-it-yourself automation stamping a date into a custom field, and we found no public information that source, IP or the wording consented to is stored with it. Nothing captured shows open and click tracking can be switched off, and the privacy policy expressly excludes clients' Contact Data from its scope. 3 9 10
List ownership, import & exit
Show reasoningHide reasoning
How this is scored
Whether the list and its history remain the sender's: import with attributes intact, full export including engagement history, deletion that executes, and no metering that prices leaving out of reach.
0 — Export is addresses only; engagement history, segments and automations cannot leave.
3 — CSV import and export of subscriber fields, but engagement history and unsubscribe state are not exportable.
5 — Full subscriber export including custom attributes, subscription status and unsubscribe state, plus API access sufficient to sync elsewhere.
8 — Everything exportable in open formats — subscribers, engagement history, campaigns and templates — with documented deletion of a subscriber across all records, and no export throttling.
10 — Exit is a documented feature: full-fidelity export of the whole account, contractual data return, deletion that is evidenced rather than asserted, and migration tooling in both directions.
The CRM Manager
Import is properly built: a bulk importer on every plan that creates, updates, sets fields, tags and adds contacts to lists in batches of 250, with exclusion and bounce checks and an asynchronous upsert endpoint — the inbound side is the strongest I've reviewed. On exit, we found no public information on exporting subscribers with engagement history or unsubscribe state, on exporting campaigns and templates, or on documented deletion of a subscriber across records. The free migration offer covers moving you in, not out. 11 12 3 4
The Deliverability Engineer
The bulk import API is documented in real depth — fields, tags, list membership, respect for bounce and unsubscribe state, batches of 250, available on all plans — but that is the inbound direction only. I found no public information on subscriber or engagement-history export or on documented deletion of a subscriber across records, and the free migration offering runs from another platform into ActiveCampaign, not out of it. 11 12 4 3
The Data Protection Officer
Import is documented in depth — bulk import and bulk sync endpoints with 250-contact batches, callbacks, status queries, bounced and exclusion-list checks, and stated rate limits — and the open API with webhooks supports syncing elsewhere. We found no public information on exporting engagement history or unsubscribe state, on documented deletion of a subscriber across all records, or on export throttling; the migration service documented is a free move into the platform. 4 11 12 13
The Shop Owner
Import is well documented — bulk import on every plan in batches of 250 with fields, tags and list membership intact, plus a bulk sync endpoint — and free migration into the platform is offered at no cost. We found no public information on exporting subscribers with engagement history and unsubscribe state, on documented deletion across all records, or on any exit tooling; every migration capability on the captured pages runs toward the vendor, not away from it. 11 12 4 13
The Integrator
The inbound side is genuinely strong: a bulk import API available on every plan carrying custom fields, tags and list membership, an upsert endpoint returning a process id, and free migration in covering data, templates and campaigns. But we found no public information on export of subscribers, engagement history, campaigns or templates, nor on documented deletion of a subscriber across all records, so exit is entirely unevidenced while entry is well served. 4 8 11 12
The Skeptic
Inbound is documented to the byte: bulk import on all plans, 250-contact batches, a 399,999-byte payload cap, stated rate limits, and free migration in. Exit is the silence — we found no public information on export of subscribers, engagement history, campaigns or templates, nor documented deletion of a contact across records; the privacy policy routes deletion to an email address and covers account information only. 3 4 11 12
Integrations & API
Show reasoningHide reasoning
How this is scored
The connection surface a newsletter lives on: shop and CRM systems, events in and out, webhooks, and an API somebody can build against without a partner agreement.
0 — No API and no named integrations; the list is maintained by CSV upload.
3 — A handful of native integrations and a read-mostly API, with no webhooks and no documented rate limits.
5 — Named integrations for common shop and CRM systems, a documented REST API with keys, and webhooks for the core subscriber events.
8 — Maintained bidirectional integrations with named systems including at least one major shop platform, event webhooks with retries, documented rate limits, and a sandbox.
10 — The tool is a component rather than a destination: transactional and marketing sending on one API, events flowing both directions, versioned API with a deprecation policy, and integrations the vendor maintains rather than lists.
The CRM Manager
Over 950 apps with named connectors for Shopify, WooCommerce, Salesforce, Stripe, Slack and Google Sheets, a documented version 3 REST API with token authentication, webhooks, and even connectors into ChatGPT and Claude — the surface is broad and the Shopify connector is built by the vendor itself. Against the higher band: the Shopify integration is documented as inbound, rate limits are published for the bulk importer rather than generally, and we found no public information on webhook retries, a sandbox, or a deprecation policy. 2 4 11 13 14
The Deliverability Engineer
A marketplace of 900-plus integrations, a Shopify integration built and documented by ActiveCampaign itself, and an open API with webhooks and published import rate limits put this past the named-integrations bar. The Shopify data flow is documented as inbound only, and I found no public information on webhook retries, a sandbox, or bidirectional sync with any named system. 14 4 5 11
The Data Protection Officer
Over 900 marketplace integrations are listed with named shop and CRM tools, the Shopify integration is built by the vendor with its own documentation, and the open API v3 includes webhooks, three pagination styles and MCP connectors for ChatGPT and Claude, with rate limits stated for the import endpoints. We found no public information on webhook retries or a sandbox, and the Shopify integration page documents inbound data flow only. 2 5 11 13 14
The Shop Owner
Shopify, Square and WooCommerce are standard ecommerce connections and the Shopify app is built by the vendor itself with the shop use cases written out; there is an open API with webhooks, documented rate limits and 950-plus apps, plus a transactional email add-on. The Shopify data flow is listed as inbound only, and we found no public information on webhook retries or a sandbox. BigCommerce, Magento and Shopify Plus sit in the premium bracket, which matters the day my shop outgrows standard Shopify. 14 2 5 11 4 13
The Integrator
This is close to the surface I want to wire against: an open API with webhooks, documented token authentication and versioned endpoints, pagination spelled out down to cursor parsers, explicit import rate limits, an import-completion callback, and a Shopify connector built and documented by the vendor itself. What I need before committing a stack is missing from the captured pages — we found no public information on a sandbox, a deprecation policy, webhook retry behaviour, or rate limits beyond the import endpoints — and the Shopify connector page describes the data flow as inbound only. 2 5 11 12 13 14
The Skeptic
A marketplace of over 950 apps, a documented REST API at version 3 with token auth, webhooks, bulk-import callbacks and pagination down to cursor parsers with a jq command, plus rate limits stated for the import endpoints. The Shopify connector is built by the vendor itself but marked "Inbound" only, and we found no public information on a sandbox or webhook retries; transactional sending rides a paid add-on. 2 4 11 13 14
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where subscriber data and behavioural tracking live, who the contracting entity is, and which subprocessors touch the send. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it — which in this category is heavily.
0 — US vendor and contracting entity, US hosting, subprocessors unnamed; subscriber behaviour leaves the EU with no stated basis.
3 — EU hosting offered as an option or for storage only, while sending, tracking or support access remains non-EU, or the subprocessor list is absent.
5 — EU hosting as standard and an EU contracting entity, but parts of the chain — sending infrastructure, analytics, support tooling — are non-EU without an explained safeguard.
8 — EU or DACH hosting with a named data-centre provider, EU contracting entity, complete subprocessor list published, and any non-EU processing named with its legal basis.
10 — Sovereign end to end and evidenced: vendor, entity, hosting, sending and every subprocessor in the EU, certification published, and no transfer that needs a Schrems II argument to survive.
The CRM Manager
The contracting entity is ActiveCampaign, LLC in Chicago, with transfers to the United States, Australia, Ireland, Brazil and Costa Rica, DPF certification and Standard Contractual Clauses as the stated safeguards, and Google Analytics, session replay and web beacons named in its own stack. We found no public information on where subscriber data is hosted, and no public information naming the subprocessors — the privacy policy describes them only as unnamed categories — so the chain cannot be verified. As a buyer who weights this heavily, DPF plus SCCs is precisely the argument I would have to make rather than avoid. 3
The Deliverability Engineer
A Chicago contracting entity with data residency unconfirmed on the vendor's own pages, subprocessors published only as unnamed categories, US Cloud Act exposure through the optional Nylas email connection, session replay and Google Analytics in the chain, and CCPA disclosures of identifiers sold to data enrichment providers. The stated Data Privacy Framework certification and Standard Contractual Clauses are the only safeguards evidenced, which is thin cover for a list whose behavioural data I am asked to trust. 3
The Data Protection Officer
The contracting entity is ActiveCampaign, LLC of Chicago and transfers are disclosed to the United States, Australia, Ireland, Brazil and Costa Rica, with Google Analytics in use and Nylas named only for the optional email connection; we found no public information on EU hosting, a data-residency option, or a named data-centre provider. The published transfer basis is Data Privacy Framework certification with Standard Contractual Clauses available, so the question of where a person's open and click behaviour lives is answered only by the Schrems II argument I will not make. 3
The Shop Owner
The contracting entity is ActiveCampaign, LLC of Chicago, information may be transferred to the United States, Australia, Ireland, Brazil and Costa Rica, session replay and web beacons are in use, and identifiers have been sold to data enrichment providers, with no hosting or delivery subprocessors named beyond the optional Nylas connection. The Data Privacy Framework certification and Standard Contractual Clauses give a stated transfer basis, which lifts this off the floor. We found no public information on EU hosting as standard or on a published subprocessor list, and data residency is not confirmed on the captured pages. 3
The Integrator
The contracting entity is ActiveCampaign, LLC of Chicago, information may be transferred to the United States, Australia, Ireland, Brazil and Costa Rica, and core subprocessors appear only as unnamed categories, with Data Privacy Framework certification and Standard Contractual Clauses as the stated safeguards. Google Analytics runs within the services and the privacy page discloses identifiers and network activity sold to data enrichment providers, so processing rests on a framework argument rather than EU hosting; we found no public information on an EU hosting option or a published subprocessor list. 3
The Skeptic
The contracting entity is ActiveCampaign, LLC of Chicago, with transfers to the United States, Australia, Ireland, Brazil and Costa Rica; the captured pages name no hosting, storage or delivery providers — subprocessors appear only as unnamed categories — and the API's own address sits at api-us1.com. Transfers rest on Data Privacy Framework certification and Standard Contractual Clauses, which is precisely the transfer argument a Schrems II challenge tests; we found no public information confirming EU data residency, and the privacy policy discloses selling identifiers and internet activity information to data enrichment providers in the preceding 12 months. 3 12
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a sender can compute the real invoice for their list size and send volume — including overage, extra domains and automation limits — from public pages alone.
0 — No public prices at all; every tier is a sales conversation.
3 — A headline price per contact tier exists, but send limits, overage rates or the tier where automation begins are not stated.
5 — Contact-tier prices public with the billing period stated and send limits given, but at least one commonly needed capability sits in an unpriced tier or add-on.
8 — Every tier priced publicly with contact and volume limits, overage rates, feature boundaries and VAT treatment stated; only genuinely custom volume lacks a number.
10 — Complete price computability: a calculator producing the annual invoice for a given list size and send frequency, including overage, additional domains and dedicated IPs.
The CRM Manager
Four plans with entry prices public — Starter at $15 /mo, Plus at $49 /mo, Pro at $79 /mo, Enterprise at $145 /mo, each billed annually — plus stated send limits of 10x to 15x the contact limit by plan, user counts, automation caps, and which plan gets A/B testing, SSO and priority support, so feature boundaries are unusually visible. The real invoice still isn't computable: prices are "starts at" and scale by contact volume without a captured tier ladder, and we found no public information on overage rates, VAT treatment, or what the SMS, WhatsApp, transactional email and custom reporting add-ons cost. The $79 USD deliverability session is the only add-on I found with a number. 2 4 7
The Deliverability Engineer
All four plans carry public prices with the annual billing period stated and send limits given as multiples of the contact limit, which lets a sender roughly size the invoice. But every add-on a newsletter operation might need — SMS, WhatsApp, transactional email, the AI add-on — is published without a number, and I found no public information on overage rates or VAT treatment. 2 4
The Data Protection Officer
All four plans carry public prices with the annual billing period stated, send limits given as multiples of the contact limit, and feature boundaries such as the five-action automation cap on Starter. Several commonly needed capabilities — SMS, WhatsApp, transactional email, AI Activities and enhanced CRM — sit in add-ons with no public prices, and we found no public information on overage rates or VAT treatment, so the invoice for a given list size is not computable from these pages. 2 4
The Shop Owner
The four plans carry public starting prices with the annual billing period stated and send limits given as multiples of the contact count, which is more than many vendors show. But I cannot compute my real invoice: the contact count behind the starting prices is not given, and we found no public information on overage rates or VAT treatment. The add-ons a shop actually buys — transactional email, SMS, custom reporting, the premium ecommerce integrations — carry no public numbers; the deliverability consultation is the only priced extra I can see, at $79 USD. 2 4 7
The Integrator
Four plan prices are public with the billing period stated, email-send multiples per plan, and visible feature boundaries such as Starter capped at five actions per automation. We found no public information on the per-contact tier ladder, overage rates, prices for the SMS, WhatsApp, transactional and AI add-ons, or VAT treatment, so the real invoice for a given list size is not computable from the captured pages. 2 4 7
The Skeptic
Four plan prices are public with the billing period stated — "Starts at $15 /mo", "$49 /mo", "$79 /mo", "$145 /mo", all "Billed annually" — and unusually the boundaries are too: email sends as multiples of the contact limit, user counts, segmentation level and where automation A/B testing begins. Still missing for a computable invoice: overage rates, VAT treatment, the contact-volume steps behind "Starts at", and any price for the SMS, WhatsApp, transactional, custom-reporting and CRM add-ons. 2 7
European sovereignty — proven facts
0 of 4 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined ⚠ unverified | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined ⚠ unverified | — | uncited Report an error |
| Subprocessors | Not determined ⚠ unverified | — | uncited Report an error |
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 30 Aug 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Legal entity, Data residency, Subprocessors. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 32 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 24 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 11 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 11 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 9 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 subprocessors facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (14)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.activecampaign.com Checked 5 Oct 2026 +1 earlier capture: 30 Aug 2026 Details →
- 2 Pricing www.activecampaign.com Checked 5 Oct 2026 +2 earlier captures: 11 Sep 2026, 30 Aug 2026 Details →
- 3 Privacy policy www.activecampaign.com Checked 5 Oct 2026 +1 earlier capture: 15 Sep 2026 Details →
- 4 Campaigns & automation — found from sitemap www.activecampaign.com Checked 5 Oct 2026 Details →
- 5 Campaigns & automation — found from sitemap www.activecampaign.com Checked 5 Oct 2026 Details →
- 6 Campaigns & automation — found from sitemap www.activecampaign.com Checked 5 Oct 2026 Details →
- 7 Deliverability infrastructure — found from sitemap www.activecampaign.com Checked 5 Oct 2026 Details →
- 8 Deliverability infrastructure — found from sitemap www.activecampaign.com Checked 5 Oct 2026 Details →
- 9 Consent, proof & tracking limits — found from sitemap www.activecampaign.com Checked 5 Oct 2026 Details →
- 10 Consent, proof & tracking limits — found from sitemap www.activecampaign.com Checked 5 Oct 2026 Details →
- 11 List ownership, import & exit — found from sitemap developers.activecampaign.com Checked 5 Oct 2026 +1 earlier capture: 30 Sep 2026 Details →
- 12 List ownership, import & exit — found from sitemap developers.activecampaign.com Checked 5 Oct 2026 +1 earlier capture: 30 Sep 2026 Details →
- 13 Integrations & API — found from sitemap developers.activecampaign.com Checked 5 Oct 2026 Details →
- 14 Integrations & API — found from sitemap www.activecampaign.com Checked 5 Oct 2026 Details →