whats-best.ai

Marketing Automation

ActiveCampaign (Automation)

Rest of world Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 1 of 4 dimensions proven

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by ActiveCampaign, LLC · www.activecampaign.com

Compare with Evalanche → Compare with HubSpot Marketing Hub → 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 Demand Gen Lead

Weighted verdict

Owns pipeline contribution and is measured on it. Wants journeys that branch on real behaviour, scoring that sales trusts, and attribution that survives a quarterly review. Unmoved by a builder that demos beautifully and cannot say which journey sent yesterday's email.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Demand Gen Lead

Journeys & orchestration

How this is scored

Multi-step automation: triggers, branching, waits, and — the part that decides whether it survives contact with reality — what happens when journeys collide.

0 — Autoresponders on a single trigger; no branching, no waits, no conditions.

3 — Linear sequences with simple conditions, one entry trigger per journey, and no visibility into where a contact currently sits.

5 — A visual builder with branching on attributes and behaviour, waits and goals, entry and exit conditions, and per-contact journey state visible.

8 — Event-driven entry from external systems, frequency capping and suppression across journeys, priority when a contact qualifies for several, versioning of a live journey, and testing against real records.

10 — Orchestration is coherent across the whole programme: one decision layer deciding what a person receives next regardless of which journey wants to send it, holdout groups for measurement, and a journey a colleague can read months later without a diagram.

Report an error

The Demand Gen Lead

The builder branches on contact actions and behaviours, goals are tracked with drop-off visibility and fallback follow-ups, and entries fire from real events — site and app actions, deal-stage changes, form tools and segment moves. What the captured pages give me nothing on is collision handling: I found no public information on frequency capping, suppression across journeys, priority when a contact qualifies for several, or versioning of a live journey, and that is the part that decides whether a programme survives a quarter. 2 4 5 7

Report an error

Lead scoring, routing & lifecycle

How this is scored

Scoring, qualification and handover to sales — including whether the customer can explain to a lead why the system decided what it decided.

0 — No scoring or lifecycle model; every contact is treated alike.

3 — A single additive score with fixed rules, no decay, no lifecycle stages and no routing.

5 — Configurable scoring on attributes and behaviour with decay, lifecycle stages, and routing to owners or teams with notification.

8 — Multiple scoring models per product or region, negative scoring, account-level scoring alongside contact-level, SLA on follow-up, and score history visible per contact.

10 — Scoring is explainable and accountable: the contribution of each signal visible per record, model changes versioned with their effect on the funnel, routing rules auditable, and predictive scoring — where offered — documented well enough for a DPO to assess it as automated decision-making.

Report an error

The Demand Gen Lead

Scoring is genuinely built out: separate models per line of business, points deducted as well as awarded, category- and product-level scores, real-time scoring from visits and clicks, automated routing to reps and deal creation once a contact's score reaches a defined point, with scores syncing to the CRM in real time. I found no public information on account-level scoring, follow-up SLAs or per-contact score history — without the history behind the number, sales trusts it less. 2 5 6

Report an error

Channels & personalisation

How this is scored

What the platform can actually send and personalise: email, SMS, push, on-site content, ads audiences — judged on what shares one profile and one suppression list.

0 — Email only.

3 — Email plus one further channel, managed separately with its own list and no shared suppression.

5 — Email, SMS or push and web forms driven from one contact profile, with dynamic content blocks and shared unsubscribe handling.

8 — The above plus on-site personalisation, ad-audience sync to the major networks, cross-channel frequency capping, and content personalised on behaviour rather than only on stored fields.

10 — Channel is a delivery detail: one profile and one consent state across every channel, next-best-channel selection, and personalisation that draws on the full behavioural record without the marketer assembling it by hand.

Report an error

The Demand Gen Lead

Email, SMS, WhatsApp, site messages, forms and landing pages run off one platform, with retargeting and prospecting audiences to Google, Facebook and LinkedIn, and personalisation driven by behaviour rather than stored fields alone. Push arrives only via integration, and I found no public information on cross-channel frequency capping or next-best-channel selection — the collision problem again. 2 4 8 9

Report an error

CRM integration & data model

How this is scored

The join that decides the implementation: how the platform and the CRM stay in agreement about who a person is, and what happens when they disagree.

0 — CSV import and export; no CRM integration and no identity resolution.

3 — One-way sync into a named CRM on a schedule, with duplicates resolved by hand and no conflict rules.

5 — Bidirectional sync with at least one major CRM, field mapping, deduplication rules, and a sync error log somebody can act on.

8 — Configurable conflict resolution per field, account and contact objects both modelled, custom objects supported, near-real-time sync with retry, and a documented API with rate limits.

10 — One record, two systems, no ambiguity: identity resolution across anonymous and known states, field-level ownership defined per system, replay of failed syncs, and a data model the customer can extend without vendor services.

Report an error

The Demand Gen Lead

