Marketing Automation
Insider
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Insider (useinsider.com) · useinsider.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.
Insider at a glance
- Vendor
- Insider (useinsider.com)
- Headquarters
- Not stated on the vendor’s pages as of 20 Oct 2026
- Data hosting
- Not stated on the vendor’s pages as of 20 Oct 2026
- Free plan
- Not stated on the vendor’s pages as of 20 Oct 2026
- Panel verdict
- The AI panel rates Insider 2/5, the mean of 6 judges. Insider One's public evidence is strongest on channels and thinnest on buying information. how scores are made
- As of
- Vendor pages captured 20 Oct 2026; evaluated by the panel 21 Oct 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Insider One's public evidence is strongest on channels and thinnest on buying information. Channel coverage scored a flat 8: 12+ native channels — web, email, SMS and RCS, WhatsApp, push, app — run from one unified profile, with ad-audience export to the major networks. Pricing transparency scored a flat 1: no prices, tiers, contact or send limits, or billing period appear, and the only cost statement is "no integration fees, no friction" with a five-day go-live. Journey orchestration sits at 6-7: the Architect drag-and-drop builder and whole-journey A/B testing are evidenced, but we found no public information on what happens when several journeys claim one person. Lead management scored 2-3, the only scoring thresholds on the pages belonging to a practitioner's email list rather than the product. Consent and profiling scored 3-4, with tracking described as automatic from setup. Sovereignty spread widest, 2 to 4, on the weight to give the vendor's statement that all collected data is stored at an AWS centre in Dublin, Ireland, while the independently sourced review records residency and subprocessors as unconfirmed.
Speaks for it
- 12+ native channels — web, email, SMS and RCS, WhatsApp, push, app — run from a single unified profile.
- Ad-audience export to Google, Facebook and TikTok, with dynamic content based on what a person last consumed, bought or abandoned.
- Architect provides a zero-code drag-and-drop builder for multi-branch journeys with A/B testing of entire flows and journey analytics.
- A 'Living Profile' is described as updating in milliseconds from CDP, CRM and offline systems.
- Eighteen named CRM connectors plus a flexible API, webhooks and warehouse destinations such as BigQuery and Snowflake.
Held against it
- No prices appear on any captured page — no tiers, contact or send limits, billing period or VAT treatment — and serious interest routes to a personalised demo behind an email form.
- The only lead-scoring thresholds on the pages belong to a practitioner's email list, and we found no public information on configurable scoring with decay, routing to owners or per-contact score history.
- The independently sourced review records data residency, the contracting entity and subprocessor exposure as unconfirmed, while the vendor page states all collected data is stored at an AWS centre in Dublin, Ireland.
- Behavioural tracking is described as automatic from setup with profiles created for anonymous visitors, and we found no public information on a stored consent record with its source or per-channel consent states.
- The integration pages describe the connected products rather than the sync mechanics: we found no public information on sync direction, field mapping, conflict or deduplication rules.
Best for
- You need 12+ channels — web, email, SMS and RCS, WhatsApp, push, app — orchestrated from one unified profile.
- You want AI-driven next-best-channel and next-best-action selection built on a real-time unified profile.
- You want a zero-code drag-and-drop journey builder with A/B testing of entire flows and real-time journey analytics.
- You are a midsize or enterprise brand running lifecycle campaigns on predictive segments such as likelihood to purchase or discount affinity.
Avoid if
- You need public pricing, tiers or send limits to build a business case before engaging sales.
- Your pipeline depends on documented lead scoring with decay, routing to owners and handover SLAs — the only thresholds shown are a practitioner's own email-list points.
- Your procurement must confirm data residency, the contracting entity and subprocessors before shortlisting — the independently sourced review records these as unconfirmed.
- Your consent model requires profiling to begin only after consent — tracking is described as automatic from setup, with profiles created for anonymous visitors.
The scores
| Criterion | Panel median |
|---|---|
| Journeys & orchestration | 3 of 5 |
| Lead scoring, routing & lifecycle | 1.5 of 5 |
| Channels & personalisation | 4 of 5 |
| Consent, tracking & profiling | 2 of 5 |
| CRM integration & data model | 2 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, 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.
The Demand Gen Lead
Architect is a real orchestration product — visual multi-branch journeys fed by a real-time profile synthesised from CRM, CDP and offline systems, whole-journey A/B testing with path and funnel analytics, and message-level frequency caps. What I could not find is the operational spine: no public information on where a contact currently sits in a journey, suppression across journeys, versioning of a live journey, or priority resolution when several journeys want the same person. 3 4 6 8
The Sales Ops Manager
The Architect journey builder is real and public: drag-and-drop multi-branch journeys, journey analytics with clicks, conversions and revenue, and A/B testing of whole flows, plus frequency caps and a claimed centralised decisioning engine with Next Best Action. What I could not find is anything on per-contact journey state, versioning of a live journey, or what happens when a contact qualifies for several journeys at once — the parts that decide whether this survives a real programme. 3 4 6 8
The Data Protection Officer
Architect is evidenced as a zero-code drag-and-drop builder for multi-branch journeys, with A/B testing of entire flows, journey analytics, and frequency caps, fed by a profile that updates from CRM and offline systems in milliseconds and positioned as a centralized decisioning engine. We found no public information on versioning of a live journey, on priority when several journeys claim the same person, or on seeing where a specific contact currently sits — the collision behaviour and per-person visibility I would need to audit what was decided about someone. 3 4 6 8
The Lifecycle Marketer
Architect is a real decision layer: multi-branch journeys in a zero-code builder, a Living Profile refreshed in milliseconds from CDP, CRM and offline systems, A/B testing of entire journey flows, and next best action picked across thousands of variables. I found no public information on versioning of a live journey, per-contact journey state, priority when several journeys want the same person, or holdout groups for measurement, and the frequency caps that are documented appear on the web push page rather than programme-wide. 3 4 6 8
The Solution Architect
Architect is documented as a zero-code, drag-and-drop builder for multi-branch journeys drawing on a real-time profile fed from CDP, CRM and offline systems, with journey-level A/B testing, real-time journey analytics, and message frequency caps. We found no public information on waits and goals, entry and exit conditions, per-contact journey state, versioning of a live journey, or priority handling when a contact qualifies for several journeys — the collision behaviour is what decides whether this survives contact with reality. 3 4 6 8
The Skeptic
A drag-and-drop builder with multi-branch journeys, event triggers like price-drop and back-in-stock, frequency caps and A/B testing of entire journey flows — the middle of the ladder is genuinely evidenced. But we found no public information on waits, entry and exit conditions, where a contact currently sits, versioning a live journey, or priority when a person qualifies for several journeys; the collision handling that decides whether this survives production is not shown on any public page. 3 4 8
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 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.
The Demand Gen Lead
The only lead-scoring detail on the captured pages is a practitioner's own point thresholds in a tips article, which says nothing about the product's scoring; what the product does evidence is propensity scores — likelihood to purchase, likelihood to engage on a channel, discount affinity — used to build segments. I found no public information on configurable scoring with decay, lifecycle stages, routing to owners, or handover with an SLA, and nothing a sales team could audit per record. 5 6 12
The Sales Ops Manager
The only lead-scoring content on the site is a guest practitioner's own email-list point thresholds, which tells me nothing about the product, and beyond that I found no public information on scoring configuration, decay, lifecycle stages, or routing and handover to sales owners. Lifecycle campaign patterns like dormant-winback and onboarding recovery and predictive segments such as likelihood to purchase exist, so this is more than nothing — but the handover to my CRM owners is unevidenced end to end. 2 5 6 12
The Data Protection Officer
The only lead-scoring figures on the pages come from a practitioner's tips post about point cutoffs on an email list, not from the platform; the product evidence is predictive segments such as likelihood to purchase, likelihood to engage on a channel, and discount affinity. We found no public information on configurable scoring with decay, lifecycle stages, routing to owners or teams, or per-contact score history. And where AI assigns purchase and churn likelihood to individuals, we found no documentation anywhere near what an Article 22 assessment would require — that absence decides this score for me. 5 6 12
The Lifecycle Marketer
The only scoring thresholds in evidence come from a guest presenter describing his own email list, not a documented product capability. The platform offers lifecycle-flavoured segments — dormant winback, onboarding drop-off recovery — and predictive likelihood attributes, but I found no public information on configurable scoring with decay, lifecycle stage models, routing to owners, or per-contact score history. 2 5 6 12
The Solution Architect
The only scoring model on the captured pages is a practitioner's own email-list point thresholds, not a platform capability; what the platform itself evidences is predictive targeting — likelihood to purchase, churn and channel engagement — used for segmentation. We found no public information on configurable scoring with decay, lifecycle stages, routing to owners or teams, score history per record, or handover to sales with an SLA. Propensity scores applied to individuals without documented explainability are precisely what a DPO will ask to assess. 5 6 12
The Skeptic
The site's lead-scoring page recounts a practitioner's own email-list practice — 60 points makes a VIP, 100 makes a Very Hot Lead — rather than a platform capability, with no decay, routing or qualification model anywhere in evidence. Lifecycle segmentation is real, with prebuilt segments, lifecycle templates and predicted propensity attributes. We found no public information on routing to sales owners, follow-up SLAs or score history per contact. 2 5 6
Channels & personalisation
Show reasoningHide reasoning
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.
The Demand Gen Lead
This is the strongest area: twelve-plus native channels off one unified profile, on-site personalisation down to banners and product recommendations, segment export to the major ad networks, dynamic content driven by what a person last consumed or abandoned, frequency caps, and an AI next-best-channel call. The gap to the top is consent: I found no public information confirming one consent state shared across every channel. 4 6 8 11 12
The Sales Ops Manager
Twelve-plus native channels driven from one platform, on-site personalisation of banners and recommendations, segment export to Google, Facebook and TikTok ads, dynamic web-push content based on last consumed, bought or abandoned, frequency caps, and an AI Next Best Channel prediction — that covers the full range and touches the top of it. I found no public information on one consent state shared across every channel, which is the piece that would move it further. 3 6 8 11 12
The Data Protection Officer
Twelve-plus native channels are evidenced from one platform — web, email, app, SMS and RCS, WhatsApp, web push, on-site experiences — alongside ad-audience export through the Google, Facebook and TikTok connectors, frequency caps, and dynamic content built on behaviour such as what someone last consumed or abandoned. Next-best-channel prediction is claimed on top of a unified profile. We found no public information on one consent state carried across every channel, which for me is the difference between a channel list and a defensible one. 3 6 8 11 12
The Lifecycle Marketer
Twelve-plus native channels driven from one profile — web, email, SMS and RCS, WhatsApp, push, app and on-site — plus ad-audience export to the major networks and personalisation drawn from automatically tracked behaviour with AI next-best-channel selection, which is exactly how it should work. Cross-channel frequency capping is not documented as such and a single consent state shared across every channel is not evidenced, which is what keeps this below the top. 3 4 6 8 11 12
The Solution Architect
Twelve-plus native channels run from one platform — web, email, SMS and RCS, WhatsApp, app and web push, on-site experiences — on a single unified profile, with segment export to Google, Facebook and TikTok ads, frequency capping, and web push content personalised on what a user last consumed, bought or abandoned. Next Best Channel prediction is explicitly documented. We found no public information showing one consent state shared across every channel, which is what would separate a coordinated programme from a well-equipped sender. 3 6 7 8 11 12
The Skeptic
Twelve-plus native channels from one platform and one 360-degree profile — web, email, SMS and RCS, WhatsApp, push, app — with on-site personalisation, ad-audience export to the major networks, and content that adapts to what a person last consumed, bought or abandoned; that is solid evidence at this level. The step beyond it is asserted only as real-time consent management: we found no public information on shared unsubscribe handling or per-channel consent states, and the frequency caps are described without saying they span channels. 6 7 8 11 12
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 — 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.
The Demand Gen Lead
There is real-time consent management for GDPR and CCPA, opt-out offered from first touch, a first-party profile approach that avoids third-party cookies, a DPA aligned to the current standard contractual clauses, and a stated readiness to erase, transfer or modify on request. What an auditor would ask for, I could not find public information on: a stored consent record with source, per-channel consent states, switching tracking off per contact, retention rules, or suppressing a named person from profiling — while behavioural profiling starts automatically once the platform is set up. 4 6 9 10 12
The Sales Ops Manager
Stated: real-time consent management for GDPR and CCPA, opt-out offered from the beginning, first-party profiles without third-party cookies, readiness to erase, transfer or modify on request, and DPA coverage of consent and data-sharing. I found no public information on double opt-in as a documented default, a stored consent record with its source, per-channel consent states, retention rules for inactive records, or suppressing profiling for an individual person — and the behavioural tracking itself is described as automatic from setup. 4 6 10
The Data Protection Officer
Tracking begins automatically at setup, enriching profiles in real time, anonymous visitors are profiled by default, and only an opt-out from the beginning is offered alongside a general claim of real-time consent management for GDPR and CCPA; first-party profiles without third-party cookies and stated readiness to erase, transfer or modify personal data are the strongest documented points. We found no public information on double opt-in, a stored consent record with its source and wording, per-channel consent states, switching tracking off for an individual, suppressing profiling per person, retention for inactive records, or erasure that reaches derived scores. For a system whose AI scores purchase likelihood per individual, the absence of anything supporting an Article 22 assessment is the deciding fact. 4 6 10 12
The Lifecycle Marketer
Real-time consent management for GDPR and CCPA, first-party profiles without third-party cookies, SCC-aligned data processing agreements, and documented readiness to erase, transfer or modify personal data are in place. I found no public information on a stored consent record with its source, per-channel consent states, a per-contact tracking switch, stated retention, or a per-contact history of what was tracked, scored and decided. 4 9 10
The Solution Architect
Behavioural and engagement tracking is described as automatic and real-time from set-up onward, with consent addressed through real-time consent management, opt-out offered from first touch, data processing agreements covering consent and data sharing, and a stated readiness to erase, transfer or modify a user's personal data. We found no public information on double opt-in as a default, a stored consent record with its source, per-contact suppression of tracking or profiling, or retention rules for inactive profiles. First-party profiles without third-party cookies are documented, which is the right direction, but the per-contact evidence trail a supervisory authority would ask for is not. 4 6 10
The Skeptic
Behavioural tracking begins automatically once the platform is set up and profiles are created for anonymous visitors, so profiling runs from the first pageview rather than after a consented state. Consent management is described as real-time under GDPR and CCPA, erasure and transfer actions are supported, and first-party profiles replace third-party cookies. But we found no public information on double opt-in as the documented default, a stored consent record with its source, per-channel consent states, switching tracking off for a single contact, or retention for inactive records. 4 6 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 — 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.
The Demand Gen Lead
Eighteen named CRM connectors plus a flexible API, webhooks, warehouse destinations and claimed identity resolution across anonymous and known profiles is genuine breadth. A connector catalogue is not a data model, though: I found no public information on sync direction, field mapping, deduplication or conflict rules, sync error handling, or API rate limits — the things that decide whose record wins when the CRM and the platform disagree. 6 8 11 12
The Sales Ops Manager
The join surface is genuinely broad — eighteen named CRM connectors, webhooks, an open API, warehouse destinations like BigQuery and Snowflake, and claimed identity resolution feeding a profile that pulls from CDP, CRM and offline systems in milliseconds. But everything I need before signing — sync direction, field mapping, configurable conflict rules, deduplication behaviour, and a sync error log somebody can act on before the pipeline report is wrong — we found no public information on any of it; the integration pages describe the CRM vendors, not the sync mechanics. 4 6 11 12
The Data Protection Officer
Eighteen CRM connectors are listed by name, a flexible API and webhooks are evidenced, identity resolution is claimed as standard CDP capability, and a "Living Profile" is described as updating in milliseconds from CRM and offline systems. But the pages show connector names, not mechanics: we found no public information on sync direction, field mapping, deduplication rules, conflict handling, error logs or retry — the material that tells a buyer what happens when the two systems disagree about who a person is. 4 11 12
The Lifecycle Marketer
Eighteen named CRM connectors including Salesforce, Dynamics and HubSpot, a flexible API for custom connections, warehouse destinations, and CDP-level identity resolution across anonymous and known states give the join real substance. The mechanics that decide implementations are undocumented: I found no public information on sync directionality, field mapping, conflict resolution, deduplication rules or error handling for the CRM link. 6 8 11 12
The Solution Architect
The integrations directory names eighteen CRMs alongside warehouses like BigQuery, Snowflake and S3, a flexible API and webhooks, and identity resolution is named as a standard CDP capability with profiles for anonymous visitors — the anonymous-to-known path exists in name. But the captured pages describe the third-party products generically and say nothing about the join itself: we found no public information on sync direction, field mapping, conflict resolution, sync error logs, custom objects, or documented API rate limits. Without field-level ownership and replayable syncs, I would not plan an implementation on this. 4 6 11 12
The Skeptic
Eighteen CRM connectors, an open API and identity resolution across anonymous and known states are all documented. But the integration pages catalogue what each connected product is rather than how the sync behaves: we found no public information on sync direction, field mapping, deduplication and conflict rules, a sync error log, or API rate limits. The join that decides the implementation rests on a demo conversation, not on public documentation. 6 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.
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.
The Demand Gen Lead
The compliance page states all collected data is stored at an AWS centre in Dublin, Ireland, available to any customer who wants EU storage — but AWS is a US provider, the DPA leans on standard contractual clauses for third-country transfers, and I found no public information on the contracting entity's jurisdiction, ownership, or any subprocessor list. For a platform profiling named EU residents, that leaves a transfer-risk question open at contract time. 2 9 10
The Sales Ops Manager
The vendor's own page claims all collected data is stored in AWS Dublin and offers that placement to any customer who wants it, but the independently sourced checks came back unknown on residency confirmation, the contracting entity, ownership, and a single named subprocessor. The DPA leans on Standard Contractual Clauses for third-country transfers, and the vendor's own compliance article argues residency is a lever rather than a guarantee — for behavioural profiles of named EU residents, that is the part I need proven, not promised. 2 9 10
The Data Protection Officer
The GDPR page states all collected data is stored with AWS in Dublin, Ireland, a centre offered to every customer wanting GDPR-scope storage, while the independently sourced sovereignty attributes record data residency and the contracting entity's jurisdiction as unconfirmed — the captured material gives different pictures for where data resides. The data processing agreements cite the Commission's Standard Contractual Clauses for transfers to third countries, and we found no public information naming subprocessors or the contracting entity. For behavioural profiles of named EU residents I weigh that gap heavily. 2 10
The Lifecycle Marketer
Storage is documented as EU-hosted on AWS in Dublin, with that centre available to any customer who wants data kept within GDPR's territorial scope. I found no public information on the contracting entity's jurisdiction, ownership or the full subprocessor list, and the SCC-aligned data processing agreements themselves indicate transfers outside the EU occur. 2 10
The Solution Architect
The captured GDPR pages state that all collected data is stored on AWS in Dublin, Ireland, available to any customer wanting GDPR-scope storage, backed by SCC-aligned data processing agreements and an in-house European law consultant. We found no public information on the contracting entity's jurisdiction, the company's ownership, or a published subprocessor list, so who else can see profiles of named EU residents cannot be assessed. For behavioural profiling of EU residents, storage residency alone does not carry the accountability chain, and it weighs heavily here. 2 10
The Skeptic
A vendor compliance post states all collected data is stored in an AWS centre in Dublin and a DPA aligned to the Standard Contractual Clauses is offered, yet the independently sourced sovereignty review marks data residency, contracting entity and subprocessor exposure as unconfirmed, ownership and jurisdiction are unknown, and we found no public information on a published subprocessor list. For a platform building behavioural profiles of named EU residents, the captured pages give a residency claim and little else to contract on. 2 10
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, 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.
The Demand Gen Lead
I found no public prices on any captured page — every path ends in dropping an email for a personalised demo, with nothing on contact tiers, send limits, or the tier where automation begins. The one pricing-relevant statement is a claim of no integration fees with a five-day go-live, which is why this is not a complete blank. 2 11
The Sales Ops Manager
I found no public prices at all — no tiers, contact bands, send limits or billing period — and every path ends in an email-for-a-personalised-demo form. The only cost signal anywhere is a claim of no integration fees with a five-day go-live, so I cannot compute even a rough annual invoice for my contact base from public pages. 2 11
The Data Protection Officer
We found no public prices anywhere — no contact tiers, send limits, billing periods or overage terms — and access to the product runs through an email-gated demo; the only cost statement on any captured page is that go-live takes five days with "no integration fees, no friction". A buyer cannot compute any part of an annual invoice from the public pages alone. 2 11
The Lifecycle Marketer
No public prices, tiers, contact-volume limits or send limits appear on the captured pages — every path to evaluation routes through a demo request. The only pricing-adjacent statements are "no integration fees, no friction" alongside a five-day go-live, which is not enough to compute anything. 2 11
The Solution Architect
The captured pages show no public prices: no tiers, no contact or volume limits, no billing period, no overage rates, and the integration hub gates access behind an email submission for a personalised demo. The only fee statement is that going live in five days involves no integration fees. A buyer cannot compute even a rough annual invoice from public pages alone. 2 11
The Skeptic
No price appears anywhere in the captured pages — no contact tiers, no send limits, no billing period, no VAT treatment — and the integrations page routes serious interest to a personalised demo behind an email form. The only cost statement on record is a marketing promise of "no integration fees, no friction" with go-live in five days. A buyer cannot compute any part of the annual invoice from public pages. 2 11
European sovereignty — proven facts
0 of 4 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 |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined ⚠ unverified | — | uncited Report an error |
| Subprocessors | Not determined ⚠ unverified | — | uncited Report an error |
Questions about Insider
Is Insider European?
Not determined: the vendor’s pages as captured do not say where Insider is based.
Where does Insider store data?
Not stated on the vendor’s pages as of 20 Oct 2026.
Does Insider have a free plan?
Not stated on the vendor’s pages as of 20 Oct 2026.
What are the best alternatives to Insider?
As of 20 Oct 2026, the panel rates ActiveCampaign (Automation) (3/5), Evalanche (3/5) and HubSpot Marketing Hub (3/5) highest among the other 16 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 Evalanche (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Insider alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 20 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 — Data residency, Subprocessors. 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.
- We could not confirm any pricing information on the vendor’s own pages as captured, so this page shows none rather than a statement we cannot stand behind. Know more? Tell us
- 24 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
- 4 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
- 4 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
- 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
- 2 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. 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 useinsider.com Checked 20 Oct 2026 Details →
- 2 Security / trust page — found from the homepage insiderone.com Checked 20 Oct 2026 Details →
- 3 Journeys & orchestration — found from sitemap insiderone.com Checked 20 Oct 2026 Details →
- 4 Journeys & orchestration — found from sitemap insiderone.com Checked 20 Oct 2026 Details →
- 5 Lead scoring, routing & lifecycle — found from sitemap insiderone.com Checked 20 Oct 2026 Details →
- 6 Lead scoring, routing & lifecycle — found from sitemap insiderone.com Checked 20 Oct 2026 Details →
- 7 Channels & personalisation — found from sitemap insiderone.com Checked 20 Oct 2026 Details →
- 8 Channels & personalisation — found from sitemap insiderone.com Checked 20 Oct 2026 Details →
- 9 Consent, tracking & profiling — found from sitemap insiderone.com Checked 20 Oct 2026 Details →
- 10 Consent, tracking & profiling — found from sitemap insiderone.com Checked 20 Oct 2026 Details →
- 11 CRM integration & data model — found from sitemap insiderone.com Checked 20 Oct 2026 Details →
- 12 CRM integration & data model — found from sitemap insiderone.com Checked 20 Oct 2026 Details →