Marketing Automation

Adobe Marketo Engage

Rest of world Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: not determined

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

An AI-assisted analysis of public evidence — not a hands-on test.

Every score, rationale and verdict on this page is AI-generated. Every claim cites the source it was read from. Nothing here is a human star review — and no score can be bought. How scores are made →

Method and versions

The Demand Gen Lead v1.0 · The Sales Ops Manager v1.0 · The Data Protection Officer v1.0 · The Lifecycle Marketer v1.0 · The Solution Architect v1.0 · The Skeptic v1.0 · rubric v1 · evaluated 5 Oct 2026

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

The captured developer pages show a journey orchestration layer with organisation-level throughput caps, per-endpoint call limits for actions and data sources, pre-deployment validation and virtual sandbox isolation — evidence of event-driven journeys reaching into external systems. I found no public information on branching, waits, goals, per-contact journey state, or suppression and priority when a person qualifies for several journeys, which keeps this mid-scale. 1

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

The captured pages show only program membership status management and static list add/remove; I found no public information on scoring, decay, lifecycle stages or routing to owners. Program member statuses are the one lifecycle-adjacent feature evidenced, and that is a campaign view, not a lead lifecycle. 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

The captured pages document data ingestion and journey governance but name no messaging channel — I found no public information on email, SMS, push, on-site content or ad audiences, let alone shared profiles or suppression across them. Journeys imply delivery of something, but the pages never say what. 1 2

Report an error

Consent, tracking & profiling

How this is scored

The platform builds behavioural profiles of named people. Consent capture and proof, tracking that can be limited, retention, and whether automated decisions about individuals are documented and contestable.

0 — Tracking always on and undocumented, single opt-in, no consent record, no retention rule, no way to exclude a person from profiling.

3 — Double opt-in available with a timestamp, cookie tracking that cannot be disabled per contact, and retention described as the customer's problem.

5 — Double opt-in as documented default with a stored consent record including source, per-channel consent states, tracking switchable per contact, and stated retention for inactive records.

8 — Consent reproducible as evidence with the wording versioned, profiling suppressible per person, retention executed per data category, documented handling of access and erasure requests including derived scores, and a cookieless or first-party tracking mode.

10 — Built for the accountability principle: a per-contact history of what was tracked, scored and decided, automated decision-making documented well enough to support an Art. 22 assessment, profiling off by default for anyone who has not consented to it, and deletion that removes derived scores as well as raw events.

Report an error

The Sales Ops Manager

Person records, person partitions and web-tracking subscription identifiers appear in the API pages, so behavioural profiling of named people is clearly in scope. I found no public information on consent capture, per-contact tracking switches, retention rules, or handling of access and erasure requests — for a platform holding these profiles, that silence is itself the finding. 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 best-evidenced area: documented upsert for persons, companies, custom objects and program members, deduplication by declared fields including Salesforce identifiers and custom attributes, a 65-minute retry window when a linked person is missing, and request status retrievable through an observability stream alongside a published API specification. What I found no public information on is per-field conflict rules, field mapping, and a bidirectional sync with a named CRM — upsert semantics are not conflict resolution, and I inherit every record that ambiguity creates. 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 contracting entity is Adobe Inc. of San Jose, California, and the captured material states no hosting location, names no subprocessors and gives no legal basis for transfers of behavioural profile data out of the EU. With profiling of named residents at stake and no sovereignty attributes on record, this sits at the floor. 1 2

Report an error

Pricing transparency not rated — the vendor publishes no price

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

I found no public pricing at all in the captured material — no contact tier, no send limits, no statement of where automation begins and no mention of onboarding fees. A buyer cannot begin to compute an annual invoice from what is published here. 1 2

Report an error

Where this could be wrong

Evidence ages. The oldest capture behind this page is from 1 Oct 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
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.

We found no public information on pricing on the pages we read (developer.adobe.com/journey-optimizer-apis/references/journeys-throttling, developer.adobe.com/marketo-apis/api/data-ingestion). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
We found no public information on compliance on the pages we read (developer.adobe.com/journey-optimizer-apis/references/journeys-throttling, developer.adobe.com/marketo-apis/api/data-ingestion). If the vendor publishes it somewhere else, send us the page. Know more? Tell us

Do you know more about Adobe Marketo Engage? Tell us Report an error on this page

Sources (2)

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

1 Journeys & orchestration — found from sitemap developer.adobe.com Checked 1 Oct 2026 Details →
2 CRM integration & data model — found from sitemap developer.adobe.com Checked 1 Oct 2026 Details →