The contact sync endpoint is documented in unusual depth — a defined lookup order across id, WhatsApp id, email and phone, upsert semantics, per-action permissions, and a source tag so integrations skip their own writes — and account and contact objects are both modelled. The hard part is what I cannot see: field-level conflict rules, a sync error log, replay of failed syncs and API rate limits are all absent from the captured pages, and the Salesforce sync direction is not stated; anonymous visitor identification hints at anonymous-to-known resolution but the identity model is not laid out. 2 5 12 13

Report an error

European sovereignty

How this is scored

Where behavioural profiles of named EU residents are processed, who the contracting entity is, and which subprocessors see them. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it — which given the profiling is heavily.

0 — Non-EU vendor and contracting entity, hosting unstated or non-EU, subprocessors unnamed, behavioural data leaving the EU with no stated basis.

3 — EU data residency for storage while tracking, sending or support access remain non-EU, or the contracting entity sits outside the EU.

5 — EU hosting as standard and an EU contracting entity, but parts of the chain — tracking scripts, AI scoring, analytics — are non-EU without an explained safeguard.

8 — EU hosting on named infrastructure, EU contracting entity, complete subprocessor list published, and any non-EU processing named with its legal basis.

10 — Sovereign end to end and evidenced: every profile, event and derived score processed in the EU by European subprocessors, certification published, and no transfer requiring a Schrems II argument to survive.

Report an error

The Demand Gen Lead

The contracting entity is ActiveCampaign, LLC in Chicago, the API lives on a US-named domain, and the stated basis for moving EU data is the Data Privacy Framework and standard contractual clauses — a transfer argument, not a residency answer. Nylas, a US-headquartered provider, is named for the optional email connection, and I found no public information on EU hosting for client data or a published subprocessor list. For behavioural profiles of named EU residents I weigh that heavily. 3 11 12

Report an error

Pricing transparency

How this is scored

Whether a buyer can compute the real annual invoice for their contact base and send volume — including the tier where automation actually begins, overage, and mandatory onboarding — from public pages alone.

0 — No public prices at all; every tier is a sales conversation, and onboarding fees are never mentioned.

3 — A contact-tier headline exists, but the tier where journeys, scoring or CRM sync begin is unstated, as is any mandatory implementation fee.

5 — Contact-tier prices public with billing period and send limits stated, but at least one commonly needed capability sits in an unpriced enterprise tier.

8 — Every tier priced publicly with contact and volume limits, feature boundaries, overage rates, onboarding costs, minimum term and VAT treatment stated.

10 — Complete price computability: annual invoice derivable for a given contact count, send volume and feature set, including overage, additional users and any implementation fee stated outright.

Report an error

The Demand Gen Lead

All four tiers carry public prices with billing period, send limits stated as multiples of the contact count, user counts and unusually clear feature boundaries — automation exists from the entry tier with a five-action cap — and onboarding and migration are free on every plan. But the contact count those "starts at" prices actually cover is not stated, the SMS, WhatsApp, CRM and AI add-ons carry no prices, and I found no public information on overage rates or VAT treatment, so the real annual invoice is not computable from public pages alone. 2 4 9

Report an error

European sovereignty — proven facts

1 of 4 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Ownership Not determined — uncited Report an error
Data residency Not determined ⚠ unverified — uncited Report an error
Subprocessors US CLOUD Act reach ⚠ unverified 0/2 pts 3 Report an error

Where this could be wrong

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.

Sources (13)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor homepage www.activecampaign.com Checked 5 Oct 2026 Details →
  2. 2 Pricing www.activecampaign.com Checked 5 Oct 2026 +2 earlier captures: 11 Sep 2026, 2 Sep 2026 Details →
  3. 3 Privacy policy www.activecampaign.com Checked 5 Oct 2026 +1 earlier capture: 15 Sep 2026 Details →
  4. 4 Journeys & orchestration — found from sitemap www.activecampaign.com Checked 5 Oct 2026 Details →
  5. 5 Journeys & orchestration — found from sitemap www.activecampaign.com Checked 5 Oct 2026 Details →
  6. 6 Lead scoring, routing & lifecycle — found from sitemap www.activecampaign.com Checked 5 Oct 2026 Details →
  7. 7 Lead scoring, routing & lifecycle — found from sitemap www.activecampaign.com Checked 5 Oct 2026 Details →
  8. 8 Channels & personalisation — found from sitemap www.activecampaign.com Checked 5 Oct 2026 Details →
  9. 9 Channels & personalisation — found from sitemap www.activecampaign.com Checked 5 Oct 2026 Details →
  10. 10 Consent, tracking & profiling — found from sitemap www.activecampaign.com Checked 5 Oct 2026 Details →
  11. 11 Consent, tracking & profiling — found from sitemap developers.activecampaign.com Checked 5 Oct 2026 Details →
  12. 12 CRM integration & data model — found from sitemap developers.activecampaign.com Checked 5 Oct 2026 +1 earlier capture: 1 Oct 2026 Details →
  13. 13 CRM integration & data model — found from sitemap www.activecampaign.com Checked 5 Oct 2026 Details →