whats-best.ai

Marketing Automation

HubSpot Marketing Hub

Rest of world Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 3 of 4 dimensions proven

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

by HubSpot, Inc. · www.hubspot.de

Compare with Evalanche → Compare with ActiveCampaign (Automation) → 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 Sales Ops Manager

Weighted verdict

Owns the CRM and inherits every duplicate the platform creates. Wants field-level ownership defined, conflict rules that are configurable rather than folklore, and a sync error log somebody can act on before the pipeline report is wrong.

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

Scored by The Sales Ops Manager

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 Sales Ops Manager

Unlimited workflow actions from Professional up, with behavioural events usable as triggers and journey analytics up to 15 phases, so this is a real engine — but nothing evidences branching, waits, entry/exit conditions or per-contact journey state, and the collision handling that stops two workflows double-mailing one lead (frequency capping, cross-journey suppression, priority) is completely absent from the evidence. 2

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 Sales Ops Manager

'Automatisches Leadscoring' is named for Professional/Enterprise workflows and attribution logs up to 10,000 interactions per contact — that is the entire evidentiary basis. No lifecycle stages, no routing to owners or teams, no decay, no negative or account-level scoring, no score history, and nothing that would let me explain a score to a lead or a DPO. 2

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 Sales Ops Manager

Email is documented down to per-tier send limits (5x/10x/20x of contact level), custom event tracking (500 definitions, 30M completions/month) and a credit-metered Customer Agent exist, and 'Omni-Channel-Marketingautomatisierung' is claimed at Professional+ — but no second channel is ever named, and SMS, push, on-site content, ad audiences, dynamic content and shared suppression are all silent. 2

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 Sales Ops Manager

This is the join that decides my implementation and the evidence offers exactly one fact: 'über 2.000' marketplace apps. No named CRM, no sync direction, no field mapping, no deduplication rules, no conflict resolution per field, no sync error log, no documented API — a big marketplace proves connectors exist; it says nothing about who owns a field when two systems disagree or how I replay a failed sync before the pipeline report is wrong. 2

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 Sales Ops Manager

The vendor is HubSpot, Inc. of Cambridge, Massachusetts, the sovereignty pipeline found jurisdiction, residency and subprocessor exposure all unknown (0 of 10), and behavioural profiles of EU website visitors run through a tracking code where HubSpot is the controller. A German support number and an Annex-3 affiliate subprocessor list do not offset that; there is no EU hosting, no published subprocessor chain and no transfer basis anywhere in this evidence. 2 3

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 Sales Ops Manager

The tier where automation actually begins is unambiguous — 10 automated actions at Starter, unlimited plus omni-channel from Professional — and send volume is stated as a multiple of the contact tier with AI usage metered in published credits per resolved conversation, which is better boundary disclosure than most. But no monetary price, onboarding fee, VAT treatment or minimum term appears anywhere in the evidence, so I still cannot compute the annual invoice. 1 2

Report an error

European sovereignty — proven facts

3 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 EU optional ⚠ unverified 1/3 pts 4 Report an error
Subprocessors US CLOUD Act reach ⚠ unverified 0/2 pts 4 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 (15)

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

  1. 1 Product page www.hubspot.de Checked 16 Sep 2026 Details →
  2. 2 Pricing www.hubspot.de Checked 16 Sep 2026 Details →
  3. 3 Privacy policy legal.hubspot.com Checked 16 Sep 2026 +1 earlier capture: 2 Sep 2026 Details →
  4. 4 Security / trust page www.hubspot.de Checked 30 Sep 2026 Details →
  5. 5 Privacy policy www.hubspot.de Checked 30 Sep 2026 Details →
  6. 6 Journeys & orchestration — found from sitemap www.hubspot.de Checked 1 Oct 2026 Details →
  7. 7 Journeys & orchestration — found from sitemap www.hubspot.de Checked 1 Oct 2026 Details →
  8. 8 Lead scoring, routing & lifecycle — found from sitemap www.hubspot.de Checked 1 Oct 2026 Details →
  9. 9 Lead scoring, routing & lifecycle — found from sitemap www.hubspot.de Checked 1 Oct 2026 Details →
  10. 10 Channels & personalisation — found from sitemap www.hubspot.de Checked 1 Oct 2026 Details →
  11. 11 Channels & personalisation — found from sitemap www.hubspot.de Checked 1 Oct 2026 Details →
  12. 12 Consent, tracking & profiling — found from sitemap www.hubspot.de Checked 1 Oct 2026 Details →
  13. 13 Consent, tracking & profiling — found from sitemap www.hubspot.de Checked 1 Oct 2026 Details →
  14. 14 CRM integration & data model — found from sitemap www.hubspot.de Checked 1 Oct 2026 Details →
  15. 15 CRM integration & data model — found from sitemap www.hubspot.de Checked 1 Oct 2026 Details →