0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Ortto Pty Ltd · www.ortto.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Ortto at a glance
- Vendor
- Ortto Pty Ltd
- Headquarters
- Not stated on the vendor’s pages as of 26 Oct 2026
- Data hosting
- Default not stated; pages mention the EU, the United States, Australia and Asia source, captured 26 Oct 2026
- Free plan
- Not stated on the vendor’s pages as of 26 Oct 2026
- Panel verdict
- The AI panel rates Ortto 2.5/5, the mean of 6 judges. Ortto, formerly Autopilot, is a marketing automation platform built around a customer data platform that feeds a visual journey builder. how scores are made
- As of
- Vendor pages captured 26 Oct 2026; evaluated by the panel 29 Oct 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Ortto, formerly Autopilot, is a marketing automation platform built around a customer data platform that feeds a visual journey builder. Its strongest area is channel coverage, where scores cluster at 7, the table's top mark: email, SMS, push, in-app messages, chat and ad-audience sync all hang off one profile, with content chosen on behaviour. Lead management is steady at 6, crediting documented score decay and round-robin routing to sales. Sovereignty is the weak point, scoring 3 throughout: the captured pages state multi-region hosting in EU, USA and Australia — one page adds Asia — but leave the contracting entity's jurisdiction, ownership and subprocessor locations unknown, which judges weighed against deep profiling of named people. Scores spread by a point on journey orchestration, 6 to 7, and on consent and profiling, 5 to 6: the higher scores credit unusually concrete access-and-erasure handling, the lower ones find no public information on frequency capping, cross-journey suppression, consent timestamps or retention limits, while Retention+ is marketed as storing activity data forever. Public pricing information amounts to a 14-day free trial.
Speaks for it
- Email, SMS, push, in-app messages, chat and ad-audience sync run off one customer data platform profile, earning channel coverage the table's top score of 7
- A visual journey builder is documented with behavioural triggers, conditions, splits, delays, entry and exit criteria, contact ejection, and version control with revert, including journeys started from new Salesforce records and activities
- Lead scoring with automatic half-life decay drives journey entry and exit, with round-robin assignment templates routing demo requests and trial users to sales
- Bidirectional Salesforce sync models lead, contact, account, opportunity, campaign, task and custom objects, with HubSpot CRM and Pipedrive also named
- Access and erasure handling is documented with a thirty-day response deadline, identity verification, and deletion and correction requests forwarded to subprocessors
Held against it
- Sovereignty scores sit at 3 with no variation, as the contracting entity's jurisdiction, ownership and subprocessor locations are not established by the captured pages
- We found no public information on frequency capping, suppression across journeys, or priority when a contact qualifies for several journeys at once
- The tracking pages advertise a first-party script that "can't be blocked", and Retention+ is marketed as storing historical activity data forever with no stated retention limit bounding it
- We found no public information on field-level conflict resolution, duplicate handling, sync retries with error logs, or documented API rate limits for the CRM integrations
- Pricing transparency scores span 0 to 2, with only a 14-day free trial appearing on the captured pages
Best for
- You run lifecycle marketing across email, SMS, push, in-app messages and ads from a single customer data platform profile, with content selected on real-time behaviour rather than stored fields alone
- You build on Salesforce and want journeys triggered from new records and activities, with lead, contact, account, opportunity, campaign, task and custom objects reachable without vendor services
- You want documented lead scoring with automatic decay feeding round-robin routing of demo requests and trial users to sales
- You need a documented access and erasure process — thirty-day responses, identity verification, and deletion and correction requests forwarded to subprocessors
Avoid if
- You must prove a European processing chain beyond the EU hosting option before signing — ask the vendor: the public pages we read do not show it
- You need bounded retention and prompt opt-outs — Retention+ is marketed as storing historical activity data forever and the policy states opt-out requests are honored within up to fifteen days
- You run overlapping campaigns and need frequency capping or cross-journey suppression documented before launch — we found no public information on either, nor on priority when a contact qualifies for several journeys
- Your sales team must be able to explain a lead's score to the individual it was computed about — we found no public information on per-contact score history or each signal's contribution to a score
The scores
| Criterion | Panel median |
|---|---|
| Journeys & orchestration | 3 of 5 |
| Lead scoring, routing & lifecycle | 3 of 5 |
| Channels & personalisation | 3.5 of 5 |
| Consent, tracking & profiling | 2.5 of 5 |
| CRM integration & data model | 3 of 5 |
| European sovereignty | 1.5 of 5 |
| Pricing transparency | 0.5 of 5 |
Journeys & orchestration
Show reasoningHide reasoning
How this is scored
Multi-step automation: triggers, branching, waits, goals — and what happens when a contact qualifies for several journeys at once.
0 — No automation; the product sends one-off campaigns only.
3 — Autoresponders or linear sequences started by a trigger such as a sign-up or a tag, with waits between steps.
5 — A visual workflow builder with triggers on behaviour and attributes, if/else branching and waits, and goals or exit conditions that take a contact out of the flow.
8 — Event-driven entry from external systems through an API, frequency capping and suppression across journeys, priority when a contact qualifies for several, per-contact journey state and reporting per step, versioning or safe editing 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 journeys documented and readable months later.
The Demand Gen Lead
The visual builder is real: conditions, splits, delays, filters, entry and exit criteria, journey ejection, version control with revert, and journeys triggered from new Salesforce records or activities — that clears the core bar and then some. What I cannot run a programme on is undocumented: we found no public information on frequency capping, suppression across journeys, or priority when a contact qualifies for several at once, and journey reporting is named without per-step or per-contact state. 3 5 6 12
The Sales Ops Manager
A visual journey builder with email, SMS, push, action, delay, condition, filter and percentage-split shapes, entry and exit criteria driven by real-time customer data, an eject action that disqualifies contacts mid-journey, version control with revert to past versions, and journeys that can start from new Salesforce records or activities. We found no public information on frequency capping, priority when a contact qualifies for several journeys, or per-step reporting, which is what I would need to trust the automation at scale. 3 5 6 12
The Data Protection Officer
A visual journey builder with behavioural triggers, conditions, delays, split paths, entry/exit criteria and contact ejection is documented, and journeys can start from Salesforce records and activities, with per-journey reporting and version control that allows reverting changes. We found no public information on frequency capping, suppression across journeys, or what happens when a contact qualifies for several journeys at once. 3 6 11 12
The Lifecycle Marketer
A visual journey builder with behavioural triggers, condition and percentage splits, waits, score-based entry and exit, and journey ejection is well documented, and version control with rollback plus journeys triggered from new Salesforce records and activities pushes it past the basics. What decides the score for me is what the pages omit: we found no public information on frequency capping, priority when a contact qualifies for several journeys, or holdout groups. 3 6 11 12
The Solution Architect
The visual builder is real and documented — triggers on lists, smart segments and form submissions, condition splits, delays and wait-until-filter, exit ejection, and version control with revert, plus journeys that can start from new Salesforce records and activities. What I cannot see is the collision handling: the captured pages show ejection of unsubscribed contacts but no cross-journey suppression, priority when one contact qualifies for several journeys, frequency capping, or per-step reporting — just reports and dashboards at journey level. That is a competent programme-level engine, not yet one decision layer. 3 5 6 11 12
The Skeptic
A visual builder with conditions, delays, splits, entry and exit criteria, contact ejection, version history and journey reporting is documented, and journeys can start from new Salesforce records and activities. But we found no public information on frequency capping and suppression across journeys, or on what happens when a contact qualifies for several journeys at once. 3 5 6 12
Lead scoring, routing & lifecycle
Show reasoningHide reasoning
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, lifecycle or lead handling at all; the product is a sending tool for lists.
3 — A rule-based lead score from attributes or engagement, or lifecycle stages set by tags or fields.
5 — Configurable lead scoring on attributes and behaviour, lifecycle or pipeline stages, and qualified leads assigned or notified to sales.
8 — Multiple scoring models per product or region, negative scoring and score decay, account-level scoring alongside contact-level, routing rules to owners or teams with follow-up SLAs, 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.
The Demand Gen Lead
Scoring is configurable across journey stages with automatic score decay, scores drive journey entry and exit, and round-robin routing templates hand demo requests and trials to sales — a score my reps could actually work. Beyond that, we found no public information on multiple scoring models, account-level scoring, follow-up SLAs, per-contact score history, or how a score would be explained to the individual it was computed about. 3 5 11
The Sales Ops Manager
Scores are built for every stage of the customer journey, trigger journey entry and exit, and degrade automatically over time, while qualified leads reach sales through round-robin assignment templates for demo requests and trial users. We found no public information on multiple scoring models, negative scoring, account-level scores, follow-up SLAs or per-contact score history, so a sales team cannot explain to a lead why a number is what it is. 3 5 6 11
The Data Protection Officer
Scores trigger journey entry and exit, decay automatically on a half-life, and a qualification journey with round-robin assignment routes leads to sales. We found no public information on multiple scoring models, negative scoring, follow-up SLAs, per-contact score history, or any statement of each signal's contribution to a score — which is what I would need to assess the scoring as automated decision-making under Article 22. 3 5 6 11
The Lifecycle Marketer
Scores built per lifecycle stage with automatic decay, qualification journeys feeding a 90-day behaviour-paced nurture, and round-robin lead assignment plus trial-to-sales routing are all evidenced. We found no public information on negative scoring, account-level scoring, follow-up SLAs, or score history visible per contact — nothing that would let a customer show a lead why the score moved. 3 5 6 11
The Solution Architect
Scores are built for every lifecycle stage with half-life decay, and they drive journey entry, exit and conditional paths; round-robin lead assignment templates route demo requests and trial users to sales, with notifications to inbox or Slack. That covers decay and routing, the two things mid-market tools usually fumble. We found no public information on negative scoring, account-level scoring alongside contact-level, follow-up SLAs, score history visible per contact, or anything that would let a customer explain a score to a lead. 5 6 3 11
The Skeptic
Scoring is documented with scores built per journey stage, half-life degradation, qualification through condition checks, and round-robin assignment of demo and trial leads to sales. We found no public information on negative scoring, multiple scoring models, account-level scoring, score history per contact, or follow-up service levels on routed leads. 3 5 6 11
Channels & personalisation
Show reasoningHide reasoning
How this is scored
What the platform can send and personalise — email, SMS, push, on-site content, ad audiences — judged on what shares one profile and one suppression list.
0 — Not a sending platform; the product cannot deliver messages on any channel.
3 — Email with merge-field personalisation, plus sign-up forms or landing pages.
5 — Email plus at least one further channel (SMS, push, or ad-audience sync) driven from the same contact profile, and dynamic content blocks based on contact data.
8 — Email, SMS and push from one profile with shared unsubscribe handling, 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.
The Demand Gen Lead
Email, SMS, push, in-app messages, forms and dynamic ad-audience sync all hang off the same CDP profile, and content selection runs on behaviour — email clicks deciding what a contact receives next — rather than only stored fields. The SMS preference center handles per-audience unsubscribe, but we found no public information on cross-channel frequency capping, shared unsubscribe handling across channels, or next-best-channel selection. 1 3 6 7 12
The Sales Ops Manager
Email, SMS, push, in-app messages, live chat, popups and forms, and synced ad audiences on Google Ads all draw on the built-in customer data platform profile, with content chosen on behaviour — email clicks decide what a contact receives next. SMS gets its own opt-in collection and a preference centre with per-audience unsubscribe; we found no public information on cross-channel frequency capping or one unsubscribe state shared across every channel. 1 3 6 7 12
The Data Protection Officer
Email, SMS, push, in-app messages and ad-audience sync all draw on the single customer-data-platform profile, with dynamic content and pacing driven by behaviour rather than stored fields alone. We found no public information on one consent state across every channel, shared cross-channel unsubscribe handling, or cross-channel frequency capping. 1 3 7 8 12
The Lifecycle Marketer
Email, SMS and push are orchestrated from one customer-data-platform profile alongside in-app messages, popups and forms, with ad-audience sync to Google Ads and other platforms, an SMS preference centre with per-audience unsubscribe, and content personalised on clicks and real-time behaviour rather than merge fields alone. We found no public information on on-site content personalisation or cross-channel frequency capping, which is what keeps it out of the top band for me. 3 6 7 12
The Solution Architect
Email, SMS, web and mobile push, live chat, in-app messages and popups all hang off one customer-data-platform profile, ad audiences are maintained dynamically in the ad platforms, and personalisation runs on behaviour — email clicks steering the next content — rather than stored fields alone, including Salesforce object values merged into email and SMS. SMS has its own consent collection and a per-audience unsubscribe preference centre. We found no public information on cross-channel frequency capping, which is the piece that keeps one profile from becoming three message streams. 1 12 7 3 6 8
The Skeptic
Email, SMS, push, in-app messages, chat, forms and ad-audience sync are all documented as driven from the one customer data platform, with dynamic content and behaviour-based pacing of messages. We found no public information on cross-channel frequency capping, and unsubscribe handling is documented per SMS audience rather than shared across channels. 1 3 6 7
Consent, tracking & profiling
Show reasoningHide reasoning
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 — The vendor states a practice that defeats consent, such as importing purchased lists or tracking named contacts with no opt-in mechanism at all.
3 — Double opt-in available and unsubscribe handled per contact.
5 — Double opt-in with the consent timestamp and source stored per contact, consent or subscription status per channel, and a documented way to answer access and erasure requests.
8 — Consent reproducible as evidence with the wording versioned, tracking switchable per contact or a cookieless or first-party tracking mode, profiling suppressible per person, retention for inactive records stated and executed per data category, and erasure covering derived scores.
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 DSGVO assessment, profiling off by default for anyone who has not consented to it, and deletion that removes derived scores as well as raw events.
The Demand Gen Lead
Two-step opt-in, SMS opt-in permission collection with a preference center, an automatic cookie opt-in prompt, and an unusually detailed request process covering access, rectification, erasure and forwarding deletions to subprocessors within thirty days. The consent timestamp and source per contact, retention for inactive records, and erasure covering derived scores are not documented, and the policy itself states opt-out requests are honored within fifteen days. 2 7 9 10
The Sales Ops Manager
Two-step opt-in, an automatic GDPR cookie opt-in prompt, SMS opt-in collection, and a genuinely documented access and erasure route — 30-day response, search across databases and backups, deletion forwarded to subprocessors, verification data deleted promptly — with AI features toggleable and customer control over model training. We found no public information on consent timestamps or sources stored per contact, per-contact tracking switches, suppression of profiling per person, or retention periods for inactive records, and Retention+ is presented as storing activity history forever. 2 7 9 10 12
The Data Protection Officer
Access and erasure handling is the best-documented area: self-service and webform channels, identity verification, a thirty-day response deadline, and forwarding of deletion and correction requests to subprocessors. Opt-in is documented as a two-step process and SMS consent is collected through forms with a per-audience preference centre. We found no public information on per-contact consent timestamps with versioned wording, tracking switched off per person, profiling suppression, retention executed per data category, or erasure covering derived scores — and the tracking pages advertise a first-party script that can't be blocked alongside Retention+ storing historical activity forever, with no stated retention limit bounding either. 2 7 9 10 12
The Lifecycle Marketer
A two-step opt-in with verification is set out, cookie tracking runs on an opt-in prompt, SMS consent is collected through popups and forms, and the access and erasure machinery is documented in unusual detail with logged requests and deletion forwarded to subprocessors. We found no public information on consent timestamps and source stored per contact, per-contact tracking switches, suppression of profiling per person, or erasure reaching derived scores — and the first-party tracking script is marketed as one that "can't be blocked". 2 7 9 10
The Solution Architect
Two-step opt-in is stated policy, a GDPR cookie opt-in prompt is documented, tracking runs first-party, and the subject-access machinery is unusually concrete — acknowledgement within ten business days, verification thresholds, 24-month request records, deletion and correction forwarded to subprocessors, AI features toggleable by the customer. We found no public information on versioned consent wording, per-person suppression of profiling, retention stated and executed per data category, or whether erasure reaches derived scores; the opt-out honour window is stated at up to fifteen days. 9 2 10 7
The Skeptic
Two-step opt-in, a documented access and erasure process with 30-day responses, verification tiers, audit and DPO review, and first-party tracking behind a GDPR cookie prompt are all on the record. We found no public information on versioned consent wording, per-contact suppression of profiling, retention limits for inactive records — a feature marketed as storing historical activity data forever — or deletion covering derived scores. 2 7 9 10 12
CRM integration & data model
Show reasoningHide reasoning
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 — No way to get contact data in or out beyond typing it in.
3 — CSV import and export, and a sync or connector to a named CRM.
5 — Two-way sync with at least one major CRM (or a built-in CRM) with field mapping, duplicate handling, and a documented API.
8 — Configurable conflict resolution per field, account and contact objects both modelled, custom objects supported, near-real-time sync with retry and an error log, and API rate limits documented.
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.
The Demand Gen Lead
Bi-directional Salesforce sync into the CDP with selective filters, lead, contact, account, opportunity, campaign, task and custom objects all modelled, and journeys tracking entry and exit by Salesforce object ID — the join exists and it is documented. We found no public information on conflict resolution per field, near-real-time sync with retry and error logging, or API rate limits, which are exactly the details that decide whether two systems stay in agreement. 3 11 12
The Sales Ops Manager
Bi-directional sync covers Salesforce, HubSpot and Pipedrive, with the Salesforce side modelling lead, contact, account, opportunity, campaign, task and custom objects, sync-all or filtered selective modes, activity-level updates, and journeys tracking entry and exit by the Salesforce object ID. That is a real join, but we found no public information on field mapping, configurable conflict resolution per field, duplicate handling beyond a create-or-update action, sync retries, an error log, or documented API rate limits — exactly the layer I need before a pipeline report can be trusted. 3 11 12
The Data Protection Officer
Bi-directional Salesforce sync into the customer data platform is documented with selective filters, account and custom objects modelled, and create, update and campaign actions; HubSpot CRM and Pipedrive sync is also named. We found no public information on field-level conflict resolution, duplicate handling, retry and error logging for failed syncs, or documented API rate limits. 3 11 12
The Lifecycle Marketer
Two-way sync with Salesforce — alongside bi-directional integrations named for HubSpot CRM and Pipedrive — covers lead, contact, account, opportunity, campaign, task and custom objects, with selective filtered sync, create-or-update actions and developer docs. We found no public information on field-level conflict resolution, duplicate handling, retry and error logs, or documented rate limits, and one captured page notes journey entry and exit tracked on the Salesforce object ID rather than the person, which is worth knowing before you build on it. 3 11 12
The Solution Architect
Bidirectional sync with Salesforce, HubSpot CRM and Pipedrive, with lead, contact, account, opportunity, campaign, task and custom objects all modelled, selective sync with filters, record create/update actions, and journeys keyed to the Salesforce object ID rather than the person — custom objects reachable without vendor services is exactly what I look for. We found no public information on field mapping, duplicate handling, per-field conflict resolution, sync retry with an error log, or documented API rate limits, and no documented path from anonymous visitor to known contact, which is the join that decides the implementation. 3 11 12
The Skeptic
Bi-directional sync with Salesforce, HubSpot and Pipedrive is documented down to lead, contact, account, opportunity, campaign, task and custom objects, with selective sync filters and journey entry and exit tracked by Salesforce object ID. We found no public information on field mapping, duplicate handling, conflict resolution between systems, retry and error logs, or documented API rate limits. 3 11 12
European sovereignty
panel opinion
Show reasoningHide reasoning
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. Dimensions the sources do not establish are unknown, not non-EU.
0 — Proven non-EU: a non-EU vendor and contracting entity with hosting and tracking stated outside the EU.
3 — One European element proven — an EU contracting entity or EU data residency stated — with the rest of the chain undocumented.
5 — An EU contracting entity and EU hosting both stated, and a data processing agreement offered.
8 — EU hosting on named infrastructure, EU contracting entity, a subprocessor list published with locations, and any non-EU processing (tracking, AI scoring, support access) 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.
The Demand Gen Lead
The EU is named among the multi-region hosting options and the trust centre publishes a subprocessor list, which is one European element. The rest of the chain is dark: we found no public information establishing the contracting entity's jurisdiction, ownership, or subprocessor locations, and the residency attribute itself carries the caveat that it was not confirmed on the vendor's own pages — a thin basis for a platform profiling named EU residents. 1 2 9
The Sales Ops Manager
Multi-region hosting including an EU option is stated on the vendor's own pages (EU, USA and Australia, with one capture also listing Asia), which proves one European element; the contracting entity's jurisdiction, ownership and subprocessor locations are not established in the captures, and the site carries a Data Privacy Framework listing, which is a US transfer mechanism. For behavioural profiles of named EU residents tracked open-by-open, that is not enough of the chain for me to sign off, but it is not proven non-EU either. 1 2 12
The Data Protection Officer
The captured pages state multi-region hosting in EU, USA and Australia, with one page adding Asia, and a Trust Centre lists sub-processors among its contents. The contracting entity's jurisdiction, ownership and subprocessor locations are unknown, and we found no public information on a data processing agreement offered to customers, so only one European element is proven with the rest of the chain undocumented — which, given the platform profiles named people, I weigh heavily. 1 2 9
The Lifecycle Marketer
Multi-region hosting including the EU is stated and participation in the Data Privacy Framework is published, so one European element is proven while the rest of the chain stays dark. Given the depth of profiling this product does — every open, click and session — the silence on contracting-entity jurisdiction, subprocessor locations and where a given customer's profiles are processed weighs heavily; the hosting regions also include the USA, Australia and Asia. 1 2 12
The Solution Architect
The vendor's own pages state multi-region data hosting including the EU (the captured pages give slightly different region lists, one adding Asia), and a trust centre lists sub-processors alongside certifications — one European element proven, the rest of the chain undocumented. The contracting entity's jurisdiction, ownership and subprocessor locations are not established by the captured pages, and the site advertises Data Privacy Framework participation, which signals a US transfer route rather than a sovereign chain. Given behavioural profiles of named people, that is enough to know EU hosting exists and not enough to know who processes them. 1 2 9 12
The Skeptic
Multi-region hosting spanning EU, USA, Australia and Asia is stated, so one European element exists, and a trust centre mentions sub-processors. But the contracting entity's jurisdiction, ownership and subprocessor locations are all unknown to us, and the vendor is listed under the Data Privacy Framework, so for a buyer weighing profiling heavily the chain is unproven beyond the EU hosting option. 1 2 9 12
Pricing transparency
Show reasoningHide reasoning
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.
3 — A public "from" price or a single tier with its contact limit.
5 — Prices per tier public with the billing period and contact limits stated, and which tier includes automation visible.
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.
The Demand Gen Lead
The captured pages state a 14-day free trial and nothing else about money — we found no public information on tier prices, contact or send limits, the tier where automation begins, overage, or onboarding costs. I cannot compute an annual invoice from public pages, so every real number is a sales conversation. 4 8
The Sales Ops Manager
The captured pages show only a 14-day free trial; we found no public prices, tier contact limits, billing periods, overage rates, or which tier automation starts on. I could not begin to compute an annual invoice from these pages. 4 8 12
The Data Protection Officer
The only public pricing information found across the captured pages is a free trial of fourteen days; no tier prices, contact or send limits, or the tier where automation begins appear anywhere. A buyer cannot compute an annual invoice from these pages alone. 1 4 8
The Lifecycle Marketer
The only public pricing information captured is a free trial, specified at fourteen days; we found no public information on tier prices, contact limits, the tier where automation begins, overage, onboarding or term. A buyer cannot begin to compute the annual invoice for their contact base from these pages. 4 8
The Solution Architect
The captured pages show a free trial and a 14-day SaaS trial, and nothing else on cost. We found no public information on tier prices, billing periods, contact limits, overage rates, or which tier automation begins at, so a buyer cannot compute an annual invoice from these pages. 4 8
European sovereignty — proven facts
0 of 6 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 | — | uncited Report an error |
|---|---|---|---|
| Hosting location |
Not determined
unverified
Why unverified?The page lists hosting regions in marketing copy without stating which region is the default or where the EU hosting is located. |
— | uncited Report an error |
| Hosting options |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Ortto
Is Ortto European?
Not determined: the vendor’s pages as captured do not say where Ortto is based.
Where does Ortto store data?
The default storage location for customer data is not stated on the vendor’s pages as of 26 Oct 2026. The vendor’s pages mention the EU, the United States, Australia and Asia as hosting locations, per the vendor’s page captured 26 Oct 2026.
Does Ortto have a free plan?
Not stated on the vendor’s pages as of 26 Oct 2026.
What are the best alternatives to Ortto?
As of 18 Nov 2026, the panel rates Braze (3/5), HubSpot Marketing Hub (3/5) and ActiveCampaign (Automation) (3/5) highest among the other 20 Marketing Automation products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Brevo (Automation) (EU-Made, France). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Ortto alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 26 Oct 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Hosting location. The page lists hosting regions in marketing copy without stating which region is the default or where the EU hosting is located.
- Weak sourcing — Hosting options. 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.
- 18 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
- 2 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
- 1 legal fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 pricing fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is 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 (12)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.ortto.com Checked 26 Oct 2026 Details →
- 2 Privacy policy — found from the homepage ortto.com Checked 26 Oct 2026 Details →
- 3 Journeys & orchestration — found from sitemap ortto.com Checked 26 Oct 2026 Details →
- 4 Journeys & orchestration — found from sitemap ortto.com Checked 26 Oct 2026 Details →
- 5 Lead scoring, routing & lifecycle — found from sitemap ortto.com Checked 26 Oct 2026 Details →
- 6 Lead scoring, routing & lifecycle — found from sitemap ortto.com Checked 26 Oct 2026 Details →
- 7 Channels & personalisation — found from sitemap ortto.com Checked 26 Oct 2026 Details →
- 8 Channels & personalisation — found from sitemap ortto.com Checked 26 Oct 2026 Details →
- 9 Consent, tracking & profiling — found from sitemap ortto.com Checked 26 Oct 2026 Details →
- 10 Consent, tracking & profiling — found from sitemap ortto.com Checked 26 Oct 2026 Details →
- 11 CRM integration & data model — found from sitemap ortto.com Checked 26 Oct 2026 Details →
- 12 CRM integration & data model — found from sitemap ortto.com Checked 26 Oct 2026 Details →