SALESmanago
Provenance unknown Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by SALESmanago Marketing Cloud Sp. z o.o. · www.salesmanago.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.
SALESmanago at a glance
- Vendor
- SALESmanago Marketing Cloud Sp. z o.o.
- Headquarters
- Not stated on the vendor’s pages as of 1 Oct 2026
- Data hosting
- In the EU by default source, captured 30 Sep 2026
- Free plan
- Not stated on the vendor’s pages as of 1 Oct 2026
- Panel verdict
- The AI panel rates SALESmanago 2.5/5, the mean of 6 judges. Manago AI — the new name for SALESmanago — is an e-commerce-oriented customer engagement platform. how scores are made
- As of
- Vendor pages captured 22 Sep 2026 to 1 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
Manago AI — the new name for SALESmanago — is an e-commerce-oriented customer engagement platform. Channel coverage is the strongest area at a flat 7: email, SMS, WhatsApp, push and web engagement run as one connected journey from a unified customer profile, triggered by cart views, wishlists, price-drop alerts and SMS keyword replies. Journey orchestration scores a level 4: we found no public information on branching, waits, goals, frequency capping or what happens when a contact qualifies for several journeys. Lead management is the weakest capability area at 0-3, three judges recording no rating for want of public information on scoring, stages or handover to sales. Consent and profiling spans 5-7, documented consent records weighed against ten-year analytics cookies. Sovereignty spans 3-4, the skeptic's 3 resting on the 'directly related to your business' exception to the GDPR page's stated rule of no transfers outside the EEA; the same page places the data centres in Poland, within the EEA. Beyond a free trial, we found no public information on tier prices, contact limits or where automation begins.
Speaks for it
- Channel coverage scores a flat 7, with email, SMS, WhatsApp, push and web engagement run as one connected journey from a unified profile
- Consent is kept as evidence — wording, date obtained and a history of changes per contact, with opt-in/opt-out changeable on the contact card
- The vendor states fully automated decisions with consequences for people are not made by default, with Article 22 GDPR addressed
- The GDPR page states data centres in Poland within the EEA and lists ISO certifications for the data centre
- Ready-made connectors for Shopify, Magento 2, PrestaShop and WooCommerce, an API with MCP, and structured import and export
Held against it
- Lead management scores 0-3, and we found no public information on lead scoring, lifecycle stages or routing to sales owners
- We found no public information on journey branching, waits, goals, frequency capping or what happens when a contact qualifies for several journeys
- No connector to a named CRM is documented, nor field mapping, duplicate handling or what happens when systems disagree about a person
- The stated rule of no transfers outside the EEA carries the exception 'unless it is directly related to your business', and we found no public information on the contracting entity's jurisdiction, ownership or subprocessor locations
- The published cookie list shows analytics cookies with ten-year lifetimes and cookies that do not expire, and we found no public information on erasure covering derived scores
Best for
- You sell on Shopify, Magento, PrestaShop or WooCommerce and want journeys triggered by carts, wishlists and price drops
- You market to known customers across email, SMS, WhatsApp, push and web from one profile, with Meta audience sync
- You need consent recorded with wording, date and change history, plus structured export, for GDPR accountability
- Your legal review values an explicit default that no fully automated decisions with consequences for people are made
Avoid if
- You need scored, staged leads handed to sales owners — the pages document commerce automation for known customers, not lead handling
- Your implementation depends on two-way sync with a named CRM, with documented field mapping and duplicate handling
- You must see a subprocessor list with locations and the contracting entity's jurisdiction before signing, not only EU hosting
- You need published tiers and limits to budget before a sales conversation
The scores
| Criterion | Panel median |
|---|---|
| Journeys & orchestration | 2 of 5 |
| Lead scoring, routing & lifecycle | 1 of 5 |
| Channels & personalisation | 3.5 of 5 |
| Consent, tracking & profiling | 3 of 5 |
| CRM integration & data model | 2 of 5 |
| European sovereignty | 2 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
Journeys are genuinely behaviour-driven — cart follow-ups, back-in-stock and price-drop triggers, keyword replies that lead into an email, a push or suppression, coordinated across email, SMS, WhatsApp, push and web. We found no public information on branching logic, waits, goals, frequency capping or what happens when a contact qualifies for several journeys at once, so I cannot place this above mid-table. 1 3 5
The Sales Ops Manager
Journeys are documented as one connected flow across email, SMS, WhatsApp, push and web, with behaviour-based entry points — a keyword reply firing a push or suppressing a follow-up, cart views and price-drop alerts starting action — and an AI assistant that builds the workflow. We found no public information on branching, waits, goals or exit conditions, and none on what happens when one contact qualifies for several journeys at once. 1 3 4
The Data Protection Officer
The captured pages market one connected journey across email, SMS, WhatsApp, push and web, with workflows built in the platform and behavioural entry points such as cart views, price-drop alerts and SMS keyword replies that can trigger an email, a push, a segment application or follow-up suppression. We found no public information on branching and waits, goals or exit conditions, frequency capping, priority when a contact qualifies for several journeys, or safe editing of a live journey. 1 3
The Lifecycle Marketer
Journeys are real and behaviour-driven: cart views, wishlists, back-in-stock and price-drop events act as triggers, keyword replies can branch into email, push, a segment or suppression of the next send, and one connected journey is documented across email, SMS, WhatsApp, push and web. What I cannot see are the mechanics a programme needs — we found no public information on waits, goals or exit conditions, frequency capping across journeys, or what happens when a contact qualifies for several at once. 1 3
The Solution Architect
Connected journeys across email, SMS, WhatsApp, push and web are documented, with behavioural entry from carts, wishlists, price-drop alerts and keyword replies that trigger cross-channel actions or suppress a follow-up — more than linear autoresponders. The captured pages do not document branching, waits, goals or safe editing of a live journey. Nor is there any statement on frequency capping or what happens when a contact qualifies for several journeys at once. 1 3 5
The Skeptic
Journeys are real and cross-channel — behavioural triggers from views, carts, wishlists and price-drop alerts, plus SMS keyword replies that start an email, a push, a segment or a suppression, are all documented. But none of the captures shows branching, waits, goals, or what happens when one contact qualifies for several journeys at once, and the Agentic AI module offers to build the workflow without showing what a workflow can contain. That sits between a triggered sequence and a documented builder. 1 3 5
Lead scoring, routing & lifecycle
n/r
n/r
n/r
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 not rated — no public information
We found no public information on lead scoring, qualification or handover to sales. The closest items on the pages I read are purchase predictions and AI-driven segmentation, which are marketing models, not a score with routing that a sales team can trust. 1 5 7
The Sales Ops Manager
The customer data platform lists purchase predictions and AI-driven segmentation — a score derived from behaviour — but we found no public information on lifecycle or pipeline stages, qualification criteria, routing to owners or handover to sales, and nothing on score history per contact. 7
The Data Protection Officer
The customer data platform offers purchase predictions and AI-driven segmentation on a unified profile, which touches scoring, and the vendor states that fully automated decisions are not made by default. We found no public information on lead scoring configuration, lifecycle stages, routing to sales owners or how a prediction is computed — nothing that would let a data protection officer assess the predictions as automated decision-making. 2 3 7
The Lifecycle Marketer not rated — no public information
We found no public information on lead scoring, qualification stages, routing to owners, follow-up SLAs or score history. The captured pages describe a customer data platform and commerce automation aimed at known customers, not lead handling or handover to sales. 1 5 7
The Solution Architect
The customer data platform page documents purchase predictions and AI-driven segmentation, the only scoring-adjacent evidence in the captured pages. We found no public information on lead scoring models, lifecycle stages, qualification or handover to sales. 5 7
The Skeptic not rated — no public information
We found no public information on lead scoring, qualification, lifecycle stages or handover to sales. The capability lists name a Customer Data Platform, marketing automation, personalisation and recommendations, and the customer-data-platform page lists purchase predictions and AI-driven segmentation — none of which documents how a lead is scored, staged, routed or explained to anyone. 5 7
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, WhatsApp, web push and on-site journeys all hang off one unified profile, with ad-audience sync to Meta and personalisation built on what customers actually do rather than only stored fields. We found no public information on cross-channel frequency capping, and unsubscribe handling is shown per channel — web push positioned as the consented channel after an email opt-out — rather than shared. 1 3 4 6 7
The Sales Ops Manager
Email, SMS with a built-in gateway, WhatsApp, web push and on-site engagement are all documented from one platform, with a unified customer profile, Meta custom-audience sync in the catalogue, and email content explicitly built on what customers do rather than who they are. We found no public information on cross-channel frequency capping or shared unsubscribe handling; the web push page instead presents push as a separate consented channel after an email opt-out. 1 3 4 6 7
The Data Protection Officer
Email, SMS, WhatsApp, web push and on-site engagement are documented as channels driven from one unified customer profile, with personalisation built on behaviour rather than stored fields and an audience sync to the Meta network. Web push is explicitly shown as a separately consented channel that continues the journey after an email opt-out. We found no public information on cross-channel frequency capping or ad-audience sync to networks beyond Meta. 1 4 6 7
The Lifecycle Marketer
Email, SMS with a built-in gateway, WhatsApp, web push and on-site engagement all hang off one unified customer profile, with Facebook Custom Audience sync and content built on behaviour such as carts and price drops rather than stored fields alone. I hold it below the top band because we found no public information on cross-channel frequency capping or a suppression list shared across every channel. 1 4 6 7
The Solution Architect
Email, a built-in SMS gateway with two-way conversations, WhatsApp, web and mobile push, on-site engagement and Facebook Custom Audience sync are all documented, with personalisation explicitly built on behaviour rather than stored fields. Unsubscribe is documented per channel rather than as one shared suppression list, and we found no public information on cross-channel frequency capping. 1 3 4 6
The Skeptic
Email, SMS, WhatsApp, web push and on-site engagement run off one unified customer profile, personalisation is explicitly behavioural, and Facebook Custom Audience sync is listed. The system knows a contact has opted out of email and offers web push as a consented alternative — that is shared consent awareness — but I found no public information on cross-channel frequency capping, and SMS or WhatsApp unsubscribe handling is not described. 1 3 4 5 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
Consent is recorded with its content, the date obtained and a history of changes on the contact card, access and rectification are handled from the platform, and the vendor states that fully automated decisions are not made by default with Article 22 GDPR addressed — that last part is rare and I credit it. We found no public information on a per-contact tracking switch or cookieless mode, and retention is asserted as established rather than stated per data category. 2 5
The Sales Ops Manager
Consent content, the date obtained and the change history are recorded per contact with opt-in/opt-out on the contact card, separate per-channel consent is visible in the cookie documentation, and access, rectification and Article 22 automated decisions off by default are all documented. We found no public information on double opt-in, cookieless or limited tracking, per-person profiling suppression, or erasure covering derived scores — while tracking cookies with ten-year lifetimes are listed. 2 4 5
The Data Protection Officer
Consent content, the date obtained and a history of consent changes are recorded per contact, opt-in and opt-out status is changeable on the contact card, access is served through export in a machine-readable format, and the vendor states retention periods are established and fully automated decisions are not made by default. Against that, the published cookie list shows analytics cookies with ten-year lifetimes and one that does not expire, and we found no public information on switching tracking off per contact, suppressing profiling per person, or erasure that covers derived scores. 2 4 5
The Lifecycle Marketer
Consent is treated as evidence: the platform records the wording, the date obtained and a history of consent changes on the contact card, cookies are published with their lifetimes, and the vendor states that fully automated decisions with consequences for people are not made by default, in terms an automated-decisioning assessment can work with. What keeps me from going higher is that we found no public information on switching tracking off per person or on erasure reaching derived scores. 2 5
The Solution Architect
The platform records the content, date and change history of each consent, opt-out is handled per channel, fully automated decisions are off by default with Article 22 addressed, and export and rectification are documented. Against that, several analytics cookies run for ten years, and we found no public information on double opt-in, a per-contact tracking switch or cookieless mode, or erasure covering derived scores. 2 4 5
The Skeptic
Consent content, date and a history of consent changes are recorded per contact, opt-in status is changeable on the contact card, and the security page states that by default no fully automated decisions with consequences for data subjects are made — the clearest Article 22 statement I have read on a vendor page. Access, rectification and structured export are documented and retention periods are said to be established. But no retention number is shown while behavioural cookies run for ten years and one never expires, and I found no public information on per-contact tracking limits or erasure covering derived scores. 2 4 5
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
The integration story is e-commerce-first — Shopify, Magento, PrestaShop, WooCommerce — plus an API and MCP for custom flows, and a stated customer data platform that syncs data from different systems into one profile updated as customers browse and buy. We found no public information on a named CRM two-way sync, field mapping, duplicate handling or conflict resolution, and that join is exactly what makes or breaks an implementation. 1 2 6 7
The Sales Ops Manager
An API with MCP support, structured import and export, ready-made e-commerce connectors (Shopify, Magento, WooCommerce, PrestaShop) and a stated sync of customer data from different systems into one profile give me a data path in. But we found no public information on a connector to a named CRM, field mapping, duplicate handling, configurable conflict rules or a sync error log — the mechanics that decide whether my pipeline report is true. 1 2 6 7
The Data Protection Officer
A documented API with MCP support and connectors to Magento, PrestaShop, Shopify and WooCommerce feed a unified customer profile that updates automatically as customers browse and buy, and import and export in a structured machine-readable format is stated. We found no public information on a connector to a named CRM, field mapping, duplicate handling, or what happens when the marketing platform and the CRM disagree about a person. 1 2 6 7
The Lifecycle Marketer
Import and export in a structured format, an API with MCP alongside it, and connectors to Shopify, Magento, PrestaShop and WooCommerce feeding a profile that updates automatically as customers browse and buy. We found no public information on two-way sync with a major CRM, field mapping, duplicate handling or what happens when the two systems disagree about a person. 1 2 7
The Solution Architect
APIs, custom data flows, MCP and ready-made e-commerce connectors for Magento 2, PrestaShop, Shopify and WooCommerce are documented, the customer data platform page promises all customer data synced into one profile updated as customers browse and buy, and the anonymous-visitor cookie links to the contact card only inside the platform. But the captured pages name no CRM, and we found no public information on field mapping, duplicate and conflict handling, custom objects or API rate limits — the details that decide an implementation. 1 2 5 6 7
The Skeptic
APIs, MCP and ready-made integrations are offered with named connectors for Shopify, Magento, PrestaShop and WooCommerce, and the customer-data-platform page says data from different systems syncs into one profile automatically. No CRM is named among the connectors, and I found no public information on field mapping, duplicate handling or what happens when the systems disagree about a person. Structured import and export is documented, which keeps this above a pure connector story. 1 2 6 7
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 captured privacy page states data centers in Poland within the EEA and a rule of no transfers outside the EEA, backed by GDPR compliance language and ISO 27001/27017/27018 certifications for the data center. The contracting entity's jurisdiction and the subprocessor chain are not established on the captured pages, and for a platform profiling named shoppers I want that chain proven rather than implied. 2 1
The Sales Ops Manager
Data centres in Poland within the EEA, a stated default of no transfers outside the EEA, GDPR-based compliance and ISO-certified infrastructure are documented — though the no-transfer rule carries a business-related exception. The contracting entity's jurisdiction, ownership and subprocessors are unestablished by what was captured, and we found no public information on a subprocessor list with locations. 2
The Data Protection Officer
The vendor's GDPR page states data centres in Poland within the European Economic Area, that as a rule no third-party providers are used and entrusted data is not transferred outside the EEA, and lists ISO certifications for the data centre. The contracting entity's jurisdiction, ownership and subprocessor locations are not established on the captured pages, so the chain beyond EU hosting remains undocumented — which matters here, since behavioural profiles of named people are the product. 2
The Lifecycle Marketer
Data centres are stated to sit in Poland within the EEA, third-party use and transfers outside the EEA are stated only where directly related to the customer's business, and the operation is described under GDPR with ISO 27018 and 27017 certifications. The rest of the chain is dark to me: we found no public information on the contracting entity's jurisdiction, a data processing agreement, or subprocessor locations, and with profiling of named people this matters heavily. 2
The Solution Architect
The GDPR page states that data centers are located in Poland within the EEA and that, as a rule, entrusted data is not transferred outside the EEA — EU hosting is proven. Contracting entity jurisdiction, a published subprocessor list with locations and a processing agreement are not established on the captured pages, so the rest of the chain remains undocumented. 2
The Skeptic
EU data residency is stated — data centres in Poland, within the EEA — alongside GDPR compliance and ISO certifications, but the no-transfer rule carries the carve-out "unless it is directly related to your business", which is exactly the loophole I read for. The contracting entity's jurisdiction and subprocessor exposure are not established on the captured pages, so only one link of the chain is proven. For a buyer weighing profiling heavily, this is a stated promise, not an evidenced chain. 2
Pricing transparency
not rated — the vendor publishes no price
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 only pricing-related item on the captured pages is a free trial offer; we found no public information on tiers, contact or volume limits, overage, or where automation actually begins. I cannot forecast pipeline spend for a quarter on the words free trial. 5
The Sales Ops Manager
The only pricing-related fact captured is a free trial; we found no public information on tier prices, contact limits, billing periods, where automation begins, or onboarding costs, so no annual invoice can be computed from the captured pages. 5
The Data Protection Officer
The captured pages list a free trial, and we found no public information on tier prices, billing periods, contact limits, overage rates, onboarding costs or which tier includes automation. A buyer cannot compute an annual invoice from these pages. 5
The Lifecycle Marketer
The only pricing-related item on the captured pages is a 'Free Trial' mention; we found no public information on tier prices, contact or send-volume limits, the tier where automation begins, overage rates, onboarding costs or minimum term. A buyer cannot estimate an annual invoice from these pages. 5
The Solution Architect
The only commercial terms on the captured pages are a free trial and web push with unlimited notifications at no extra cost per message. We found no public prices — no tiers, contact limits, billing periods or the tier where automation begins — so an annual invoice cannot be computed from public pages alone. 4 5
The Skeptic
The only pricing signal on any page I read is a free trial; the captured pages show no tier price, contact limit, send-volume limit, overage rate, onboarding fee or term. A buyer cannot even find which tier automation begins at, let alone compute an annual invoice for a given contact base. The real cost looks like a conversation with sales, and nothing on these pages suggests otherwise. 5
European sovereignty — proven facts
1 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 |
EU by default
unverified
Why unverified?"As a rule" and the explicit carve-out for customers headquartered outside the EEA mean some customer data may leave the EEA; no subprocessor list or other pages are available to verify. |
2/4 pts | 2 Report an error |
| Hosting options | Not determined | — | 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 SALESmanago
Is SALESmanago European?
Not determined: the vendor’s pages as captured do not say where SALESmanago is based.
Where does SALESmanago store data?
SALESmanago stores customer data in the EU by default, though not exclusively, per the vendor’s page captured 30 Sep 2026.
Does SALESmanago have a free plan?
Not stated on the vendor’s pages as of 1 Oct 2026.
What are the best alternatives to SALESmanago?
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: SALESmanago alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 22 Sep 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. "As a rule" and the explicit carve-out for customers headquartered outside the EEA mean some customer data may leave the EEA; no subprocessor list or other pages are available to verify.
- 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 (salesmanago.com, manago.ai/gdpr, manago.ai/sms, manago.ai/web-push, manago.ai/cookies, manago.ai/integrations and 1 more). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
- 39 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
- 13 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
- 5 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
- 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
- 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 (7)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.salesmanago.com Checked 22 Sep 2026 Details →
- 2 Security / trust page — found from the homepage manago.ai Checked 30 Sep 2026 Details →
- 3 Channels & personalisation — found from sitemap manago.ai Checked 1 Oct 2026 Details →
- 4 Channels & personalisation — found from sitemap manago.ai Checked 1 Oct 2026 Details →
- 5 Consent, tracking & profiling — found from sitemap manago.ai Checked 1 Oct 2026 Details →
- 6 CRM integration & data model — found from sitemap manago.ai Checked 1 Oct 2026 Details →
- 7 CRM integration & data model — found from sitemap manago.ai Checked 1 Oct 2026 Details →